Cisco Support Community
Community Member

CiscoWorks processes were not stopped even after the daemons were stopped


I am upgrading the Ciscoworks Common Services from 3.0.5 to latest which is 3.0.6

I am now running into issues that will not allow the successful installation of 3.0.6



process. You must stop all processes listed below to

proceed successfully with this installation.

Click Next to proceed with the installation.

Click Cancel to exit.

cd \Program Files\CSCOpx

cd \Program Files\CSCOpx\CSCOpx\MDC\Apache\Apache.exe

cd \Program Files\CSCOpx\CSCOpx\bin\cmf_crash_handler.dll

cd \Program Files\CSCOpx\CSCOpx\bin\libeay32.dll

cd \Program Files\CSCOpx\CSCOpx\bin\perl.dll

cd \Program Files\CSCOpx\CSCOpx\bin\ssleay32.dll

cd \Program Files\CSCOpx\CSCOpx\MDC\Apache\ApacheCore.dll

cd \Program Files\CSCOpx\CSCOpx\MDC\Apache\Win9xConHook.dll

cd \Program Files\CSCOpx\CSCOpx\MDC\Apache\modules\ApacheModulePerl.dll

cd \Program Files\CSCOpx\CSCOpx\MDC\Apache\modules\mod_jk.dll

cd \Program Files\CSCOpx\CSCOpx\objects\perl5\lib\MSWin32-x86\auto\Socket\Socket.dll


Looking at the fix in 3.0.6 docs i see it reference CSCsj05465 but it did not give me how to shut those processes manually.

(Only Cisco Staff have Access to CSCsj05465) Does anyone have a solution to upgrade successfully ?

Community Member

Re: CiscoWorks processes were not stopped even after the daemons

I stopped Ciscoworks Web Services in Windows Services and it resolved it

Cisco Employee

Re: CiscoWorks processes were not stopped even after the daemons

This indicates that your services configuration may be incorrect. Most CiscoWorks services should be set to Manual startup in the Services control panel. The only services that can be Automatic are Daemon Management, syslog, RSH, TFTP, and the IPM services. If you have changed any of the service startup parameters for the other services, set them back to Manual, and reboot.

CreatePlease to create content