Microsoft Windows Server 2003 Service Pack 1: COM limits

Resolving The Problem

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 machine, perform the following steps to edit the new machine-wide COM limits and grant rights to "ANONYMOUS LOGON":

1. Open the Component Services Microsoft Management Console.
2. Expand Component Services until you see My Computer.
3. Right-click My Computer and click Properties.
4. Click the COM Security tab.
5. In the Access Permissions section, click Edit Limits.
6. Click Add. The Select Users or Groups window opens.
7. Click Locations. If the server is part of a domain, you might be prompted for a domain login. If so, click Cancel, then select the server in the tree (not the domain) and click OK.
8. In the Select Users or Groups window, click Advanced.
9. Click Find Now.
10. Select ANONYMOUS LOGON and click OK twice.
11. In the Access Permissions window, select ANONYMOUS LOGON.
12. Enable (Allow) both Local Access and Remote Access, then click OK to save your changes.
13. In the Launch and Activation Permissions section, click Edit Limits.
14. Repeat steps 6 to 10 to add the user ANONYMOUS LOGON.
15. In the Launch Permissions window, select ANONYMOUS LOGON.
16. Enable (Allow) Local Launch, Remote Launch, Local Activation, and Remote Activation, then click OK to save your changes.