Exception in CE 7.1 EHP1

Hi Gurus,
We are in the process of testing CE 7.1 .1 EHP1 as a part of upgradation. When we deployed the existing DCs that was work in CE 7.1 SP5 , we are getting few errors in some of the applications. As per our observation ,DCs that are having custom controller model nodes that are mapped to View (directly to UI elements), is giving Java Null Pointer exception on Page loading. When we tried to create custom nodes and map to the same UI element , this issue has been resolved. I Know it is not recommended to map Model nodes to UI elements directly , but still this was not throwing any exceptions in the previous versions. Is this a bug in CE 7.1.1 EHP1 ?
Thanks in Advance ,
Tony Isaac.

Hi
Try this
1.Select the Dc >Right Click>Select Development component--Select Show in Component navigator
2. Right click on the graphical component>Sync/create project>Select sync used Dc.
3. in pop up select all the Dc and Finish.
otherwise some problem in NWDS plug-ins.
Regards
Satish

Similar Messages

IDoc Exception (4) Unsupported Operation from NW EP 7.0 ehp1 to ECC 6

Hi fellow coders
I'm trying to send an IDoc (WPUWBW01) that I make in Java on an SAP NW EP 7.0 ehp1 SPS5 to an ECC 6.0 ehp4 SPS5.
I'm using the jar-files: jrfc.jar (external) and sapidoc70.jar (included in the PAR-file).
It works to request a transaction ID
//com.sap.mw.jco.JCO.Client.createTID()
String tid = client.createTID();
But when I try to send the IDoc (after I've done a "doc.checkSyntax()") with the send command:
//void com.sap.mw.jco.JCO.Client.send(Object arg0, String arg1)
//com.sap.mw.idoc.IDoc.Document
client.send(doc, tid);
I get the following exception:
com.sap.mw.idoc.IDoc$Exception: (4) IDOC_ERROR_UNSUPPORTED_OPERATION: Usage of SAP Java Connector IDoc Class Library is not supported in current environment.
As you can see it's not a JCo-exception but an IDoc exception, that makes me puzzled.
Some of the options are:
1. A port needs to be opened on ECC?
2. An RFC source/destination port needs to be created? In transaction SM59/SICF/WE21?
3. A module or the like needs to be activated in the ECC?
Any pointers in the right direction will be rewarded.
Thank you
/Petter

Has this type of Java -> IDoc communication without the JCo connector for third parties never been done before?
Any tips will be appreciated.
/Petter

Exception Aggregation (Average) displaying incorrect values after EHP1 Upgr

Hi All,
Exception Aggregation (Average) displaying incorrect values after EHP1 Upgrade in our BW system
We have recently upgraded the system to EHP1. After the upgrade some of the queries where we are using Exception Aggregation (Average) started giving the incorrect values.
Eg. We are displaying three Key Figures KF1, KF2 and KF3 (=KF1 %A KF2) against Store Hierarchy. In KF3 we are using Exception Aggregation (Average) on a characteristic 0PLANT.
There are 14 rows against 0PLANT and out of those 2 rows are blank for KF1, so for KF3. When it is calculating the average of these key figures its dividing the total value by 12 instead of 14 which is not correct in our case. Earlier it was dividing the total by 14.
So in this case 'Average' and "Average of all values <>0" are behaving the same way.
Kindly provide some inputs on this.
Best Regards,
Sachin Verma
+44 7506740018

Hi,
Thanks for viewing the thread. And happy to let you know that the issue was resolved.
The solution was:
Two formulas (local) were created, one including the formula variable with replacement path for ZD1, with exception aggregation on ZD1, and the other with formula variable with replacement path for ZD2, with exception aggregation on ZD2. Both these formulas are hidden.
Another formula (local) was created for u2018time takenu2019 = formula with ZD1 u2013 formula with ZD2, with exception aggregation total on u2018ZDOCNOu2019.
For the second instance, when one requires exception aggregation on records that has multiple values for keys, a nesting of formulas can be done displaying only the ones required.
For e.g. a formula with exception aggregation on say characteristic u2018item no.u2019 can be hidden, and included in another formula for exception aggregation on characteristic u2018document no.u2019. This is a typical case where one can achieve calculation before aggregation for a calculated key figure, formula or a counter.
Hope it might help someone, and saves time and effort for a similar issue posted.
Also would like to keep this thread open for exploring better solutions.
Regards,
Vijay

SAP NW CE 7.1 EHP1 NWDS Preview Version Installation issue

I am running into follow error message when trying to install NWDS of SAP NW CE 7.1 EHP1 Preview Version
Error Message:
Unable to complete action for feature "SAP NetWeaver Developer Studio Java EE" due to errors
Error Details:
Unable to complete action for feature "SAP NetWeaver Developer Studio Java EE" due to errors.
Unable to complete action for feature "SAP NetWeaver Developer Studio Facades" due to errors.
    Execution failed! Commmand: "msiexec.exe /norestart /qb /i librfc32.msi /lvx C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log ALLUSERS=2 REBOOT=ReallySuppress". Exit value: "1639". Working directory: "C:SAPCE-EPH1NWDSIDENWDS_platformeclipse eaturescom.sap.netweaver.developerstudio.facades_7.1.0.081107100357". Log file: "C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log".
    Execution failed! Commmand: "msiexec.exe /norestart /qb /i librfc32.msi /lvx C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log ALLUSERS=2 REBOOT=ReallySuppress". Exit value: "1639". Working directory: "C:SAPCE-EPH1NWDSIDENWDS_platformeclipse eaturescom.sap.netweaver.developerstudio.facades_7.1.0.081107100357". Log file: "C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log".
Unable to complete action for feature "SAP NetWeaver Developer Studio Facades" due to errors.
    Execution failed! Commmand: "msiexec.exe /norestart /qb /i librfc32.msi /lvx C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log ALLUSERS=2 REBOOT=ReallySuppress". Exit value: "1639". Working directory: "C:SAPCE-EPH1NWDSIDENWDS_platformeclipse eaturescom.sap.netweaver.developerstudio.facades_7.1.0.081107100357". Log file: "C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log".
    Execution failed! Commmand: "msiexec.exe /norestart /qb /i librfc32.msi /lvx C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log ALLUSERS=2 REBOOT=ReallySuppress". Exit value: "1639". Working directory: "C:SAPCE-EPH1NWDSIDENWDS_platformeclipse eaturescom.sap.netweaver.developerstudio.facades_7.1.0.081107100357". Log file: "C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log".
Execution failed! Commmand: "msiexec.exe /norestart /qb /i librfc32.msi /lvx C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log ALLUSERS=2 REBOOT=ReallySuppress". Exit value: "1639". Working directory: "C:SAPCE-EPH1NWDSIDENWDS_platformeclipse eaturescom.sap.netweaver.developerstudio.facades_7.1.0.081107100357". Log file: "C:DOCUME1PEdalaLocal SettingsTempcom.sap.netweaver.developerstudio.facades_librfc32.msi_install_standard.log".
Before error message is displayed, I get Windows Pop message with Windows Installer message as below:
Windows ® Installer. V 3.01.4000.1823
msiexec /Option
Install Options
          i - Status messages
          w - Nonfatal warnings
          e - All error messages
          a - Start up of actions
          r - Action-specific records
          u - User requests
          c - Initial UI parameters
          m - Out-of-memory or fatal exit information
          o - Out-of-disk-space messages
          p - Terminal properties
          v - Verbose output
          x - Extra debugging information
          + - Append to existing log file
          ! - Flush each line to the log
- Log all information, except for v and x options
     /log
          Repairs a product
          p - only if file is missing
          o - if file is missing or an older version is installed (default)
          e - if file is missing or an equal or older version is installed
          d - if file is missing or a different version is installed
          c - if file is missing or checksum does not match the calculated value
          a - forces all files to be reinstalled
          u - all required user-specific registry entries (default)
          m - all required computer-specific registry entries (default)
          s - all existing shortcuts (default)
          v - runs from source and recaches local package
Setting Public Properties
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
Please advice?
Best regards,
Sridhar

Hi,
Although I have not encountered this error in my installation copy - you can try the following:
Take the zip file for NWDS to another machine and install it. If you do get the same error - then the zip file was damanged in the transfer - if not then probably it is an issue with the Microsoft Installer files that you are using. If you are using a legal version of Windows then upgrade to the latest updates and then try again. You can try the same steps after shutting down and restarting your PC.
Most probably the zip file is damaged since the MSI has run successfully.for the CE WAS.
p256960.

Error in EHP1 Portal Installation

Dear All,
I am facing a weird error while install EHP1 Portal system. When it comes to phase Install Software units, it always fail with the same error. System details are below:
System: Netweaver Portal EHP1 System (Usage Type: As Java, EP, EP Core and DI)
OS: Linux Red hat 5.2
Database: DB2 9.7 FP 3
JDK: 1.4.2
Please check below error log:
sapinst_dev.log:
ERROR      2011-03-16 14:30:02.174 [iaxxejsbas.cpp:204]
FJS-00003 uncaught exception: nw.sdm.deploymentErrorWithLog:
SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check /usr/sap/trans/instlogdir/sapinst_instdir/NW701/AS-JAVA/DB6/CENTRAL/
/callSdmViaSapinst.log for more information. (in script unknown, line 0: ???)
TRACE      2011-03-16 14:30:02.790 [syuxctask.cpp:1382]
           CSyTaskImpl::start(bool)
A child process has been started. Pid = 2832
TRACE      2011-03-16 14:30:02.914 [syuxctask.cpp:1382]
           CSyTaskImpl::start(bool)
A child process has been started. Pid = 2833
ERROR      2011-03-16 14:30:05.434 [sixxcstepexecute.cpp:950]
FCO-00011 The step enableUsageTypes with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|enableUsageTypes was
executed with status ERROR ( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog:
SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check /usr/sap/trans/instlogdir/sapinst_instdir/NW701/AS-JAVA/DB6/CENTRAL/
/callSdmViaSapinst.log for more information. (in script unknown, line 0: ???)).
callSdmViaSapinst.log:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [a2zportalprd] with user name: [Administrator]
                                Check your login information.
                                Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. Root exception is co
m.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
        at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
        at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
        at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
        at javax.naming.InitialContext.init(InitialContext.java:233)
        at javax.naming.InitialContext.<init>(InitialContext.java:209)
        at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
        at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51
System is running and I am able to login with administrator user id. There is only single server node and there is no error related to expiration time. SDM is also running. Secure store is also correct. Still I am facing same problem. I checked on SDN as well and found many reference of the same problem but none of them resolved my problem.
Please suggest.
Thanks
Sunny

Hi Sunny,
Check note 1313644 and 609603. Hope it helps.. The 1st link seems to have the same issue.
Also Refer:
SDM Problem installing SAP Netweaver EHP2
ERROR: Cannot connect to Host: [SERVER] with user name: [J2EE_ADMIN]
Rgds,
Soujanya

System Monitoring - Solman 7 EHP1

Hi
Solution Manager 7.0 EHP1 / Windows 2008 / Oracle
Satellite System R/3 Enterprise extn set 110 / Solaris on Sparc / Oracle
I am having trouble configuring System monitoring on solution Manager. Here is what I have done
Added the satellite system to SLD, Configured data collector (RZ70) in the satellite system, Pushed data from SLD to SMSYS (automatic transfer).
Installed CCMS agent + CCMSPING agent in satellite system. Checked connectivity in solman with RZ21. Connectivity is fine.
Created Monitor sets and monitors in CCMS for monitoring satellite system. Client data is visible in CCMS.
Created a solution in DSWP. Created logical component in SMSY. Assigned the logical component to the solution. Now I can see the data in DSWP.
Here are my questions
==================
1. In DSWP, everytime I have to view data, I have to click on "Setup System Monitoring" to view the alerts in the satellite system
I see a red alert reading for instance availability. Similarly,
In the system monitoring workcenter, I see the status of both the solution manager and the satellite system greyed out with a cross. When I move my mouse over it, it reads, no CCMSPING data available.
Any idea as to why this happens?
2. For what I see after I click on "Setup System Monitoring" I have parameters which I can configure. I see default values for these parameters. Is there like a recommendation or a template which can be used to setup these monitoring parameter values?
3. I have configured the ccmsping in the solution manager (for the solution manager) however the ccmsping service refuses to run. It throws a error reading "The system could not find the file specified". The ccmsping exe file is present in the location stated. Are there other files that this is looking for?
4. While registering the agent in the satellite system, I first registered with the CSMREG id. It failed with the message,
INFO: [SMG:040:CSMREG] connected to SMG, host sapsm.NA.XXX.NET, System Nr. 00, traceflag [ ]
INFO: SMG release is 701 , (kernel release 701 )
        RFC Error Info:
         message:
         status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
         intstat:
      Go Ahead anyway? n/[y] :
INFO: handling destination SAPCCM4X.SAPR3PR1.00
ERROR: can't register at SMG. RfcRc = 2, AUTHORITY_NOT_AVAILABLE
RFC Error Info for SALF_CSM_AGENT_REGISTER
message:
status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
intstat:
I then did this with a dialog user. That worked. Agent was registered in solution manager. Any idea on why this error would show up with the CSMREG? I am concerned about issues which can come up when the password for the dialog user changes.
I am not sure how to upload screenshots of what i see, probably if i do that, it will be easy to relate to the issue which I am mentioning here. Is there a way I can do that?
Let me know if you need any more information from my side to understand this.
Ideas will be appreciated.
thanks
Ravi

Hello Ravi,
Additionally you will want to look at SAP Note 1175058 - Problems with CCMSPING in SAP Solution Manager, especially
c) Ensure that the message server host name in the monitoring options of CCMSPING and the message server of the corresponding main instance of the relevant system is the same in the SAP Solution Manager landscape
(SMSY). Important: The monitoring options of CCMSPING must not be configured using an IP address.
Regards,
Paul

Could not validate SPNEGO token.java.lang.Exception: Checksum error.

Hello consultant:
We are trying configurated SSO usind SPNEGO module
We have a portal 7.0 ehp1 and Active Directory Microsoft versión 2003 native
we have followed the steps described in note Sap 1457499"Note 1457499 - SPNego add-on"
When we have logged with user Active Directory and we try access to portal we obtain following error:
Authorization check user error
We have Deploy the Web diagtool from SAP Note 1045019 on the J2EE server, run it and perform the
following steps:
1. Select "Component" = "security" and "Activity" = "all"
2. Click the "Go" button, followed by the "Add All" button
3. Select "Component" = "All" and in the "Search pattern" field write "com.sap.security.spnego"
4. Click the "Go" button, followed by the "Add All" button
5. Start the tool
Then we have reproduce the problem and stop the tool. The generated zip file will contain following error:
15:45:20:078 Error J2EE_GST_PRD SAPEngine_Application_Thread[impl:3]_15 ~p.security.spnego.krb5.crypto.DesCrypto Checksum error! checksum: 0xc46bfed8d0dbc54221ee75405c8cd5ac; calculated checksum: 0x6ead7e801608b729a6957597327f2ba5
15:45:20:078 Error J2EE_GST_PRD SAPEngine_Application_Thread[impl:3]_15 ~m.sap.security.spnego.SPNEGOLoginModule Could not validate SPNEGO token.
java.lang.Exception: Checksum error.
at com.sap.security.spnego.krb5.crypto.DesCrypto.decrypt(DesCrypto.java:43)
at com.sap.security.spnego.krb5.KrbEncryptedData.decrypt(KrbEncryptedData.java:81)
at com.sap.security.spnego.krb5.KrbApReq.decrypt(KrbApReq.java:67)
at com.sap.security.spnego.SPNEGOLoginModule.parseAndValidateSPNEGOToken(SPNEGOLoginModule.java:234)
at com.sap.security.spnego.SPNEGOLoginModule.processAuthorizationHeader(SPNEGOLoginModule.java:385)
at com.sap.security.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:102)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.login(LoginModuleLoggingWrapperImpl.java:185)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:70)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631)
at javax.security.auth.login.LoginContext.login(LoginContext.java:557)
at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:912)
at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.login(AuthenticationService.java:367)
at com.sapportals.portal.prt.connection.UMHandler.handleUM(UMHandler.java:126)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:181)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sap.portal.navigation.Gateway.service(Gateway.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Could you help us?
Many thanks for your collaboration

<< Do not post the same question across a number of forums >>

Upgrade from NW 7.0 EHP1 to NW 7.3

Hi All,
I am upgrading NW 7.0 EHP1 to NW 7.3 and reached the downtime phase.
I got halted by an error in UNDEPLOY_THE_OLD_DB_CONTENT phase of downtime step.
The logs are as follows :
UNDEPLOY_THE_OLD_DB_CONTENT_UTO_01.LOG
Aug 31, 2011 5:47:16 AM Info: com.sap.sdt.j710.db.DBContentUtilImpl [Threadmain,5,main]: T
he /usr/sap/EHD/JC00/SDM/root/origin/sap.com/tc/TechSrv/XML_DAS_Init/SAP AG/0/7.0103.20081105085233.0000/XML_DAS_Init.sda sda archive will be undeploy.
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:883) [Threadmain,5,main]:
Exception has occurred during the execution of the phase.
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:884) [Threadmain,5,main]:
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.j710.db.DBContentUtilImpl.undeploySDAContent(DBContentUtilImpl.java:131) [Threadmain,5,main]:
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Error: com.sap.sdt.j2ee.phases.PhaseTypeUndeployDBContent.execute(PhaseTypeUndeployDBContent.java:79) [Threadmain,5,main]:
Error during undeployment of DB content. Details:java.io.FileNotFoundException: testconn.log (No such file or directory)
java.io.FileNotFoundException: testconn.log (No such file or directory)
Aug 31, 2011 5:47:16 AM Info: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:925) [Threadmain,5,main]: P
hase UPGRADE/OFFLINE_MIGRATION/UNDEPLOY_THE_OLD_DB_CONTENT has been completed.
I suppose that it is not able to find testconn.log (No such file or directory) but not sure where it will be.
Please provide a solution or workaround.
Thanks

Hi,
The log files are ideally created in the upgrade folder - log subdirectory:
/usr/sap/<SID>/upg/java/log/
Please check in this folder if the file exists. Also check if the read/write permissions to this folder are fine for user <sid>adm. It could be that the file is getting created due to lack of permissions.
Regards,
Srikishan

Unable to deploy application in CE 7.1 EHP1

Hi All,
I have created an webdynpro dc application in CE 7.1 EHP1. Its a simple hello world program.
However when I deploy I get the following error:
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'demo.sap.com/welcomemali' is not deployed on the server. Please check the used URL for typos.
     at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:364)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:566)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:504)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:169)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:230)
     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'demo.sap.com/welcomemali' since it is not a Web Dynpro object.
     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:87)
     at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:37)
     at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:362)
     ... 50 more
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name demo.sap.com/welcomemali exists.
     at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:264)
     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:85)
     ... 52 more
Can anyone help?
Regards,
Malita

Hi Malita,
The error trace says 'No Web Dynpro application exists' & 'It is not a Web Dynpro object'
Please verify if you have created the WD application, if so delete it & then create a new application object.
Do a build for the project & create archive.
Then for the application object, choose the context menu option 'Deploy New Archive & Run'.
I hope this solves your issue.
Kind Regards,
Nitin

Webservice configuration in SAP Netweaver CE 7.1 EHP1

Hello,
I am trying to configure the webservices(SAP ME) in SAP Netweaver CE 7.1 EHP1. I follow the procedure below.
1.Log on to SAP NetWeaver Administrator Console by launching the following URL:
http://<host>:<port>/nwa.
2. Choose SOA Management Application and Scenario Communication Single Service Administration .
3. Search for the Web service:
           Eg. BOMProcessingIn
4. Select port type
5. In the bottom window, select associated ServicePort
6. Choose the Security tab.
7. Choose Edit.
8. Select the Transport protocol.
9. Check the UserID/Password under HTTP Authentication.
10. Save
while saving I am getting an error : A problem in the backend.Please refresh the UI.
Log Message:
Message:
[EXCEPTION]
com.sap.esi.esp.admin.ui.helper.exceptions.TechnicalException: Problem occured at the backend. Please refresh the UI.
at com.sap.esi.esp.admin.ui.helper.impl.JMXWSConfigManager.updateRTConfig(JMXWSConfigManager.java:356)
at com.sap.esi.esp.admin.ui.admin.BindingDataView.onActionSave(BindingDataView.java:1007)
at com.sap.esi.esp.admin.ui.admin.wdp.InternalBindingDataView.wdInvokeEventHandler(InternalBindingDataView.java:686)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Date:     2010-09-21
Time:     18:32:18:600
Category:     com.sap.esi.esp.admin.ui.admin.AdminComp
Location:     com.sap.esi.esp.admin.ui.admin.AdminComp
Application:     sap.com/tclmitsamuimainframe~wd
Thread:     Thread[HTTP Worker [@1298169768],5,Dedicated_Application_Thread]
Data Source:     j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
DSR Transaction:     0c8868e0c5d011df967500155d046701
Message Code:
Session:     1
Transaction:
User:     Administrator
Time Zone:     0-400
CSN Component:     BC-ESI-WS-JAV
DC Component:     sap.com/tcesiespitsamui~wd
Correlation ID:     458750850000000004
DSR Root Context ID:     F6B4F240C5CF11DFAA0100155D046701
DSR Connection:     0c8868e0c5d011df967500155d046701
DSR Counter:     0
Log ID:     00155D04670100200000000200001384
Host:
System:
Instance:
Node:     server0
Request you for any help.
Regards,
Guru.
Edited by: gurunadh kumar on Sep 22, 2010 12:40 AM

Hi Gurunadh Kumar
It is not easy to read your question, anyway I made it and let me try to summarize it before providing your the solution:
Reproducing steps when configuring the webservices(SAP ME) in CE 7.1 EHP1.
1. Log on to SAP NetWeaver Administrator Console by launching the following URL: http://:/nwa.
2. Choose SOA Management Application and Scenario Communication Single Service Administration .
3. Search for the Web service: Eg. BOMProcessingIn
4. Select port type
5. In the bottom window, select associated ServicePort
6. Choose the Security tab.
7. Choose Edit.
8. Select the Transport protocol.
9. Check the UserID/Password under HTTP Authentication.
10. Save while saving I am getting an error :
A problem in the backend.Please refresh the UI. Log Message: Message:
[EXCEPTION] com.sap.esi.esp.admin.ui.helper.exceptions.TechnicalException:
Problem occured at the backend. Please refresh the UI.
I have checked through the exception stack traces, this should be caused by the patch level inconsistency between the following
components on your CE7.11 system:
   - ESP_FRAMEWORK
   - ENGINEAPI
   - J2EE-FRMW
To resolve this problem, please download the lastest patch for all the above software components as per the current SP level,
and deploy them to your system, then try the same steps again.
Best Regards,
Thunder
Edited by: Thunder Feng on Sep 22, 2010 10:52 AM

Unable to test enterprise services in SAP SRM 7.0 EhP1

Hi experts,
For my recent project, we have enabled "PI Independent Enterprise Services" business function in our SRM 7.01 EhP1 system. While to trying to test some of the enterprise services, we are facing some error. I am pasting the request message and the response that I got from the enterprise service InternalRequestSRMByElementsQueryResponse_in. While defining the end point, I have used basic authentication settings. Note that I am testing this ES with my own user id and password which is a valid on for the SRM system. Can someone help please?
Request message:
POST /sap/bc/srt/xip/sapsrm/internalrequestsrmbyel/100/sapsrm_internalrequestsrmbyel/sapsrm_internalrequestsrmbyel_binding HTTP/1.1
Host: <host>:<port>
Content-Type: text/xml; charset=UTF-8
Connection: close
Authorization: <value is hidden>
SAP-PASSPORT: 2A54482A0300E60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000064353632326163306235363431316530383330333030303030323337663833320000000002D5622AC0B56411E0830300000237F832D562EADFB56411E0AD3800000237F83200000001000000002A54482A
Content-Length: 753
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body><ns1:InternalRequestSRMByElementsQuery_sync xmlns:ns1='http://sap.com/xi/SAPGlobal20/Global'><InternalRequestSelectionByElements><CreationDatePeriod><StartDate>2011-04-01</StartDate><EndDate>2011-07-22</EndDate></CreationDatePeriod></InternalRequestSelectionByElements></ns1:InternalRequestSRMByElementsQuery_sync></SOAP-ENV:Body></SOAP-ENV:Envelope>
Response that I got:
HTTP/1.1 200 OK
content-type: text/xml; charset=utf-8
content-length: 915
accept: text/xml
sap-srt_id: 20110723/194910/v1.00_final_6.40/4E24C49F23184117E1008000097C2FFA
sap-srt_server_info: SRM_100,167 ,http://sap.com/xi/SRM/SE/Global,InternalRequestSRMByElementsQueryResponse_in,InternalRequestSRMByElementsQuery_sync,126
server: SAP NetWeaver Application Server / ABAP 702
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Header/><soap-env:Body><n0:InternalRequestSRMByElementsResponse_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"><Log><BusinessDocumentProcessingResultCode>5</BusinessDocumentProcessingResultCode><MaximumLogItemSeverityCode>4</MaximumLogItemSeverityCode><Item><SeverityCode>4</SeverityCode><Note>Abort occurred; Internal request not read</Note></Item><Item><SeverityCode>4</SeverityCode><Note>Abort The attributes of the user are inconsistent or not defined. See transaction PPOMA_BBP. on Internal request level</Note></Item><Item><SeverityCode>4</SeverityCode><Note>Abort An exception with the type CX_GDT_CONVERSION occur red, but was neither handled locally, nor declared in a RAISING clause on Internal request level</Note></Item></Log></n0:InternalRequestSRMByElementsResponse_sync></soap-env:Body></soap-env:Envelope>

Hi Gaurav,
Thanks for responding. Yes, all the backend config are in place since I am able to successfully run an equivalent RFC (BBP_PD_SC_GETLIST) and another RFC named BBP_PD_SC_GETDETAIL from SE37. The problem seems to be something very specific to the ES. May I request you to run this ES at your end (if possible) and let me know the result possibly with the input and output message similar to the one I pasted in the origincal question.
Thanks in advance,
Nilay

EhP1 installer error (RFC of "SUBST_START_REPORT_IN_BATCH" failed)

Hi,
we are trying to upgrade our CRM 7.0 to the EhP1 and the EhP1 installer is blocked with the error:
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: RFC call to SUBST_START_REPORT_IN_BATCH failed with key RFC_ERROR_SYSTEM_FAILURE (SYSTEM_FAILURE): connection closed without message (CM_NO_DATA_RECEIVED)
Log files report the following errors:
(altntfi.sav)
#---- MASKING file ALTNTFI.LOG from G:\usr\sap\CR7\EHPI\abap\log
#---- TIME: 20111125115607 PHASE: ALTNTAB_FILL
1 ETQ201 Entering upgrade-phase "ALTNTAB_FILL" ("20111125111509")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSR4
4 ETQ399   auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/ALTNTAB_FILL'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = '30'
2 ETQ399 Arg[1] = 'ALTNTFI.ELG'
4 ETQ399 Set environment for shadow connect:
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '07', GwService = 'sapgw07'
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ399   default TPPARAM: SHADOW.TPP
4 ETQ010 Date & Time: 20111125111509
4 ETQ265 Starting report "RDDNT2MT" with variant "SAP_INIT" in batch
4 ETQ359 RFC Login to: System="CR7", Nr="07", GwHost="SYSKCRMDEV1", GwService="sapgw07"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
2EETQ360 RFC of "SUBST_START_REPORT_IN_BATCH" failed:
2EETQ361 code/exception : SYSTEM_FAILURE
2EETQ362 key             : RFC_ERROR_SYSTEM_FAILURE
2EETQ364 message         :
2EETQ399 connection closed without message (CM_NO_DATA_RECEIVED)
4 ETQ359 RFC Login to: System="CR7", Nr="07", GwHost="SYSKCRMDEV1", GwService="sapgw07"
4 ETQ232 RFC Login succeeded
2EETG894 Exception "SYSTEM_FAILURE" raised, write variant failed with error code -1
2EETG890 Exception "SYSTEM_FAILURE" raised, job scheduling failed with error code -1
2EETQ261 Start of batchjob "RDDNT2MT" failed
4 ETQ010 Date & Time: 20111125111548
We have logged through GUI to the shadow instance but we can't test the function module SUBST_START_REPORT_IN_BATCH: the shadow instance continuously dumps (in SE37, ST22, ST11, SU01... with dumps LOAD_PROGRAM_CLASS_MISMATCH, GETWA_WRONG_LENGTH, LOAD_TYPE_VERSION_MISMATCH...). When I don't have a dump (i.e. I try to activate the function module in SE37 without opening it), the GUI closes with the error: "Work process restarted, session terminated " and in the logfile dev_disp shows me:
Fri Nov 25 11:15:30 2011
*** ERROR => DpHdlDeadWp: W5 (pid 17996) died (severity=0, status=0) [dpxxwp.c     1522]
Any help would be greatly appreciated.
Thanks,
Davide

Hi Davide,
Please try out below mentioned steps
Set the USER Environment Variable u2018auth_shadow_upgradeu2019 to u20181u2019 for the <SID>adm user (set the variable while logged in as that user)
Change the Shadow Instance service to run with the <SID>adm account
Stop the Shadow Instance (you can leave the Central and SCS Instances running)
Start the Shadow Instance
Continue the EHPI process from where it left off
Hope this helps.
Regards,
Deepak Kori

NWDI in SAP EHP1 for NW 7.3

Hi All,
I am new to NWDI concept.
Can any one provide me the step by step process for NWDI in EHP1 for NW 7.3.
I am having the doc for 7.x but this not explains the process correctly.
When I do so it is asking for more configuration.
Please let me know the DOC start from SLD config.
Regards
R.Prakash

Hi All,
Please let me know the steps I followed is right:
1. http://<host>:50000/sld/ -> Set up the SLD and it started running.
2.http://<host>:50000/sld/fun -> Enabled the "CM services","NWDI using CMS" and NWDI using CM services - recommended","SLD" and "service Registry".
3. http://<host>:50000/nwa -> configuration->scenarios->Config Wizard
and tried to run the "DI CMS - create application skeleton" but I am getting error as
"Error: unknown exception: Cannot find software component release (Vendor/Name/Release valenet.net/MYCOMPONENTS/1.0) in CMS. UpdateCMS Server or/and check SLD component content.Error: unknown exception: Cannot find software component release (Vendor/Name/Release valenet.net/MYCOMPONENTS/1.0) in CMS. UpdateCMS Server or/and check SLD component content."
same error I am getting when running "Integration of MII with existing NWDI".
I guess the information filled in the create track is wrong. Can any one tell me the step I followed is right and also where can I get the information about the Software Components?
Regards
R.P

SOLMAN EhP1 xml file problem

I am upgrading my Solution Manager 7.0 from stack 17 to stack 18(EHP1) but whenever I try to generate the xml file on the service marketplace, all I get is "The table does not contain any entries"
To recreate...
go to service.sap.com/swdc --> SAP Support Packages --> Support Package Stacks --> SAP Solution Manager 7.0
Then...
Target Stack = SAP SOLUTION MANAGER 7.0 EHP 1-Initial Delivery
Source Stack = 17 (8/2008)
when I click NEXT, it goes straight to page 3 of 3, and I get buttons for Previous Step, Print List, Save as file, Add to download basket, Side Effects report, etc...
Then the table where all the packages should be is empty, except for the message "the table does not contain any entries"
We have tried this with multiple people on multiple machines, all the same result. By the way I just upgraded from abap & java stack 15 to 17.. and I had no issues getting the xml file there. (I downloaded the DVDs of the actual patches so I just need the xml)
Thanks!
Edited by: Bill McCrea on Jan 15, 2009 2:42 PM

After reading your question, I went to the SPstack webpage, and selected a SOLMAN EHp1 stack 16-17, DB2 UDB. when I was on the "Step 3 of 3 Downloadable support packages" I was able to select the Save as File button and I was able to generate the XML. It may have been a temporary problem. Make sure that you don't have a pop-up blocker that would prevent the window from appearing.
Regards
---Bill

PI 7.1 EHP1 Mapping with Variables feature

HI,
Anyone can point to a blog/something explaining how the variables works in the graphical mapping editor? (PI 7.1 EHP1)
It's working fine for simple one-to-one mapping, but as soon as queues and context come in I'm never getting the expected results.
Now I'm trying to populate a variable to be re-used in 2 differents target fields.
source -> useOneAsMany -> splitByValue -> trim -> variable.
variable -> target1
variable -> some logic -> target 2
Exception: values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD)
Are VARIABLE single value and cannot be used as a ResultList?
Edited by: Martin Lavoie Rousseau on Mar 8, 2011 7:45 PM

The screenshot made me notice the occurence of the variable is 0..1 so my guess would be it can only be single value and not ResultList.
Also the Display Queue option is not working properly.
This looks like a nice feature on paper but is really limited.

Exception in CE 7.1 EHP1

Similar Messages

Maybe you are looking for