Just for my reminder for the next time here are two things I learned today during a Sametime 8.5.2 installation. I did a test installation following the instructions in Frank’s presentation.

However the installation of the Meeting Server failed with the following error:

ADMA0158I: [EJBDeploy] Error executing deployment: java.lang.RuntimeException. Error is Application “com.ibm.etools.ejbdeploy.batch_extension” could not be found in the registry.

To solve this error I  deleted the contents of the following directory EXCEPT for the ‘config.ini’ file (there is a technote describing a similar issue while upgrading to Sametime 8.5.2 IFR1):

$WASHOME/deploytool/itp/configuration

I also had also to delete the reference to the Meeting Server in the Websphere profile registry. Just delete the line referencing your meeting server installation (something like “<profile isAReservationTicket=”false” isDefault=”false” name=”meetingSTMPNProfile1″ path=”C:\IBM\WebSphere\AppServer\profiles\meetingSTMPNProfile1″ template=”C:\IBM\WebSphere\AppServer\profileTemplates\default”/>) in the file

$WASHOME/properties/profileRegistry.xml

After I did that, I restarted the installation of the meeting Server and everything went fine then.

Later I had also a problem while installing the Media Manager. As soon as I started the installation manager on the machine it failed without an error message (no splash screen apeared at all). You just saw a java dump appearing but with no real information about the crash reason.

I think that the issue might have been related to my specific environment. I installed the servers in a Virtualbox environment and I solved the issue by decreasing the RAM for the machine temporarily to 3048 MB and adding a second virtual processor. I have no idea why this might have been an effect but afterwards the installation manager could be started without problems again and the Media Manager installation went fine.

Tagged with:  

Leave a Reply

© 2000-2015 Michael Urspringer