Summary

When using the Arcana Scheduler API to connect a client on one computer to the service on another computer, creation of the ADSSession object will fail with Error 70 (Permission Denied) if the DCOM permissions are not set correctly.

The DCOM permissions on the server (the computer running the Arcana Scheduler service) must be set to grant access and launch permissions to the user account under which the client is running.

Note that these security settings are separate from the security features built in to the Arcana Scheduler and its API. Changing the DCOM settings will allow the client to create the API components, but the API will still authenticate the client (through the ADSSession.Connect method) to ensure that the user has permission to administer the Scheduler.

More Information

To view or modify the settings, use the Windows dcomcnfg utility.

With dcomcnfg, first check the default launch and access permissions for the computer. If the appropriate user account has not been granted these permissions, you can proceed in either of two ways:

• Modify the default launch and access permissions to grant permission to the user. Note that this will give the user or group these permissions for all DCOM components on the computer for which no settings have alread been made. This may be appropriate for administrative accounts.
• Modify the launch and access permissions for the Arcana Scheduler API components only. For each of the following components, grant access and launch permissions to the appropriate user or group:

ADSJob Class
ADSNetworkConnection Class
ADSNetworkResource Class
ADSSchedule Class
ADSSession Class