Hello all,

I've done a package for the XP desktop which contains a sysocmgr custom action to install the Message Queuing component/s - works fine, all tested and signed off.

Been asked to do the same package up for Citrix so have done up an appropriate transform. The custom action is running fine (no errors in the log) but the component/s are not being installed... Running the exact same command line from a cmd prompt installs the component/s as expected.

Can't remember doing a sysocmgr CA on W2k3 server package before - wondered if there are any knows issues... Anyone experienced this?

Unfortunately there is no specific logging functionality for sysocmgr.exe [:@]

Thanks,
Rob.
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
Can you show what command line are you using? and how are you putting in your package?
Answered 09/29/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
0
It's a standard sysocmgr.exe command line, called as deferred CA (system context) just before InstallFinalise:

sysocmgr.exe /i:c:\windows\inf\sysoc.inf /u:"C:\Path To\Files\mess_queue.txt" /r /q

CA type is 3170 - Synchronous (Ignore Exit Code)

I tried setting the CA not to Ignore Exit Code and the CA still completes OK (as far as msiexec is concerened!)

Cheers,
Rob.
Answered 09/29/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
How about the VBScab "What the hell went wrong?" technique?

That is:
- install your package
- kick off a lightweight snapshot tool and take a 'Before' s/s
- install from the command line
- take an 'After' s/s
Answered 09/29/2009 by: VBScab
Red Belt

Please log in to comment
0
I can't see how that would help... Won't that just show up the component installation changes?

None of the components are being installed on the W2k3 box... it's not like just 1 or 2 are missing...
Answered 09/29/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Sorry, Rob, I mis-read your post. I took it to mean that they weren't appearing in the component view. You're saying that they're plain not installed.

I'll get me coat...
Answered 09/29/2009 by: VBScab
Red Belt

Please log in to comment
0
I'll get me coat...

lol class.

No problem mate, always appreciate the suggestions - it's easy to sometimes overlook the most straight forward troubleshooting!
Answered 09/29/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Did a quick test on XP and the following log files that were touched which may be of interest that I could find was:
C:\WINDOWS\comsetup.log
C:\WINDOWS\msmqinst.log
C:\WINDOWS\setupapi.log
C:\WINDOWS\setuperr.log

The others are:
C:\WINDOWS\ocgen.log
C:\WINDOWS\FaxSetup.log
C:\WINDOWS\iis6.log
C:\WINDOWS\ntdtcsetup.log
C:\WINDOWS\tsoc.log
C:\WINDOWS\imsins.log
C:\WINDOWS\msgsocm.log
C:\WINDOWS\tabletoc.log
C:\WINDOWS\MedCtrOC.log
C:\WINDOWS\netfxocm.log
C:\WINDOWS\ocmsn.log


Used the command:
sysocmgr.exe /i:C:\WINDOWS\inf\sysoc.inf /u:"C:\Storage\mess_queue.txt" /r /q

mess_queue.txt content:
[Components]
msmq_Core = ON
msmq_LocalStorage = ON
;msmq_ADIntegrated = ON
msmq_TriggersService = ON
;msmq_HTTPSupport = ON
;msmq_RoutingSupport = OFF
;msmq_MQDSService = OFF
Answered 09/29/2009 by: AngelD
Red Belt

Please log in to comment
0
Thanks - I'll take a look at the logs [:)]

Looks like I should have tried Ian's suggestion afterall!

I'll get me coat...
Answered 09/30/2009 by: MSIPackager
Third Degree Black Belt

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