Hi,

We have a deployable MSI of the main autocad 2010 package (created with the admin setup method) - along with the lang pack and vc++ 2008 redist etc - which seems to work fine.
However the client requires that we have some of the object enablers(OE)/addons packaged as well.
When we try to run the install for the OE's or the Subscription Pack the setup says that we don't have any valid 2010 products installed, when clearly we do.
So it would seem that the OE's are checking for a registry key or something that says Autocad 2010 is installed, which is perhaps missing from our install
I have extracted the MSI from the OE's but they do not have any appsearch or reglocator's.
Does anyone have any ideas?

Cheers
0 Comments   [ + ] Show 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.

Answers

0
So are you saying that even when you've extracted the msi's they still don't install?

There may be a custom action in there thats doing the checking . But the main AutoCAD msi's and patches do use appsearch and launch conditions.
Answered 03/31/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
As ever, procMon will show you what file or registry entry the set-up is interrogating. Used sensibly with your installer's debugger, you could easily determine whether a CA is responsible.
Answered 03/31/2010 by: VBScab
Red Belt

Please log in to comment
0
Sorry, probably wasn't making myself clear
the autocad package works fine
but the OE's fail to install from both MSI and EXE as they can't see that an Qualifying Product is installed
hence there must be a registry key/pointer missing in the main package.
so i am hoping someone knows what the reg key/pointer is...
I've found a Property that gets used called ACAD_NO_QUALIFYING_PROCUCT_OK - however it's only referenced in 2 locations as part of an IF statement, and I can't find where it actually gets it's value from.
Answered 03/31/2010 by: ditch_nz
Purple Belt

Please log in to comment
0
No, you were clear, but perhaps I wasn't :)

If you run one of the OEs through your authoring tool's debugger, step-by-step while running ProcMon alongside, as soon as you see the message to the effect that no qualifying product is installed, ProcMon will be showing you a NAME NOT FOUND error in its Registry view and the debugger will be halted on the action which is interrogating that registry entry. The only hitch is that ProcMon will only highlight the first missing key: you'll have to go through the pain of creating that, then the next one, then the next, and so on. Sure, someone here might know what the entry is but how long have you waited already? By the time someone comes along, you could be packaging the next release! :)
Answered 04/01/2010 by: VBScab
Red Belt

Please log in to comment
0
thanks VBScab. I've resisted doing that, brings back the days of yesteryear of using regmon and filemon to do the same thing....
just thought someone might have a quick fix...
Answered 04/05/2010 by: ditch_nz
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity