Version

All

Date

1 Jul 2001

Summary

After a user installs a Scheduling Engine and attempts to connect to a remote Argent Queue Engine, a message is displayed stating the Scheduling Engine does not recognize the remote machine as an Argent Queue Engine.

The Argent Queue Engine is shown in the Scheduling GUI with a red “X” through it.

Technical Background

This issue is caused by the account used by the Argent Job Scheduler Service not having sufficient rights to read the registry on the remote Argent Queue Engine server, or the Remote Registry Service is not running.

Resolution

Verify the rights are incorrect by logging onto the Scheduling Engine as the ARGENT service account, use REGEDT32 to connect to the registry of the remote Argent Queue Engine machine and read the key

HKEY_LOCAL_MACHINE/SOFTWARE/ARGENT

If able to browse this key, then this KBI article does not apply.

If unable to browse this key using the ARGENT service account, then proceed.

1. Close the Argent Scheduling Engine GUI.
2. Stop the Argent Job Scheduler services.
3. Have the Customer log on locally to the remote Argent Queue Engine machine as the ARGENT service account.
4. If a W200x machine, ensure the Remote Registry Service is running.
5. Uninstall the Argent Queue Engine service.
6. The ARGENT key within HKEY_LOCAL_MACHINE/SOFTWARE will remain.
7. Modify the rights on this key using REGEDT32 to give the ARGENT service account full control over the key.
8. Reinstall the Argent Queue Engine service using the ARGENT service account.
9. Restart the Argent Job Scheduler services on the Scheduling Engine.
10. The Argent Scheduling GUI should now see the remote Argent Queue Engine.