locked
Peer Name Resolution Protocol, Peer Networking Grouping, PNRP Machine Name Publication Service cannot start, error code 0x806320a1

    Question

  • Hello,

     

    I am having trouble with my Homegroup settings in Windows 7 Professional, namely that though I can see other computers that should be in my Homegroup (and that can see me in their Homegroup) in the Network tab, I cannot access these computers in the Homegroup tab. Instead, I get the message that no other computers are in my Homegroup.

     

    I have tried the following up to now:

    - Deleting the contents of C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking

    - Enabling IPv6 in the Network settings (was always enabled)

    - Inserting a DisabledComponents Key in the registry for IPv6 and setting its value to "0"

    - Downloading "clean" PNRPsvc and p2pimsvc Registry keys and importing them (failed, as the keys seem to be in use even with stopped services on a clean boot)

    - Setting Peer Name Resolution Protocol, Peer Networking Grouping and PNRP Machine Name Publication Service to Automatic and to Log On via a local system account and attempting to restart them via services.msc

    When I tried this last step, I couldn't get any of the three named services to restart. Peer Name Resolution Protocol returns error code 0x806320a1 ("PEER_E_SERVICE_NOT_AVAILABLE - The Peer Collaboration infrastructure, which includes People Near Me, is not available. This code will also be returned whenever an attempt is made to utilize the Collaboration infrastructure from an elevated process" according to http://msdn.microsoft.com/en-us/library/dd433181%28VS.85%29.aspx), while Peer Networking Grouping and PNRP Machine Name Publication both return error 1068: "The Dependency Service or Group failed to start".

    Peer Networking Identity Manager, Homegroup Listener and Homegroup Provider all run (stop and start again) without any hitches.

    I cannot leave my Homegroup, even on a clean reboot ("Windows couldn't remove your computer from the Homegroup"), and it won't display my Homegroup Password, either. I can open the Change Password dialogue, but I cannot actually change a password ("Windows cannot set up a homegroup on this computer"). I have tried resharing some of my files to no effect.

    Starting the Homegroup Troubleshooter leads me to troubleshoot Network Options, which tells me (unsurprisingly) that "Either the Peer Name Resolution Protocol service (PNRPsvc) or the Peer Networking Identity Manager service (p2pimsvc) is not running", but cannot fix the problem. Skipping or canceling Network Diagnostics on the Homegroup Troubleshooter leads to an interesting result: although the troubleshooter tells me "Peer Networking Grouping Service isn't running" if allowed to finish its run, the missing homegroup computers actually appear in my homegroup tab just after canceling/skipping network diagnostics, before the troubleshooter finishes. These computers remain visible in my homegroup and can be browsed, but cannot be found without re-running the troubleshooter if I navigate away from the homegroup in the same window, then try to return.

     

    This issue appears to be distinct from the very similar issue which can be solved by deleting files from C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking, as those files have NOT magically reappeared and I'm still having the problem. Does anybody have any idea what I can do?

    • Moved by Max Wang_Chinasoft Wednesday, April 27, 2011 11:27 PM forum consolidation (From:Networking)
    Wednesday, December 15, 2010 12:43 AM

All replies

  • It could be idstore.sst is corrupted. This post may help: Can't start Peer Name Resolution Protocol: error 0x806320a1
    Bob Lin, MS-MVP Networking, Internet, Routing, VPN Troubleshooting on

    http://www.ChicagoTech.net

    How to Setup Windows, Network, VPN & Remote Access on

    http://www.howtonetworking.com

    Wednesday, December 15, 2010 10:28 PM
  • Hi,

     

    Thanks for the response. Unfortunately, I cannot open the link you provided, as it returns a "Page not Found" error. I have already tried deleting idstore.sst (see above, deleting the contents of C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking); it did not resolve the issue.

    Thursday, December 16, 2010 10:32 AM
  • Or try the link: http://www.chicagotech.net/netforums/viewtopic.php?f=3&t=14250

    also quoted: "After deleting, idstore.sst, i tried to leave my homegroup but it still didn't work. Then i clicked troubleshoot homegroup and it displayed, problem found and fixed by "Homegroup needs to be refreshed." It refreshed and after that, tada! I was able to leave my homegroup".


    Bob Lin, MS-MVP Networking, Internet, Routing, VPN Troubleshooting on

    http://www.ChicagoTech.net

    How to Setup Windows, Network, VPN & Remote Access on

    http://www.howtonetworking.com

    Friday, December 17, 2010 10:05 PM
  • Again, let me quote from my original post:

     

    "I cannot leave my Homegroup, even on a clean reboot ("Windows couldn't remove your computer from the Homegroup"), and it won't display my Homegroup Password, either. I can open the Change Password dialogue, but I cannot actually change a password ("Windows cannot set up a homegroup on this computer"). I have tried resharing some of my files to no effect.

    Starting the Homegroup Troubleshooter leads me to troubleshoot Network Options, which tells me (unsurprisingly) that "Either the Peer Name Resolution Protocol service (PNRPsvc) or the Peer Networking Identity Manager service (p2pimsvc) is not running", but cannot fix the problem . Skipping or canceling Network Diagnostics on the Homegroup Troubleshooter leads to an interesting result: although the troubleshooter tells me "Peer Networking Grouping Service isn't running" if allowed to finish its run, the missing homegroup computers actually appear in my homegroup tab just after canceling/skipping network diagnostics, before the troubleshooter finishes. These computers remain visible in my homegroup and can be browsed, but cannot be found without re-running the troubleshooter if I navigate away from the homegroup in the same window, then try to return."

    Saturday, December 18, 2010 9:40 AM