When does Siebel Adapter NT Service fail to start?
Article ID: KB0085507
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel | - |
| Not Applicable | - |
Description
Resolution:
The Siebel Adapter NT Service might fail to start due to the permission settings for the Windows user. The error usually occurs because Siebel tries to find an ODBC source normally registered by the client installation. This ODBC source will be under the client section and not visible to other users. Therefore, using the above steps should ensure that the ODBC source is visible to the adapter.
If you are using dedicated client (adapter configured to connect to Siebel as a dedicated client) configuration try the following steps:
1. Check if you are able to connect using the Siebel client with the same parameters (.cfg file, user and password) used by the adapter.
2. If the above step succeeds, change the NT Service parameter of the adapter by choosing the logon options as "Local System" and checking "Interact with Desktop".
3. Now start the NT Service and check if the adapter is able to startup.
If this does not work, perform the following checks:
1. Open the .cfg file.
2. Check the value for the entry "DataSource".
3. Go to the section [<value for DataSource>] and check the value for 'ConnectString'
4. Check if there is a DSN by this name and that this DSN is visible to the windows user trying to start the adapter. Else change the logon parameters of the adapter to be the same as the user that installed the Siebel Client.
Or create a new System DSN and provide that as the ConnectString in the .cfg being used to start the adapter.
The Siebel Adapter NT Service might fail to start due to the permission settings for the Windows user. The error usually occurs because Siebel tries to find an ODBC source normally registered by the client installation. This ODBC source will be under the client section and not visible to other users. Therefore, using the above steps should ensure that the ODBC source is visible to the adapter.
If you are using dedicated client (adapter configured to connect to Siebel as a dedicated client) configuration try the following steps:
1. Check if you are able to connect using the Siebel client with the same parameters (.cfg file, user and password) used by the adapter.
2. If the above step succeeds, change the NT Service parameter of the adapter by choosing the logon options as "Local System" and checking "Interact with Desktop".
3. Now start the NT Service and check if the adapter is able to startup.
If this does not work, perform the following checks:
1. Open the .cfg file.
2. Check the value for the entry "DataSource".
3. Go to the section [<value for DataSource>] and check the value for 'ConnectString'
4. Check if there is a DSN by this name and that this DSN is visible to the windows user trying to start the adapter. Else change the logon parameters of the adapter to be the same as the user that installed the Siebel Client.
Or create a new System DSN and provide that as the ConnectString in the .cfg being used to start the adapter.
Issue/Introduction
When does Siebel Adapter NT Service fail to start?
Feedback
Yes
No
Powered by
