This problem occurs because the default identity for the application is set as Interactive User. Interactive user refers to the user that is logged on directly to the server console. If no interactive user exists, the application fails when it tries to assume the interactive user‘s identity.

To resolve this problem, change the identity for the server application to run under a particular user. To do this, on the Identity tab of the Application Properties dialog box, click This User. In addition, if it is feasible, you can ensure that a user is interactively logged on to the server console while the application is running.

In Microsoft Windows Server 2003, work around this problem by using the /Console switch to log on to Console0. To do this, follow these steps:

1. Click Start, click Run, type mstsc /console, and then click OK.
2. Log on to the computer.

Steps to reproduce the behavior

1. Create a new, empty COM+ Server application. Accept the default settings.
2. Add any component to the application. The component must not already be in another COM+ application.
3. Try to start the application remotely when no user is interactively logged on to the server console.