Highlights

Monday, October 8, 2012

SOLVED! - System Error 2221 has occurred

For some reason, a user suddenly cannot use the "NET USE" command to map network drives. Windows logon is working, but accessing network shares become very strange, with "System Error 2221 has occurred" message. This probably is a stored credential problem.

SOLUTION: Press your Windows' Start / Launch, in "Search programs and files" field type "Credential Manager" and you should see it shows up on the list. Run it.

Check the stored credentials and remove related credentials, by click on the "Remove from vault". Now, try your NET USE command to map drives again.
Posted by at
Labels:

38 comments:

  1. AnonymousOctober 17, 2012 at 9:49 PM

    I was getting the same problem, drive mappings were not working.
    I deleted the entry in Credential Manager and rebooted, worked like a dream

    ReplyDelete
  2. AnonymousFebruary 18, 2013 at 7:57 AM

    just found this answer through various searches, and you have just solved a problem i have had for 2 days. Thank You so much

    ReplyDelete
  3. AnonymousMarch 28, 2013 at 11:18 AM

    Good work Jack.
    My situation is that all the people having this issue at my work are only getting it through the VPN. We have confirmed that a person would have to log off the VPN then clear the credentials required (and choose correctly from the myriad of listed items) then log back onto the VPN and clear the session credentials and go back through the VPN log off/on process again. We've confirmed it all a half a dozen times but still searching for that elusive permanent fix that removes the need for the laborious work-around of credential-clearing-log-on-off-on etc.
    Keep up the good work.
    Cheers,
    Grumpy Old IT Guy.

    ReplyDelete
  4. AnonymousJuly 10, 2013 at 2:43 AM

    Helped me today. Thanks. Trevor.

    ReplyDelete
  5. AnonymousJuly 26, 2013 at 3:13 AM

    Hello Jack. I work at a multinacional company, on Brazil's subsidiary. This post have just helped me a lot with an issue in Chile. Thanks! Gustavo, from Brazil.

    ReplyDelete
  6. AnonymousAugust 13, 2013 at 5:22 AM

    THAT'S THE FACT JACK! Thank you sir! This helped me too.

    ReplyDelete
  7. AnonymousSeptember 16, 2013 at 5:15 PM

    Thanks man, that did the trick

    ReplyDelete
  8. EldeeSeptember 23, 2013 at 7:18 PM

    Thanks a lot, that helps a lot on VPN / credential issues

    ReplyDelete
  9. AnonymousOctober 28, 2013 at 3:18 PM

    Thank you!

    ReplyDelete
  10. DEAD BLOGDecember 29, 2013 at 12:21 AM

    Excellent! Thank you! This solved a Windows Server 2012 Essentials based domain for accessing a windows 8.1 drive. Excellent!

    ReplyDelete
  11. AnonymousJanuary 6, 2014 at 8:33 AM

    Amazing! Saved me hours of aggravation. Thanks

    ReplyDelete
  12. AnonymousFebruary 19, 2014 at 7:34 PM

    thx, saved my ass with that one :)

    ReplyDelete
  13. AnonymousFebruary 22, 2014 at 1:10 AM

    worked perfect thank you

    ReplyDelete
  14. AnonymousJuly 15, 2014 at 9:42 PM

    Works!! Hot damn...Thank you!

    ReplyDelete
  15. Code CornerAugust 12, 2014 at 4:03 AM

    Awesome! Thank you so much!

    ReplyDelete
  16. AnonymousSeptember 11, 2014 at 3:39 PM

    thanks for the tip!! Appreciate it

    ReplyDelete
  17. AnonymousOctober 16, 2014 at 10:41 PM

    Nice one....Thanks

    ReplyDelete
  18. AnonymousOctober 24, 2014 at 10:27 PM

    Worked again, thanks!

    ReplyDelete
  19. AnonymousNovember 14, 2014 at 3:42 AM

    Had an SVP encounter this issue today. People freaked out.. Thank you for allowing me to calmly save the day.. The solution expressed here works like a charm.

    May also correct an error showing in the GUI of "An extended error has occured".

    ReplyDelete
  20. AnonymousDecember 5, 2014 at 5:08 AM

    I love you! This just saved me from a massive headache I was having for 2 days. Come to Jamaica and feel alright! DJ Archie.

    ReplyDelete
  21. AnonymousJanuary 20, 2015 at 2:45 AM

    great :D

    ReplyDelete
  22. AnonymousJanuary 30, 2015 at 9:53 PM

    Nice work! I'll try to remember credential manager next time. Very handy!

    ReplyDelete
  23. AnonymousMarch 11, 2015 at 4:09 AM

    I encountered this today - a user logged onto her PC with a local account (which she was not supposed to do) and tried to run an application that connected to an application server which munged the credential for that member server. Following these instructions on her PC fixed it and I learned something new at the same time! (I've also removed the local profile. Bad user, Bad!)

    ReplyDelete
  24. AnonymousMarch 27, 2015 at 10:02 PM

    Worked for me. A connection to our fileserver was using an incorrect username. I could only map the drive by IP address and not with FQDN

    ReplyDelete
  25. AnonymousAugust 22, 2015 at 4:57 AM

    I've been trying to figure out a strange file share access issue for an hour now. Finally caught this error after testing with net use and found this page. Removed the bad credentials and things were instantly fixed. Thanks!

    ReplyDelete
  26. AnonymousFebruary 21, 2016 at 7:01 PM

    Worked for me, too
    Thanks a lot for posting solutions,
    Axel

    ReplyDelete
  27. UnknownMarch 9, 2016 at 8:49 PM

    I owe you a beer next time you visit Oslo :)

    ReplyDelete
  28. AnonymousJuly 6, 2016 at 2:19 AM

    Worked for me!
    I was looking at TCP/IP settings and a dozen other things.
    Thanks for the help!!

    ReplyDelete
  29. UnknownAugust 11, 2016 at 7:34 AM

    Thaank you so much!! Worked like a charm.

    ReplyDelete
  30. It guyJanuary 7, 2017 at 8:11 AM

    Thx! U are The Best

    ReplyDelete
  31. UnknownJanuary 12, 2017 at 4:32 PM

    thank you ,this was the reason !!

    ReplyDelete
  32. AnonymousAugust 1, 2017 at 7:00 PM

    Would just like to add my appreciation as well - that did the trick. Will remember this one, very useful.

    ReplyDelete
  33. Terry PolzinSeptember 18, 2017 at 9:44 PM

    Yes, very useful

    ReplyDelete
  34. AnonymousJanuary 10, 2018 at 2:38 AM

    Thanks ran into this first time ever - it worked. Dave Ross

    ReplyDelete
  35. PaddyWhackeryMarch 5, 2018 at 11:32 PM

    Thank you

    ReplyDelete
  36. UnknownApril 3, 2018 at 9:56 PM

    Thanks Man! and 'thanks Microsoft'

    ReplyDelete
  37. UnknownApril 3, 2018 at 9:57 PM

    Thanks! ...in a sarcastic voice...'thanks Microsoft'

    ReplyDelete

Subscribe to: Post Comments (Atom)