• 5

I need to query a windows service for the path to it's executable via the command prompt. I think the way I would do this is:sc qc myServiceName, but when I do that, I get the following error:

[SC] QueryServiceConfig FAILED 122:

The data area passed to a system call is too small.

[SC] GetServiceConfig needs 1094 bytes

I think this means that the sc command is sending a data structure to some other library that is too small for the data that needs to be returned. Instead of SC nicely retrying with a larger data structure (1094 bytes) it bombs out and gives me this ugly error message. Thanks Micro$oft.

So is there a way to work around this error? I just need the path to the executable, but will parse it out of some other text if needed.

You can do this in PowerShell with a WMI query like this:

$service = get-wmiobject -query 'select * from win32_service where name="winrm"'; echo $service.pathname

This will give you the full path, including options as they are shown in services.msc. Just replace winrm in my example with whatever service you want to search for.

The above query for winrm should output C:WindowsSystem32svchost.exe -k NetworkService

  • 1
Reply Report

I found an workable solution:

reg query "HKLMSystemCurrentControlSetServices<serviceName>" /v "ImagePath"

Of course this needs some parsing, but it gives me the full path that the services.msc dialog box provides.

  • 1
Reply Report

I encountered this problem too when trying to get the details of a service where the path to the executable was very long. This discussion contains a workaround; you can pass a buffer size as an argument to sc qc. That is, if you do:

sc qc <service name> 5000

the "data area passed to a system call is too small" error goes away.

Also see SC QC MSDN page:

sc [<ServerName>] qc [<ServiceName>] [<BufferSize>]


<BufferSize> Specifies the size (in bytes) of the buffer. The default buffer size is 1,024 bytes.

  • 4
Reply Report