When an issue occurs that is logged in the Windows Event Logs on the ServiceDesk server, a matching ticket is also created.
The following is an example of how a ServiceDesk ticket can be created based on an issue in the Windows Event Log:
IM-000001: W3SVC: Application pool 'DefaultAppPool' exceeded its job limit settings.
Incident: IM-000001 assigned to you.
W3SVC: Application pool 'DefaultAppPool' exceeded its job limit settings.
System Event Error: <server_name> (Warning) Event Happend: 9/10/2010 15:15:19 PM UserName / Source / Machine Name: Not Found / W3SVC / <server_name> Category: (0) Message: Application pool 'DefaultAppPool' exceeded its job limit settings.
Click Here To View Incident http://<server_name>/ProcessManager/Reports/OpenProcess.aspx?ReportSessionID=<GUID>
The SD.Feeder.WindowsEventMonitor project is automatically published during the ServiceDesk install. This will monitor the Windows Event Logs for issues and then create new ServiceDesk tickets based on them. This is working as designed.
Unpublish the SD.Feeder.WindowsEventMonitor project if these type of tickets are not wanted to be tracked in ServiceDesk.
Stop IIS by running IISRESET /STOP from a command prompt.
Go to the <ServiceDesk_installation_drive>:\Program Files (x86)\Altiris\Workflow Designer\WorkflowDeploy\Release folder.
Delete the SD.Feeder.WindowsEventMonitor folder.
In IIS, go to Web Sites > Default Web Site. If the virtual directory is still there, delete this.
Restart IIS by running IISRESET /START.
Note: Tickets cannot be deleted. Set any that this process created to Closed to remove them from being active.
Imported Document ID: TECH139569
Subscribing will provide email updates when this Article is updated. Login is required.