megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here!
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

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!

Both ODBC and JDBC drivers stopped working on May 9, even with updated attributes

edited Jun 2, 2025 2:28PM in Ask A Guru 6 comments

I am unable to connect to SuiteAnalytics Connect both via ODBC and JDBC connections. Has this happened to anyone else?

I'm stuck in NetSuite Support hell with a case that's not moving forward and its a significant impact to our business.

The last successful use of SuiteAnalytics Connect was Saturday, May 7th. Since Monday, May 9th, all of our data refresh processes, both automated and manual, have failed to connect to NetSuite. I traced it back to the ODBC and JDBC driver connections, which both return "TCP/IP error, connection timed out" errors.

I assume it is related to the "Required Update of SuiteAnalytics Connect Drivers" update (linked below), but I have updated all attributes and drivers according to the documentation. I've tested it on the work network and also my home network and receive the same error, reducing the likelihood of firewall interference.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders