sysocmgr.exe Custom Actions on W2k3 server

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 [:@]


0 Comments   [ + ] Show comments

Answers (8)

Posted by: abking99 13 years ago
Second Degree Blue Belt
Can you show what command line are you using? and how are you putting in your package?
Posted by: MSIPackager 13 years ago
3rd Degree Black Belt
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!)

Posted by: anonymous_9363 13 years ago
Red Belt
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
Posted by: MSIPackager 13 years ago
3rd Degree Black Belt
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...
Posted by: anonymous_9363 13 years ago
Red Belt
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...
Posted by: MSIPackager 13 years ago
3rd Degree Black Belt
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!
Posted by: AngelD 13 years ago
Red Belt
Did a quick test on XP and the following log files that were touched which may be of interest that I could find was:

The others are:

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

mess_queue.txt content:
msmq_Core = ON
msmq_LocalStorage = ON
;msmq_ADIntegrated = ON
msmq_TriggersService = ON
;msmq_HTTPSupport = ON
;msmq_RoutingSupport = OFF
;msmq_MQDSService = OFF
Posted by: MSIPackager 13 years ago
3rd Degree Black Belt
Thanks - I'll take a look at the logs [:)]

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

I'll get me coat...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ