W2K3 HELP!!!!!!

  • Thread starter Thread starter Stacie
  • Start date Start date
S

Stacie

I have 5 w2k terminal servers that run great. I just got a new w2k3
terminal server and twice a day it blue screens on me. It's always happens
around noon and after 5pm. The BSOD is from kernal_apc_pending_during_exit.
It suggested disabling BIOS memory, caching or shadowing. I don't think
this is the problem. In the event log I have system errors, a save dump log
and application hang logs (not always from the same app).

Second, I found out that I need to purchase all new CALs for this server....
and having to buy two licenses??? I've tried activating my other w2k3
server (not a terminal server) as a licensing server and it wouldn't
activate - it only would allow me to connect to another licensing server.
What am I missing (besides the licenses)????

TIA
 
I don't know where you have read that the BIOS memory caching
could be the cause. If you have a look at the MSDN Bug Check Code
page for STOP error 0x20, you'll see that a faulty driver is
listed as the probable cause:

http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/ddtools/hh/ddtools/bccodes_2pbb.asp?frame=true

I would uninstall all non-native drivers, starting with all
printer drivers. Map your clients printers to native drivers
instead.

Regarding the licensing:
Yes, you must have a 2003 CAL and a 2003 TS CAL for every
user/device. Nothing new there, that has always been the case for
a TS client.
About the TS Licensing server: did you install it (with Add/Remove
programs - Add Windows components)? Did it install OK? If not,
what error message did you get? If it installed alright, but it
can't be activated, what error message did you get there? What
does the EventLog show you?
 
If you're familuar with bsod - when you get one it gives you the error, and
then a possible solution/cause. Thats where I read BELOW the stop error
code it suggested todisabling BIOS memory, caching or shadowing - NOT that
the BIOS memory caching would be the cause. So, I received this information
for the BSOD itself. But I will try changing my drivers... thanks
 
Aaaah!
I've had my fair share of BSODs on NT4.0 and W2K, but I still have
to encounter my first one on a Windows 2003 system :-)
So no, I didn't know that it tries to offer a troubleshooting
solution. But it seems that at least in your case, this feature
isn't perfect yet.
 
Back
Top