EP7 upgrade from SP11 to SP12

Hi experts,
We are using read-write connection to LDAP from SAP Portal EP7 NW04s.
All user groups are maintained in LDAP and in portal we have assigned relevant roles to these groups.
After weve upgraded EP7 from SP11 to SP12, we cant see the roles that are assigned to the groups.
It is reasonable to assume, that roles are still related to groups and we just cant see it, because users get the relevant roles when they enter the portal.
Had anybody upgraded SP11 to SP12 and experienced the same problem?
Thanks in advance,
Inna

Hello, I am having the same problem. But nobody answered...
Look at this thread : Worksets problems after upgrade to SP12
Did you find a solution??
Thanks in advance!

Similar Messages

Upgrade from SP11 to SP14

Hi All,
I'm currently trying to upgrade from SP11 to SP14. I started with upgrading the J2EE Engine.
Whe doing so the Installation stops at step 17 with the
following error message in log-file callSdmViaSapinst.log:
ERROR: Not deployed. Deploy Service returned ERROR:
 java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
 Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
Has anybody encountered a similar problem and can help me?
Thanks,
Stephan

Hi Vasu,
here is the complete StackTrace as found in callSdmViaSapinst.log. I hope this is what you meant by installation path. BTW, restarting the installation didn't help.
Regards,
Stephan
05/12/12 14:24:31 - ***********************************************************
05/12/12 14:24:36 - Start updating EAR file...
05/12/12 14:24:36 - start-up mode is lazy
05/12/12 14:24:39 - EAR file updated successfully for 2766ms.
05/12/12 14:24:39 - Start deploying ...
05/12/12 14:24:42 - EAR file uploaded to server for 2547ms.
05/12/12 14:24:56 - ERROR: Not deployed. Deploy Service returned ERROR:
 java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
 Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].; nested exception is:
 com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
 at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
 at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
 ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
 at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
 at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:482)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
 Caused by: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
 at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
 at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
 ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
 at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
 at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
 at com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException.writeReplace(WebDeploymentException.java:99)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
 at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:135)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:296)
 ... 8 more
 For detailed information see the log file of the Deploy Service.
05/12/12 14:24:56 - ***********************************************************
Dec 12, 2005 2:24:56 PM Info: End of log messages of the target system.
Dec 12, 2005 2:24:56 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 12, 2005 2:24:56 PM Error: Aborted: development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050606164207.0000':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tc~uddi..
Reason: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].; nested exception is:
 com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
 at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
 at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Application alias [uddi] for application [sap.com/tc~uddi] already exists in the HTTP Provider Service. The application that holds this alias is [sap.com/com.sap.uddi].
 at com.sap.engine.services.servlets_jsp.server.container.DeployAction.deploy(DeployAction.java:144)
 at com.sap.engine.services.servlets_jsp.server.container.WebContainer.deploy(WebContainer.java:104)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:467)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Dec 12, 2005 2:24:57 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 12, 2005 2:24:57 PM Info: --------------- Deployment was successful -----------------
Dec 12, 2005 2:24:57 PM Info: Summarizing the deployment results:
Dec 12, 2005 2:24:57 PM Error: Admitted: D:TempSAP_SP14J2EE-RUNT-CDJ2EE-ENGONLINESAPJTECHS14_0.SCA
Dec 12, 2005 2:24:57 PM Error: Processing error. Return code: 4

Error after SPS upgrade from SP10 to SP12

Hi Friends,
Recently we have done SOLMAN 7.1 sp upgrade from sp10 to sp12.
Now I want to perform configuration activities in SOLMAN_SETUP.
But when I am trying to do SYSTEM PREPARATION, I am facing error in first step(Maintain Users).
"Error: Number of elements in the collection of node COMPONENT CONTROLLER.1.NAMESPACES violates the carnality".
Kindly suggest me how to clear this above error and proceed further. Further please let me know as a SOLUTION MANAGER consultant what are the steps I need to perform post SP upgrade. I am not BASIS guy. So please let me know what are the activities which need to be performed by BASIS guy and SOLMAN guy
Please find the attached screen shot for the error screen.
Thanks & Regards,
Solman Starter

Go the transaction STMS, if a window appears when you start the transaction that's mean it is not configured.
Only in this case :
1. Logon on to client 000 with DDIC.
2. Execute transaction SE06
3. Select the Database Copy or migration option
4. Press the Post-installation Processing button.
5. When prompted Do you want to re-install the CTS? Press the Yes button
6. When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected. Press the checkmark button to continue.
7. When prompted Change originals from PRD to QUA?, press the Yes button
8. When prompted Delete TMS Configuration?, press the Yes button
9. When prompted Delete old TMS configuration?, press the Yes button
10. When prompted Delete Old Versions of transport routes?, press the No button
Concerning the initial problem, i found this note :
http://service.sap.com/sap/support/notes/2025884

Upgrade from SP11 to SP19

Hi,
We are planning to upgrade from SP11 to SP19. EP system is on UNIX.
And we dont have any KMC for Portal.
Can anyone forward me the documents or step-by-stp guides or links for this?
And i need information what are the advantages with SP19 for portal?
I can say thanks with points.
Here i am adding my mail id: [email protected]
Thanks in Advance,
Sanjeev

All the guides for upgrading to a new support package can be found in the SAP MarketPlace at <a href="http://service.sap.com/nw04maintenance">NW04 Maint</a>.
SP19 will have all the latest bug fixes, which is why you should apply it.
Cheers

Error after upgrade from SP9 to SP12

Hi,
I just upgraded our system to NetWeaver SP12 from SP09. Now my all WD applications after deploy no working. I have made WD Hallo world as test and receive the Error
java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/api/IWDEventHandlerId
 at java.lang.Class.getDeclaredConstructors0(Native Method)
 at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
 at java.lang.Class.getConstructors(Class.java:865)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:68)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.<init>(DelegatingInterfaceView.java:44)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:131)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Can anybody suggest the reason?
Thanks in advance!
Regards,
Raissa

It works for WebDynpro without RFC-Model.
Thanks a lot.
For WebDynpro with RFC-Model i receive the Error
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Der Funktionsbaustein "DD_DOMA_GET" ist nicht 'remote' aufrufbar.
 at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:417)
 at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1256)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3721)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3165)
 at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:173)
 at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:164)
 at com.sap.mdi.ddtypes.DDDomain.<init>(DDDomain.java:45)
 at com.sap.mdi.ddtypes.DDDataelement.<init>(DDDataelement.java:59)
 at com.sap.mdi.ddtypes.DDField.<init>(DDField.java:71)
 at com.sap.mdi.ddtypes.DDScalarField.<init>(DDScalarField.java:30)
 at com.sap.mdi.ddtypes.DDStructure.<init>(DDStructure.java:87)
 at com.sap.mdi.ddtypes.DDFlatStructure.<init>(DDFlatStructure.java:23)
 at com.sap.mdi.ddtypes.DDFactory.analyseJCOReturn(DDFactory.java:475)
 at com.sap.mdi.ddtypes.DDFactory.getDDObject(DDFactory.java:434)
 at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:282)
 at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
 at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
 at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:753)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
 at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
 at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:373)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Have You any idee?
Raissa

Exception in rpdata after upgrade from SP11 to SP18

Hi All,
after updating Web AS and ADS from NW04 SP11 to SP18 I get the following error when testing the ADS webservice via http://:/AdobeDocumentServices/Config.
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method rpData.
 at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:148)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NullPointerException
 at java.lang.String.<init>(String.java:390)
 at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source)
 at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source)
 at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source)
 at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:120)
 ... 25 more
java.lang.NullPointerException
 at java.lang.String.<init>(String.java:390)
 at com.adobe.AdobeDocumentServicesWorker.execute(Unknown Source)
 at com.adobe.AdobeDocumentServicesEJB.processRequest(Unknown Source)
 at com.adobe.AdobeDocumentServicesEJB.rpData(Unknown Source)
 at com.adobe.AdobeDocumentServicesLocalLocalObjectImpl0.rpData(AdobeDocumentServicesLocalLocalObjectImpl0.java:120)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
I´ve updated the ADS regarding to this thread: https://forums.sdn.sap.com/click.jspa?searchID=1034429&messageID=1964510 and SAP Note 727168.
But I couldn´t remove and register the "ReaderRights" because I´m getting the error:
Error while loading service Document Services Configuration
com.sap.engine.services.adminadapter.exception.AdminException: com/adobe/service/sap/configuration/ConfigurationException
when choosing the "Document Services Configuration" service in Visual Admin
We don´t want to use interactive forms at the moment (just PrintForms) so we don´t need the ReaderRights, correct?
Does anyone have an idea what´s wrong?
Thanks in advance
Helmut

Are you using Windows platform?
If you are using windows platform you can use Visual Administrator for viewing your logs.
regards,
Sujesh

How to upgrade sneak preview NW 2004s from SP9 to SP12 ?

Hi Experts,
I've downloaded and using SAP Evaluation NW 7.0 (2004s) SP9 - Sneak preview.
Now wanted to upgrade from SP9 to SP12.
Can you please tell the process whether can we do this on sneak preview? If yes, then how to achieve it?
Thanks
Mohan Krishna

Hi Mohan,
Sneak preview is not meant to be patched, nor is it possible to patch it at all.
Regards,
Vinoth.M

Upgrade from XI 3.0 (SP17) to PI 7.0 (SP12): Best Practices

Hi mates,
I've a few questions regarding the upgrade to PI 7.0.
If the upgrade process is done in phased manner i.e. DEV, QA, PRD in that order over a period of 3 weeks,
How do we handle the transports from DEV->QA->PRD when DEV is 7.0 and QA & PRD on 3.0 using CMS?
Will there be inconsistencies when transports are moved, because a few features could be different or internal representation of IR/ID content could be different in 3.0 & 7.0?
What are the upgrade best practices, phased manner or all at a time?
Please throw more light on this. I appreciate the inputs from people who've helped clients upgrade from 3.0 to 7.0. Any SAP documentation related to this?
I looked at the thread Transports from XI 3.0 to PI 7.0 but the answert is very generic, w/o any supporting documentation and real time experience.
thx in adv
praveen

> Hi mates,
>
> I've a few questions regarding the upgrade to PI
> 7.0.
>
> If the upgrade process is done in phased manner i.e.
> DEV, QA, PRD in that order over a period of 3 weeks,
> How do we handle the transports from DEV->QA->PRD
> when DEV is 7.0 and QA & PRD on 3.0 using CMS?
Im my experience you should implement a change freeze for this period, with the exception of emergency transports - and these have to be justified.
> Will there be inconsistencies when transports are
> moved, because a few features could be different or
> internal representation of IR/ID content could be
> different in 3.0 & 7.0?
Full regression testing will be needed on each interface. If you implement a change freeze this process becomes easier
>
> What are the upgrade best practices, phased manner or
> all at a time?
Allow plenty of resources to fully test every interface, as you would with any upgrade.
You could also take the time to implement the new <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bbbd55-5004-2a10-f181-8bb096923cb6">CTS+</a> for this new version to avoid any further transport issues (PI7.0 SP12 +). A new method for a new system!
Also, how is your SLD set up for XI? This can have an impact.

Upgrading from ECC 6.0 Sp11 to SP15

Hi,
We plan to Upgrade from ECC 6.0 Sp11 to SP15.
I like to find the documents for SP 15 to estimate the effort required for upgrading.
It would be great if some one provide me the info where to get this.
Thanks
Senthil

Hi
Support Packages:-
SAP delivers various types of program corrections with Support Packages as part of the software maintenance. Support Packages automatically correct a whole range of errors by downloading corrections into the SAP System. Two categories of Support Packages are available: ABAP Support Packages and Java Support Packages.
Enhancement package:
New functionality will be added to your existing sofware components
Please go thorugh link http://service.sap.com/erp-ehp for more information
Regards
Uday

MSY does not start after upgrade from 50SP6 to SP11

Hello experts again,
after upgrading from 50sp6 to sp11 I cannot start MSY.
I've implemented note 1099457 - AMT is starting now,
but MSY still does not start.
Has anybody some experience what this could be ?
Thanks and best regards
Gerd

Hi,
as I assume the AMT is installed completely new when doing a SP upgrade because it is a standard tool which you cannot enhance. Therefore it is running properly.
Regarding MSY you need to perform a full generation within MAS (Visual Studio) after changing the generation settings to MSY (similar to MSA) because the runtime files like MSY.DLL need to be fitting to the new SP11 framework dlls.
Regards,
Wolfhard

Context Menu disappeared after EP7 upgrade

Hi all,
We've recently upgraded our sandbox and dev portals to EP7. Since then, we've noticed that in KM, the context menus that should be located to the right of the files/folders is missing. Actually, it would be more appropriate to say that they're invisible rather than missing because if I hover my mouse over the area where it should be, the mouse pointer changes. If I click on this area, the menu comes up.
Has anyone seen this problem before? What do I need to do to fix it?
Thanks!
-Stephen Spalding
Web Developer
Graybar

Hi Stephen,
if you upgraded from EP6, please reimport old EP6 theme into EP7.
I and others had corrupted theme after the upgrade from EP6 to EP7.
The major bug is all web dynpros don't load ok.
Give this a try before modifying your theme.
Brad

Upgrading from EP 6.0 to 7.0

Hi ,
We are upgrading from EP6.0 to 7.0 ,We have many webdynpro applications written in 6.0 now if we upgrade to 7.0 do we have to make any changes to the applications , will the applications run on 7.0 with out any modifications??
Regards,
ravi.

Hai,
Some of the Controls added newly in Webdynpro 2004s. some UI elements like IFrame are depricated, but i seen all of my applications developed in 2004 are working in EP7.0 .
This thread discussing the differences between nw04 and nw04s
NW2004 vs. NW2004s
Regards,
Naga

T code SP11 AND SP12

Dear Friends,
can you explain me detail analysis of T code SP11 and SP12.
and how basis administrator analysis it.
thanks,
Regards,
Sachin

Dear Sri,
i want forground page information when i am execute T Code SP11.
The details of that page are as follows,
                                                                                TemSe object name         -
Object - Data type    -
Creator                -
Creation time        -
(from)     -
Expiry Date            -
         (to)        -
Length (Bytes)         -
         (at least)
Program Name     -
I am waiting for your reply.
Thanks,
Regards,
Sachin

Upgrading from EP60 to EP70

We are currently using EP 6.0 SP2 Patch 4 and we want to upgrade to EP 7.0. We have very minor customizations (a few iViews and style sheet changes).
Rather than patching our existing portal to the latest EP 6.0 patch level, migrating it to NW2004 and then upgrading to NW2004S, we would simply prefer to create a new EP 7.0 instance and transport our most recent EP 6.0 package to it. We would then manually recreate the custom iViews and any style sheet changes.
Will this work okay? I would appreciate feedback from anyone who has taken this route.
Regards,
Calvin

Hi,
I think it should work. Depending on how complex your security settings are you might also have to export and import these [securiting settings|http://help.sap.com/saphelp_nw70/helpdata/en/d6/7dd241d98eda6fe10000000a1550b0/frameset.htm].
If you are using KM content you will have to transport this as well.
Are you using some kind of SSO (to the backend or to the portal?) Then you will have to recreate the trusts between the systems.
All in all I would recommend to do the upgrade. Especially if you did not modify a lot then the upgrade from EP6 to EP7 works (almost) without problems.
Please let me know if I can help you further on this,
Holger.

WAS 640 Upgrade to SP11

I am planning to upgrade my laptop WAS 640 SP9 installation to SP11. Where can I finds a document that outlines the steps to do this upgrade ? How about the upgrade files ? Where to find these ? Please advise.
Thanks !

HI Srikanth..
Just now i am also going for an upgradation to SP11.So i hope i can help u a bit on that.
The first thing u shud do is to get the required pdf guide
(Support Package Stack Guide - SAP NetWeaver 04 SP Stack 11) from service.sap.com/instguidesnw04..It will give u the step by step upgradation help.
Below are the patches or upgrade files in ur words , that u need to download from service.sap.com/swdc
1)CTRLORA11_0-20000118.SAR
2)J2EERT11_0-10001982.SAR
3)J2EERTOS11_0-20000118.SAR
4)SAPINST11_0-20000118.SAR
(Assuming ur underlying DB is oracle & window as ur OS)
Extract the files using SAPCAR and start ur journey towards SP11.
Note: Do follow the pre- & post-installtion steps.
Do send me the feedback n also the points , if it helps u.
Regards,
sandip agarwal

EP7 upgrade from SP11 to SP12

Similar Messages

Maybe you are looking for