Terminal Server 2003 has NTVDM error at logon.

l have a win 2003 Terminal server and when you log on as any AD user it will display this error:

NTVDM.EXE - System Error

NTVDM encountered a hard error.

error
Options are close or ignore.

If you click ignore a dos box comes up and displays the commands for drive mappings from the AD logon script.


error2
If you click close or ignore it simply progresses to the next drive mapping map request in the logon script....

error3
It does this for every drive mapping request in the logon script once you click close or ignore and will finally go away once all the drives have been requested to map from the logon script.

The other odd thing is that if you simply use control alt delete and endtask the error at logon all the mapped drives are already mapped and operational. So im not sure why this is happening.

I tried installing this hotfix from microsoft but it did not resolve the error.

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

Anyone got any other ideas how to resolve?

Thanks in advance for your feedback/suggestions!
IT_Field_TechnicianAsked:
Who is Participating?
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.

Adam LeinssServer SpecialistCommented:
I would check config.nt and autoexec.nt for any rogue settings:

http://support.microsoft.com/kb/314106
0
IT_Field_TechnicianAuthor Commented:
There are no rogue settings in the config.nt or the autoexec.nt.

Thanks!
0
IT_Field_TechnicianAuthor Commented:
Anyone have any other suggestions to resolve this one?
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

IT_Field_TechnicianAuthor Commented:
I beleive this related to something in active directory but im not sure where to look.
0
IT_Field_TechnicianAuthor Commented:
I guess im keeping my own question alive here - I have been reviewing the errors that I am seeing in the logs and they are pointing me to check the group policy for the terminal server. However, the group policy on the terminal server says "not configured" for every single option.

So I have moved to looking at the group policy on the domain controller but there again it says "not configured" for all options!

So whats is controlling the group policy for my terminal server????????????? Any ideas?
0
Adam LeinssServer SpecialistCommented:
I would run the command "set" from the server having the issue and then "set" from a working server and compare the two for differences.  I suspect it's a bad variable in the environmental settings for your command/cmd environment.  You would do this by running "cmd.exe" and then "set".
0
IT_Field_TechnicianAuthor Commented:
Im checking this now. thanks you!
0
IT_Field_TechnicianAuthor Commented:
All the environment variable pretty much match up and the only extra thing that is on the server in questions set results is this:

__COMPAT_LAYER=EnableNXShowUI

Any ideas what this is and if its needed?
0
Adam LeinssServer SpecialistCommented:
Not sure what that is, if you go into

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\AppCompatFlags\Layers

Is it listed there?
0
IT_Field_TechnicianAuthor Commented:
regedit
Heres what I see in there.
0
Adam LeinssServer SpecialistCommented:
It has something to do with application compatibility, but why would explorer.exe be listed there?  I would be tempted to right-click on Layers, do an export to the C: drive and then remove the whole explorer.exe key and then see if you get different results with mapping drives.
0
Sudeep SharmaTechnical DesignerCommented:
Did you checked the following registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation (should be 0)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\Win95TruncatedExtensions value (should be 1)

Did you checked for the path of the Temp directory in User Profile?

Please check the following article which has more information on the points above.

http://social.technet.microsoft.com/Forums/windowsserver/en-US/aaede3d8-9372-4449-b20f-9adc05a9e6f7/ntvdm-encountered-a-hard-error?forum=winservergen

Sudeep
0

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
IT_Field_TechnicianAuthor Commented:
Adam,

I will try your suggestion when i could schedule some downtime to restart the server after making the suggested change and let you know how it goes....


Sudeep,

i was looking into your response and i noticed that some of the users that log onto this server have a local profile and others have a roaming profile:

Question
I dont beleive we even use roaming profiles and wondered what would be the impact if i changed all users to local profile?

Will i need to reconfigure outlook and such (remap network drives) on each users profile on the server?

Will they lose dekstop icons if i do this? Will it recreate a new profile for them if i do this?

thanks!
0
IT_Field_TechnicianAuthor Commented:
This is still open
0
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.