Skip to Content

All (SMP 3.0/Agentry users),

SAP Digital Services, tries to be proactive by sharing the knowledge to all our customers before the need arises.

We would like to share the latest fixes that we have for SAP Mobile Platform 3.0. One of the reported issues is that the languages overrides or localization is not properly being picked up by the SMP 3.0 server.

With this report, we did some study on both development and production type of server and release the fix for it.

If you are using Agentry applications (Work Manager, Inventory Manager, Rounds, Service Manager and others) in SMP 3.0, this solution may be needed for your production deployment if you are using a non-English language (ex: French, German and others).

Please reference: SAP KBA # 2349360 – Agentry Language / Localization overrides (.ini) not being picked up by SMP 3.0 for more details.

We would like to thank all users/developers and community who have brought this to our attention so we may immediately release a fix for it. We value your feedback and support for our mobility products in the ERP/CRM world of SAP.

Best Regards,

Mark Pe
SAP Platinum Support Engineer

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Ranjith Lingala

    Hi Mark Pe,

    I am Transporting Work Manager 6.3 application in SMP 3.0 SP09, for that i have done all necessary changes and also it’s link up with SSO.
    For SSO also i did necessary changes, but after all the changes and restarting both the servers (instance1 and instance2 i.e because in production we have two nodes with Apache Load Balancing) i am getting below errors in Server log “XXXXXXXX-smp-server.log”
    2017 01 10 00:06:43#0-600#ERROR#com.sap.mobile.platform.server.agentry.console###Agentry Dev Def Load Loop Thread########Exception: 00:06:43 01/10/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user COMSMP – com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 20, ssf error= 25 – Signature couldn’t be verified (20) – Invalid password for signer (25)
    ),     at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:241)

    and under agentry “startup.log” we are getting below Exceptions.

    00:06:25 01/10/2017: Agentry Server Agent: Starting threads.
    00:06:25 01/10/2017:    1 initial threads.  Threads will auto-scale.
    00:06:25 01/10/2017: Agentry Server Agent: Adding messages.
    00:06:25 01/10/2017: Event: 1, 4, Agentry Server Agent v130.9.3.10
    00:06:25 01/10/2017: Loading agent from ag3.dll
    00:06:25 01/10/2017: Starting com.sap.wm63_ec41
    00:06:25 01/10/2017: com.sap.wm63_ec41: reading config file
    00:06:25 01/10/2017: Exception: 00:06:25 01/10/2017 : 27 (LocalizationException), Localization Exception (Skipping the ‘en’ localization because no matching override files were found.  ), agent\ChickamingAgent.cpp#3414:ChickamingAgent::initializeLocalizations
    00:06:27 01/10/2017: Event: 20, 150, Loading Development application definitions
    00:06:41 01/10/2017: Initializing HTTPXML-HTTPXMLSystemConnection from ag3httpxmlbe.dll
    00:06:41 01/10/2017: HTTPXMLSystemConnection: Reading configuration information.
    00:06:41 01/10/2017: HTTPXMLSystemConnection: Setting name to ‘HTTP-XML Back End’.
    00:06:41 01/10/2017: HTTP-XML Back End: Initialized.
    00:06:41 01/10/2017: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v130.9.3.10) from ag3httpxmlbe.dll
    00:06:41 01/10/2017: Initializing Java-SAPJavaConnection from ag3javabe.dll
    00:06:41 01/10/2017: SAPJavaConnection: Reading configuration information.
    00:06:41 01/10/2017: SAPJavaConnection: Setting name to ‘Java Back End’.
    00:06:41 01/10/2017: Java Back End: Initialized.
    00:06:41 01/10/2017: Java Back End: Java Virtual Machine already initialized.
    00:06:43 01/10/2017: Exception: 00:06:43 01/10/2017 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Could not login user COMSMP – com.syclo.sap.auth.sso.TicketVerifierException: MySapEvalLogonTicketEx failed: standard error= 20, ssf error= 25 – Signature couldn’t be verified (20) – Invalid password for signer (25)
    ),     at com.syclo.sap.auth.LoginModuleSSO.verifyTicket(LoginModuleSSO.java:241)

    00:06:43 01/10/2017: Failed to init Java Back End (Java v130.9.3.10) from ag3javabe.dll
    00:06:43 01/10/2017: Event: 20, 151, Application definitions failed to load.  Either the publish has not completed or there is a server misconfiguration.  Please check server log for details.
    00:06:44 01/10/2017: com.sap.wm63_ec41: Starting threads.
    00:06:44 01/10/2017:    1 initial threads.  Threads will auto-scale.
    00:06:44 01/10/2017: Event: 20, 4, com.sap.wm63_ec41 v130.9.3.10
    00:06:44 01/10/2017: Event: 0, 0, Old log files moved into D:\SAP\MobilePlatform3\Server\log\agentry\rolled\2017-01-10-000625
    00:06:44 01/10/2017: Event: 0, 23, Agentry startup is complete.

    Also i saw your thread “https://archive.sap.com/discussions/thread/3583730” in that u mentioned how to do delete/undo.

    In above thread your mentioned if we have one or more versions in Production so that will be delete latest one and re publish the application again as another version of application.

    But in my scenario, we are deploying the application very first time earlier we don’t have any apps into the server. So, how will resolve by above issues(errors/exception) if not how will remove the application completely which we have deployed into the server without taking any backup to deploy the application from the scratch again.

    Thanks,
    Ranjith Lingala

    (0) 
    1. Mark Pe Post author

      Ranjith,

      Hi. I believe you need to start a new thread as this Broadcast Resolution is tied to Localization fix.  If you are complaining about the SSO issue. This way we can help from SAP to further analyze your issue. If you are complaining about the localization you can also try to open a new thread but refer to this thread tied to the fix (if it did not fix your issue). You may notify my name again or do an @ symbol + name in your description so we can get notified. This way you own the question and we can drive experts to answer it.

      Best Regards,
      Mark Pe – SAP Platinum Support Engineer

      (1) 

Leave a Reply