System creation error
Hi,
I am using EP 7.1,NW04S.
I am trying to create a system .For that here I followed the navigation like
System administrationSystem confi syatem Landscape NewSystem(from templates)selected SAP system using dedicated application serverNextsystem namesystem id
So, system is created. But once I am testing the connectivity from back end it is given error like
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Could not retrieve default alias. Make sure the system object has at least one alias.
How to resolve this error to get the connection successfully?
Thanks,
Kundan
Hi,
you will find system alias in the DISPLAY dropdown that is located right side of your buttons.
Click on Display > select system alias -> click on new -> give some name -> click on Add -> and click on save.
refer the below link also
[http://wiki.sdn.sap.com/wiki/display/EP/HowtoCreateSystemObjectinthePortalforConnectingtoSAPBackend+Systems]
check this link also. you can find where exactly to create alias
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0087569-8ea3-2c10-20bb-c799dc258950?QuickLink=index&overridelayout=true]
Edited by: VV on Mar 12, 2010 9:14 AM
Similar Messages
-
System creation error in System administration
Please find the below error when iam trying to create the System in System administration->system configuration-->portal content i have created one folder in that foder i made right click and system from template iam getting this below error
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 10:52_23/07/09_0023_42172150
Refer to the log file for details about this exception.Refer to the log file for details about this exception.
Where is that.
can u paste the log here.
Regards,
Ravi -
R/3 source system creation error(Idoc is missing)
Hi expert's.
i have created an r/3 source system in BI 7. but it's showing error when i am activating it.
error as follows.
1. Basic type ZSMA087 does not exist EA 447
2. Incorrect IDoc type ZSDF085 in the ALE definition of the source system RSAR 373
for the above error 1 i checked in the RSBASIDOC table. it showing the idoc type. when i am checked with the source system that is r/3 system in the partner profile for logical system. it's showing the incorrect idoc type in RSSEND outbound parameters for that logical system
when i am changed that idoc type it's showing error as follows.
"entry RSSEND zsma087 does not exit in edimsg.
after that i checked with this table edimsg. for the rssend outbound option it's won't have the idoc type zsma087. table edit is also not possible on that.
so please help me to solve the issue.
regards
Harikrishna NHi Hari,
Are you using ECC6.0 system or Bw(bi7.0) & R/3 source system
Regards,
Vijay. -
Hi..
I cannot create R/3(productive) source system at BW (development)
I checked password, cross-client and client specific are all changeble (t-code SCC4) and namespaces, sofeware are also modifiagle (t-code SE06) at R/3.
At BW, RFC connection is Ok (SM59) and R3 side, RFC also connected w/o problem.
But the error is still not resolved.
What I have to do now..Hi Ravi..
Error massage is...
Massage No. RSAR502
Diagnosis
With Remote Function Call to system error Screen output without connection to user. ccurred.
and runtime error massage is (ST22)
DYNPRO_SEND_IN_BACKGROUND
Rita -
UWL system creation error?
Hi,
I'm trying to setup UWL configuration for ESS/MSS. During minimal configuration of UWL setup, I'm assigning one of the system alias which is connecting to the R3 system using SAPLogonTicket method. We got same uid maintained in portal and ECC6.
I defined UWL system and when I clicked on Register button, I get below message
(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:
(Connector) :com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias UWL_System. Contact your system administrator.
OK, then I wanted to test the connection of system object that is used by UWL. WebAS, ITS connection tests are successfully, but "Test connection with connector" failed with below error
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
As suggested in this thread which was posted by me sometime ago
Standard UWL configuration error?
I tried to use System Administrator >> Support >> SAP Transaction >> choose the system aliase that is used for UWL and entered SU01 tcode, it pops with windows for UID/PWD, why is this happening even when all the parameters are correctly defined in System object?
Thanks
PraveenHi Geet,
I still have no luck. I tried exactly what you said and followed all notes. Here are the steps that I followed and error message
1) UWL_Service user didn't exist in the R3, so created and assigned roles that are required as you mentioned and as mentioned in note 873932, 1109225, 1133821, 1171615.
2) Set up RFC destination in Visual admin and binded to the UWL_Service user for system_alias$WebFlowConnector. In my case the system alise is SAP_ECC_HumanResources.
3) Restarted the server.
4) Configured new UWL system with SAP_ECC_HumanResources system alise. Click register button I got below error
Error in retrieving logical system id for system SAP_ECC_HumanResources:
com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: User is missing credentials for connecting to alias SAP_ECC_HumanResources. Contact your system administrator.
User :<USER.R3_DATASOURCE.XXXXXXX> getting data from system : <SAP_ECC_HumanResources >: JCO error in checking/creating UWL service user:
com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: User is missing credentials for connecting to alias SAP_ECC_HumanResources. Contact your system administrator.
User :<USER.R3_DATASOURCE.XXXXXXX> getting data from system : <SAP_ECC_HumanResources >: JCO error in reading configuration::com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: User is missing credentials for connecting to alias SAP_ECC_HumanResources. Contact your system administrator.
Error in loading configuration for system SAP_ECC_HumanResources:com.sap.netweaver.bc.uwl.UWLException: (Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:(Connector) :com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias SAP_ECC_HumanResources. Contact your system administrator.
Thanks
Praveen
Edited by: Praveen11 on Jul 7, 2009 7:10 AM -
System creation error for email communication
I am getting runtime error in creating system for
com.sap.netweaver.coll.appl.gw
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 12:36_15/09/10_0001_5046050
Refer to the log file for details about this exception.
I am unable to send mail from KM because I have to give the alis name of this system to the colloboration groupware transport to
create mail transport.
Kindly help me to resolve this issue.
regards,
Abhishekh Singh
Enteg InfotechThanks for quick response , I checked the log file I am getting the following error, even I am
trying to create system by administrator or the user having super admin access but still I am getting
this error.
Please help me to resolve this issue.
Exception ID:10:52_16/09/10_0002_5046050
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.defaultSystemWizard
Component class : com.sap.portal.admin.wizard.impl.DefaultSystemWizard
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
at java.security.AccessController.doPrivileged(Native Method)
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.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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.ClassCastException
at com.sap.portal.pcm.NewObjectDescriptor.addText(NewObjectDescriptor.java:167)
at com.sap.portal.pcm.NewObjectDescriptor.putTextAttribute(NewObjectDescriptor.java:115)
at com.sap.portal.pcm.iviewserver.NewIVSObjectDescriptor.setTitle(NewIVSObjectDescriptor.java:447)
at com.sap.portal.admin.wizard.AbstractPCMWizard.setSpecialAttributes(AbstractPCMWizard.java:578)
at com.sap.portal.admin.wizard.AbstractPCMWizard.finalizeDescriptor(AbstractPCMWizard.java:297)
at com.sap.portal.admin.wizard.panes.SavePane.doAfterSubmit(SavePane.java:113)
at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:356)
at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174)
at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99)
at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
Regards,
Abhishekh Singh
Enteg Infotech -
Error while source system creation/Source system transport
Hi,
In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
Message no. RSAR502
Diagnosis
With Remote Function Call to system GWPCLNT900 error connection closed
(no data) ccurred.
Procedure
Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
KrishnaHi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier -
Error: 3816: Local System Creation during install was not successful.
Hello,
This is our first time installing Oracle Wokflow 2.6.3 Standalone.
We are having problems with the Event Manager.
When we access the event manager pages:
pls/wf/wf_event_html.listevents?resetcookie=T
pls/wf/wf_event_html.listsystems?resetcookie=T
etc.
We get this error:
Error: 3816: Local System Creation during install was not successful. Please review the install log file for errors.
Error Stack:
WF_EVENT_HTML.isAccessible(EVENTS)
WF_EVENT_HTML.ListEvents()
The installation was successful.
We cannot change the Local System in the Global Workflow Preferences option.
The table WF_systems is empty.
Should the local system appear in this table?
ThanksSoftware component sap.com/LM-TOOLS with version 7.00.9.3 is found on the system but in the stack it is listed with version 7.00.9.0.
Software component sap.com/SAP-JEECOR with version 7.00.9.1 is found on the system but in the stack it is listed with version 7.00.9.0.
You are trying to upgrade a system with the lower version of sap.com/LM-TOOLS and sap.com/SAP-JEECOR. The other thing I notice is that if you are upgrading to EhP4/EhP1 NW then the version of LM and SAP-JEECOR should look something like 7.01.3.0.
Are you using MOPZ to download EhP's ? As the error message says synchronize the system with SAP Solution Manager and then generate a new stack file.
Hope this helps.
Thanks,
Naveed -
Download Helper Screen Capture worked to capture video if the default "no audio" option is active. But, no audio. The "speakers" or "microphone" audio options are confusing....the audio to be captured is from the video, so what do you choose? With either "speakers" or "microphone" selected, the captured file has poor audio and no video. Re-capture efforts (speakers) get "Invalid capture file error" and "File Creation error- Unable to rename/copy audio file"
The paid upgrade of "Converter" doesn't work.
Instructive documentation - not very good.
Suggestions - Need time delay between initiation of "Record" and starting the video to be recorded.
Could use timer tracking of the record process.
Are there operating system limitations? (Have Windows XP Pro)That is an issue for the developer of that Download Helper.
-
Excise Invoice creation error -Billing document does not exists
Dear Experts,
I have created supplementary sales order, billing with refernece through sales order by VF01.
Now I want to create Excise Invoice but system gives error Billing Document does not exists
I have checked billing document in VBRK table & it is showing in table.
My item categroy is L2N -and set it to C
I have assigned Billing type under Outgoing excise invoice ->Assign billing type to delivery type still my excise invoice is not generating.
Pl. guide me.
Thanks
TruptiResolved my problem.
Actually in Billing item categroy if you put SD Doc. Catg. as M you can do excise invoice even if you have not created the
outbound delivery.
So cycle will be Supplementary Sales Order->VF01 with ref. to SO->J1IIN -Excise invoice creation.
Thanks to all.
Trupti. -
Request creation error for mitigation control workflow
Dear Expert,
I had activiate the workflow from RAR to CUP on Mitigated User assignment, I had completed following customizing:
1)RAR->configaration->Workflow
2)CUP->configaration->initiator, stage, path.
but when I created mitigated user assignments in RAR, after click "Submit", error popup: "Request creation error"
can some one help?
thanks!Dear,
the log is below:
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server YYY:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
ERROR service 'SAPGW00' unknown
TIME Thu May 20 13:33:16 2010
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -3
MODULE niuxi.c
LINE 1732
DETAIL NiPGetServByName2: service 'SAPGW00' not found
SYSTEM CALL getservbyname_r
COUNTER 375
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: END POOINT URL: http://9.186.143.129:50100/AEWFRequestSubmissionService_5_2/Config1?style=document
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: before submit:
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: wftype: MITIOBJ reqid: GRC01
May 20, 2010 2:10:50 PM com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext
FINEST: validfrom: 2010-05-20 validto: 2011-05-20
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: MITREFNO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOMITREFNO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: CT01
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: RISKID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MORISKID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: ZC02
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: LANG
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: LANG
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: EN
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: MONITORID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MONITORID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: GRC01
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: Integer
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: STATUS
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOSTATUS
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 0
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: DATE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: VALIDFROM
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: VALIDFROM
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 05/20/2010
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: DATE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: VALIDTO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: VALIDTO
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 05/20/2011
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: BU ID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: BUID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: null
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: Approver ID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: MOAPPROVERID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: null
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: OBJTYPE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: OBJTYPE
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: U
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Data Type: String
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Descripton: OBJID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Name: OBJID
May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
INFO: Value: 207471
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null
May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
WARNING: 2010: null -
Delivery Note to Subcontract creation error "Essential transfer parameters
Hi
I am facing issue in return delivey
Delivery Note to Subcontract creation error "Essential transfer parameters are missing in record:000001".
Could you please let me know the casue of this error and where exactly i can see error.
Regards
vikcyHi Vicky,
Check If the Customer number(Plant) has been maintained in the vendor master record control data and the vendor should also be maintained in the customer master data. Once you maintain this system determines the shipping point based on the customer master and the shipping data missing. Kindly try delivering after maintaining these and let me know If you need any more information on this.
Regards
Ram Pedarla -
Application System creation problem
Hi All !
We are using Designer 6.0 and Oracle 8.1.5
After successful login when we try to create Application System following
error message appears:
RME-00011: Operation 'INS' on ci_application_systems has failed
When we try see the Cause/Action, we find following:
// Cause: An API operation request has been failed for some reason
// Action: Examine other reported errors for specific details.
It is to be noted that we don't get any other error message and we can not
move forward without creation of application system.
Prompt help would be highly appreciated.
Atul
nullHello Atul,
I had the same problem with 8.1.6.
Solution:
edit init.ora
set the following:
large_pool_size = 2097152
should work
Juergen
null -
Child creation Error on vms HELP
Hi,
Iam trying to execute a file from withing a java program on VMS This is my code
public class BAMBOE {
public static void main(String[] args) {
BamboeRunner boe = new BamboeRunner();
boe.start();
import java.io.*;
public class BamboeRunner extends Thread implements Runnable {
public void run() {
try {
Process process = Runtime.getRuntime().exec("@SIMPEL");
process.waitFor();
return ;
catch (Exception e) {
e.printStackTrace();
return ;
}But I keep getting the following error:
java.io.IOException: Child creation error: error 100052
VMS error code: error 100052
at java.lang.UNIXProcess.<init>(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at BamboeRunner.run(Compiled Code)Anybody that can help me fix this problem please??I've managed to get somewhere with this...
I've got it to work by having the system command I want to run in a com file and specifying the full path to that file in the exec method without the '@'...
e.g.
Process proc = Runtime.getRuntime.exec("ppoi_dev:[user.dba_ppoi.matt.proc]proc.com");
where the file
ppoi_dev:[user.dba_ppoi.matt.proc]proc.com
contains
$ dir
When I run this I can get the output from the dir command by reading from the InputStream of the Process object.
Have fun. -
Unable to Log-in *SAP System Message : Error while reading a Dynpro*
Hi,
We are facing issues while logging-in through SAP logon 710.
The system throws an error dialog box with the below message:
SAP System Message : Error while reading a Dynpro
At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.Hi Please find the contents of std_server.out below.
stdout/stderr redirect
node name : server0
pid : 4124
system name : KEC
system nr. : 01
started at : Mon Jul 27 15:44:57 2009
[Thr 5656] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00 PatchLevel 110760.44 is starting...
Loading: LogManager ... 250 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 93 ms.
Loading: LockingManager ... 32 ms.
Loading: ConfigurationManager ... 1032 ms.
Loading: LicensingManager ... 0 ms.
Loading: CacheManager ... 93 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (16 ms).
Service cross started. (31 ms).
Service file started. (31 ms).
Service memory started. (31 ms).
Service timeout started. (16 ms).
Service trex.service started. (32 ms).
Service userstore started. (0 ms).
Service jmx_notification started. (15 ms).
Service p4 started. (62 ms).
Service classpath_resolver started. (16 ms).
Service deploy started. (3722 ms).
Service MigrationService started. (31 ms).
Service bimmrdeployer started. (0 ms).
Service log_configurator started. (5177 ms).
Service locking started. (0 ms).
Service http started. (126 ms).
Service naming started. (157 ms).
Service failover started. (16 ms).
Service appclient started. (31 ms).
Service javamail started. (47 ms).
Service ts started. (47 ms).
Service jmsconnector started. (47 ms).
Service licensing started. (15 ms).
Service connector started. (93 ms).
Service iiop started. (94 ms).
Service configuration started. (16 ms).
Service webservices started. (265 ms).
Service dbpool started. (1204 ms).
Service UT started. (0 ms).
Jul 27, 2009 3:45:09 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: " Error while reading a dynpro ". This message is critical if it appears during the startup of the AS Java.
Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Error while reading a dynpro
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Error while reading a dynpro
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Error while reading a dynpro
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Error while reading a dynpro
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 27, 2009 3:45:09 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Maybe you are looking for
-
I recently purchased an HP Deskjet 3050A All-In-One J611 series printer and it is not compatible with the version of the operating system on my mac book pro. I am currently running on OS X 10.4.11 and the printer is compatible with v10.5 or higher.
-
Optimize the following update on per_all_assignments_F
Hi I am trying to optimize this sql which is taking a long time to complete. declare cursor c1 is select person_id, annual_rt from xxdl.xxdl_papf_scrambling_view; begin for i in c1 loop update PER_ALL_ASSIGNMENTS_F set as_attribute4 = i.annual_rt whe
-
Delivering Error and Scheduling Error
I just wanna schedule a report, when I'v configured schedule, and click 'submit', the following error displayed: 'java.sql.SQLException: ORA-02289: sequence does not exist ' Same error occurred when I wanna deliver it to a printer which is already co
-
Down Payment Request Percentage affects tax
Hi Experts, I have an issue to be cleared in A/P Down Payment Invoice. Scenario: Purchase Order has a certain tax amount in addition to the total value. I try to add a A/P Down Payment invoice for this order. When the DPM is changed to a particul
-
Application crashes nearing 28 concurrent transactions
Its been a while folks.... I used to post and answer allot here back in the day when i was coding in CF daily. Here is the problem... more details will follow when I get them. I was tasked by my director to look into a problem for an application on t