IBM Sametime 9.0 – To Install Fixes turn off Autostart


I just ran into a problem installing Sametime fixes I had not seen happening for a while – and therefore forgot all about it.

Allot of Sametime fixes require an update via the IBM Installation manager. This means that allot of what is actually going on in the background is virtually invisible to you – unless you also tail the Dmgr, NodeAgent and server components’ WebSphere logs.

I had a case where I was installing The Poodle Update for Sametime 9 and it was consistently failing with errors (from the InstallationManager log) such as

CRIMA1217E: A problem occurred during the execution of the E:\IBM\WebSphere\STSCServerCell\build_console.xml file.

Explanation: A package has an issue that cannot be resolved by Installation Manager.

exec returned: -1 [E:\IBM\WebSphere\STSCServerCell\build_console.xml:1629]

I had to put my thinking cap on and after a while of me pulling out some of my hair (no worries, it grows back quickly) I remembered:

The update process has allot of phases where it starts and stops the Dmgr/NodeAgent/Component server several times during the installation process. The Dmgr and NodeAgent are never a problem, however if you tend to set the auto-start of the component servers (Media server, STPRoxy, SSC Server, etc.) via the WAS Server settings – Java and Process Management – Monitoring Settings … then the Component servers always restart when the NodeAgent is started. The installer expects them to no be running and some of the commands in the scripts try to start them and get errors back they have no error handlers for – so the whole install fails.

So – just turn it off, save the setting and sync the Nodes -no need to restart the servers prior to installing the fix. Then you just have to remember to set the auto-start again after you are done so the servers start automatically . . . .

AND: Check after the POODLE fixes are installed, always check the servers virtual hosts settings, I almost always have one that was reset, this time it was the STAdvanced server that was reset to default_host and nothing was working correctly.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s