Re: NTVDM encountered a hard error
- From: "Jenny wu \(MSFT\)" <v-yanniw@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Aug 2005 01:25:38 +0800
Hi,
Thank you for posting here!
I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
greatly appreciated!
For your description, I understand that you get the "NTVDM encountered a
hard error" when you run applications like TrendMicro or MS-DOS. if I am off
base, please don't hesitate to let me know.
Based on my research, the issue is a Server issue. I suggest that you post
this question into the microsoft.public.windows.server.general newsgroup.
you can find the newsgroup in following link:
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=microsoft.public.windows.server.general%20&dg=&cat=&lang=en&cr=US&pt=&catlist=73789D5F-4DB8-4D45-81E2-42064A655D3D&dglist=&ptlist=~Microsoft%20Windows%20Server
The reason why we recommend posting appropriately is you will get the most
qualified pool of respondents, and other partners who the newsgroups
regularly can either share their knowledge or learn from your interaction
with us. Also, this is to make sure that the responders can better track
the problem Thank you for your understanding.
I also would like to give you some information about the issue.
____________________________________________________________
how to configure to prevent access to 16-bit applications in Windows Server
2003
Requirements: At least Microsoft Windows Server 2003
Location: Computer Configuration\Windows Components\Application
Compatibility\
Description:
Specifies whether to prevent the MS-DOS subsystem (ntvdm.exe) from running
on this computer. This setting affects the launching of 16-bit applications
in the operating system. By default, the MS-DOS subsystem runs for all users
on this computer.
You can use this setting to turn off the MS-DOS subsystem, which will reduce
resource usage and prevent users from running 16-bit applications. To run
any 16-bit application or any application with 16-bit components, ntvdm.exe
must be allowed to run. The MS-DOS subsystem starts when the first 16-bit
application is launched. While the MS-DOS subsystem is running, any
subsequent 16-bit applications launch faster, but overall resource usage on
the system is increased.
If the status is set to Enabled, ntvdm.exe is prevented from running, which
then prevents any 16-bit applications from running. In addition, any 32-bit
applications with 16-bit installers or other 16-bit components cannot run.
If the status is set to Disabled, the default setting applies and the MS-DOS
subsystem runs for all users on this computer.
If the status is set to Not Configured, the default applies and ntvdm.exe
runs for all users. However, if an administrator sets the registry DWORD
value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault to
1, the default changes to prevent all 16-bit applications from running.
Note
This setting appears in both Computer Configuration and User Configuration.
If both settings are configured, the Computer Configuration setting
overrides.
ADM File: system.adm
-------------------------------------------------------------------------------
You can refer to the following KB articles to troubleshooting the issue:
Troubleshooting NTVDM and WOW Startup Errors
http://support.microsoft.com/?id=220155
Troubleshooting MS-DOS-Based Programs in Windows
http://support.microsoft.com/?id=s65214
Entries in Config.nt or Autoexec.nt May Cause NTVDM Errors
http://support.microsoft.com/?id=156687
The Ntvdm.exe program may quit unexpectedly on non-VME processors
http://support.microsoft.com/?id=817901
Disabling the MSDOS and WOWEXEC Subsystems on Terminal Server
http://support.microsoft.com/?id=220159
APPSEC.EXE Application Security Tool: Cannot Add NTVDM.EXE As Documented
http://support.microsoft.com/?id=279639
The Art of Performance Monitoring
http://www.microsoft.com/resources/documentation/windowsnt/4/workstation/reskit/en-us/01art.mspx
I apprecitate you understanding. I am looking forward to work with you in
future.
Have a nice day!
Best Regards,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check
the "Notify me of replies" box to receive e-mail notifications when there
are any updates in your thread. When responding to posts via your
newsreader, please "Reply to Group" so that others may learn and benefit
from your issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
"AEV" <tvaluikas@xxxxxxxxxxx> wrote in message
news:%23rT3XyClFHA.2156@xxxxxxxxxxxxxxxxxxxxxxx
> Crina,
>
> I need some help and you have the only link on the net talking about the
> problem.
>
> First off I am sorry for posting in the SBS group twice (nested it the
> first time) but I have no choice. I am
> running 2003 Stanard Server and am currently working on a major
> deployment.
> We have just noticed that on random servers we are getting "NTVDM
> encountered a hard error" when running apps like TrendMicro or command
> from
> start | run. I reviewed the below message thread you had from this group
> and
> indeed I cannot run SYSEDIT on the servers in question. It even gets more
> interesting from there. We have two domains and logging into SERVER1 with
> my
> domain1 acct I can run SYSEDIT. However logging into SERVER1 with my
> domain2
> acct I get the "NTVDM encountered a hard error". Others logging in get no
> errors, while other may error on both accounts. very weird. I am wonder if
> this might be somewhat of an undocumented bug?
> All servers are NT2003 Standard SP1 with all patches to date.
>
> To toss more unto it some servers are DC's and some are just member
> servers.
>
> Thanks
> Tony
>
.
- Prev by Date: Fatal error of incoming Fax
- Next by Date: (New Subject): How to eliminate prompt for credentials when using RPC over HTTP
- Previous by thread: Fatal error of incoming Fax
- Next by thread: SSL Publishing to WEB Server and Disable Binding
- Index(es):
Relevant Pages
|
