Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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.

share|improve this question

4 Answers 4

up vote 2 down vote accepted

I found an workable solution:

reg query "HKLM\System\CurrentControlSet\Services\<serviceName>" /v "ImagePath"

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

share|improve this answer

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.

share|improve this answer

Try it using the wmic command line utility. Here's an example of a service on my machine called CrashPlanService.

C:\Users\Ben>wmic service CrashPlanService get PathName

"C:\Program Files\CrashPlan\CrashPlanService.exe"

Basically, wmic service <<YourService>> get PathName.

share|improve this answer
Doesn't quite work. But, on the other hand, this works: "wmic service | find "<servicename>" –  djangofan Nov 22 '11 at 23:57
@djangofan what output do you get, and with which service? Maybe you've got a different version of wmic (I'm on Windows 7 SP1)? –  Ben Pilbrow Nov 23 '11 at 0:34
@Ben Pilbrow That didn't work for me either. wmic isn't getting the path name (just returns "PathName" with nothing on the following line). Not sure if this is because there are a lot of parameters embedded in the path making it very long. –  Jared Nov 23 '11 at 14:53
worked for me but i had to process the result a little: ((wmic service SQLBrowser get PathName) -match """)[0].replace(""", "") –  19kt4 Nov 23 '12 at 0:09

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:\Windows\System32\svchost.exe -k NetworkService

share|improve this answer
Unfortunately, I can't depend on powershell since XP doesn't have it by default. I need support for XP, server 2008, and 7, all without installing any additional software. –  Jared Nov 23 '11 at 17:48
@Jared that's too bad. You're unable to run this from a single machine against a bunch of remote machines? –  MDMarra Nov 23 '11 at 18:24
No this is actually a bit of script to go in the uninstaller for an application. I figured out a solution that works and added an answer for it though. –  Jared Nov 23 '11 at 20:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.