[cylosoft]

Ever since the update to 2016.1 on Friday night, all web service integrations have stopped working.

We can successfully login and can call the .getDataCenterUrls(“[acctID]”) method. All other methods, including getServerTime(), are throwing an error: “Your connection has timed out. Please log in again.”

We have integration versions of 2010.1, 2012.1, 2013.1 and have done testing in 2016.1. They all have the same error.

I have tried setting timeouts of 5 minutes and 1 hour.

Anyone experiencing a similar issue?
This is a cached copy. Click here to see the original post.

[taylor@abptech.com]

Does your integration support TLS1.2? I know this was the only thing I had to worry about this year, though it technically wasn’t being released until 2016_02 I think.

[cylosoft]

It should support TLS1.2, but I’m not specifically setting the Security Protocol. One of the apps on my dev machine is running .net 4.5 from a Windows 8 machine. This is experiencing the same issue.

[jschneller]

We were upgraded on Friday and run 2013.1 web services. We have not experienced any problems so far and our code/servers are not set up for TLS 1.2 yet. I will have more info next week when we move to code/servers which support TLS 1.2.

[cylosoft]

NS Documentation shows that the CookieContainer should be supported. https://system.netsuite.com/app/help…489690806.html. After the 2016.1 update, it appears this is no longer the case. I was able to get this working by assigning the Passport to the Service instead of using the login (passport)

[vconnect]

Are you using C# or Java? CookieContainer is a C# class. If you’re using Java, then make sure you set .setMaintainSession(true); and that you are using the patched version of Axis 1.4.

[cylosoft]

We are using C#. This has been listed as “Defect: 388423 – Web Service Session errors”. Update: “…identified the resolution for this issue and they are targeting release of fix for on 5/12.”

[Author]

Posts