cancel
Showing results for 
Search instead for 
Did you mean: 
My Areas

Sign in or create account

to get a personalized navigation.

Avi Cohen
PARTNER

Error from get SalesOrder

by Avi Cohen (Updated ‎02-02-2021 13:47 by Yildirim VISMA )

Hi,

 

I am getting an error from my integration that i dont understand what problem is. 

The integration seems to work correctly anyway so i am not sure if it is a problem.

 

I will copy one of the the error messages ;

java.io.IOException: Server returned HTTP response code: 500 for URL: https://integration.visma.net/API/controller/api/v1/salesorder/004075

 

[HTTP connection response header : null : HTTP/1.1 500 Internal Server Error, HTTP connection response header : Date : Tue, 14 Jul 2020 06:15:09 GMT, HTTP connection response header : Strict-Transport-Security : max-age=31536000; includeSubDomains, HTTP connection response header : Content-Type : application/json; charset=utf-8, HTTP connection response header : ipp-request-id : 30e3fce6-91b4-41f8-9927-95637204f1a0, HTTP connection response header : X-Content-Type-Options : application/json, HTTP connection response header : Pragma : no-cache, HTTP connection response header : X-Handled-By : Acumatica-PX.Export/AuthenticationManagerModule, HTTP connection response header : Referrer-Policy : origin-when-cross-origin, HTTP connection response header : VnfInstanceId : financials_3872, HTTP connection response header : Strict-Transport-Security : value="max-age=31536000; includeSubDomains", HTTP connection response header : Cache-Control : no-cache,no-cache, HTTP connection response header : Feature-Policy : geolocation 'none'; vr 'none'; payment 'none'; midi 'none'; microphone 'none'; fullscreen 'none'; encrypted-media 'none'; camera 'none'; autoplay 'none';, HTTP connection response header : Expires : -1, HTTP connection response header : X-XSS-Protection : 1;mode=block, HTTP connection response header : Set-Cookie : LegacyUI=0; path=/; secure; HttpOnly,UserBranch=19; path=/; secure; HttpOnly,Locale=TimeZone=GMTE0000U&Culture=en-GB; path=/; secure; HttpOnly,LicenseRoles=; expires=Mon, 13-Jul-2020 06:15:09 GMT; path=/; secure; HttpOnly,UserDisplayName=; expires=Mon, 13-Jul-2020 06:15:09 GMT; path=/; secure; HttpOnly, HTTP connection response header : Connection : close, HTTP connection response header : Transfer-Encoding : chunked, HTTP connection response header : null : null]response body : {"message":"VismaId: 99653e5b-478f-44e7-8123-500e002181d3. The column name '[FeaturesSet].[B2CServiceAutoInvoice]' is invalid.\r\nThe column name '[FeaturesSet].[JournalVoucher]' is invalid.\r\nThe column name '[FeaturesSet].[SeveraIntegration]' is invalid.\r\nThe column name '[FeaturesSet].[VatAdjustment]' is invalid.\r\n"}

8 REPLIES 8
Yildirim
VISMA

by Yildirim

Hello, 
do you see any warning/error messages when you open the same salesorder on the Financials ERP ?

Avi Cohen
PARTNER

by Avi Cohen

Hi Yildirim,

 

Thanks for quick answer. 

I dont see any warning or error messages on the Financials.

Yildirim
VISMA

by Yildirim

Hi Avi, 

thank you for the information. Have these errors been occurring randomly or do you receive with every GET operation ?
could you please send your API Client ID , Financials Company Name & ID via developersupport@visma.com ? 

Avi Cohen
PARTNER

by Avi Cohen

Hi Yildirim,

 

I think the errors have been occuring randomly because if it was not randomly i should have got it every get operation. The integration program executes every 15 minutes and  the last error was 08:15. 

 

 

Avi Cohen
PARTNER

by Avi Cohen

I already send an email with details you requested.

Yildirim
VISMA

by Yildirim (Updated ‎14-07-2020 15:30 by Yildirim VISMA )

Thanks, we've received the details.
We've conveyed this to our infrastructure team and the case is currently being investigated.We'll get back to you with more information.

Avi Cohen
PARTNER

by Avi Cohen

Thanks again for quick response. 

Accepted solution
Yildirim
VISMA

by Yildirim

Hello, 

The mentioned issue has been diagnosed and corrected by recycling the unhealthy API node everything should now be running as expected. If you still receive the error, please inform us with transaction details.