Руководство По Установке для Cisco Cisco Tidal Enterprise Scheduler 6.2
16-2
Cisco Tidal Enterprise Scheduler Installation Guide
OL-32249-01
Chapter 16 Troubleshooting
TES Fails to Install a Copy of msvcr71.dll
TES Fails to Install a Copy of msvcr71.dll
Occasionally, TES fails to install a copy of msvcr71.dll (Windows 2003) or msvcr100.dll (Windows
2008) in the same directory as saMaster.exe, instead it depends on this .dll to already be installed in the
System32 directory by optional components which are not found in a fresh, fully patched, install of
Windows.
2008) in the same directory as saMaster.exe, instead it depends on this .dll to already be installed in the
System32 directory by optional components which are not found in a fresh, fully patched, install of
Windows.
Any attempt to start TES without the .dll will fail , and the failure will occur so early in TES's launching
process that TES will not write a log file. Most means of launching TES (services control panel, Tidal
Service Manager) will fail without error, but attempting to run saMaster.exe from the command line will
report the missing .dll in an error message.
process that TES will not write a log file. Most means of launching TES (services control panel, Tidal
Service Manager) will fail without error, but attempting to run saMaster.exe from the command line will
report the missing .dll in an error message.
Workaround:
Copy msvcr71.dll or msvcr100.dll into the same directory as the saMaster.exe executable. A copy can be
found next to the java.exe executable in the JVM install (as it too requires the Microsoft Visual C
runtime, but Sun does not assume an optional Microsoft component is providing it via System32).
found next to the java.exe executable in the JVM install (as it too requires the Microsoft Visual C
runtime, but Sun does not assume an optional Microsoft component is providing it via System32).
Verifying and Enabling COM Object Access (Windows Agents)
This is required for Windows agents if it’s not already done.
To verify and enable COM object access:
Step 1
From the Windows Start menu, choose Run. The Run dialog displays.
Step 2
In the Open field, enter DCOMCNFG and click OK. The Component Services dialog displays.
Step 3
Choose Component Services > Computers.
Step 4
Right-click My Computer and choose Properties from the resulting menu. The My Computer
Properties dialog displays.
Properties dialog displays.
Step 5
Select the COM
Security
tab.
Step 6
In the Launch and Activation Permissions section, click Edit Default. The Launch and Activation
Permission dialog displays.
Permission dialog displays.
Step 7
In the Group or user names section, highlight your user account and verify that your account has Allow
Launch access.
Launch access.
Step 8
If the account has a Deny value, select Allow.
Step 9
Click OK.
Step 10
If the user is not listed, click Add and add the user ensuring the user has Allow Launch access.
Step 11
Click OK.
OCSEXIT Jobs
If you find that jobs created using the OCSEXIT variable, that run on Windows agents, and that
consistently end in Completed Abnormally, you may need to update your system path.
consistently end in Completed Abnormally, you may need to update your system path.