Has anyone seen an event with ID 7000 in the system event log when deploying a client to a 64-bit server? Error description is "The SMS Process Event Driver service failed to start due to the following error: The system cannot find the file specified". Thanks!

This is an old post that evidently never got answered Did you get yoru answer? Is this SMS 2003 or Config Mgr 2007?

Closing due to no update in two months. If the issue comes back, feel free to open a new thread.

We Have the same issue here. Any help would be appreciated. Thanks, Event Type:ErrorEvent Source:Service Control ManagerEvent Category:NoneEvent ID:7000Date:10/22/2008Time:9:45:25 AMUser:N/AComputer:PCPVMEXCH07Description:The SMS Process Event Driver service failed to start due to the following error: The system cannot find the file specified. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If you restart the SMS Agent Host service, does it work then?

I am having the same problem. Everytime I restart the SMS Agent Host service I get the same error.

This is an old post, but I figured I'd post what I did to fix it in our environment. We updated our SCCM clients via vbscript and started getting this error on all of the X64 boxes afterwards. Investigating, I found that the upgrade changed the file name of the SMS Process Event Driver binary, but didn't update it in the registry. Before the update, the binary was likely named prepdrvAMD64.sys. Afterwards, it was named prepdrv.sys. To remediate, I lauched regedit and drilled down to HKLM\System\CurrentControlSet\Services\prepdrvr. I then edited the ImagePath string changing ONLY the name of the file. Before: \??\C:\WINDOWS\SysWOW64\CCM\prepdrvAMD64.sys After: \??\C:\WINDOWS\SysWOW64\CCM\prepdrv.sys After this, I could start the service via Devmgr or command line. From the command prompt, I typed "net start prepdrvr" and it started up successfully. If you do so via Devmgmt.msc, click View->Show Hidden Devices, Expand "Non-Plug and Play Drivers", Double-click on SMS Process Event Driver and click the Driver Tab. Click Start and it should start fine. However, the "exclamation point" won't clear until after a reboot. That's how we were able to fix it in our environment, although I'm not really sure why it even occurred in the first place. Either way, I figured I'd post up in the hopes that somebody may get some value out of it. Regards, D. Snider