I just completed the upgrade to service pack 7 but cannot get the application to launch. Anyone out there that has been through this that can offer some insight please?
thanks, Marcia
Can you be more specific as to what happens when you try to launch the application? Are there any messages, etc?
Hi,
Thanks for answering - applying the service pack over New Year's eve is not a good idea for GE support but the best time for our clinics and physicians.
Yes, what happened was the service pack installed without issues. I could not launch the application because when I added the text to the jobs.txt file the upgrade of the client crashed each time I would launch it with the following error:
Unhandled exception caught in ExceptionAttacher.cpp - AfxWinMain.
Error occurred at 1/1/2015 03:12:14.
I uninstalled the client and removed the last entry to the jobs.txt file that I had added from the instructions for the service pack and then reinstalled successfully. I am not sure why this happened but I was able to update the 45 Xenapp server clients without problems
I also noticed that the JBOSS did not update smoothly. Initially, I uninstalled the JBOSS application and then did the update per the instructions for updating JBOSS on a separate server. On the first run through, the server rebooted after the JBOSS install (I did not select "NO" to reboot - big mistake), I installed the Service Layer. I believe this caused the JBOSS to fail to begin with however, when I uninstalled and reinstalled JBOSS and the Service Layer it continued to fail. Luckily, after installing Service pack 7, I backed up the Service Layer folder before going forward with the JBOSS installation. Having failed at getting JBOSS to worked several times, I deleted the Service Layer folder and copied over the one I had saved to the CentricityStaging directory and was successful with JBOSS finally.
I find the instructions for these service packs woefully inadequate but I managed to get through it.
thanks,
Marcia
Having to have JBOSS now for the application now as a requirement is horrible, and can't believe they have designed the architecture this way. Its the worst of both worlds, having to support a fully thick client and a application service layer with GUI components in it. its laughable really.
But the real reason for my comment is, to make sure you have a tool, like baretail (on windows) to tail the logs of the JBOSS server logs so you can accurately determine when the JBOSS server is started and stopped.
I have dealt with numerous people who just stop the service, and IF the service stops normally assume JBOSS is completely stopped, which is hardly ever accurate.
We applied to SP7 onto two systems this past weekend. One from SP3 and another from SP6. No particular issues occurred during the upgrade.