/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hello guys,
I'm trying to publish MS Office 2003 SP3 in HP CSDB. It seems there is a mismatch between " Template Summary Property" in MSP file and "ProductCode" in MSI file. I used "MsiInfo.exe [path to database] -p [edited_value]" but it generated Error 110. Unable to open database.

It seems database is read-only. How can I make it writable?

I'll appreciate any help.
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
That rather depends on why it's read-only, doesn't it? Or , indeed, if it really is read-only.

Does the file have its read-only attribute set? Does the user account you're using have sufficient rights to the file and/or its container folder? Check file *AND* share permissions: it wouldn't be the first time I've seen Windows gets its drawers in a twist with conflicting and/or mutually exclusive permissions.
Answered 10/22/2008 by: VBScab
Red Belt

Please log in to comment
0
No, the attribute is not read-only and I have sufficient rights to this file.

I should maybe merge/convert the MSP file to an MSI to make it open and edit?
Answered 10/22/2008 by: mehappy
Orange Belt

Please log in to comment
0
I think you mean the package code (Revision summary information property, number 9) and not the ProductCode in the MSI.
Answered 10/22/2008 by: AngelD
Red Belt

Please log in to comment
0
Hi Kim,

No I mean ProducKey. As you know every msp file has a "Template Summary Property". The Template Summary property of a patch package (.msp file) is a semicolon-delimited list of the product codes that can accept the patch. If there is a mismatch it will generate an error. So I tried to opent the patch (.msp file) by using MsiInfo.exe to see what are values in Template Summary. But it seems is not that easy! :-/
Answered 10/22/2008 by: mehappy
Orange Belt

Please log in to comment