Terminal Server Issues

  • Thread starter Thread starter Cary Shultz \( MVP - WIN2000 AD \)
  • Start date Start date
C

Cary Shultz \( MVP - WIN2000 AD \)

Howdy!

I have not been able to figure this out. We are
constantly having to reboot our Terminal Server ( every
second or third day ) as users are getting kicked out all
the time. Unfortunately I do not know exactly
what "kicked out" means as I am not on-site. The woman
here is not able to get a whole lot of information as to
what that means exactly as she is being called from the
remote users.

EventIDs indicate lots and lots of 1000 errors.
Specifically "Windows cannot load your profile. Please
increase the registry size and restart the computer"
along with "Windows cannot load the user's profile but
has logged you on with the default profile for the
system. DETAIL - Insufficient system resources exist to
complete the requested service" and "Windows cannot
unload your registry file. If you have a roaming
profile, your settings are not replicated. Contact your
administrator. DETAIL - Access is denied. Build number
((2195)".

We are running WIN2000 SP3 on a member server with the
majority of critical updates ( missing the last three
weeks or so ). Most of the TS Users are in remote
offices. There is a Site-to-Site" VPN set up from each
of the offices to this location. Users log on locally to
their WIN2000 Pro or WINXP Pro systems and then use
Citrix MetaFrame 1.8 SP3 to connect to our TS. NOTE:
this is also happening, although not as often, to the few
users here at this location who *ONLY*log on locally to
their WIN2000 Pro or WINXP system and then use Citrix to
connect to the TS.

Was on the phone with MS today due to a 4097 error.
Apparently the woman here tried to reboot the TS but it
frooze so she hit the power button, waited a few moments,
turned it back on. She then watched everyone log back on
( through the Citrix Manager ) and about five minutes
later everyone was getting kicked out again.

I have run DCDIAG /V on the two WIN2000 SP3 DCs and
NETDIAG /V on all four WIN2000 SP3 servers. No problems
on any of the four appear. Zip! Not a one!!!!

Anyone able to give me some ideas?

Thank you and sorry for the rant.

Cary
 
EventID 1000 (with source Userenv, I presume?) is a very common
one. Have a look here for a large number of causes and possible
solutions:
http://www.eventid.net/display.asp?eventid=1000&source=userenv

Additional hotfixes for this issues (that haven't made it yet to
EventID.net):

828153 - UsrClasses Hive Does Not Unload During Logoff Because of
an Intermittent Handle Leak in Spoolsv.exe - pre-SP5 hotfix
http://support.microsoft.com/?kbid=828153

827825 - "Windows Cannot Unload Your Registry Class File" Error
Message When You Log Off Terminal Services
http://support.microsoft.com/?kbid=827825
 
-----Original Message-----
EventID 1000 (with source Userenv, I presume?) is a very common
one. Have a look here for a large number of causes and possible
eventid=1000&source=userenv

Additional hotfixes for this issues (that haven't made it yet to
EventID.net):

828153 - UsrClasses Hive Does Not Unload During Logoff Because of
an Intermittent Handle Leak in Spoolsv.exe - pre-SP5 hotfix
http://support.microsoft.com/?kbid=828153

827825 - "Windows Cannot Unload Your Registry Class File" Error
Message When You Log Off Terminal Services
http://support.microsoft.com/?kbid=827825

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

"Cary Shultz \( MVP - WIN2000 AD \)"

.
Click to expand...
Vera,

Thank you for the reply. I have spent about 90 minutes
going through the eventid.net page concerning the 1000
error. This seems to be all over the place ( Printers,
TightVNC, Viruses, Anti-Virus Software, et al ) as far as
fixes and solutions go.

I will take a look at the MSKB Articles that you provided
me. Thank you very much! I actually have the patch from
MS PSS for 827825 that I received about two hours ago and
am going to apply it tonight.

Still concerned about the 4097 error. MS sent me to
Citrix. This error is supposed to be fixed by MetaFrame
1.8 SP2. We are running MetaFrame 1.8 SP3!

Vera, any problems with applying WIN2000 SP4? I have
heard about permission changes, specifically to Documents
and Settings. Thank you yet again!

Cary Shultz

PS...yes, userenv!
 
Vera,

Thank you for the reply. I have spent about 90 minutes
going through the eventid.net page concerning the 1000
error. This seems to be all over the place ( Printers,
TightVNC, Viruses, Anti-Virus Software, et al ) as far as
fixes and solutions go.

I will take a look at the MSKB Articles that you provided
me. Thank you very much! I actually have the patch from
MS PSS for 827825 that I received about two hours ago and
am going to apply it tonight.

Still concerned about the 4097 error. MS sent me to
Citrix. This error is supposed to be fixed by MetaFrame
1.8 SP2. We are running MetaFrame 1.8 SP3!

Vera, any problems with applying WIN2000 SP4? I have
heard about permission changes, specifically to Documents
and Settings. Thank you yet again!

Cary Shultz

PS...yes, userenv!
Click to expand...

Presumably, you have been on MF 1.8, SP2 before SP3? I'm not sure
that upgrading to SP3 fixes the problem with the COM+ drive
mappings. Did you fix them manually by running the drvremap
utility, as documented in CTX 457309?
http://knowledgebase.citrix.com/kb/entry.jspa?entryID=1983

Personally, I would not upgrade to W2K SP4 when you have so many
unresolved issues. Chances that they get worse are bigger than
that they will be solved.
 
Hello!

clients getting kicked out constantly is a typical sign of
missing CALs for terminal server. You need client access
lisenses and to register them
 
-----Original Message-----
"Cary Shultz \( MVP - WIN2000 AD \)"
Click to expand...
in

Presumably, you have been on MF 1.8, SP2 before SP3? I'm not sure
that upgrading to SP3 fixes the problem with the COM+ drive
mappings. Did you fix them manually by running the drvremap
utility, as documented in CTX 457309?
http://knowledgebase.citrix.com/kb/entry.jspa? entryID=1983

Personally, I would not upgrade to W2K SP4 when you have so many
unresolved issues. Chances that they get worse are bigger than
that they will be solved.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
.
Click to expand...

Vera,

I agree with you. I am not going to do anything to this
machine before we can get a handle on things.

When this TS was set up about five months ago, I
installed WIN2000 Server and the TS part of things. My
boss then took over and installed Citrix MetaFrame 1.8
and then applied SP3 right away. It has been running
smoothly up until about three weeks ago. I was not
involved with this part as I was off doing something
else. I can not tell you if he used drvremap utility. I
will have to ask him.

In the last four business days it has froozen twice (
usually at one time and then about 50 minutes later ).
Now, it frooze at 11:05 EDT this morning and has not
froozen again ( knock on wood ).

I have looked in the logs and have noticed that directly
preceeding any freeze there have been several big print
jobs ( somewhere in the neighborhood or 20-30 plus pages
at 30MB - 60MB in size, usually MS Word 2000 documents,
but somethimes pages from a web site ).

This is about the only thing that I can find in common.
To my knowledge, there have neither been any additional
print devices added nor have the printers ( read:
drivers ) been changed. I am looking into this but am
not sure how to proceed. The remote offices are in
Blacksburg and Richmond, respectively. I am in Roanoke -
about 45 minutes away from Blacksburg and about 3 hours
away from Richmond.

Thank you for your follow up.

Cary
 
Thank you for your reply.

We have properly taken care of this. The clients are not
getting kicked out, per se; The Terminal Server is
freezing, causing me to have to push the "On/Off" button
on the TS as restarting the TS is not possible.

However, I will check and double-check again just to be
sure.

Cary
 
Vera,

I agree with you. I am not going to do anything to this
machine before we can get a handle on things.

When this TS was set up about five months ago, I
installed WIN2000 Server and the TS part of things. My
boss then took over and installed Citrix MetaFrame 1.8
and then applied SP3 right away. It has been running
smoothly up until about three weeks ago. I was not
involved with this part as I was off doing something
else. I can not tell you if he used drvremap utility. I
will have to ask him.

In the last four business days it has froozen twice (
usually at one time and then about 50 minutes later ).
Now, it frooze at 11:05 EDT this morning and has not
froozen again ( knock on wood ).

I have looked in the logs and have noticed that directly
preceeding any freeze there have been several big print
jobs ( somewhere in the neighborhood or 20-30 plus pages
at 30MB - 60MB in size, usually MS Word 2000 documents,
but somethimes pages from a web site ).

This is about the only thing that I can find in common.
To my knowledge, there have neither been any additional
print devices added nor have the printers ( read:
drivers ) been changed. I am looking into this but am
not sure how to proceed. The remote offices are in
Blacksburg and Richmond, respectively. I am in Roanoke -
about 45 minutes away from Blacksburg and about 3 hours
away from Richmond.

Thank you for your follow up.

Cary
Click to expand...

Now that I reread the whole thread, I notice that you have 2
different Event 1000: the one with "access denied", which is most
common and is *possibly* fixed by 828153 or 827825, and one with
"increase the registry size". Have you checked the registry size?
 
-----Original Message-----


Now that I reread the whole thread, I notice that you have 2
different Event 1000: the one with "access denied", which is most
common and is *possibly* fixed by 828153 or 827825, and one with
"increase the registry size". Have you checked the registry size?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
.
Click to expand...
Vera,

I *believe* that we have resolved the Event 1000 issues.
This is now the least of my conerns, however.

But, to answer your question: Yes, I increased the
registry size from the 80MB that it was to 120MB. It
did monitor this and the largest that I ever saw it reach
was 42MB. Furthermore, I did indeed apply those two
patches. As of the last two days, the only Event 1000
messgages that I am receiving would be due to the McAfee
AntiVirus Software. It is just letting me know that the
update failed ( no worries on this as we have it set up
to retrieve the superdat files from a server - which is
actually getting them from a local machine that is acting
as the mirror. The superdat is updated every fifth day
of so. Thus, for the four days where there is no update
it fails'; hence, the Event 1000 'error' ).

My concern now is that we are experiencing a freeze twice
a day. Happened again today at 11:02AM EDT and 3:35PM
EDT. The only thing that I can find is that there are
typically the several rather large print jobs from the
remote office that immediately precede the Terminal
Server freezing. This is starting to really annoy
everyone. I am not sure how to procede from here!

Vera, Thank You very much for following this post.

Cary
 
My concern now is that we are experiencing a freeze twice
a day. Happened again today at 11:02AM EDT and 3:35PM
EDT. The only thing that I can find is that there are
typically the several rather large print jobs from the
remote office that immediately precede the Terminal
Server freezing. This is starting to really annoy
everyone. I am not sure how to procede from here!

Vera, Thank You very much for following this post.

Cary
Click to expand...

< parts of thread deleted for brevity >

When the server freezes, what do you have to do to get it running
again (if anything)? Does it require a reboot? Does it start
running again spontaneously after a certain time? Do you have to
restart the printer spooler? Are all users kicked off?

Do these large print jobs consistently come from the same
printer(s)? If so, which printer models and drivers? Do they use
the native W2K printer driver or did you install a 3th party
printer driver? If so, I would start by completely uninstalling
this 3th party driver and map the printer to a native driver
instead. Many 3th party printer drivers are not completely TS
compatible and can cause all kinds of problems.
These articles might help:

"Removing 3th Party printer drivers"
http://thethin.net/citrixse/white/Docs/Removing3rdPartydrivers.zip

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

CTX626451 - Sample WTSUPRN.INF File for Use in Autocreation
http://knowledgebase.citrix.com/kb/entry.jspa?externalID=CTX626451

Another factor to investigate is the size of the print jobs. Is
this exceptional in your situation, or quite normal? Can you
provoke a freeze by printing one of these big documents from one
of the printers involved (i.e does it happen *every time* they
print such a big document)?
 
-----Original Message-----



< parts of thread deleted for brevity >

When the server freezes, what do you have to do to get it running
again (if anything)? Does it require a reboot? Does it start
running again spontaneously after a certain time? Do you have to
restart the printer spooler? Are all users kicked off?

Do these large print jobs consistently come from the same
printer(s)? If so, which printer models and drivers? Do they use
the native W2K printer driver or did you install a 3th party
printer driver? If so, I would start by completely uninstalling
this 3th party driver and map the printer to a native driver
instead. Many 3th party printer drivers are not completely TS
compatible and can cause all kinds of problems.
These articles might help:

"Removing 3th Party printer drivers"
http://thethin.net/citrixse/white/Docs/Removing3rdPartydri vers.zip

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

CTX626451 - Sample WTSUPRN.INF File for Use in Autocreation
externalID=CTX626451

Another factor to investigate is the size of the print jobs. Is
this exceptional in your situation, or quite normal? Can you
provoke a freeze by printing one of these big documents from one
of the printers involved (i.e does it happen *every time* they
print such a big document)?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
.
Click to expand...
Vera,

Thank you for replying. After the installation of WIN2000
and Terminal Server I did not install anything. My boss
took over from there. I will have to find out what
drivers he used. I am *assuming* that he used the HP
drivers ( as the printers are mostly the HP LJ1200,
LJ1300, LJ2100 and LJ2200 ).

When this happens, we sit there for some 15 minutes and
nothing happens. It is quite froozen! I can look at the
taks manager and there are no applications running and
there is very little activity in the processes tab and the
performance tab. This is a bit bothersome....

I actually have to kill the server by hitting the On/Off
button. I can not get to Start | Shutdown and Ctrl-Alt-
Del simply ends up letting me know that it can not end.
Power off, wait 15 seconds, Power on! Spooler Service
does not give any errors. At least, none that I have
found.

The number of rather large print jobs within a few moments
of each other seems to be a hit and miss thing. Meaning,
there can be four or five "20 minute periods" in which
seven, eight, nine large print jobs go out without
incident and then the next time BAM! Or, it can be the
second time and then about 50 minutes later BAM! again.
Today, knock on wood! has been a quiet day.

However, there is something of potential interest! The
log indicates that one of the ladies in Blacksburg printed
a 681 page document. I noticed this as I have been
monitoring this closely. I spoke with my contact here in
Roanoke, who contacted the lady in Blacksburg. She said
that it was really only about 168 pages, not the indicated
681. We asked about several other lager print jobs (
according to pages printed ) and they claimed that each
was significantly fewer than what the logs indicate. This
does not add up to me!!!!

Any ideas? I am guessing that you would stick with your
suggestion about changing print drivers. I would agree (
but do not really have the technical knowledge or
experience just yet! ) but can not really do anything
right now as boss is out of town for Thanksgiving and will
not be back until next week.

Again, thank you very much, Vera!

Cary


PS...I just started a 'Part II' post today at about 11:36
AM.
 
-----Original Message-----



< parts of thread deleted for brevity >

When the server freezes, what do you have to do to get it running
again (if anything)? Does it require a reboot? Does it start
running again spontaneously after a certain time? Do you have to
restart the printer spooler? Are all users kicked off?

Do these large print jobs consistently come from the same
printer(s)? If so, which printer models and drivers? Do they use
the native W2K printer driver or did you install a 3th party
printer driver? If so, I would start by completely uninstalling
this 3th party driver and map the printer to a native driver
instead. Many 3th party printer drivers are not completely TS
compatible and can cause all kinds of problems.
These articles might help:

"Removing 3th Party printer drivers"
http://thethin.net/citrixse/white/Docs/Removing3rdPartydri vers.zip

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

CTX626451 - Sample WTSUPRN.INF File for Use in Autocreation
externalID=CTX626451

Another factor to investigate is the size of the print jobs. Is
this exceptional in your situation, or quite normal? Can you
provoke a freeze by printing one of these big documents from one
of the printers involved (i.e does it happen *every time* they
print such a big document)?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
.
Click to expand...
Vera!

Additionally, the print job sizes and frequencies are
quite normal as this is an Insurance company and they are
constantly printing out Certificates of Insurance, Claim
Forms, Proposals, et al! As alluded to in my post from
about three minutes ago, I can not reproduce this
freeze 'on demand' ( read: by printing the suspected
document ). The ladies arequite co-ordinated in their
printing. Three ladies will print large jobs within 45
seconds to two minutes of each other. We have suggested
that they 'undo' this co-ordination. Each is printing to
her own locally attached printer.

HTH and Thank You!

Cary
 
Vera,

Thank you for replying. After the installation of WIN2000
and Terminal Server I did not install anything. My boss
took over from there. I will have to find out what
drivers he used. I am *assuming* that he used the HP
drivers ( as the printers are mostly the HP LJ1200,
LJ1300, LJ2100 and LJ2200 ).

When this happens, we sit there for some 15 minutes and
nothing happens. It is quite froozen! I can look at the
taks manager and there are no applications running and
there is very little activity in the processes tab and the
performance tab. This is a bit bothersome....

I actually have to kill the server by hitting the On/Off
button. I can not get to Start | Shutdown and Ctrl-Alt-
Del simply ends up letting me know that it can not end.
Power off, wait 15 seconds, Power on! Spooler Service
does not give any errors. At least, none that I have
found.

The number of rather large print jobs within a few moments
of each other seems to be a hit and miss thing. Meaning,
there can be four or five "20 minute periods" in which
seven, eight, nine large print jobs go out without
incident and then the next time BAM! Or, it can be the
second time and then about 50 minutes later BAM! again.
Today, knock on wood! has been a quiet day.

However, there is something of potential interest! The
log indicates that one of the ladies in Blacksburg printed
a 681 page document. I noticed this as I have been
monitoring this closely. I spoke with my contact here in
Roanoke, who contacted the lady in Blacksburg. She said
that it was really only about 168 pages, not the indicated
681. We asked about several other lager print jobs (
according to pages printed ) and they claimed that each
was significantly fewer than what the logs indicate. This
does not add up to me!!!!

Any ideas? I am guessing that you would stick with your
suggestion about changing print drivers. I would agree (
but do not really have the technical knowledge or
experience just yet! ) but can not really do anything
right now as boss is out of town for Thanksgiving and will
not be back until next week.

Again, thank you very much, Vera!

Cary


PS...I just started a 'Part II' post today at about 11:36
AM.
Click to expand...

Cary,

could it be that the spooler is running out of disk space?
If the spooler is in the default location (on the same partition
as the OS), then you could get into problems, including a freezing
system.
There used to be an excellent W2K Printing White Paper on
Microsofts website, which I can't find anymore. I'll copy the most
relevent parts here:

The differences in rendering size on the server compared to the
resulting client-side size underscore the need to plan for
sufficient disk space for the Spooler folder on the Terminal
Server. By default, this location exists in the following path:
%SYSTEMROOT%\System32\spool\PRINTERS
This path resides on the same partition as the OS. If the OS is on
a small partition, this can affect redirected printing, especially
if disk space is exhausted under heavy load. You can move the
Spooler folder location to another folder, or to a partition on
another drive set. To change the location, open the Printers
folder on the Terminal Server, choose File, Server Properties, and
then choose the Advanced tab. This global setting applies to all
queues on the server, including redirected queues.
Job sizes written to the Spooler folder on the server side are
based primarily on the contents of the job. As the results show,
large and complex PDF and Word documents that contain a great deal
of text formatting and many bitmap images can swell the job to a
size many times larger than the original file size.
The results emphasize that if you pause the server-side print
queue and spool a print job, the job can appear very large when
compared to other versions of the OS or when spooling the same job
or document on the client side. This is because the spooled job on
the server is written to disk in enhanced metafile (EMF) format
and has not finished rendering to RAW (ready to print) format for
transmission across the Virtual Channel down to the client.
 
Hello Vera!

Again, I thank you for your time and effort. The Terminal Server is
configured as a three disk RAID5 with only one partition ( 67.7GB ).
Currently, there are 58GB free. This was one of the first things that I
considered but I did not mention it anywhere. Sorry! That is my fault.

So, the incredibly large sizes make sense. However, the page count is still
curious.

And I apologize for starting another link. I will not do that again. My
bad!

Thank you again,

Cary
 
Too bad! I really thought this would be the explanation.
If I understand your situation correctly, there is a *lot* of
printing going on. That could well mean that the perceived
connection in time between the big printouts and the freeze is
just coincidental, isn't it? Wouldn't *any* freeze be likely to
happen after a printout of some sort?
I'm beginning to suspect that you could have a hardware problem.
We've had quite a number of these (on Dell PE, although not
2650s), and their behaviour was irratic, to say the least. I also
found that the human mind likes to detect a pattern, even if there
really isn't any.

Can you take this TS out of business for a couple of hours and run
Dells hardware diagnostics program?
 
Double Drats!

I was hoping that I was not seeing something that is just not there!!!! I
will also say that there were no issues yesterday and there were no issues
today! Although there was an unusually large amount of printing today! End
of the month as well as Thanksgiving Day tomorrow for us here in the US.
And most of us will have Friday off as well!!!! Good for the mind to have a
little bit of a break!

And speaking of the mind - I agree with you. There really was no pattern.
As I mentioned. I can not explain why there have not been any problems in
the last two days.

I will contact Dell on Friday and do the hardware Diagnostics. Friday I can
take all the time I need as no one will be in the office.

Vera, I really do appreciate your help and guidance.

If there is ever anything I can do!

Cary
 
Vera,

Have not yet run the hardware diagnostics on this Dell PE 2650. However,
not for the lack of trying. On Sunday I was on hold for 90 minutes before I
gave up. Monday I was on the phone with them for about two hours trying to
1) get to their ftp site to get DSET and once I finally did get it and run
it 2) try to get the results back to them. It just would not work. Via
e-mail, via ftp, from within DSET, through the apps themselves. What a
pain! Tuesday I tried again, only with their 'normal' diagnostic tools but
the dang things would not work. And I was on the phone with them for that!
I must admit that I am not really a Dell fan to begin with and this sure
doesn't do anything to dissuade me from that opinion. Plus, the server
technician Monday was constantly talking about Communist propaganda and
bravda.ru or some web site! Where are the guys in Nova Scotia ( 'Compaq' )
when you need them?!?!?!?

I just wanted to keep you posted. Once we do get this resolved I will let
you know what it was so that you will have the info. It might help you to
help someone else in another similar situation.

BTW - no crashes on Tuesday or Wednesday of last week! No one really using
it on Thursday or Friday ( due to Thanksgiving ) and no one using it on
Saturday or Sunday. However, on Monday when I logged on at the server
itself at 5:30pm it took about three minutes to get the desktop and then it
froze. I sat there for about 10 minutes before I simply powered it down,
waited the 15 seconds and then powered it back on!!!! If there was any
lingering thought that it was still printer related that pretty much went -
for the most part - out the window!

Again, thank you for all your help.

Cary
 
Cary,

Thanks for your update. A pity that Dell support wasn't more
helpfull. We have actually pretty good experiences with them. Have
downloaded and installed DSET a number of times, never had a
problem. Only problem that I've had with sending the results back
to them is when the attached file is too big or when the attached
ZIP archive is not password protected. In both cases, the mail may
disappear into the bit bucket without a warning to the receiver or
the sender. I always insist on receiving an acknowledgement email.

And yes, it sounds more and more like a hardware problem.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
 
Hello Vera,

It had been quiet for several days and then it hit the proverbial fan. It
froze five times yesterday - three times within a time period of 60 minutes!
Ran the DSET again last night and everything is working and in fine order
( according to DSET! ). Except, of course, for the five freezes. I opened
up the Server and unseated everything ( except the CPUs ) and reseated
everything.

I will note that the gentleman with whom I spoke last night was much more
aware and helpful. Thank you for the tip about the zip file not being
password protected. I will call Dell and see if we should try that.
According to the first tech support agent ( back around the 1st ) there
should not have been a size issue for them inbound - and it is definitely
not an issue for us outbound.....

I am going to get on the phone with HP to see if there is a 'Terminal Server
aware" driver for the HP LJ1200. I know that you and Matthew always suggest
the drivers from the WIN2000 Server CD so we will look at that as well....I
am starting to loose my hair on this!!!!!

As always Vera, I appreciate your time....

Cary
 
One more follow up - doing a memory dump to see what is going on....

It has been happening again!!!!

Thanks,

Cary
 
Back
Top