1. Kaseya
2. VSA
3. Ticketing

The Email Reader's log reports the error "wodPop3 Error: Login ERROR: The service has not been started.

Problem
Tickets do not appear to be created when sending emails to the address checked by the email reader.

The Email Reader's log reports the error "wodPop3 Error: Login ERROR: The service has not been started.".  All subsequent log entries fail in a similar fashion. The Email Reader reports as not able to connect, and clicking Connect Now results in a failed connection.

Looking at the services on the VSA server, there does not appear to be a service WODPOP3 running.

05/25/2008 22:57:11 KEmailReader Begins 
05/25/2008 22:57:12 0 Emails, 0 Tickets Added, 0 Tickets Updated 
05/25/2008 22:57:12 KEmailReader Ends 

05/25/2008 23:01:10 KEmailReader Begins 
05/25/2008 23:01:11 wodPop3 Error: Login ERROR: The service has not been started. 
05/25/2008 23:01:11 0 Emails, 0 Tickets Added, 0 Tickets Updated
 

 

CAUSE

This was caused by an issue on the Microsoft Exchange server running the POP server.
 

 

RESOLUTION

Rebooting the Exchange server resolved the issue.
 

 

APPLIES TO

Ticketing tab
Email reader
Microsoft Exchange
POP

Browse this section

• Alert does not raise or delays alarms, tickets, emails
• Configure SMTP to deliver mail internally
• Configure VSA server to send outbound email using local IIS SMTP server
• How to format email notifications that are sent out via the Ticketing module?
• How does Kaseya integrate with Autotask, Connectwise or another ticketing system or PSA?
• How to Auto-populate the Submitter's Information Field in KLC > Ticketing > Create page
• How to to setup email notifications to be sent out for machine groups
• How to Create a Custom Ticketing Field in Ticketing Module
• How to hide hidden notes in Ticketing and to Define access to each ticket field?
• IIS SMTP service on the Kaseya server takes a long time to detect bad email addresses
• See more