Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Connection timeout with Ruby script
When running a Ruby script using classes generated through wsdl2ruby (part of SOAP4r), the login is successful, but a subsequent search generates a SOAP fault complaining that the connection has timed out. The query is submitted immediately following the successful login. If the same steps are executed manually from within the Ruby interactive interpreter (irb), the login and the search are both successful.
Removing all of the flow control and error checking, the script boils down to this:
service = NetSuiteService.new
service.login(uid, pwd)
service.getFutureEvents
service.logout
NetSuiteService is a slim wrapper around NetSuitePortType generated by wsdl2ruby. Even if I replace it with direct calls to NetSuitePortType (as per the code below) from the script, the result is the same.