Archive for the ‘Windows Service’ Tag

The Windows Modules Installer Service keeps starting and stopping.

Friday, December 12th, 2014

While checking a performance issue on a Windows 2008 server; I noticed the system log had these messages logged every three minutes or so.

The Windows Modules Installer service entered the running state.
The Windows Error Reporting Service service entered the running state.
The start type of the Windows Modules Installer service was changed from /
   demand start to auto start.
The start type of the Windows Modules Installer service was changed from /
   auto start to demand start.
The Windows Modules Installer service entered the stopped state.
The Windows Error Reporting Service service entered the stopped state.

The application log showed these messages roughly the same period of time (I didn’t seriously compare):

Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to /
   Active Directory Domain Services(R) for Windows user <domain\user>.
Without the corresponding UNIX identity of the Windows user, the user cannot access /
   Network File System (NFS) shared resources.
Verify that the Windows user is in Active Directory Domain Services and has access permissions.

I spoke to the users and they reported a previous experiment with NFS and they no longer needed the NFS service or client anymore. I removed the role and disabled the two services (server needed a reboot but it was in use).

The messages stopped.

Not sure why the modules installer was getting invoked and it wasn’t worth researching at this point.

I may look into it later.


saveIndx: Unknown index name from ELIM

Monday, August 11th, 2014

While reviewing a server for an issue; I noticed a few messages from LSF.

saveIndx: Unknown index name <name> from ELIM

This message is reported a missing flag from lsf.shared. A quick edit and a process and service restart and the message went away.


Can’t remote desktop to a windows 2008 R2 server

Tuesday, June 17th, 2014

This was a strange problem. I have a simple Windows 2008 R2 server with remote desktop services installed. Everything was properly configured. Plenty of licenses and diagnostics reported the license server was available.

The problem? Can’t access the server through remote desktop. No errors in the logs and the only message available to me was the generic:

Did all the noob checks and I even reloaded Remote Desktop Services, removed and re-added the server to AD.

Still no access.

I installed tightvnc as I did not want to live at the machine and found I had remote access.

I checked the registry to see if port 3389 was configured and it was.

I used portqueryui to see if the port was in use and it reported:

TCP port 3389 (ms-wbt-server service): NOT LISTENING!

A quick telnet to port 3389 confirmed this.

The firewall was not running and there wasn’t a web server or any other process trying to use that port and thus block Remote Desktop Services. I was tempted to declare too much time debugging this and reload but I decided to dig around the Net a little more and stumbled on an old discussion on technet.

As mentioned in the post by itdoug; I found the hidden device driver called “remote desktop services security filter driver” disabled (You just bring up the Device Manager, select show hidden devices and look under Non-Plug and Play Drivers).

I tried to enable it and it failed. I then uninstalled it and rebooted.

Remote Desktop worked after that.


The account used is a computer account. Use your global….

Thursday, July 25th, 2013

While scripting a report; I noticed a bogus error about a file version being wrong.

I examined the server in question and found the server service was not running.

I tried to start it but it stopped right away with the following message in the system event log.

The Server service terminated with the following error:
The account used is a computer account. Use your global user account or local user account to access this server.

Another server with the same problem would give this message:

Windows could not start the Server service on Local Computer Error: 1808: The account used is a computer account. Use your Global user account or local user account to access this server.

The service was configured correctly.

An odd problem and it’s cause was the fact a couple users placed URLs in the system Path variable (ie \\server\mount\dir).

Removing the entries and a reboot of the server corrected the issue.

Restart windows service from Linux

Monday, April 2nd, 2012

I had a request on how to restart the three LSF services from a script. The person worked on the farm team and did not relish the idea of using remote desktop or VNC.

I thought about a Powershell script or using a batch script to run the PsService from sysinternals. It looked simple as the command is as follows:

psservice \\<computer> -u <domain\username> -p password stop service <service name>

psservice \\<computer> -u <domain\username> -p password start service <service name>

I contacted the user and asked a couple more questions and learned she wanted to run the script from Linux. Of course this required a change in my approach as I like to keep things as simple as possible especially when a user will write their own script. I decided to abandon windows scripts and find away to see if Linux could handle this via the windows management interface.

Looking around the Net, I found a way I didn’t even consider. Simply install the Samba-Common. This offers the Net utility(or as close to it as possible) for the Linux host. The particular command in question is Net RPC service command:

To list out the services on a Windows computer:

net rpc service list -I <IP Address> -U “<domain\username>%<password>”

If you wish to use the command line; simply remove “%<password>” and you will be prompted for a password.

To start or stop a service; you would enter:

net rpc service {start|stop} <Service Name> -I <IP Address> -U “<domain\username>%<password>”

Again, if you wish to use the command line, simply remove “%<password>” and you will be prompted for a password.

The account used will have to have local admin privileges so if you decide to script it, secure the file to yourself since the password will be plain text.

Much as I would like to impress you with my great knowledge; there was a sense of urgency to the request so I went to the Net and I did get help from the following sites so credit must be given where credit is due.