This was resolved for us yesterday at approximately 4PM EST 8/8/2011

To create that dll we used the IKVM to convert the jar file that you can get from https://system.netsuite.com/download/NLSingleSignOn.zip, once you have that dll you can use the .NET dll generated to create the tokens you need for Single Sign On.

Below is the code we that makes the mapSSO request. The actual soap request was stored a XML file and we string.Format to populate the correct values in the SSO request. using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Net; using System.Xml; using System.Configuration;…

We are successfully using SSO via .NET but getting to this point was difficult. Eventually we got a good support rep who helped us through the process. Debugging was a challenge, we make extensive use of the mapSSO webservice and the only debugging we could do was the response we received. We also made use of Actional…

IKVM can be found at the following url: http://www.ikvm.net/userguide/tutorial.html

To add values to a custom field via the web services is a little tricky at first but once you understand how to do it, it works well enough. The code below is from an integration we have to create invoice records but the custom fields work the same for all objects. First you need to know the id of your custom fields, this…

We are also getting complaints from our NetSuite users, especially those that are entering transactions.

Just got off the phone with NetSuite Support, they are experiencing some TCP/IP issues and moving the case to a defect.

Seem to be having the issues again we have entered another case: 2437578

I have created a ticket #2436858, let's see where that goes.

system2.netsuite.com is allowing us to edit records but on system.netsuite.com we can't even edit a customer record. status.netsuite.com is not indicating any issues, why is that?

Now also experiencing issues in PA. Very unfortunately time of year for this to happen.

Users in our Connecticut office and our Coventry UK office are also experiencing very slow response or not able to get to the page. In PA we are not experiencing problems

Seems to be working again in PA

We have case #2294839 open and referenced this defect number

I've opened a support case and I am going through all the basics with the rep... Case # 1818198

Just for kicks I thought I'd check the status page, it reports 100% uptime. I'm surprised the netsuite monitoring systems haven't picked this up...

We are back up as well.

A S1 defect has been created # 231141

We seem to be having a similar issue but for use it seems to be isolated to Help Desk cases.

The fix seems to have fixed our problem.

We have noticed the same issue with our inbound cases as well. In the event of an issue with our internal systems we can generate short floods of inbound cases. When this happens we've always had an issue with the number of generated cases not matching the number of emails sent by the system. This can cause problems…

Our ODBC connection is also not functioning....:h_a_w:

We have successfully installed this version of the ODBC driver on a Windows Server 2003 Standard X64. Because this is only a 32bit driver you have to use the 32 Bit ODBC manager to set up and manage the DSNs. The path to this manager is usually C:\WINDOWS\SysWOW64\odbcad32.exe

Down in PA