Skip to main content
Known Participant
October 9, 2014
Question

CF 10 Service suddenly stopped

  • October 9, 2014
  • 1 reply
  • 528 views

Hello,

This issue occurred twice this week. Our CF application server suddenly stopped. When I checked the Event Viewer log, here are the errors I found:

The description for Event ID 263 from source ColdFusion 10 Application Server cannot be found. Either the component that

raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the

component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ColdFusion 10 Application Server

1432

The description for Event ID 261 from source ColdFusion 10 Application Server cannot be found. Either the component that

raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the

component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ColdFusion 10 Application Server

240

C:\ColdFusion10\cfusion\bin\coldfusionsvc.exe

ColdFusion 10 Application Server

When I restarted the CF server, this is the warning from the Event Viewer:

The description for Event ID 3 from source ColdFusion 10 Application Server cannot be found. Either the component that

raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the

component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ColdFusion 10 Application Server

668

Thanks in advance.

    This topic has been closed for replies.

    1 reply

    Inspiring
    October 15, 2014

    Have you made any changes on the server, which started throwing this failure behavior?