Catelog of Event IDs and Sources

[Thomas M.]

I have been working on a problem involving some errors in my System log. I
was able to solve the problems, but it seems like the process was more
difficult than it should have been because I had a hard time figuring out
from the error code exactly which service was causing the problem. I had
some 4008 and 4010 errors and the LPDSVC service was the source. It turns
out that the TCP/IP Print Services service was not started. The problem was
that the information I found regarding these errors never indicated a
linkage between LPDSVC and the TCP/IP Print Services service. If it had,
starting up that service would have been my first move. It would be handy
if there was a list along the lines of the following:

Source Services
-------- ---------
LPDSVC TCP/IP Print Services
any other service that are related to LPDSVC

Is there a way to get a list, or is there a catalog somewhere, of all the
error sources and their corresponding services?

--Tom

 

[Wesley Vogel]

LPDSVC is the SERVICE_NAME. TCP/IP Print Services is the DISPLAY_NAME.

Services - Service Name & Display Name

There are several ways to do this. Here are three that I know of.

Open Services...
Start | Run | Type: services.msc | Click OK |
Scroll down to and double click the service you want to stop |
On the General tab, Service name: take note of the Service Name not the
Display Name | Close Services

Look in...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

The command:

sc query state= all

will display the SERVICE_NAME and DISPLAY_NAME of all services & drivers.

Any commands using the command prompt will require using the Service Name
not the Display Name.

I.e. Net Stop, Set Start, SC commands, etc.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Thomas M.]

First off, let me apologize for taking so long to reply. Truth be told, I
forgot that I had posted this message, probably because the immediate
problem had been solved so the issue was not on my mind as much.

That being said, thanks for the excellent information! The first method
doesn't work so well in the situation that I described because you would
need to know the display name of the service, and that's the information
that I was missing, but it is still useful for verifying that you've found
the right service. The second and third methods would both work in the
situation that I had, and I guess that my personal preference would be the
third method. The reason that I like the third method is that it can be put
into a batch file that redirects the output to a text file and then opens
that text file. You can set a shortcut to the batch file, so the
information is just a few clicks away. I created the following batch file
and then created a shortcut to run the file:

@Echo off

:: Writes information regarding services to a text file.
sc query state= all > Services.txt

:: Opens the text file.
Services.txt

--Tom