• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9897
  • Last Modified:

MSGINA Event ID: 1010

Is there a way to find out which users has this problem?

Event Type:      Error
Event Source:      MsGina
Event Category:      None
Event ID:      1010
Date:            2/12/2007
Time:            12:52:37 PM
User:            N/A
Computer:      SERVER
Failed to set the user's home directory (Drive H: connected to Share \\server\Users).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 55 00 00 00               U...    
1 Solution
Failed to set the user's home directory (Drive H: connected to Share \\server\Users)...

Not sure, but I would think there is a problem ... check the users profile... make sure that the format is \\server\users\jsmith


aelroyAuthor Commented:
its a little hard to determine which profile it is. it there a utility that can tell me which user tried to login?

also, is there a way to find out last logon time for all users?
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

You can go to the security log (event viewer) and match the time of the above event with that in the security log and match the two.  The security log will tell you who/what attempted to set the home directory.  From there, you can debug the issue.
I'm pretty new to EE so I don't know what to do here, exactly.  My solution works every time -- not very brilliant but it gets the job done...

Bad Had
I got rid of my MSgina even 1010!!

I've just spend three days trying to find the answer as to why I 'm getting MSgina event 1010 errors.
I found when I logged onto a domain controller using remote desktop it didn't map my user area and a new event 1010 was logged.

I tried to map my home area manually from command prompt net use x: \\crdc01\users\aday and I was told " The local device name is already in use"

I opened up disk manager and the engineer that build the server had assigned the cd-rom the letter X so when I was logging on it was being denied! I changed the drive letter to z and all users have there home drives again and the msgina events have gone away ;)
VBScripts, net use commands, batch files, etc. can all bomb if there are any physical drives already mapped.  ALWAYS check "my computer" and disk manager to be sure that there will not be conflicts.
i found another solution for microsoft.
Here is http://support.microsoft.com/?scid=kb%3Ben-us%3B836683&x=13&y=13
Our solution was to restart the workstation service from the command prompt.  
cmd > net start workstation

I believe a windows update hung or caused an issue.  after researching the topic there were a lot of responses that involved the fact that the server might have a local drive with the same drive letter which the person's mapped drive was trying to use.  So i searched for how to view what drives were currently being used and came across the 'net view', 'net use', 'net session', etc.  when i went to run one of them it told me the workstation service was not started and to type 'net start workstation'.  i started it up and voila!
Failed MS Update caused our issue also.  Apparently a failed Microsoft Update stopped several services, including Workstation Service. Service issues presented themselves when users would not receive drive mappings when launching a TS application.  Starting services worked to resolve this in our ENV.  

There were other Automatic services that were also stopped.  

Thanks for the tip, this saved me from having to reboot the server during Prod hours.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now