on 01-03-2016 2:37 PM
Hello Experts,
We are using Work Manager 6.2 with Customer Service component.
We are able to send our documents and pictures into SAP from client devices.
But when we try to see an attachment inside the client devices, push is not working.
Error what we get is : DocumentPushRequestSteplet /SYCLO/CX_CORE_SUBQUEUE_MGR: :Invalid push scenario id SWM62_BDS_DOCUMENT_PUSH for mobile app SAP_CUSTOMER_SERVICE_21 .
On the error above; it shows the wrong push scenerio id since we use Customer Service; our push scenerio is "SCS21_BDS_DOCUMENT_PUSH" which comes with standard configuration.
I have checked all related configuration and all seems ok.
Anyone can help me how it gets the wrong push scenerio id ?
Best Regards;
Gokhan
Hi Gokhan,
Could you please attach the SMP server log and Agentry event log?
Best Regards,
Charlie
SAP Product Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Charlie,
Thanks for the reply,
I am sending you the SMP server log and Agentry Event Log.
On the SMP server Log only this is turkish because of our Localization : "/SYCLO/CX_CORE_SUBQUEUE_MGR:Mobil uygulama SAP_CUSTOMER_SERVICE_21 için geçersiz push senaryosu tanıtıcısı SWM62_BDS_DOCUMENT_PUSH"
which means : "/SYCLO/CX_CORE_SUBQUEUE_MGR::Invalid push scenario id SWM62_BDS_DOCUMENT_PUSH for mobile app SAP_CUSTOMER_SERVICE_21 ."
SMP Server Log ;
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########setParameters::DocumentPushRequest Call Time=20160104114913 |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########setParameters::BEGIN_TS=20160104114913 |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########setParameters::VALIDITY=8 |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########execute::::GZMBKM1::before BAPI execute: /SYCLO/CORE_SUB_REQ_CRT |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########execute::begin |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########validateDestination::begin |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########execute::::GZMBKM1::after BAPI execute: /SYCLO/CORE_SUB_REQ_CRT |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########checkForErrors::1::message ID::E:: - 000 |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########checkForErrors::1::message::E::04.01.2016 11:49:13 - /SYCLO/CX_CORE_SUBQUEUE_MGR:Mobil uygulama SAP_CUSTOMER_SERVICE_21 için geçersiz push senaryosu tanıtıcısı SWM62_BDS_DOCUMENT_PUSH |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########User::rethrowException::begin |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########User::rethrowException::Exception caught: 04.01.2016 11:49:13 - /SYCLO/CX_CORE_SUBQUEUE_MGR:Mobil uygulama SAP_CUSTOMER_SERVICE_21 için geçersiz push senaryosu tanıtıcısı SWM62_BDS_DOCUMENT_PUSH |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########User::rethrowException::COM.SYCLO.AGENTRY.AGENTRYEXCEPTION: 04.01.2016 11:49:13 - /SYCLO/CX_CORE_SUBQUEUE_MGR:MOBIL UYGULAMA SAP_CUSTOMER_SERVICE_21 IÇIN GEÇERSIZ PUSH SENARYOSU TANITICISI SWM62_BDS_DOCUMENT_PUSH |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.BAPI.BAPIERRORHANDLER.INIT(BAPIERRORHANDLER.JAVA:76) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.BAPI.BAPIERRORHANDLER.<INIT>(BAPIERRORHANDLER.JAVA:48) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.BAPI.BAPI.CHECKFORERRORS(BAPI.JAVA:370) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.BAPI.BAPI.RUN(BAPI.JAVA:239) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.COMPONENT.DOCUMENTMANAGEMENT.STEPHANDLER.DOCUMENTPUSHREQUESTSTEPHANDLER.RUN(DOCUMENTPUSHREQUESTSTEPHANDLER.JAVA:46) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.COMPONENT.DOCUMENTMANAGEMENT.STEPLET.DOCUMENTPUSHREQUESTSTEPLET.EXECUTE(DOCUMENTPUSHREQUESTSTEPLET.JAVA:71) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## AT COM.SYCLO.SAP.STEPLET.DOSTEPLET(STEPLET.JAVA:169) |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########throwExceptionToClient::begin |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread########throwExceptionToClient::com.syclo.sap.component.documentmanagement.steplet.DocumentPushRequestSteplet::throwExceptionToClient::2506::DocumentPushRequestSteplet - 04.01.2016 11:49:13 - /SYCLO/CX_CORE_SUBQUEUE_MGR:Mobil uygulama SAP_CUSTOMER_SERVICE_21 için geçersiz push senaryosu tanıtıcısı SWM62_BDS_DOCUMENT_PUSH |
2016 01 04 11:49:13#+0200#INFO#System.out###Agentry LODOSQ Worker Thread######## |
2016 01 04 11:49:13#+0200#ERROR#System.err###Agentry LODOSQ Worker Thread########com.syclo.agentry.BusinessLogicException: 04.01.2016 11:49:13 - /SYCLO/CX_CORE_SUBQUEUE_MGR:Mobil uygulama SAP_CUSTOMER_SERVICE_21 için geçersiz push senaryosu tanıtıcısı SWM62_BDS_DOCUMENT_PUSH |
2016 01 04 11:49:13#+0200#ERROR#System.err###Agentry LODOSQ Worker Thread######## |
2016 01 04 11:49:13#+0200#ERROR#System.err###Agentry LODOSQ Worker Thread######## at com.syclo.sap.User.rethrowException(User.java:1128) |
2016 01 04 11:49:13#+0200#ERROR#System.err###Agentry LODOSQ Worker Thread######## at com.syclo.sap.component.documentmanagement.stephandler.DocumentPushRequestStepHandler.run(DocumentPushRequestStepHandler.java:52) |
2016 01 04 11:49:13#+0200#ERROR#System.err###Agentry LODOSQ Worker Thread######## at com.syclo.sap.component.documentmanagement.steplet.DocumentPushRequestSteplet.execute(DocumentPushRequestSteplet.java:71) |
2016 01 04 11:49:13#+0200#ERROR#System.err###Agentry LODOSQ Worker Thread######## at com.syclo.sap.Steplet.doSteplet(Steplet.java:169) |
2016 01 04 11:49:13#+0200#ERROR#com.sap.mobile.platform.server.agentry.console###Agentry LODOSQ Worker Thread########Exception: 11:49:13 01/04/2016 : 20 (Agentry3), Java Business Logic Error (com.syclo.agentry.BusinessLogicException: DocumentPushRequestSteplet - 04.01.2016 11:49:13 - /SYCLO/CX_CORE_SUBQUEUE_MGR:Mobil uygulama SAP_CUSTOMER_SERVICE_21 için geçersiz push senaryosu tanıtıcısı SWM62_BDS_DOCUMENT_PUSH), |
Agentry Event Log;
01/04/2016 12:01:48, 0, 0, 0, Thr 5472, New files opened events.log, messages.log
01/04/2016 12:01:48, 0, 0, 2, Thr 5472, Loading the Agentry Runtime's public/private key for password exchanges.
01/04/2016 12:01:48, 0, 0, 2, Thr 5472, Key pair loaded successfully.
01/04/2016 12:01:48, 0, 0, 2, Thr 5472, Agentry Startup
01/04/2016 12:01:48, 0, 1, 4, Thr 5472, Agentry Server Agent v130.9.0.3
01/04/2016 12:01:48, 0, 20, 4, Thr 5472, DEMO3 v130.9.0.3
01/04/2016 12:01:48, 0, 21, 4, Thr 5472, LODOSQ v130.9.0.3
01/04/2016 12:01:48, 0, 0, 0, Thr 5472, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2016-01-04-120142
01/04/2016 12:01:48, 0, 0, 23, Thr 5472, Agentry startup is complete.
01/04/2016 12:01:57, 0, 20, 5, Thr 5472, DEMO3
01/04/2016 12:01:57, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-0-app"
01/04/2016 12:01:57, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:02:29, 0, 24, 4, Thr 3620, Loaded HTTP-XML Back End (HTTPXML v130.9.0.3) from ag3httpxmlbe.dll
01/04/2016 12:02:35, 0, 23, 4, Thr 3620, Loaded Java Back End (Java v130.9.0.3) from ag3javabe.dll
01/04/2016 12:02:38, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:02:38, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
01/04/2016 12:02:38, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-10-app"
01/04/2016 12:02:38, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:03:00, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:03:00, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-10-app"
01/04/2016 12:03:00, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-11-app"
01/04/2016 12:03:00, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:03:15, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:03:15, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-11-app"
01/04/2016 12:03:15, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-12-app"
01/04/2016 12:03:15, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:03:31, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:03:31, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-12-app"
01/04/2016 12:03:31, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-13-app"
01/04/2016 12:03:31, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:03:45, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:03:45, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-13-app"
01/04/2016 12:03:45, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-14-app"
01/04/2016 12:03:45, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:03:59, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:03:59, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-14-app"
01/04/2016 12:03:59, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-15-app"
01/04/2016 12:03:59, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:04:15, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:04:15, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-15-app"
01/04/2016 12:04:15, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-16-app"
01/04/2016 12:04:15, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:04:30, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:04:30, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-16-app"
01/04/2016 12:04:30, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-18-app"
01/04/2016 12:04:30, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
01/04/2016 12:04:44, 0, 20, 153, Thr 3620, Finished loading Production application definitions for default localization
01/04/2016 12:04:44, 0, 20, 151, Thr 3620, Finished loading Production application definitions using file "SAPWM-v1-0-18-app"
01/04/2016 12:04:44, 0, 20, 150, Thr 3620, Loading Production application definitions using file "SAPWM-v1-0-19-app"
01/04/2016 12:04:44, 0, 20, 152, Thr 3620, Loading Production application definitions for default localization
Best Regards,
Gokhan
Hi Gokhan,
Please review the SAP Note -
2013399 - DocumentPushRequest Steplet Invalid Push Scenario ID :
http://service.sap.com/sap/support/notes/2013399
Cheers,
Stephen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.