Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2
14-418
Cisco Tidal Enterprise Scheduler 6.2 User Guide
6.2.1
Chapter 14 Troubleshooting
Troubleshooting the Master
Step 6
Click OK, then exit the
Service Control Manager.
Adding Access Permissions to an Account with dcomcnfg
Note
This procedure must be run as Windows Administrator.
To add access permissions to an account:
Step 1
Click the Windows Start button, then select Run and type dcomcnfg in the Open field.
Step 2
Click the Applications tab in the DCOM dialog.
Step 3
Select the idsMail server from the Applications list (listed as This server object provides a universal
Email send/receive...) and click Properties.
Email send/receive...) and click Properties.
Step 4
When the idsMail dialog displays, click the Security tab.
Step 5
In the first section on the tab, select the Use custom access permissions option.
Step 6
Click the Edit button for access permissions to display the Registry Value Permissions dialog.
Step 7
Click Add
to display the
Add Users and Groups
dialog.
Step 8
Select and add the TES master user account from the Add Users and Groups dialog.
Step 9
Click OK and click OK again in the Registry Value Permissions dialog to return to the Security tab.
Step 10
In the second section on the tab, select the Use custom launch permissions option.
Step 11
Click the Edit button to display the Registry Value Permissions
dialog.
Step 12
Click Add and select the TES master user account from the Add Users and Groups
dialog.
Step 13
Click OK and click OK again to close the Registry Value Permissions dialog.
Step 14
Click OK to exit the idsmail dialog.
Step 15
Click OK again at the DCOM dialog to save your changes and exit.
Step 16
Reboot the master machine.
Database Connectivity Loss
If database connectivity is lost, the Master pauses itself and continues to poll for connectivity. When the
Master finds connectivity working, it resumes (on its own) and continues job processing as usual.
During normal operation, database connectivity is checked every 15 seconds. If connectivity is lost, the
Master checks every 5 seconds for connectivity.
Master finds connectivity working, it resumes (on its own) and continues job processing as usual.
During normal operation, database connectivity is checked every 15 seconds. If connectivity is lost, the
Master checks every 5 seconds for connectivity.