Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

CCM Trace Errors

When I configure and set on trace, either for all devices or a single device I get errors. Any thoughts?

An error occurred during your query.

Error Code = 0x-7fffbfe6.

Error Description = 006~ASP 0177~Server.CreateObject Failed~The server process could not be started because the configured identity is incorrect. Check the username and password. .

An error occurred during your query.

Error Code = 0x-7ff5ec71.

Error Description = 'myTool' is null or not an object.

An error occurred during your query.

Error Code = 0x-7fffbfe6.

Error Description = 006~ASP 0177~Server.CreateObject Failed~The server process could not be started because the configured identity is incorrect. Check the username and password. .

An error occurred during your query.

Error Code = 0x-7ff5ec71.

Error Description = 'myCommandLine' is null or not an object.

Rory

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: CCM Trace Errors

Looks like one more lovely bug...

CSCdu25900 Bug Details

Release Notes

Symptom:

When attempting to configure traces within CCMAdmin, the following error is displayed

when navigating to the trace configuration page:

"An error occured during your query

Error code = 0x-7fffbfe6

Error description = 006~ASP0177~Server.CreateObject Failed~The Server process could not be started because the configured identity is incorrect. Check Username and Password."

Workaround:

CiscoSysFileMgr.exe" is dated "Created December 03 2000,Modified January 23 2001".

Please check whether the CiscoSysFileMgr.exe is available under C:\ProgramFiles\Cisco\bin. Also check if there are multiple instances in the Windows NT task manager. If so kill all

the instances of the CiscoSysFileMgr and start a fresh query. CiscoSysFileMgr.exe is the one that is used to create the object for merging the files.

Step 1. Login as administrator to the CallManager machine.

Step 2. Kill any instance of "CiscoSysFileMgr.exe". In this case go to the task manager and check for the process Ciscos~1.exe. Kill all the instances.

Step 3. Then run on dos command prompt at "C\Program files\cisco\bin (First unregister and then register back) > CiscoSysFileMgr.exe -UnregServer > CiscoSysFileMgr.exe -RegServer

Step 4. The above three steps need to be done on all machines Even if step 2 does not apply, i.e, there are no instances of CiscoSysFileMgr.exe, try step 3 and 4 anyway.

The CiscoSysFileMgr.exe is the application that is used to merge the files and we are creating an instance of this application in the tracecollection web application.

In the web page (traceForm.asp) the object creation of this application is giving error as it's not registered on your system. By killing the process from the taskmanager it'll only kill the instance of this application(CiscoSysFileMgr.exe) and it'l

l affect only the tracecollection and it doesn't affect the callmanager in any way. ( at most increase the performance of the callmanager as it uses the CPU of the callmanager). This application needs to be registered on the callmanager where the tra

ceCollection/traceGathering tool is installed.

3 REPLIES
Silver

Re: CCM Trace Errors

Looks like one more lovely bug...

CSCdu25900 Bug Details

Release Notes

Symptom:

When attempting to configure traces within CCMAdmin, the following error is displayed

when navigating to the trace configuration page:

"An error occured during your query

Error code = 0x-7fffbfe6

Error description = 006~ASP0177~Server.CreateObject Failed~The Server process could not be started because the configured identity is incorrect. Check Username and Password."

Workaround:

CiscoSysFileMgr.exe" is dated "Created December 03 2000,Modified January 23 2001".

Please check whether the CiscoSysFileMgr.exe is available under C:\ProgramFiles\Cisco\bin. Also check if there are multiple instances in the Windows NT task manager. If so kill all

the instances of the CiscoSysFileMgr and start a fresh query. CiscoSysFileMgr.exe is the one that is used to create the object for merging the files.

Step 1. Login as administrator to the CallManager machine.

Step 2. Kill any instance of "CiscoSysFileMgr.exe". In this case go to the task manager and check for the process Ciscos~1.exe. Kill all the instances.

Step 3. Then run on dos command prompt at "C\Program files\cisco\bin (First unregister and then register back) > CiscoSysFileMgr.exe -UnregServer > CiscoSysFileMgr.exe -RegServer

Step 4. The above three steps need to be done on all machines Even if step 2 does not apply, i.e, there are no instances of CiscoSysFileMgr.exe, try step 3 and 4 anyway.

The CiscoSysFileMgr.exe is the application that is used to merge the files and we are creating an instance of this application in the tracecollection web application.

In the web page (traceForm.asp) the object creation of this application is giving error as it's not registered on your system. By killing the process from the taskmanager it'll only kill the instance of this application(CiscoSysFileMgr.exe) and it'l

l affect only the tracecollection and it doesn't affect the callmanager in any way. ( at most increase the performance of the callmanager as it uses the CPU of the callmanager). This application needs to be registered on the callmanager where the tra

ceCollection/traceGathering tool is installed.

Community Member

Re: CCM Trace Errors

On the nail marina. Sorted...

Cisco Employee

Re: CCM Trace Errors

These are database errors and generally not a good sign. Looks like a password was changed somewhere possibly. Check the system and application event logs for corresonding errors. Also check sql replication and authentication. If you can't find a specific issue, please open a TAC case.

134
Views
0
Helpful
3
Replies
CreatePlease to create content