Real Time Automation, Inc.
92
1-800-249-1612
Common Error Messages:
The error message will alert if the message is for an XML or a JSON message. It will also indicate which
line (x) and column (y) of the encoded data message contained the error and the reason why it triggered
an error. Typically, the error message will als
o be followed by the client’s IP address.
1)
Server Error Strings
a)
Parsing Errors
i)
[XML/JSON] Parser (line: X col: Y): Invalid DEVICE Name
ii)
[XML/JSON] Parser (line: X col: Y): Invalid POINT Name
iii)
[XML/JSON] Parser (line: X col: Y): Over/Underflow for POINT Data
iv)
[XML/JSON] Parser (line: X col: Y): Invalid Data type for POINT
v)
[XML/JSON] Parser (line: X col: Y): [XML/JSON] Formatting Error
vi)
Invalid [XML/JSON] File Post Procedure
b)
Internal Errors
–
Should rarely see and indicated a major problem in the gateway
i)
[XML/JSON] Output I/O Failure
ii)
[XML/JSON] Output Buffer Overflow
iii)
Internal POST Error (500)
c)
HTTP Errors
i)
Error 404: URL Invalid.
d)
URL-Encoded POSTs
–
Will show “Invalid Post Attempt” followed by one of the following:
i)
POST to invalid Device: [Device Name]
ii)
Failed Write (Invalid Point Name) to [Device Name]
iii)
Failed Write (Overflow) to [Device Name] : [Point Name]
iv)
Failed Write (Invalid Data Type) to [Device Name] : [Point Name]
2)
Client Error Strings
a)
HTTP Client Post rejected by server. Responded: xxx (xxx is an HTTP status other than 200)
b)
HTTP Client: Invalid Socket
c)
HTTP Client: Socket Closed
d)
HTTP Client: Socket Read Failed
e)
HTTP Client: Socket Read Timeout
f)
HTTP Client: Cannot Resolve Host
g)
HTTP Client: Cannot Connect
h)
HTTP Client: Invalid URL
i)
HTTP Client: Invalid Response
j)
HTTP Client: Proxy xxx
