This topic lists common error message and their corresponding solutions.
The error or fault responses from Tally.NET Server are received in the following XML format:
<ENVELOPE>
<HEADER>
<VERSION>1</VERSION>
<STATUS>1</STATUS>
</HEADER>
<BODY>
<DATA>
<STATUS>
<CODE>15004</CODE>
<MSG.LIST>
<MSG>Invalid Request</MSG>
</MSG.LIST>
</STATUS>
</DATA>
</BODY>
</ENVELOPE>
|
# |
Error Code |
Error |
Description |
|
1 |
2013 |
Invalid Tally.NET ID or Password. |
Provide correct username and password in TPAuthenticateUser request. |
|
2 |
15002 |
Invalid request. |
Tally.NET Server is not able to identify the request. Contact Tally Solutions Pvt. Ltd. with request XML. |
|
3 |
15005 |
Invalid request. |
Tally.NET Server is not able to process the request. This could be because of the request format mismatch. Tally.NET Server expects requests to be in UTF-16 (Unicode) and Little Endian format. |
|
4 |
16001 |
Request cannot be served, please try later. |
Tally.NET Server internal error. This happens only when the server is not available at the time. This issue does not occur in a live scenario. |
|
5 |
16010 |
Request cannot be served, please try later. |
Tally.NET Server internal communication error. This happens only when the authentication server is busy. Retrial is suggested. |
|
6 |
16027 |
Invalid Session. |
Token is not incremented properly for each request, or the SessionID sent in the TPAuthenticateUser is invalid. |
|
7 |
16032 |
Company is currently not connected with Tally.NET Server. |
The expected company from Tally.ERP 9 is not connected to Tally.NET Server. Connect valid companies from Tally.ERP 9. |
|
8 |
16063 |
You have exceeded the Tally.NET user session limit. |
Logout from the existing Tally.NET user session. |
If the editor—eclipse, xcode—displays an error, clean the project.
