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
0000: 55 00 00 00               U...    
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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?
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
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.  
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.