- SAP Community
- Products and Technology
- Additional Q&A
- GRC RAR Background Job throws errors
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
GRC RAR Background Job throws errors
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 02-23-2011 11:16 AM
Hi,
I am configuring RAR on AC53 SP13 with latest patches with ECC-Sandbox and ECC-DEV system:
ERROR 1:
-Error-Management report background job completed 100%, but showing error in log report.
-Find Attached Job ID:45 log report: Sandbox_Management_Report_Error.txt
Steps:
-I created a connector in configuration-connectors tab for ECC-Sandbox.
-I created a logical system for sandbox system-.
-Uploaded-static and object data and all rule upload files successfully.
-I run generate rules from configuration->logical systems->Generate Rules successfully.
-I scheduled background jobs successfully for User/Role/Profile-Full Synchronization and Batch risk Analysis.
-Error-Management report background job completed 100%, but showing error in log report.
ERROR 2:
-Error-When I schedule Batch User/Role/Profile Risk Analysis Full-sync background job, Role, Profile and Critical Action risk analysis completed successfully, but User Risk Analysis shows ERRORS.
-Find Attached Job ID:43 log file. DEVbox_Batch_Risk_Analysis_User_FullSync.txt
-I added new connector for ECC-DEV system and not created logical system for DEV.
-uploaded-static and object data and function authorization files upload files successfully.
-I run generate rules from Configuration-Rule Upload- Generate Rules successfully.
-I changed User Master Source to ECC-DEV system.
??-I observed in Rule Architect->Rule Library ->Number of Active Rules are Double in number of initially exists (i.e. 64,831*2=1,29,662). Is it correct?
-I scheduled background job for User/Role/Profile-Full Synchronization success fully.
-Error-When I schedule Batch User/Role/Profile Risk Analysis Full-sync background job. Role, Profile and Critical Action risk analysis completed successfully, but User Risk Analysis shows ERRORS.
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
1. Please check the performence settings and set "No" value for the option "Use Net Weaver Logical Lock Yes/No? before scheduling the job. finally switched "YES" after completed batch jobs.
2. Check the Daemon Manager status- the workthreads are runnig on all server nodes after scheduling batch jobs.
Regards,
Arjuna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Thanks for your sugesstion,
i changed to NO state and restarted the server. i again run the background job for the USER RISK ANALYSIS under Batch Risk Analysis in Full SYnc mode give same error. the Analysis is completing upto 79% and reset showing errors.
-User/role/profile data Sync successfully
-Batch risk ananlysis on Role/Profile analysis completed successfully.
Only user risk analysis throwing error...
Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
DEVbox_Batch_Risk_Analysis_User_FullSync:
Feb 22, 2011 2:21:13 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1005
Feb 22, 2011 2:21:13 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1005
Feb 22, 2011 2:21:13 PM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IUserListInputElement.wdGetObject(IPublicBackendAccessInterface.java)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
at com.virsa.cc.comp.BackendAccessInterface.searchUser(BackendAccessInterface.java:761)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.searchUser(InternalBackendAccessInterface.java:4279)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.searchUser(InternalBackendAccessInterface.java:4748)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchUser(DataExtractorSAP.java:548)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.userIsIgnored(DataExtractorSAP.java:529)
at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:702)
at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:121)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1493)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:318)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1347)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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:1060)
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)
Feb 22, 2011 2:21:14 PM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthChgUserInputElement.wdGetObject(IPublicBackendAccessInterface.java)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedUsers(BackendAccessInterface.java:3674)
at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedUsers(BackendAccessInterface.java:3664)
at com.virsa.cc.comp.BackendAccessInterface.getObjDetails(BackendAccessInterface.java:1425)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.getObjDetails(InternalBackendAccessInterface.java:4327)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.getObjDetails(InternalBackendAccessInterface.java:4796)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjDetails(DataExtractorSAP.java:630)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.getObjInfoFromSource(AnalysisEngine.java:4527)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1846)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:318)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1347)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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:1060)
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)
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:43 : Analysis done: JENNIFERT elapsed time: 529 ms
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 43 Status: Running
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 43 Status: Running
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Detailed Analysis Time:
Risk Analysis Time: Started @:Tue Feb 22 14:21:11 PST 2011
Rule Load Time: Started @:Tue Feb 22 14:21:11 PST 2011
Rule Load Time:2460millisec
Org Rule Loop Time: Started @:Tue Feb 22 14:21:13 PST 2011
Rule Loop Time: Started @:Tue Feb 22 14:21:13 PST 2011
Rule Loop Time:302millisec
Org Rule Loop Time:302millisec
Risk Analysis Time:3011millisec
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
INFO: Job ID:43 : Exec Risk Analysis
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:43 : Before Rules loading, elapsed time: 1 ms
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:43 : Analysis starts: 105030146
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1005
Feb 22, 2011 2:21:14 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1005
Feb 22, 2011 2:21:14 PM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Sandbox_Management_Report_Error:
Feb 22, 2011 2:47:25 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 22, 2011 2:47:25 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_UC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_UC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 46
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_UC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_UC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 46
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_UC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_UC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 46
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_UC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_UC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 46
Feb 22, 2011 2:47:25 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 22, 2011 2:47:25 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 22, 2011 2:47:25 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 22, 2011 2:47:25 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_NUC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_NUC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 48
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_NUC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_NUC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 48
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_NUC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_NUC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 48
Feb 22, 2011 2:47:25 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
INFO: Exception in Server SLD_NUC:
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Feb 22 14:47:25 PST 2011.
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=SLD_NUC GWHOST=sapr3001.psamer.ps.ge.com GWSERV=54200
ERROR internal error
(this retcode should be handled by caller of NI-layer)
TIME Tue Feb 22 14:47:25 201
RELEASE 701
COMPONENT NI (network interface)
VERSION 38
RC -7
MODULE gwxx_mt.c
LINE 480
DETAIL NiIRead: hdl 10 buffer too small (636<1213485524)
SYSTEM CALL NiRead
COUNTER 48
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Unify your process and task mining insights: How SAP UEM by Knoa integrates with SAP Signavio in Technology Blogs by SAP
- Cloud Integration: Manually Sign / Verify XML payload based on XML Signature Standard in Technology Blogs by SAP
- developer studio 7.31 configure external libraries not coming, throwing error in eclipse in Enterprise Resource Planning Blogs by Members
- VSCode Fiori Application Wizard throwing invalid version error in Technology Q&A
- Converting a custom tcodes output into Local File throws runtime error in Enterprise Resource Planning Q&A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.