on 10-08-2015 2:42 PM
Hi All
When I try to pass confirmed hours from SAP Work Manager to the SAP the system shows next error.
--
Logging user into server
Logged in
Sending client info
Sending time info...
Receiving time info...
Sending OperationEdit...
Sending LaborAdd...
LaborAddSteplet - Actual date(s) is in the future (check parameters)
Server error - please contact your administrator (13)
Logging user out
--
Date-Time on Client, SMP Server and in the SAP Server is same and correct.
Time zone and daylight saving time is the same and correct.
I set the work time in the past.
But it works inly when the time is set to yesterday or earlier.
In the file
C:\SAP\MobilePlatform3\Server\log\agentry\events.log
I found next lines
---
10/16/2015 14:49:46, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini
10/16/2015 14:49:46, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini
10/16/2015 14:49:48, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini
10/16/2015 14:49:48, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini
10/16/2015 14:51:45, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini
10/16/2015 14:51:45, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini
10/16/2015 14:54:53, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini
10/16/2015 14:54:53, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini
10/16/2015 14:54:54, 1, 20, 26, Thr 4616, com.syclo.agentry.BusinessLogicException: Measurement time cannot be in the future
---
What it could be? I don't have Agentry.ini file on the SMP Server Computer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the Timezone Aliases section is now in the SMP Cockpit in the application
You can see the wiki about how the section needs to be set: Set Up Time Zone Alias in Agentry.ini Configuration File - SAP Mobility - SCN Wiki
Konstantin,
Please make sure you have maintained same time zone in SAP (SU01) as well as in Agentry. To set timezone in Agentry you can use management cockpit..
In Management cockpit select your application and go to backend tab. there you can set this. (Java section or HTTP/XML section)
After setting these values make sure to restart Agentry instance(or SMP server).
Thanks
Ajitesh
I set Time Zone Name In Management cockpit (Java section or HTTP/XML section) and restarted SMP.
It doesn't help.
The error is still the same.
It tested next values for "Time Zone Name"
- (UTC+03:00) Moscow, St. Petersburg, Volgograd (RTZ 2)
- (UTC+03:00)
- MSK
If any of these values, the problem persists.
How can I check that entered value is correct and accepted by the server correctly?
The "Time Zone Name" field accepts any abracadabra value.
The client doesn't pull the Sap user time zone. In the Events.log file are you still getting:
Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.in
If yes. This shows the server doesn't understand the timezone (RTZ 2 (зима) ) and will need to be added to the timezone aliases section that looks like:
RTZ 2 (зима)=<System timezone name that matches>
If the server doesn't understand the timezone the client is getting, it will not be able to convert the time time to match the server. Set Up Time Zone Alias in Agentry.ini Configuration File - SAP Mobility - SCN Wiki
Agentry.ini file will not be there if you are using production version of application. Every configuration needs to be done in management cockpit itself.
Please make sure all the time zone is same. I can see you have maintained RUS03 timezone in SAP but in SMP it is UTC-3. Please modify this timezone to RUS03. also try to set your mobile's timezone to RUS03.
Thanks
Ajitesh
In the SAP Management Cockpit
Application
SAPWM62
APP SPECIFIC SETTINGS
Time Zone Aliases
I put next line
--
RTZ 2 (зима)=(GMT+03:00)
--
Now On Transfer Data SMP write next error in the events.log
10/20/2015 18:42:20, 0, 17, 10, Thr 5412, SAPWM62 v130.7.0.4
10/20/2015 18:42:55, 0, 20, 16, Thr 4828, Threads in thread pool 'SAPWM62' expanded to 2. Adding thread 4412
10/20/2015 18:42:55, 0, 20, 154, Thr 4412, Client Time Zone '(GMT+03:00)' alias was not found in TimeZoneAliases in Agentry.ini
10/20/2015 18:42:55, 0, 20, 154, Thr 4412, Client Time Zone '(GMT+03:00)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini
10/20/2015 18:42:56, 1, 20, 26, Thr 4412, com.syclo.agentry.BusinessLogicException: Measurement time cannot be in the future
Measurement time cannot be in the future
Next variants
RTZ 2 (зима)=(GMT+03:00)
RTZ 2 (зима)=MSK
RTZ 2 (зима)=Russia TZ 2 Standard Time
RTZ 2 (зима)=RUS03
don't work
Last error is
10/20/2015 19:06:35, 0, 20, 154, Thr 3420, Client Time Zone 'RUS03' alias was not found in TimeZoneAliases in Agentry.ini
10/20/2015 19:06:35, 0, 20, 154, Thr 3420, Client Time Zone 'RUS03' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini
at least you get this :
LaborAddSteplet - Actual date(s) is in the future (check parameters)
Server error - please contact your administrator (13)
we are just getting :
Server error - please contact your administrator (13)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Experts,
I am also facing same Issue. I did changes in SMP Application backend
Time Zone=(UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.
But getting same error on first transmit. But after transmitting 2-3 times it get transmitted successfully. This scenario happens with all operations.
So where exactly we are missing???
Thanks & Regards,
Ashish Sarode
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Konstantin Kulikov ,
This is general issue, when SMP server & SAP Servers are located in different time zone. To resolve this issue, maintain the time zone in tcode SU01. Refer the following screen shot.
Hope this will help you.
Regards,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See at SAP note:
"0002185367 SAP Work Manager error on transmit - AddLaborTime - Actual date(s) is in the future”
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Konstantin,
which version of work manger you are using and on which client r u testing?
Also try to add the proper timezone parameter in the Agentry.ini file
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.