Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Pop Quiz You only have until June 20, 2025, 11:00AM ET to comment your answers and earn rewards! Click here for more details.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
SuiteWorld 2025 registration is officially OPEN
SuiteWorld is the largest annual gathering of the NetSuite community! It will be held in Las Vegas on October 6-9, 2025. Our customers and partners look forward to SuiteWorld every year as a place to hear the latest from NetSuite, get hands-on learning, and connect with each other. Register now!
SuiteWorld is the largest annual gathering of the NetSuite community! It will be held in Las Vegas on October 6-9, 2025. Our customers and partners look forward to SuiteWorld every year as a place to hear the latest from NetSuite, get hands-on learning, and connect with each other. Register now!
Suddenly ODBC error via old Netsuite.com connector
Hello, I've being using an old connector (Netsuite.com) with SuiteAnalytics connect. I has been working fine 3 years.
Suddenly today I started getting this error:
"Network problem, connection unexpectedly closed by peer"
It happens even before I enter the username in ODBC.
The new "Nesuite2.com" data source works fine.
I know that "Nesuite.com" is th old way but my customer has many proccesses based on it and it'll take time to migrate to the new one.
But nowhere it said that it is going to be shut down.
So it might be something in the definitions that needs to be fixed...
0