none
PNRPsvc and p2pimsvc has failed to start

    Question

  • Hi there,

    I tried to set up a homegroup for my laptop so that other laptops can get acces to files on this laptop, but I do have a problem. I have research couple of websites and they had said to go into services.msc and look into  PEER Name Resolution Protocol and Peer Networking Grouping. I tried to start these two services , but  Peer Name Resolution Protocol shows an error 1079 :The account specified for this service is different from the account specified for other services running in the same process.The Peer Networking Grouping shows an error 1068 : the dependency service or group failed to start.

    I have also upload the network dignostics log for you guys to look at

    http://cid-5d27eace859ed426.skydrive.live.com/self.aspx/network%20dignostics%20log

    Do let me know as soon as possible as to how to fix this problems.

    Regards,

    Ranjeet Bassi

    Monday, April 26, 2010 3:52 PM

Answers

  • Hi,

     

    This issue can occur by virus or corrupted system files. To troubleshoot the issue, please try the following steps.

     

    1. Upgrade the virus definition and run a complete scanning on the machine.

     

    2. Copy the following files on another Windows 7 machine which Peer Name Resolution Protocol can start normally and import them to the problematic one.

     

    a. Locate the pnrpsvc.dll file under the folder C:\Windows\System32. Remove the old one and paste the new one.

     

    b. Navigate the following registry key on another Windows 7 machine and export it. Then, please copy and import it on the problematic machine.

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PNRPsvc

     

    If the issue persists after performing above suggestions, I suggest you run System File Checker (SFC) to verify whether any system file is corrupted.

     

    Thanks,

    Novak

    • Marked as answer by Novak Wu Thursday, May 06, 2010 9:02 AM
    Thursday, April 29, 2010 7:21 AM

All replies

  • Wow It's really surprising that 43 people viewed the discussion post , but didnt take their time to even reply to the post. I mean there must be someone who actually fixed this problem.
    Wednesday, April 28, 2010 10:27 PM
  • Hi,

     

    This issue can occur by virus or corrupted system files. To troubleshoot the issue, please try the following steps.

     

    1. Upgrade the virus definition and run a complete scanning on the machine.

     

    2. Copy the following files on another Windows 7 machine which Peer Name Resolution Protocol can start normally and import them to the problematic one.

     

    a. Locate the pnrpsvc.dll file under the folder C:\Windows\System32. Remove the old one and paste the new one.

     

    b. Navigate the following registry key on another Windows 7 machine and export it. Then, please copy and import it on the problematic machine.

     

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PNRPsvc

     

    If the issue persists after performing above suggestions, I suggest you run System File Checker (SFC) to verify whether any system file is corrupted.

     

    Thanks,

    Novak

    • Marked as answer by Novak Wu Thursday, May 06, 2010 9:02 AM
    Thursday, April 29, 2010 7:21 AM
  • I had the 1079 error which really was a 0x80630203 while attempting to start the PEER Name Resolution Protocol service.  All the suggestions didn't work until I found this post related to the XP Peer-to-Peer Networking Component:

    http://support.microsoft.com/kb/817754/en-us

    I fixed the permissions (in my case it was the MachineKeys folder) and voila after a reboot I have my homegroup problem fixed.


    Saturday, April 02, 2011 4:20 PM
  • One more comment.  The original problem likely arose because the poster changed the "Log on" account for the Peer Resolution Protocol service from "Local Service" to either the "Local System account" or a specific user id.  Once it is set back to "This account" with "Local Service" and the password blanked out, this particular issue should disappear (as long as all peer services use the same account) and the original problem will resurface.  That was my case which is why I posted the solution above.

    Saturday, April 02, 2011 4:33 PM