NetSuite - Only One Connection Per Set Of User Credentials May Be Made At A Time

NetSuite - Only One Connection Per Set Of User Credentials May Be Made At A Time

book

Article ID: KB0078894

calendar_today

Updated On:

Products Versions
TIBCO Cloud Integration - Connect ( Scribe ) -

Description

The NetSuite API limits each NetSuite User to a single API connection based on that User's login credentials. This can cause TIBCO Scribe® Online Solutions that use a NetSuite Connection to fail with the following errors if other calls are made to the NetSuite API using the same credentials.

Only one request may be made against a session at a time
The operation has timed out


When running a TIBCO Scribe® Online Solution that uses a NetSuite Connection, keep in mind that any one of the following actions also makes a connection to the NetSuite API and can cause the running Solution to fail: 

  • Running another Solution that connects to NetSuite using the same credentials.
  • Debugging a Map that connects to NetSuite.
  • Creating more than one NetSuite Connection using the same credentials.
  • Clicking OK on the Connection Configuration dialog for your NetSuite Connection.
  • Testing the NetSuite Connection.
  • Refreshing Metadata for NetSuite
  • Retrieving Metadata for a new Map that connects to NetSuite.

Some options to prevent your NetSuite Solutions from failing include: 

  • Upgrading your NetSuite User license to allow multiple connections to the API.
  • Purchasing additional NetSuite User licenses.
  • Pausing NetSuite Solutions when you need to do other work that connects to NetSuite.
  • Using a single Solution that contains all of your NetSuite Maps, so they never execute at the same time.
  • Scheduling Solutions to run at staggered intervals to prevent them from trying to access the API at the same time.

For additional information, see the following in the TIBCO Scribe® Online Help: TIBCO Scribe Online Connector For NetSuite

 

Issue/Introduction

Errors: Only one request may be made against a session at a time The operation has timed out