Error: Error opening data source

Cause(s): Permission issues either on the Scribe Service Logon User, DSN, Local Admin/Scribe Console User Group or Scribe Queues.

When a DTS runs from the TIBCO Scribe® Insight Workbench, it runs in the security context of the logged in Windows user that is running the Workbench. When a DTS is run by an Integration Process on the TIBCO Scribe® Insight Server, "in the Console", it runs in the security context of the login of the user of the Windows services for Insight. These types of security issues usually do not impact credentials for connections used in DTS files, but do impact resources located on the network, such as files, ODBC DSNs, or message queues. Problems in these areas can usually be solved by understanding what resources are needed for the DTS to run and making sure that the domain account used for the Insight services has privileges to access those resources.

Following are a collection of troubleshooting ideas that usually solve this type of problem. If these ideas do not help you resolve the issue, open a support case and we will work with you to find a resolution.  

Troubleshooting: 

• Ensure the Scribe User has been added to the local administrator group and the Scribe Console Users Group.
• Ensure the Scribe services are set to run using a domain account which has access to the Scribe Internal Database in SQL. By default, the services are set to log in as as the local system account. The best practice is to configure the services to log in using a specific domain user. If you need more information about the Scribe services, refer to the TIBCO Scribe® Insight Installation Guide.
• Ensure the DSN is created as a System DSN. When setting up an ODBC Data Source you have the option to set up by User DSN or System DSN. A User DSN is specific to a user on the workstation. For example, if you log on to a machine as user "John," set up a User DSN, then log off, and then log on to the machine as user "Tony", "Tony" will not see the Data Source. Why? It's specific to John's profile, not Tony's. Conversely, if you set up a System DSN, it does not matter who logs on to the machine; all users that logon to that workstation will have access to that Data Source.
• If this is a File integration, ensure a UNC path to the folder where the files are located is configured in the Console Security section. 
• If this is a queue based job, verify the Queues have been shared in the Console and the Scribe user has Full Control to the Scribe/CRM queues via Computer Management > Services > Message Queuing.
• On a Queue based job verify the XML and XDR files are not corrupt. One way to do this is to:
  1. Save the XML body from the Queue Browser in the Console  
  2. Open the publisher and generate a new XDR
  3. Open the Workbench and update the Source with the newly saved XML and XDR