In preparation for an upgrade of a customer’s Sametime 8.5.1 infrastructure to 8.5.2 IFR1 I built a scaled down (“cell profile”) version on three servers to test the process and to give them the latest flavour for them to test before touching production.
The install of 8.5.1 went smoothly, the only sticking point when upgrading to 8.5.2 was with the Meeting server. The upgrade stalled with an error of “exec returned 105.”
Checking the logs in /var/ibm/InstallationManager/logs/ant/ I saw the following at the very end.
[exec] WASX7209I: Connected to process “dmgr” on node DMgrNode using SOAP connector; The type of process is: DeploymentManager
[exec] WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[/opt/IBM/WebSphere/STMServerCell/SametimeMeetingServerOffering/SametimeServer/STMeeting/meeting/meeting.properties]”
[exec] Starting meeting setup
[exec] Reading Properties
[exec] inside loadproperties
[exec] “Built-in Mail Provider(cells/HEVL31STMCell1/nodes/HEVL31STMNode1/servers/STMeetingServer|resources.xml#builtin_mailprovider)”
[exec] WASX7017E: Exception received while running file “/opt/IBM/WebSphere/STMServerCell//meeting_mailSession.py”; exception information: com.ibm.websphere.management.exception.ConfigServiceException: ADMG0037E: A new instance of the MailSession object cannot be created because the jndiName attribute of an existing MailSession object has the same value as mail/CalendarIntegrationMailSession.
/opt/IBM/WebSphere/STMServerCell/build_meeting.xml:1898: exec returned: 105
Total time: 4 minutes 3 seconds
I logged into the deployment manager for the Meeting server and and went to Resources – Mail – Mail Sessions and deleted CalendarIntegrationMailSession.
The upgrade worked successfully when run again.
PS – if you need to recreate the object then check out Setting up calendar integration with the Sametime Meeting Server.