We had a problem earlier today with the server and it appears that numerous connections were cut off and the lock files either still exist or are unable to be created. I have stopped and restarted all the services numerous times but this has not remedied the situation.
How can I remove the lock file that is causing this error manually?
Well I really appreciate that response for the future. It turns out that my problem is MUCH weirder. I started analyzing the users postoffice files and folders to see what was different from the users who were logging in without issue and it turns out that all these users (about 25 of them) had no "inbox" folder. It had been deleted. I am sure these users didn't delete the folders themselves, but I have no idea why this would happen.
The only way I could see this occuring programatically ie via MailEnable and not something that has physically deleted the folders is when an upgrade was performed a person upgrading selected to install the program in a new program location. This would mean that your install is in two locations on your server and the inboxes for the config tab folders are not created until they are accessed via the ME Admin MMC.
Thanks for the reply, but this was not the case. MailEnable started throwing these errors in the middle of a day. we hadn't touched the install in quite a while. this is a server that's been running ME for over 2 years with no problems like this. Very odd. I'll re-post if I see any other interesting info in the logs or anything.
I had a similar problem after testing the beta version of the Statistics application. When I uninstalled it a number of inbox folders were removed for some reason.
Honestly until you said that I couldn't have imagined that that would have been the problem. But that is EXACTLY what happened. My partner was testing out the statistics app and that is right when the problem started.
I'll submit some beta feedback. I just went back and re-read the page where the actual beta stats app is posted and it does clearly state that I shouldn't have installed it on a live production install. That is our fault. But this is probably valuable feedback for ME on this app. It was a huge problem for us last week.