General
The response to failed request
Error message categories
General instructions when error messages occur
General
Send one message at a time and wait for Netvisor's Web Service Interface to respond before you send the next message. Overlapping messages to the same customer environment cause different errors. We recommend that the timeout for messages is at least 120 000 ms. This helps in avoiding unnecessary errors.
Log and follow Web Service Interface traffic, including errors. The requests should be recorded transaction based. If the Web Service Interface does not respond it is recommended that you try to send the message a few times and then take a longer break. Controlling errors should be done in the external system and the error description received from Netvisor's Web Service Interface should be saved and shown as it is.
If you need help in interpreting error messages you can contact our partner support in tuki.netvisor@visma.com.
The response to failed request
If there are errors in handling the request, the Web Service Interface returns <Status>FAILED</Status> in ResponseStatus-element. Here's an example of a response to a failed request:
<Root>
<ResponseStatus>
<Status>FAILED</Status>
<Status> AUTHENTICATION_FAILED :: Integration keys are not valid. Please check the keys specific to the user and partner.</Status>
<TimeStamp>01.01.2018 12:00:00</TimeStamp>
</ResponseStatus>
</Root>
Error message categories
AUTHENTICATION_FAILED
Authentication of the request failed. Check the credentials, HTTP-headers and MAC-calculation.
INVALID_DATA, INVALID_DATA_SIZE
The sent data is invalid or of wrong size. Check the material and given parameters.
DUPLICATE_DATA
The sent data already exists in Netvisor. Check the material and given parameters.
REQUEST_NOT_UNIQUE
The transaction ID has already been used. The ID must change in every request.
PERIOD_LOCK
The accounting period is locked and material can not be imported before opening the period in Netvisor.
SERVICE_ACCESS_ERROR
No access rights or the application where the material is imported/retreived is not in use.
SYSTEM_MAINTENANCE
System is under maintenance. During maintenance requstes can not be made.
TECHNICAL_ERROR
Other error caused by a technical error. The response message returns only error category and error identifier without any further explanation. Technical errors should also be logged. Using the error identifier our partner support and maintenance can help in figuring out the error.
General instructions when error messages occur
INVALID_DATA
Please read the more detailed description of the error from the error message.
Make sure the syntax is correct:
- The given elements are in the same order as in the resource DTD.
- All compulsory elements are given.
- All compulsory elements have a value.
- All tags have a counterpart.
a) Importing working hours:
INVALID_DATA :: Data form incorrect:. Entry type not found with given allocation data.
An entry type with the same number as the collector ratio number is needed (e.g. <CollectorRatio type="number">123</CollectorRatio> -> add an entry type with number 123). The entry types can be added in Netvisor UI and instructions in Finnish can be found here. When working hours are imported, check the entry types forms so that the hours will appear on the pay slip. This should always be tested in the test environment.
b) Importing sales invoices:
INVALID_DATA :: Data form incorrect:. VAT code cannot be retrieved from posting suggestion because no posting suggestion has been given.
The error appears because VAT code is not given in the invoice row. When the VAT code is not given, the system tries to find VAT code from the account suggested in the element accountingAccountSuggestion. When no account is given in that element, an error is returned. VAT code should always be given in the invoice row. Also note that the VAT percentage should also be given.
AUTHENTICATION_FAILED
AUTHENTICATION_FAILED :: Integraatioavaimet eivät kelpaa. Ole hyvä ja tarkista käyttäjä- ja kumppanikohtaiset avaimet.
AUTHENTICATION_FAILED :: Integration keys are not valid. Please check the keys specific to the user and partner.
a) The user (userID) given in HTTP-header 'X-Netvisor-Authentication-CustomerId' does not exsist or is not active.
b) The partner (partnerID) given in HTTP-header 'X-Netvisor-Authentication-PartnerId' is not found.
SERVICE_ERROR
SERVICE_ACCESS_ERROR :: Palveluvirhe. Yritys on estänyt pääsyn rajapintaresurssiin: X
SERVICE_ACCESS_ERROR :: Service error. The company has restricted access to the interface resource: X
The API interface resource 'X' mentioned in the error message is not allowed in Netvisor, enable the API interface resource as instructed
TECHNICAL_ERROR
TECHNICAL_ERROR :: Error when handling material:. Error identifier: 00001
An error in handling material caused by some other technical error. Contact partner support (tuki.netvisor@visma.com) for help in solving the error.
Tunnistautuminen epäonnistui
Company not found or no access granted. See documentation. This error is returned when the user doesn't have access right to target company's Netvisor environment or the company is no longer active in Netvisor. In this case, make sure if the user has access rights to target company's Netvisor environment and if the company is still active in Netvisor.
Did you find it helpful? Yes No
Send feedback