In order to resolve the above error it may be possible, based on your NetSuite environment and permissions, to create another CData Netsuite connection to the same environment using a different user and also a different Application ID. The Application ID is how the connection communicates with NetSuite and determines concurrent sessions. By default the TIBCO Scribe CData NetSuite connector uses the Application "CData NetSuite Connector" when connecting to NetSuite, but a custom one can be created and used in the connection as an additional parameter to bypass the concurrent session error. Details are below:
1. In TIBCO Scribe Online create a new CData Netsuite connection to the same environment using a different user than the connection that is currently established.
2. Navigate to NetSuite and log in as an Administrator.
3. Navigate to Setup > Integration > Manage Integrations.
4. Once in Manage Integrations you will see the list of Applications including the "CData NetSuite Connector".
5. Select "New" and then create a new application, ensure that the name is unique and the "Authentication" section is filled out correctly based on the type of authentication you are using for the TIBCO Scribe CData NetSuite connection > Select "Save".
6.Once saved, the Application ID will be generated, copy this new Application ID from the Application that was just created.
7. Return to TIBCO Scribe Online, navigate back to the new connection that you created for the CData Netsuite connection and in the "Additional Parameters" section input Application Id = "...." (inside the quotes input the new Application ID that was copied from the previous step > Select "Test" and then "OK".
Once the connection is saved, you can now use this new connection with the new application ID to run
simultaneously as the other job/solution that is also connecting to NetSuite.