...
Various DCOM settings can cause problems with SQL Trigger calls to NLINK.
| Note |
|---|
|
This page is relevant to 32-bit Windows XP Professional and 32-bit Windows Server 2003 only. |
Stored Procedure Creation Script
...
DCOM Settings (NLINK Server and SQL Server on different machines)
If the NLINK Server and Microsoft SQL Server are on different computers, then DCOM security settings have to be properly configured for the trigger to work. The instructions assume that you are familiar with, and have the appropriate privileges to be able to perform systems administration tasks on your Windows system.
Configure DCOM the Computer running the NLINK Server:
- Run “dcomcnfg” from the command line.
- Navigate to “Component Services->Computers->My Computer”
- Open the Properties window for “My Computer”.
- Select the “COM Security” tab.
- In the “Launch and Activation Permissions” section, click the “Edit Limits” button.
- Select the “Everyone” group and check the “Allow” check-box for “Remote Activation”.
- Navigate to “Component Services->Computers->My Computer->DCOM Config->NLINK”
- Open the Properties window for the NLINK application.
- Select the Security tab.
- In the “Launch and Activation Permissions” section, choose “Customize” and click the “Edit…” button.
- Add the domain “Authenticated Users” group and allow “Remote Activation”.
| Info |
|---|
| May need additional “Launch and Activation Permissions” settings if the Microsoft SQL Server machine and NLINK Server machines are started with specific accounts (e.g. Microsoft SQL Server service is started with specific account rather than using “Local System Account”). |
| Info |
|---|
Windows Firewall (or any similar application) may also cause issues. Please contact your on-site systems administration professionals for help regarding Firewalls. |
Configure DCOM on the SQL Server computer:
- If NLINK Server is not installed on the machine, then create proper registry entries. Import the “NLink Connector.reg” file (available from Junot Systems) into the registry.
- Run “dcomcnfg” from the command line.
- Navigate to “Component Services->Computers->My Computer->DCOM Config”
- Open the Properties window for “NLINK”
- Select the “Location” tab.
- Un-check “Run application on this computer”.
- Check “Run application on the following computer:”
- Enter the name of the host computer on which NLINK is installed.
...
Testing New-Style Stored Procedures
With new-style stored procedure use the Test sp_NLINK new.sql script which is available from Junot Systems.
Look at values returned in @ErrorMsg, to debug issues.
...
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | NLINK |
|---|
| showSpace | false |
|---|
| sort | modified | showSpace | false |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label = "sql" and type = "page" and space = "NLINK" |
|---|
| labels | sql |
|---|
|
If the NLINK Server and Microsoft SQL Server are on different computers, then DCOM security settings have to be properly configured for the trigger to work. The instructions assume that you are familiar with, and have the appropriate privileges to be able to perform systems administration tasks on your Windows system.
Configure DCOM the Computer running the NLINK Server:
Windows Firewall (or any similar application) may also cause issues. Please contact your on-site systems administration professionals for help regarding Firewalls.
Configure DCOM on the SQL Server computer: