WatchDirectory home page
WatchDirectory Startseite (Deutsche Version)
Site WatchDirectory (Français)
  Welcome, Guest. Please Login or Register
YaBB - Yet another Bulletin Board
   
  HomeHelpSearchLoginRegister  
 
Page Index Toggle Pages: 1
wdPostman doesn't start any more (Read 3275 times)
Stan
YaBB Newbies
*
Offline



Posts: 20
wdPostman doesn't start any more
Jul 12th, 2013 at 5:16pm
 
Hi Gert,

We are happy users of WD since 2009 I think.

Today I had a problem with some stupid application filling up my C: drive on the server.

After resolving this, wdPostman service won't start. Restarted the server.
I tried uninstalling and installing the service, I even upgraded to the newest version of WD. Changed the user for the service.
No avail.

I have no relevant Event Viewer entries, nothing.

Is there any way to diagnose what may be the problem?

Help...

Kind regards
Stan
Back to top
 
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2233
The Netherlands
Re: wdPostman doesn't start any more
Reply #1 - Jul 12th, 2013 at 8:41pm
 
Hello Stan,

What happens when you run cmd.exe and enter the following commands:
C:
CD "\Program Files (x86)\WatchDirectory"
wdpostman -run

this will start wdpostman as "a normal program" (not as a Windows Service). Do you see any errors?

Maybe one of the messages waiting for wdpostman to deliver is corrupt and causes the issue. In that case clear the email queue, see
http://blog-en.gdpsoftware.com/2009/04/q-clear-email-queue.html

modified: changed -start to -run
Back to top
 

Gert Rijs - gert (at) gdpsoftware (dot) com
Blog: http://blog-en.gdpsoftware.com/
End Alzheimer's: http://www.alz.org&&...
WWW WWW GdPSoftware  
IP Logged
 
Stan
YaBB Newbies
*
Offline



Posts: 20
Re: wdPostman doesn't start any more
Reply #2 - Jul 13th, 2013 at 9:15am
 
Hi Gert,

Thank you very much for the reply.

Actually, I solved the issue myself half an hour later - the history database file was corrupt. When I removed it - wdPostman started with no issues.

I sure could have used some clue in the system Event Log (where services should signal issues), or an error file of some sort  at least Undecided  It was a lot of guesswork  Wink

I'm not sure why the history file got corrupt, I have WD installed on a different drive, and all the tasks are also on another drive, so why did running out of space on C: cause this?... Anyway, this seems as a pretty easy recovery situation, if the db is corrupt - rename it to .bak, create a new one automatically and put a history message to that effect in the new db.
This is a production machine and I count on it to be fault tolerant to a certain degree...

BTW, the history viewer was showing the contents (lots of "wdPostman service started" type messages, when I repeatedly tried to start the service), so it wasn't completely corrupt...

This is a first major issue with WD in 3 years, so it's pretty stable anyway Grin
Thanks again for the great application  Smiley

Cheers
Stan
Back to top
 
 
IP Logged
 
Page Index Toggle Pages: 1