Results 1 to 9 of 9

Thread: NTVDM encountered a hard error

  1. #1
    Chad Guest

    NTVDM encountered a hard error

    We have recently upgraded our Terminal Server to 2003 SP1. Users are now
    getting a "NTVDM encountered a hard error" when they try to run a 16 bit app.
    Any ideas?

  2. #2
    CL Guest

    Re: NTVDM encountered a hard error

    Hi Chad,

    Have the file permissions on the 16 bit app's location changed?

    Coraleigh

    "Chad" <Chad@discussions.microsoft.com> wrote in message
    news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    > We have recently upgraded our Terminal Server to 2003 SP1. Users are now
    > getting a "NTVDM encountered a hard error" when they try to run a 16 bit
    > app.
    > Any ideas?




  3. #3
    Chad Guest

    Re: NTVDM encountered a hard error

    Don't think so. The app directory is actually on a different server. It's
    just a shortcut on the Terminal Server. I think the upgrade to SP1 is what
    changed something. I'm a domain admin and I get the same error.

    "CL" wrote:

    > Hi Chad,
    >
    > Have the file permissions on the 16 bit app's location changed?
    >
    > Coraleigh
    >
    > "Chad" <Chad@discussions.microsoft.com> wrote in message
    > news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    > > We have recently upgraded our Terminal Server to 2003 SP1. Users are now
    > > getting a "NTVDM encountered a hard error" when they try to run a 16 bit
    > > app.
    > > Any ideas?

    >
    >
    >


  4. #4
    CL Guest

    Re: NTVDM encountered a hard error

    Check your Group Policy and make sure that Computer
    Configuration/Administrative Templates/Windows Components "Prevent access to
    16-bit applications" is set to Disabled. Also check the registry and make
    sure that the DWORD
    value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault is
    set to 0.

    Coraleigh

    "Chad" <Chad@discussions.microsoft.com> wrote in message
    news:3B8B257E-4FC1-4FD7-8B97-580A16743F26@microsoft.com...
    > Don't think so. The app directory is actually on a different server.
    > It's
    > just a shortcut on the Terminal Server. I think the upgrade to SP1 is
    > what
    > changed something. I'm a domain admin and I get the same error.
    >
    > "CL" wrote:
    >
    >> Hi Chad,
    >>
    >> Have the file permissions on the 16 bit app's location changed?
    >>
    >> Coraleigh
    >>
    >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    >> news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    >> > We have recently upgraded our Terminal Server to 2003 SP1. Users are
    >> > now
    >> > getting a "NTVDM encountered a hard error" when they try to run a 16
    >> > bit
    >> > app.
    >> > Any ideas?

    >>
    >>
    >>




  5. #5
    CL Guest

    Re: NTVDM encountered a hard error

    Check your Group Policy and make sure that Computer
    Configuration/Administrative Templates/Windows Components "Prevent access to
    16-bit applications" is set to Disabled. Also check the registry and make
    sure that the DWORD
    value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault is
    set to 0.

    Coraleigh

    "Chad" <Chad@discussions.microsoft.com> wrote in message
    news:3B8B257E-4FC1-4FD7-8B97-580A16743F26@microsoft.com...
    > Don't think so. The app directory is actually on a different server.
    > It's
    > just a shortcut on the Terminal Server. I think the upgrade to SP1 is
    > what
    > changed something. I'm a domain admin and I get the same error.
    >
    > "CL" wrote:
    >
    >> Hi Chad,
    >>
    >> Have the file permissions on the 16 bit app's location changed?
    >>
    >> Coraleigh
    >>
    >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    >> news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    >> > We have recently upgraded our Terminal Server to 2003 SP1. Users are
    >> > now
    >> > getting a "NTVDM encountered a hard error" when they try to run a 16
    >> > bit
    >> > app.
    >> > Any ideas?

    >>
    >>
    >>




  6. #6
    Chad Guest

    Re: NTVDM encountered a hard error

    "Prevent access to 16-bit applications" is set to "not configured" under
    Computer Configuration and User Configuration. DisallowedPolicyDefault is
    set to 0.

    The application in question is being run from Windows 2000 Server. However,
    I did not find such a policy on that OS and users can access the application
    fine over the LAN, just not the Terminal Server running on Server 2003 SP1.

    "CL" wrote:

    > Check your Group Policy and make sure that Computer
    > Configuration/Administrative Templates/Windows Components "Prevent access to
    > 16-bit applications" is set to Disabled. Also check the registry and make
    > sure that the DWORD
    > value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault is
    > set to 0.
    >
    > Coraleigh
    >
    > "Chad" <Chad@discussions.microsoft.com> wrote in message
    > news:3B8B257E-4FC1-4FD7-8B97-580A16743F26@microsoft.com...
    > > Don't think so. The app directory is actually on a different server.
    > > It's
    > > just a shortcut on the Terminal Server. I think the upgrade to SP1 is
    > > what
    > > changed something. I'm a domain admin and I get the same error.
    > >
    > > "CL" wrote:
    > >
    > >> Hi Chad,
    > >>
    > >> Have the file permissions on the 16 bit app's location changed?
    > >>
    > >> Coraleigh
    > >>
    > >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    > >> news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    > >> > We have recently upgraded our Terminal Server to 2003 SP1. Users are
    > >> > now
    > >> > getting a "NTVDM encountered a hard error" when they try to run a 16
    > >> > bit
    > >> > app.
    > >> > Any ideas?
    > >>
    > >>
    > >>

    >
    >
    >


  7. #7
    CL Guest

    Re: NTVDM encountered a hard error

    This KB may be worth a read...
    http://support.microsoft.com/default...b;en-us;220155


    "Chad" <Chad@discussions.microsoft.com> wrote in message
    news:4AB4195B-3D76-4BB5-961A-BDFC0504EB01@microsoft.com...
    > "Prevent access to 16-bit applications" is set to "not configured" under
    > Computer Configuration and User Configuration. DisallowedPolicyDefault is
    > set to 0.
    >
    > The application in question is being run from Windows 2000 Server.
    > However,
    > I did not find such a policy on that OS and users can access the
    > application
    > fine over the LAN, just not the Terminal Server running on Server 2003
    > SP1.
    >
    > "CL" wrote:
    >
    >> Check your Group Policy and make sure that Computer
    >> Configuration/Administrative Templates/Windows Components "Prevent access
    >> to
    >> 16-bit applications" is set to Disabled. Also check the registry and
    >> make
    >> sure that the DWORD
    >> value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault
    >> is
    >> set to 0.
    >>
    >> Coraleigh
    >>
    >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    >> news:3B8B257E-4FC1-4FD7-8B97-580A16743F26@microsoft.com...
    >> > Don't think so. The app directory is actually on a different server.
    >> > It's
    >> > just a shortcut on the Terminal Server. I think the upgrade to SP1 is
    >> > what
    >> > changed something. I'm a domain admin and I get the same error.
    >> >
    >> > "CL" wrote:
    >> >
    >> >> Hi Chad,
    >> >>
    >> >> Have the file permissions on the 16 bit app's location changed?
    >> >>
    >> >> Coraleigh
    >> >>
    >> >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    >> >> news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    >> >> > We have recently upgraded our Terminal Server to 2003 SP1. Users
    >> >> > are
    >> >> > now
    >> >> > getting a "NTVDM encountered a hard error" when they try to run a 16
    >> >> > bit
    >> >> > app.
    >> >> > Any ideas?
    >> >>
    >> >>
    >> >>

    >>
    >>
    >>




  8. #8
    Chad Guest

    Re: NTVDM encountered a hard error

    I was able to open sysedit.exe ok, which the KB article says means nothing is
    wrong with NTVDB or WOW. But it also says this article only applies to
    Windows NT Server.

    "CL" wrote:

    > This KB may be worth a read...
    > http://support.microsoft.com/default...b;en-us;220155
    >
    >
    > "Chad" <Chad@discussions.microsoft.com> wrote in message
    > news:4AB4195B-3D76-4BB5-961A-BDFC0504EB01@microsoft.com...
    > > "Prevent access to 16-bit applications" is set to "not configured" under
    > > Computer Configuration and User Configuration. DisallowedPolicyDefault is
    > > set to 0.
    > >
    > > The application in question is being run from Windows 2000 Server.
    > > However,
    > > I did not find such a policy on that OS and users can access the
    > > application
    > > fine over the LAN, just not the Terminal Server running on Server 2003
    > > SP1.
    > >
    > > "CL" wrote:
    > >
    > >> Check your Group Policy and make sure that Computer
    > >> Configuration/Administrative Templates/Windows Components "Prevent access
    > >> to
    > >> 16-bit applications" is set to Disabled. Also check the registry and
    > >> make
    > >> sure that the DWORD
    > >> value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault
    > >> is
    > >> set to 0.
    > >>
    > >> Coraleigh
    > >>
    > >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    > >> news:3B8B257E-4FC1-4FD7-8B97-580A16743F26@microsoft.com...
    > >> > Don't think so. The app directory is actually on a different server.
    > >> > It's
    > >> > just a shortcut on the Terminal Server. I think the upgrade to SP1 is
    > >> > what
    > >> > changed something. I'm a domain admin and I get the same error.
    > >> >
    > >> > "CL" wrote:
    > >> >
    > >> >> Hi Chad,
    > >> >>
    > >> >> Have the file permissions on the 16 bit app's location changed?
    > >> >>
    > >> >> Coraleigh
    > >> >>
    > >> >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    > >> >> news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    > >> >> > We have recently upgraded our Terminal Server to 2003 SP1. Users
    > >> >> > are
    > >> >> > now
    > >> >> > getting a "NTVDM encountered a hard error" when they try to run a 16
    > >> >> > bit
    > >> >> > app.
    > >> >> > Any ideas?
    > >> >>
    > >> >>
    > >> >>
    > >>
    > >>
    > >>

    >
    >
    >


  9. #9
    CB Guest

    Re: NTVDM encountered a hard error

    I had the same NTVDM Hard Error reported to me for a 16 bit application under
    terminal services.

    The answer was found by using the Filemon utility.

    Access denied message in the Filemon log.

    Corrected permissions and all okay.

    Obviously this will not apply to everyones problem but may help someone.

    CB

    "Chad" wrote:

    > I was able to open sysedit.exe ok, which the KB article says means nothing is
    > wrong with NTVDB or WOW. But it also says this article only applies to
    > Windows NT Server.
    >
    > "CL" wrote:
    >
    > > This KB may be worth a read...
    > > http://support.microsoft.com/default...b;en-us;220155
    > >
    > >
    > > "Chad" <Chad@discussions.microsoft.com> wrote in message
    > > news:4AB4195B-3D76-4BB5-961A-BDFC0504EB01@microsoft.com...
    > > > "Prevent access to 16-bit applications" is set to "not configured" under
    > > > Computer Configuration and User Configuration. DisallowedPolicyDefault is
    > > > set to 0.
    > > >
    > > > The application in question is being run from Windows 2000 Server.
    > > > However,
    > > > I did not find such a policy on that OS and users can access the
    > > > application
    > > > fine over the LAN, just not the Terminal Server running on Server 2003
    > > > SP1.
    > > >
    > > > "CL" wrote:
    > > >
    > > >> Check your Group Policy and make sure that Computer
    > > >> Configuration/Administrative Templates/Windows Components "Prevent access
    > > >> to
    > > >> 16-bit applications" is set to Disabled. Also check the registry and
    > > >> make
    > > >> sure that the DWORD
    > > >> value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault
    > > >> is
    > > >> set to 0.
    > > >>
    > > >> Coraleigh
    > > >>
    > > >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    > > >> news:3B8B257E-4FC1-4FD7-8B97-580A16743F26@microsoft.com...
    > > >> > Don't think so. The app directory is actually on a different server.
    > > >> > It's
    > > >> > just a shortcut on the Terminal Server. I think the upgrade to SP1 is
    > > >> > what
    > > >> > changed something. I'm a domain admin and I get the same error.
    > > >> >
    > > >> > "CL" wrote:
    > > >> >
    > > >> >> Hi Chad,
    > > >> >>
    > > >> >> Have the file permissions on the 16 bit app's location changed?
    > > >> >>
    > > >> >> Coraleigh
    > > >> >>
    > > >> >> "Chad" <Chad@discussions.microsoft.com> wrote in message
    > > >> >> news:C01F0D88-78EF-4AD2-8C79-2C4F575A839A@microsoft.com...
    > > >> >> > We have recently upgraded our Terminal Server to 2003 SP1. Users
    > > >> >> > are
    > > >> >> > now
    > > >> >> > getting a "NTVDM encountered a hard error" when they try to run a 16
    > > >> >> > bit
    > > >> >> > app.
    > > >> >> > Any ideas?
    > > >> >>
    > > >> >>
    > > >> >>
    > > >>
    > > >>
    > > >>

    > >
    > >
    > >


Similar Threads

  1. Replies: 3
    Last Post: 12-10-2011, 08:04 PM
  2. NTVDM CPU has encountered an illegal instruction
    By Nadhe in forum Windows XP Support
    Replies: 4
    Last Post: 02-08-2010, 04:27 PM
  3. ntvdm.exe has encountered an illegal instruction
    By im abcd in forum Operating Systems
    Replies: 12
    Last Post: 15-06-2010, 10:55 PM
  4. Replies: 5
    Last Post: 09-01-2010, 06:07 PM
  5. "NTVDM encountered a hard error"
    By Magnus Kirkerud in forum Windows Server Help
    Replies: 4
    Last Post: 30-09-2005, 06:43 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,640,108.99146 seconds with 17 queries