Problem Note 63049: "ERROR: The specified timestamp is not valid..." occurs when you read data from a PICOMP table under Linux and UNIX
 |  |  |  |  |
Under the following conditions, SAS/ACCESS® Interface to the PI System fails to read data from the PICOMP table:
- You use Linux or UNIX.
- You use SAS/ACCESS Interface to the PI System via the PI web application programming interface (API).
- Your time zone is GMT + hour, where hour is greater than 0.
In this scenario, you see the following error message:
ERROR: SASPIWEB(restAPIGet): GET request failed. Status code was 400 - Bad Request
ERROR: HTTP Status 400: Unknown HTTP error.
ERROR: Unable to execute request:
ERROR: The specified timestamp is not valid. If more details are needed, please contact your PI Web API administrator for help in enabling debug mode.
ERROR: The START= and END= options must use the regional date/time format configured in your PC's Control Panel and NOT in a SAS date or time format. For example: "mm/dd/yyyy hh:mm:ss" (US) or "dd.mm.yyyy hh:mm:ss" (Germany) or "dd/mm/yyyy hh:mm:ss"(France), etc. The time part ("hh:mm:ss") is optional.
ERROR: Access to tag (PI Point) failed.
ERROR: HTTP Status 400: Unknown HTTP error.
ERROR: Unable to execute request:
ERROR: The specified timestamp is not valid. If more details are needed, please contact your PI Web API administrator for help in enabling debug mode.
ERROR: The START= and END= options must use the regional date/time format configured in your PC's Control Panel and NOT in a SAS date or time format. For example: "mm/dd/yyyy hh:mm:ss" (US) or "dd.mm.yyyy hh:mm:ss" (Germany) or "dd/mm/yyyy hh:mm:ss"(France), etc. The time part ("hh:mm:ss") is optional.
ERROR: Access to tag (PI Point) failed.
The issue is caused by a time stamp that indicates the earliest possible time ("1970-01-01T00:00:01") in the local time zone format being passed in. The issue arises when this time is converted to GMT in the web API in a time zone with a positive GMT offset (for example, GMT+2 in Norway). This conversion results in a GMT time of Dec 31, 1969, which is invalid.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to the PI System | 64-bit Enabled AIX | 9.4 TS1M5 | 9.4 TS1M6 |
| 64-bit Enabled Solaris | 9.4 TS1M5 | 9.4 TS1M6 | ||
| HP-UX IPF | 9.4 TS1M5 | 9.4 TS1M6 | ||
| Linux for x64 | 9.4 TS1M5 | 9.4 TS1M6 | ||
| Solaris for x64 | 9.4 TS1M5 | 9.4 TS1M6 | ||
| Microsoft® Windows® for x64 | 9.4 TS1M6 | 9.4 TS1M6 | ||
A fix for this issue for SAS/ACCESS Interface to the PI System 9.43 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D3W.html#63049
When using SAS/ACCESS® Interface to the PI System to read data from the PICOMP table, you might see the following message: "ERROR...GET request failed. Status code was 400 - Bad Request...HTTP Status 400...Unable to execute request...The specified timestamp is not valid..."
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-01-03 09:13:21 |
| Date Created: | 2018-10-09 23:31:42 |