Set up email notification for ADC errors - GoToWebinar

Find an Answer

Search GoToWebinar articles, videos and user guides   Your search term must have 2 or more characters.

Browse Articles

Set up email notification for ADC errors

You can set up email notifications for error messages and status messages for Active Directory Connector (ADC) events.

Back to Active Directory Connector Contents

The following additional requirements are needed for this process:

  • SMTP(S) server (to send status information) -- SMTP service account (user/password) for sending emails (only if it's necessary for your SMTP server)
  • SSL certificate -- May be required to connect to the SMTP server and Domain Controller securely (optional)

You can also Set up email notification for ADC status.

Create an email task in the Windows Event Viewer

1. Open the Windows Event Viewer (Start > All Programs > Administrative Tools > Event Viewer).

2. With the ADC installed, the Windows Event Viewer will show an additional event log called ADCSLog (under the Applications and Services Logs folder). Select the new event log in the left navigation.

3. In the records pane, right-click the event for which you’d like to receive email notifications and select Attach Task To This Event from the drop-down menu.

4. In the Create a Basic Task wizard, name your task and click Next > Next.

5. Select Send an email and click Next.

6. Fill out the From, To, Subject, Text, Attachment and SMTP server fields and click Next.

7. Click Finish to save your new task.

Specify when the notification email is sent using the Windows Task Scheduler

1. Open the Windows Task Scheduler (Start > All Programs > Administrative Tools > Task Scheduler).

2. In the left navigation, select Task Scheduler Library > Event Viewer Tasks.

3. Right-click the new task created in the prior set of steps and select Properties.

4. On the General tab, click Run with highest privileges check box.

5. On the Triggers tab, select On an event and click Edit. Enable the Delay task for check box and enter 2 minutes and click OK. If you do not add a delay, new events that arrive will trigger additional actions before the actual action is completed.

6. On the Actions tab, review the actions that will occur when your task starts. The following actions are required; you can add, edit or delete as needed. Click OK when finished.

  • Stop task (disable_task.bat) – schtasks /Change /TN "Event Viewer Tasks\ADCSLog_Error" /DISABLE
  • Get error (error_status.bat) – del %temp%\error_status.txt wevtutil qe ADCSLog /q:"*[System[Provider[@Name='AD Conn'] and (Level=2) and TimeCreated[timediff(@SystemTime) <= 120000]]]" /f:text /rd:true > C:\temp\error_status.txt
  • Enable task (enable_task.bat) – schtasks /Change /TN "Event Viewer Tasks\ADCSLog_Error" /ENABLE

Test the configuration

Retrieve all error events from the last two minutes and save them to c:\temp\error_status.txt. From there, the new task created in Step #1 should collect the error events and attach them to the email.

The following events represent examples of error messages and what they mean if they're reported in the Active Directory Connector service.

Event[0]: Log Name: ADCSLog Source: AD Conn Date: 2013-02-28T16:11:59.000 Event ID: 0 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: de-pc-dev-018.ad.corp.expertcity.com Description: 2013-02-28 16:11:59,502 [WorkOrderThread] ERROR - Writing OSD data: Organizer ADConnEG2T@trash-mail.com was not created Event[3]: Log Name: ADCSLog Source: AD Conn Date: 2013-02-28T16:11:58.000 Event ID: 0 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: de-pc-dev-018.ad.corp.expertcity.com Description: 2013-02-28 16:11:58,257 [WorkOrderThread] ERROR - Writing OSD data: Server response exception: {StatusCode": "409", "StatusCodeAsString": "Conflict", "Response": "The remote server returned an error: (409) Conflict."}
Event[1]: Log Name: ADCSLog Source: AD Conn Date: 2013-02-28T16:11:59.000 Event ID: 0 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: de-pc-dev-018.ad.corp.expertcity.com Description: 2013-02-28 16:11:59,499 [WorkOrderThread] ERROR - Writing OSD data: Server response exception: {"StatusCode": "409", "StatusCodeAsString": "Conflict", "Response": "The remote server returned an error: (409) Conflict."} Event[4]: Log Name: ADCSLog Source: AD Conn Date: 2013-02-28T16:11:56.000 Event ID: 0 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: de-pc-dev-018.ad.corp.expertcity.com Description: 2013-02-28 16:11:56,966 [WorkOrderThread] ERROR - Writing OSD data: Organizer ADConn2.User2@trash-mail.com was not created
Log Name: ADCSLog Source: AD Conn Date: 2013-02-28T16:11:58.000 Event ID: 0 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: de-pc-dev-018.ad.corp.expertcity.com Description: 2013-02-28 16:11:58,260 [WorkOrderThread] ERROR - Writing OSD data: Organizer ADConn1.User1@trash-mail.com was not created Event[5]: Log Name: ADCSLog Source: AD Conn Date: 2013-02-28T16:11:56.000 Event ID: 0 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: de-pc-dev-018.ad.corp.expertcity.com Description: 2013-02-28 16:11:56,963 [WorkOrderThread] ERROR - Writing OSD data: Server response exception: {"StatusCode": "409", "StatusCodeAsString": "Conflict", "Response": "The remote server

See also