on 11-09-2015 7:52 AM
Setting of time zone described in the note #2116194 is performed.
Time zone in the Transaction code: STZAC is active
As Agentry.ini is no longer used, we set the time zone value the Management Cockpit.
In the Application SAPWM62 section Back END - JAVA-1
and HTTPXML-2
The text for Time Zone Name is taken from RegEdit
Microsof -> WindowsNT -> Time Zones -> Russian Standard Time
Value Name - Display
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Retesting showed
that at the first attempt to open file the Work Manager opens a small window in the upper right corner,
but it is closed immediately, so it is not clear what information it displays.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Konstantin,
This error is also caused by a mismatch in time zone. The story is, if your client (mobile device) transmits it's data will be presented to SMP 3.0 to present it to SAP. If there is a discrepancy with time, the SAP backend will think that the request is old and there is no reason to push the document to the device.
Please see if it is related to:
http://service.sap.com/sap/support/notes/2116194 (Also available in the same Troubleshooting attach document link Resmi provided above and it is #11).
The link above shows that you need to make sure of the time zone difference between where you installed SMP 3.0 and what it looks like in SAP. You may need to review the registry key on the time zone format and add this in your Agentry.ini (under [Java-1] setting timeZoneName). For details see the link 2116194.
Hope this helps,
Mark Pe
SAP Platinum Support Engineer (Mobility)
I performed all the recomindations described in the KBA 2116194.
Mobile application for SMP is unlocked.
Time zone is the same on the Client, SMP Server and SAP ERP
SAP Time Zone is active in Transaction code: STZAC.
Time zone is filled in SAP Management Cockpit for Application SAPWM62
The simptoms are the same as it desribed in the KBA 2116194.
There are no errors in the startup.log or events.log files
Lost records in the BDV-VP7-PC-smp-server.log file is
2015 11 13 17:52:01#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###closeConnection::begin |
2015 11 13 17:52:01#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###endStatefulConnection::begin |
2015 11 13 17:52:01#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###endDestination::begin |
2015 11 13 17:52:01#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###endJcoSession::begin |
2015 11 13 17:52:01#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###com.syclo.sap.workmanager.PushUserSession::endEnablePush::::-------------------------------- |
Konstantin,
Hi. One way to debug further is to use the /SYCLO/Admin to look at the Push Monitoring area to see if you have each of your pushes completed and at the same time canceled. The trick is to see if your push gave enough time to push the said document to the device. There is a push timer normally set at somewhere around 30 seconds to do the work. If your push requires more time you can adjust this time. It is known to fix download documents. I may need to find the KBA that explains it (with pictures).
Best Regards,
SAP Mobile Support Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I applied the recommendations described in the note 2169241.
So I recreated Work Manager Server zip files with
[PUSH_LOGON]
ENABLED=true
I recreated Work Manager in SMP.
Restarted SMP.
It doesn't help.
The simptoms are the same.
In the BDV-VP7-PC-smp-server.log There is the last entry:
-----
2015 11 10 18:10:25#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###release::begin |
2015 11 10 18:10:25#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###closeConnection::begin |
2015 11 10 18:10:25#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###endStatefulConnection::begin |
2015 11 10 18:10:25#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###endDestination::begin |
2015 11 10 18:10:25#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###endJcoSession::begin |
2015 11 10 18:10:25#+0300#INFO#System.out##anonymous#Agentry SAPWM62 Worker Thread###com.syclo.sap.workmanager.PushUserSession::endEnablePush::::-------------------------------- |
2015 11 10 18:11:15#+0300#INFO#System.out##anonymous#Thread-7905###Session timer for user: DBOLSHAKOV ending. Session locked: false Cancelled: true |
2015 11 10 18:11:24#+0300#INFO#System.out##anonymous#Thread-8076###Session timer for user: DBOLSHAKOV ending. Session locked: false Cancelled: true |
------
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.