Summary

When using the Arcana Scheduler API from an active server page (ASP) or other web server script, several factors can cause problems.

More Information

The following problems are commonly encountered.

"Access Denied" error when creating the ADSSession object

Two common problems can cause a permission error when you try to create the ADSSession object.

First, the NTFS permissions on the "adscom.dll" (in the Arcana Scheduler program directory) may not be set to use the IIS account access. If the permissions look OK, try moving the DLL to the winnt\system32 directory. To do so:

  • Open a command prompt and navigate to the directory that contains the DLL.
  • Unregister the component with the command "regsvr32 /u adscom.dll"
  • Move the DLL to the winnt\system32 directory
  • Navigate to the system32 directory and reregister the dll using the command "regsvr32 adscom.dll"

Second, the COM security settings may not allow the IIS account to create the object. See article I02000035 for information on verifying and modifying these settings.

Error calling the Connect method

If you are able to create the ADSSession object but get error &hC0040005, &hC0040009, or &hC00413E6 when calling the Connect method, this indicates that the IIS account has not been granted permission to administer the Scheduler.

By default only members of the Administrators group are allowed to connect to the Scheduler. You will need to grant permission to the IIS account. This is done using the scheduler's Configuration Editor tool; look for the "Security: customizing" topic in the online help index for details. The basic steps required are:

  • Using the NT user administrator, create a new NT security group called "Scheduler Administrators".
  • Add the account used by IIS to this new group.
  • Using the Configuration Editor, create a new Scheduler security group called "Scheduler Administrators", set it to "Use NT Security Group" for authentication, and specify "Scheduler Administrators" as the NT security group to use.
  • Either add the Administrators group to the new Scheduler Administrators group (using the Windows user manager) or add the Administrators group in the Configuration Editor (see article I02000045 for information on why this is necessary).
  • Save the changes made in the Configuration Editor.
  • Stop and restart the Arcana Scheduler service so it recognizes the security changes.