AS Java applications not starting after patching from 2004s SPS10 to SPS11

Question

Hi folks,
after patching our NetWeaver 2004s from SPS10 to SPS11 and the Kernel from 7.00.83.0 to 7.00.95.0, the applications on the AS Java do not start up automatically any more.
Under the following URLs, the same error is shown:
http://<fully qualified host name>:51000/
http://<fully qualified host name>:51000/nwa
http://<fully qualified host name>:51000/sap/monitoring/SystemInfo
http://<fully qualified host name>:51000/useradmin/
http://<fully qualified host name>:51000/wsnavigator
http://<fully qualified host name>:51000/uddiclient
503   Service Unavailable
SAP J2EE Engine/7.00
Application stopped.
Details: You have requested an application that is currently stopped
http://<fully qualified host name>:51000/webdynpro/welcome/Welcome.jsp
itself works, the two links Content Administrator and Web Dynpro Console both lead to the same 503 error described above
On http://<fully qualified host name>:51000/irj, the error message is different:
com.sap.engine.services.deploy.container.ApplicationInManualStartUpException:
Application sap.com/com.sap.portal.fpn.accessservice cannot be started because is in MANUAL start-up mode..
Exception id: 09:33_09/05/07_0003_102709250
See the details for the exception ID in the log file
In std_server0.out we have the following entries, right after the list of all services that were started:
ServiceManager started for 39904 ms.
Framework started for 46720 ms.
SAP J2EE Engine Version 7.00   PatchLevel is running!
PatchLevel January 31, 2007 18:37 GMT
May 9, 2007 9:40:19 AM  com.sap.portal.prt.sapj2ee.error [SAPEngine_Application_Thread[impl:3]_3] Fatal:
The last line with com.sap.portal.prt.sapj2ee.error is listed another 131 times, and there is also the following message:
### Excluding compile:  com.sapportals.portal.prt.jndisupport.util.AbstractHierarchicalContext::lookup
We can connect to the system using Visual Administrator. Under Server->Services->Deploy, most applications are not running. It is possible to start a few applications manually, others however do not start showing different exceptions.
We have AS ABAP and AS Java installed, as well as BI, DI, EP and EPC. AS ABAP seems to be running fine.
We have also noticed the following deviations in JSPM:
BC_FES_IGS is Release 7.00 SP Level 7.0
EP_BUILDT is Release 7.00 SP Level 10.0
SAP_BUILDT is Release 7.00 SP Level 0.0
All other components except for the Kernel are Release 7.00 SP Level 11.0 or 11.2
What could be wrong, and what can we do to solve it?
Best regards,
Robert Schulte

Answer 1

Thanks for your response, usha rani
1. We already tried that, unfortunately, it does not help
2. We checked the kernel version thoroughly after you suggested it, everything seems to be fine. We had a Unicode kernel before, and we still have one.
3. safemode is already set to NO
4. J2EE's default.trace is full of exceptions, but none of them is pointing me into a helpful direction.
Perhaps the exceptions mean more to someone else:
java.lang.Exception: Exception loading and instanciating sub-manager:
com.sap.caf.km.repositorymanager.CAFSecurityManager
(java.lang.ClassNotFoundException: com.sap.caf.km.repositorymanager.CAFSecurityManager)
com.sapportals.wcm.repository.runtime.CmConfigurationProvider#
sap.com/irj#com.sapportals.wcm.repository.runtime.CmConfigurationProvider.Component
<SetRoomIdForDiscussionObjects> will not be available.
Failed to load class
<com.sap.netweaver.coll.room.impl.filter.DiscussionSetRoomIdPropertyFilterManager>
#J2EE_GUEST#0####1e820b50fe4111db8e780013724175b4#SAPEngine_Application_Thread[impl:3]_22
##0#0#Error##Plain###
java.lang.ClassNotFoundException:
com.sap.netweaver.coll.room.impl.filter.DiscussionSetRoomIdPropertyFilterManager
com.sap.portal.prt.runtime.broker#sap.com/irj#
com.sap.portal.prt.runtime.broker#J2EE_GUEST#0####
1e820b50fe4111db8e780013724175b4#SAPEngine_Application_Thread[impl:3]_22##0#0#
Error#1#/System/Server#Java###
[PortalServiceItem.startServices] service initialisation failed:
tc.eu.odi.conn.uwl|OdiBridgeService
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException:
Could not instantiate implementation class com.sap.tc.eu.odi.conn.uwl.OdiBridgeService
of Portal Service tc.eu.odi.conn.uwl|OdiBridgeService because: could not load the service
com.sap.engine.services.deploy.container.ApplicationInManualStartUpException:
Application sap.com/com.sap.portal.fpn.accessservice cannot be started
because is in MANUAL start-up mode.
There are many more entries in default.trace.