Running the DB2 Document Manager server on a Microsoft Windows Server 2003 Service Pack 1 system

Content

If you have remote DB2 Document Manager clients that fail to connect to a DB2 Document Manager server that is running on a Microsoft Windows Server 2003 Service Pack 1 system, edit the system-wide COM limits and grant rights to "ANONYMOUS LOGON".

1. Open the Control Panel and double-click Add or Remove Programs. In the Add or Remove Programs window:
   
   a. Click Add/Remove Windows Components in the left pane.
   
   b. In the Windows Components Wizard, double-click Application Server and verify that the following options are selected:
   
   Enable network COM+ access
   Internet Information Services (IIS)
   
   c. Click OK to close the Application Server window.
   
   d. Click Cancel to close the Windows Components Wizard.
   
   e. Close the Add or Remove Programs window.
2. From the Control Panel, double-click Administrative Tools and then double-click Services. In the Services window:
   
   a. Verify that the following services are started. If they are not both started, start them.
   
   COM+ Event System
   COM+ System Application
   
   b. Close the Services window.
3. From the Control Panel, double-click Component Services. In the Component Services window:
   
   a. Expand Component Services until you see My Computer.
   
   b. Right-click My Computer and select Properties from the popup menu.
   
   c. In the Properties window, click the COM Security tab.
   
   d. In the Access Permissions section, click Edit Limits.
   
   e. Click Add.
   
   f. In the Select Users or Groups window, click Locations.
   
   If the server is part of a domain, you might be prompted for a domain login. If you are, click Cancel, then select the server in the tree (not the domain) and click OK.
   
   g. In the Select Users or Groups window, click Advanced and then click Find Now.
   
   h. Select ANONYMOUS LOGON and click OK twice.
   
   i. In the Access Permissions window, select ANONYMOUS LOGON.
   
   j. Enable (Allow) both Local Access and Remote Access, then click OK to save your changes.
   
   k. In the Launch and Activation Permissions section, click Edit Limits.
   
   l. Repeat steps e to h to add the user ANONYMOUS LOGON.
   
   m. In the Launch Permissions window, select ANONYMOUS LOGON.
   
   n. Enable (Allow) Local Launch, Remote Launch, Local Activation, and Remote Activation.
   
   o. Click OK to save your changes.