Hello,
I've had Email Parser setup and running great on my windows 7 x64 box for a couple of months and I love it. I am trying to set it up so that is will continue to check for emails and parse them even when no user is logged in and I'm at a dead end. I have enabled it to run as a windows service, verified that the service is starting up and authenticating correctly, however it will not retrieve emails or parse them until I log in to the machine and run the executable. Is this expected behavior? should I be able to run this without a user being logged in?
Thanks for whatever guidance!
I've had Email Parser setup and running great on my windows 7 x64 box for a couple of months and I love it. I am trying to set it up so that is will continue to check for emails and parse them even when no user is logged in and I'm at a dead end. I have enabled it to run as a windows service, verified that the service is starting up and authenticating correctly, however it will not retrieve emails or parse them until I log in to the machine and run the executable. Is this expected behavior? should I be able to run this without a user being logged in?
Thanks for whatever guidance!
The Email Parser service is meant to be run wether or not the user is logged in. It should parse emails even if the user is logged off.
We will investigate this issue. Thanks for posting
We will investigate this issue. Thanks for posting
Any update on this issue?
We are experiencing the exact same thing. If the issue can't be easily identified and resolved, we need to run switch to alternative software, which would be a shame - AEP perfectly fits our needs.
Sounds a lot like others are experiencing this issue as well:
troubleshooting-f4/service-is-running-b ... -t317.html
We are experiencing the exact same thing. If the issue can't be easily identified and resolved, we need to run switch to alternative software, which would be a shame - AEP perfectly fits our needs.
Sounds a lot like others are experiencing this issue as well:
troubleshooting-f4/service-is-running-b ... -t317.html
I think this issue has been fixed in the latest release(4.5). I've even test this myself. What version of the program are you using? (see Preferences > About)
Of course if the problem persists it will be fixed as soon as possible. This is a very important feature.
If you have an older version, first uninstall the service add-on and the program itself. Then download both from the download section of the web site and install. First Email Parser then the service add-on
Of course if the problem persists it will be fixed as soon as possible. This is a very important feature.
If you have an older version, first uninstall the service add-on and the program itself. Then download both from the download section of the web site and install. First Email Parser then the service add-on
Hi Support,
I have this problem too.
I use the latest version of Email Parser (v 4.5).
I installed the Email Parser, then I created the parsing routine.
After that, I installed the service and connected both together.
I rebooted the system to be sure, everything is working.
The service was running but did not processed any E-Mails. After I launched the UI-Application the mail processing started. I closed the Mail-Processing and it continued to process.
But that is not the expected behaviour of the service.
So.... What went wrong?
I tried it on two systems:
Windows 10 Pro and Windows Server 2012 R2
I have this problem too.
I use the latest version of Email Parser (v 4.5).
I installed the Email Parser, then I created the parsing routine.
After that, I installed the service and connected both together.
I rebooted the system to be sure, everything is working.
The service was running but did not processed any E-Mails. After I launched the UI-Application the mail processing started. I closed the Mail-Processing and it continued to process.
But that is not the expected behaviour of the service.
So.... What went wrong?
I tried it on two systems:
Windows 10 Pro and Windows Server 2012 R2
Hi there,
Contact support via email. We will probably need to access the machine where Email Parsing is running to see what could be wrong.
Contact support via email. We will probably need to access the machine where Email Parsing is running to see what could be wrong.
- All times are UTC -
