| |
October 14/2008
Here is something another tech mentioned that solved an NTVDM freezing with word
integration:
The
issue is in the start-up that loads the modules for Dell support Centre.
Anything pointing to Dell Support needs to be disabled ('sprtcmd' I believe is
the real culprit) but for the sake of it not updating that module again, I just
disabled all that were pointing to the Dell support.
Jan 29/2008
This next solution is still being tested.
Click here to find out more about
setting affinity to 1 single CPU.
Jan 16/2008
Here is a statement someone made that experienced the same thing.
My solution to came to mind when i realized
i was working in a rdp client session, which of course can't go full-screen. So
I try going windowed mode and everything works just fine. And when I have users
log onto domain without terminal session the program works fine too with or
without full screen mode.
Jan 15/2008
Most ntvdm errors can be fixed
by modifying the TEMP and TMP environment settings to make
them 8.3 namespace compatible.
The default path for the TEMP directories is %USERPROFILE%\Local
Settings\Temp
Which will (typically) expand to something like:
C:\Documents and Settings\Administrator\Local Settings\Temp
16 bit applications can’t manage the spaces or long file
names, and will generate
ntvdm
errors, even if they are not explicitly referencing the TEMP
directory.
You can either use a common temp location (e.g. C:\Temp) or
use the short version of the path. For the Administrator ID,
the short filename path is
C:\DOCUME~1\ADMINI~1\LOCALS~1\TEMP
Your can check these names by using ‘dir /x’
The variable settings can then be changed for each user by
going into
My Computer -> Properties -> Advanced -> Environment
Variables ->
Set TEMP and TMP to c:\temp or the short filename version
You should also consider the PATH environment variable, and
any INI files that may be used. The short filename for the
"c:\Program Files" directory is "c:\progra~1"
May 11/2007 - Update
Check Printer name and the length of the printer name in Terminal Server.
Shorten it, and try again.
Please visit this Microsoft website document and please review
http://support.microsoft.com/default.aspx?scid=kb;en-us;314106
May 10/2006 - Update
Another customer reported NTVDM printing an invoice when printing to a Lexmark.
April 6/2006 - Update
One customer reported that it's only happening to people printing to Lexmark
printers in Terminal Server. If this is the case, please either phone or
email us to let us know that this is happening to you.
techsupport@power-broker.com
March 29/2006 - Update
One customer reported that by going into the computers BIOS, and disabling the Hyperthreading feature on all computers in the office and even the server eliminated NTVDM
error messages. The symptoms of the problems this office was experiencing
was Power Broker was randomly freezing when they were accessing the program.
There was an issue with an incompatibility with Intel's Hyperthreading
technology.
If you have some Terminal Server users having NTVDM errors and some do not,
compare the Terminal Server user I.D.'s against each other. Try making a
new Terminal Server I.D. that matches the ones that do not get the error and try
testing. Should you find that your test user I.D. works, then delete/reset
the existing Terminal Server user I.D. to match one of the users I.D.'s that are
not experiencing the problem. At one office that experimented with
permissions, they reduced the amount times they got a NTVDM error by three
quarters by giving the users more permissions. In this one case, the tech
gave two people admin rights, and then watched how many times they got the
error. Slowly take permissions back to watch how it effects the user.
If your experiencing this error when printing, try also giving print protocol
full permissions and see what effect this has.
Ensure that you have c:\windows\system32\autoexec.nt and config.nt on the
server
Edit copy and paste the contents of these two files into and email and email
them to
techsupport@power-broker.com mentioning what procedure you were doing
when you got the NTVDM error, what operating system your server is, and if
you are on a Terminal Server network.
Please mention how often this has been happening, and how long has this been
happening for.
If you are using Terminal Server, right click on your Power Broker icon,
select Properties, the Screen tab, please try checking 'Window' instead of
'Full Screen' as a temporary test.
If in Terminal Server, email
techsupport@power-broker.com if your user profiles are stored on the
workstation or on the terminal server.
Do you have your temp files set to a shared directory with full read/write
permissions.
tmpfiles = g:\temp
tmpfiles = c:\temp
Sitting at a workstation, go to Start, Search, Files and Folders, and search
for a file called win.app on 'MyComputer'. Email
techsupport@power-broker.com
how many. Please include a screen capture if you know how to generate
a screen capture.
At a dos prompt, go to your \BRO directory, and email how many m0*.dbf /s files
your search finds.
At a DOS prompt, make a folder called c:\tempfile . You would then go to a
\BRO prompt in DOS, and then type xcopy *.tmp /s c:\tempfile . Once
copied, go to your c:\tempfile and type dir, and then email back how many files
were found.
At a DOS prompt, ensure that everyone is out of Power Broker and then type edit
config.fpw and email back what is in this file.
In Power Broker, could you go to Utilities, Insert Policy Control Records, and
email back what number you have at the bottom of your screen.
At a DOS prompt, browse to your \BRO directory, and then type this:
You would then email the c:\test.txt to
keithvan@power-broker.com
mentioning the type of errors you experience.
Symptoms:
A terminal server user will try and print and they get the NTVDM error. At
the same machine, logged into Power Broker with the same user, but logged into
another Terminal Server user i.d., they do NOT get the error.
|
|
NTVDM encountered a hard error