Service doesn’t start because no password is set for my user account

I am running G-Lock Email Processor and I’m trying to set up a rule which would update the remote database upon receiving bounced emails. I tried to run the service under a user account, but it resulted in logon failure because the access password is not set on my machine. What should I do to get the G-Lock Email Processor service started?

By default all modern versions of Windows have a Local Security policy that restricts users with blank passwords to logging on at the local console only. In other words, a user with a blank password must physically be at the computer in order to log on. The user cannot log on as a service, as a batch user, over a network, etc.

This can be changed by changing the policy under Local Policies -> Security Options. Or by changing the LimitBlankPasswordUse value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa to zero.

But, and this is very important, this will set up a serious hole in your security since users with blank passwords will now be able to log on remotely and blank passwords are pretty easy to guess.

With that said, we recommend that you either set up an access password for your account or use the Task Center in G-Lock Email Processor instead of the service.

Interested? Learn more about our G-Lock Email Processor email parser and extractor tool.

Was this article helpful?

Related Articles