Hi All,

I am upgrading an application delloite V1.0 which is already deployed to thousands of computer. Application has pre-req of msxml 4.0 which was part of build when application went live. Now i am dealing with the application which will be upgrade to v1.0 and msxml 4.0 is no more part of new build. We have msxml6.0 as part of build. This application hardcodedly needs msxml4.0.I included msxml4.0 merge module in my package and tried to upgrade the older version. in restricted user application throws error "error 1904 C:\Program Files\Common Files\Deloitte\TMC\AbacusShellExtensions.dll failed to register" can any one please suggest .....
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
If the upgrade works as an administrator, with no problems, then its a permissions issue.

P
Answered 01/20/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
If i launch the shortcut once again in the user it doesn not go for repait and it launch perfectly fine. and application is launching fine in administrator.
Answered 01/20/2009 by: packengg
Orange Belt

Please log in to comment
0
permissions are already given to HKLM\SOFTWARE\Deloitte\Abacus Technology and installdir
Answered 01/20/2009 by: packengg
Orange Belt

Please log in to comment
0
permissions are already given to HKLM\SOFTWARE\Deloitte\Abacus Technology and installdir...except that that isn't the location where registration information is written. That'll be somewhere in HKLM\Software\Classes\CLSID (ghosted as HKCR\CLSID).

Your package is attempting to register a DLL in User context instead of System. Almost guaranteed to fail...

I'd bet my last pound that it's doing that either via the SelfReg table or by a Custom Action calling RegSrv32. If it's a vendor MSI, you can either live with that nonsense (but you'll still need to switch the context, of course) or proceed as for a captured MSI. If you have captured the install to your own MSI, then do the registration properly, by extracting the COM information into a .REG, importing that .REG and having your authoring tool (which is...?) populate the advertising tables.
Answered 01/20/2009 by: VBScab
Red Belt

Please log in to comment
0
I agree with VBScab, and my test would have proved that ;)

When I talk about permissions I dont just mean under 1 hive I mean under them all, which includes the HKCU key which is why I asked if your package worked as an adminsitrator.

P
Answered 01/20/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
my test would of proved that ...would have proved that.

No offence, Paul but this is a common error, owing to the 'of' sound which is used when the conjugation is spoken in short form, as in "my test would've proved that".

Is there no end to my pedancy? LOL
Answered 01/20/2009 by: VBScab
Red Belt

Please log in to comment
0
There we go just to be different, have a "have" NURF!

Oh and trust me ill be checking out each of your posts for "errors" going forward ; )

P
Answered 01/20/2009 by: Inabus
Second Degree Green Belt

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