...
Successful request and response means that the operation was successful. For an explanation about the responses for the various operations in the api, see the one description of
...
Generate document describes the various operations for generating dokuments
...
Post Processing contains operations that are often used after a generate document, generate<TYPE>
.
...
Monitoring events is the preferred way to check for changes in data.
...
the operation.
For the generate<TYPE>
(Generate document) operations, note that even if the response is a successful one, it might contain information messages(INFOMELDING) that may be important later in the process.
If the information messages are not taken into account, it may affect the tinglysing operation.
See the errorGroup explanation for information about INFOMELDING.
Soap fault response(500)
Anchor |
---|
| a_soapfaultresponse |
---|
| a_soapfaultresponse |
---|
|
Elements in the Description of the soap fault response, inside the <soap:Body><soap:SoapFault>
elementelements. See examples
Element | Description |
---|
faultcode | Values: soap:Server - conveys the fault is on the server side and there exists a detail element with more information
soap:Client - The xml message is incorrectly formed or contains incorrect information. The faultstring is the only source of more information.
|
faultstring | Human readable error message. Note, if the soap fault response contain more that one documentMessage , the faultstring is a concatenation of the documentMessages. |
detail | Contains detailed error information structured as documentMessages provided faultcode is soap:Server |
FellesDokumentException | Exception wrapper |
exceptionId | A timestamp that identifies the error message. Important for solving support cases. |
documentMessages | A wrapper that contains at least one documentMessage with errorGroup other than INFOMELDING |
documentMessage/detail | Detail message |
documentMessage/errorGroup | errorGroup tells you what category of error messages this is and it should decide further action. Correct the request data or simply try again. See table for explanation |
documentMessage/message | Short message |
documentMessage/errorCode | Error code number, identifying the message |
ErrorGroup explanation
ErrorGroup | Explanation | Action |
---|
INTERNFEIL | Internal error - There is a state in data, environment or configuration that we couldn't recover from. | Try again. Another server might handle this request |
VALIDERINGSFEIL | Validation error - the request does not validate. These are business / professional / legal reasons why the request did not validate. Validation rules for this error involves verifying request data with grunnboken. In the last validation rule, we actually validates the complete document using Statens Kartverk validation service. Example | Verify and correct the data in the request. |
EKSTERNFEIL | External error - This means that one of the external services we depend on to complete the request does not respond or is faulty. | Try again later. The external services we use are seldom faulty for a longer period. |
UKJENT_FEIL | Unknown error - A flaw in the code or it may also be that the server which processed the request had a problem | Please try again, if the problem persists contact support |
INPUTFEIL | Bad request - The xml message validates, but data in the message does not meet requirements. |
ExamplesNot authorized, accessing data owned by others Property/cooperative share/document referred in the request does not exist in grunnboken.
Example | Verify and correct the data in the request. |
Anchor |
---|
| a_infomelding |
---|
| a_infomelding |
---|
| INFOMELDING | Information message - No error, just information. Both fault response and successful responses might have INFOMELDING. Example | |
Example soap fault messages
...
Expand |
---|
title | Validation error example - missing signature |
---|
|
Code Block |
---|
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>
Kartverket rapporterer: Mangler signatur for organisasjon: 321 654 987
</faultstring>
<detail>
<ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
<exceptionId>1625040509848</exceptionId>
<documentMessages>
<documentMessage>
<detail>Mangler signatur for organisasjon: 321 654 987</detail>
<errorGroup>VALIDERINGSFEIL</errorGroup>
<message>Kartverket rapporterer</message>
<errorCode>9014</errorCode>
</documentMessage>
</documentMessages>
</ns2:FellesDokumentException>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope> |
|
Anchor |
---|
| validationerror |
---|
| validationerror |
---|
|
Expand |
---|
title | Validation error example - Grunnbok mismatch |
---|
|
Code Block |
---|
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Det er avvik mellom innsendte opplysninger og det som står oppført i grunnboken. Det kan være feil hjemmelshaver, eiendom/borettsandel eller eiendomsnivå: Gjelder 10038239762 LUNDELAND MADS ANDRE</faultstring>
<detail>
<ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
<exceptionId>1625215833724</exceptionId>
<documentMessages>
<documentMessage>
<detail>Gjelder xxxxxxxxxxx LUNDELAND MADS ANDRE</detail>
<errorGroup>VALIDERINGSFEIL</errorGroup>
<message>Det er avvik mellom innsendte opplysninger og det som står oppført i grunnboken. Det kan være feil hjemmelshaver, eiendom/borettsandel eller eiendomsnivå</message>
<errorCode>9014</errorCode>
</documentMessage>
</documentMessages>
</ns2:FellesDokumentException>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope> |
|
Expand |
---|
title | Input error - document not found for given id |
---|
|
Code Block |
---|
| <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Fant ikke dokument med id=123: null</faultstring>
<detail>
<ns2:FellesDokumentException xmlns:ns2="http://dokument.ws7.etinglysing.no/">
<exceptionId>1625215328560</exceptionId>
<documentMessages>
<documentMessage>
<errorGroup>INPUTFEIL</errorGroup>
<message>Fant ikke dokument med id=123</message>
<errorCode>9002</errorCode>
</documentMessage>
</documentMessages>
</ns2:FellesDokumentException>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope> |
|
Anchor |
---|
| Infomeldingeks |
---|
| Infomeldingeks |
---|
|
...