SocialConnections 9 in Stuttgard Nov 5-6, I am speaking again!

I just noticed that I forgot to announce to the world that I will be at SocialConnections 9 in Stuttgart next. The dates to save are November 5 – 6 and the location for the Shindig is STUTTGART in good old Germany.

The agenda is already finalized , take a look right here:

You will actually find me in there twice because this time I am not just presenting my own, riveting content but also co-presenting with a good friend of mine, Christoph Stoettner. Him being Bavarian and I being half Austrian we are able to totally confuse the crowd with insider talk and strange dialects that most Germans north of the Weißwürschtl Grenze (see below) have allot of trouble understanding – but don’t worry, the actual presentation will be in English.

For all of those among you who want to know more about the everlasting love-hate-indifference relationship between the north and south of German speaking people, look this up: Weißwurstäquator. And additionally, just for the insiders – we count our Swiss friends and brethren as human and normal, even though nobody else really understands Schwyzerdütsch. But the Swiss are just cool and know it, so we accept them as is.

As you can see, next to the unbelievably captivating content and massive amount of slides that Christoph and I will be presenting, we are fully prepared for any linguistic duel that might be waiting.

I do hope to see allot of you at the conference, judging fro the agenda it promises to be quite the exciting – sign up and let me know if you are planning to come!

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.

IBM Sametime 9.x – Linux Install Errors – Installation Manager Failed Validation

I am blogging this one becuase when it happened to me I did not find a solution for it anywhere.


Problem Scenario

Installing ST9 Video Manager on Red Hat 6.4 – using either built-in IBM Installation Manager that comes with the installation package or a preexisting Installation Manager (used to install WebSphere first). When starting the install you get as far as choosing the package to install and then you get an error – “Validation Failed” in the Installation Manager interface. In the console used to execute the Installation Manager you see the error:

IBM installation manager error “Failed to determine a hostname for WAS to use”

I looked far and wide for this one in Google and bing to no avail – until I had a hunch: the host configuration for the server was incorrect.



In the ssh session execute the command [system-config-network] to verify the fully qualified host name entered there. In my case there was a typo in the name so the Installation Manager was never able to look up the Red Hat server it was running on successfully. Edit/fix the entry and then save it. A restart is not necessary, though this change did kill the X11 forwarding I had going so I simply ended the ssh session and reconnected again and then the install went flawless.

ICONUK – Here I Come!

Just booked my flights for ICONUK – it is my first time flying Virgin Atlantic so I am curious how that will be! Everybody tells me they are fantastic …

Will you be attending ICONUK? I am looking forward to talk all things Connections and Sametime ….








See you there!

ICON UK – Agenda Released

I just received this in the mail – as I will be speaking I hope some of y readers might attend. Even if it is only to get some free coffee and scottish shortcake ….

Meet us in London for ICON UK!

Won’t you join us?

ICON UK is a two-day event for all users of IBM software to meet, learn, and network. Members of the IBM team, 18 IBM Champions, and other fantastic and knowledgeable members of the IBM software community will give top-notch presentations and will be available to answer questions. At the end of day two, there will be a never-been-done-before “Ask IBM and the IBM Champions” session. View the full agenda here.

We hope you’ll be able to join us again this year! See date and time details below.

The ICON UK Team
Monday, Sept. 21, 2015
Tuesday, Sept. 22, 2015

Monday from 08:00 – 19:00
Tuesday from 08:00 – 18:00

IBM Client Centre, IBM Southbank, Upper Ground, London


Click Here to Register

ICONUK Sep. 21&22, London – I’ll be speaking again

Just got this in the email:

Good News! Your session IBM Connections – Installing the Free “Extras” and  Integrating with other Products has been approved for ICON UK 2015
Tim and I are finalizing the schedule and it should be online tomorrow.

Thanks again for your submission and we are looking forward to seeing you  in September

Will I see you guys there?

Monday 21st & Tuesday 22nd September 2015

Mon 08:00 – 19:00 (Gala dinner 20:00 – 23:00)
Tue 08:00 – 18:00

IBM Client Centre, IBM Southbank, Upper Ground, London

IBM Sametime 9 – Advanced Server Log-in Not Working

Solved an interesting problem this morning. In a new environment (rebuild/replacement of a V 7 awareness only system) that I built for clients our users were not able to log in to the ST Advanced Servers broadcast communities and chat rooms from their integrated Sametime client in Notes even though they were able to log-in through a browser and had full functionality. At the same time off-line messaging was not working either – but everything else was working just fine.

No matter of trace was giving me the reasons … until I had an epiphany during a thunderstorm this morning – the fact that one of our dogs is deathly afraid of thunder and will try to get INSIDE of you if in any way possible, actually prompted some thoughts that helped me find the issues in one go.

I was pretty sure that something was keeping policies from being applied correctly, there had to be something with the way users were being identified. during the upgrade I had not  paid enough attention to some of the changes I was testing – I forgot to add the [objectGUID] (using AD as the LDAP directory) to the search filters. Awareness will still work and Meetings as well … however the rest is going to be strange. I had also had some problems looking up users when adding them to the buddy list – that is when I had the epiphany that it was all related.

Here the changes to the Search Filters:

Search filter for resolving person names:

Original: (&(objectclass=user)(|(mail=%s*)(samAccountName=%s*)(cn=%s*)))
New:       (&(objectclass=user)(|(mail=%s*)(objectguid=%s)(samAccountName=%s*)(cn=%s*)))

Search filter to use when resolving a user name to a distinguished name:

Original: (&(objectclass=user)(|(mail=%s)(cn=%s)(samAccountName=%s)))
New:       (&(objectclass=user)(|(mail=%s)(objectguid=%s)(cn=%s)(samAccountName=%s)))

Search filter for resolving group names:

Original: (objectclass=group)
New:       (&(objectclass=group)(|(objectguid=%s)(cn=%s*)))



Well, proves once again that it is all about BASICS, BASICS, BASICS ….