Friday, February 11, 2005

Windows 2003 Black Login Screen

We had a server at work that whenever you tried to access the console or TS into the server it just displays a black screen. You could do a ctrl-alt-del and if you tabbed just right you could log into the server. The server then functioned correctly. We finally got around to dealing with it the other day. I did the standard Google searches and checked out Microsoft's knowledgebase but had no luck. I finally broke down and called Microsoft. Turns out this is a known issue, but not enough people have called in for it to become a knowledgebase article.

The cause of this issue is because the colors for the Default user are all set to black (0 0 0). This was caused by the system drive running out of space. The disk space issue was caused by a Computer Associates product that went out of control and filled up the drive. To correct the issue I had to export the "HKEY_USERS\.DEFAULT\Control Panel\Colors" key from a working server and import it into the broken server. Once I changed the registry entries the server started displaying the login screen just like you would expect.

You can use RegINI to do this remotely. Save the following setting in a file caled registry.key and use that as an RegINI input parameter to remotely make the changes.


HKEY_USERS\.DEFAULT\Control Panel\Colors
ActiveBorder = 212 208 200
ActiveTitle = 10 36 106
AppWorkSpace = 128 128 128
Background = 102 111 116
ButtonAlternateFace = 181 181 181
ButtonDkShadow = 64 64 64
ButtonFace = 212 208 200
ButtonHilight = 255 255 255
ButtonLight = 212 208 200
ButtonShadow = 128 128 128
ButtonText = 0 0 0
GradientActiveTitle = 166 202 240
GradientInactiveTitle = 192 192 192
GrayText = 128 128 128
Hilight = 10 36 106
HilightText = 255 255 255
HotTrackingColor = 0 0 128
InactiveBorder = 212 208 200
InactiveTitle = 128 128 128
InactiveTitleText = 212 208 200
InfoText = 0 0 0
InfoWindow = 255 255 225
Menu = 212 208 200
MenuText = 0 0 0
Scrollbar = 212 208 200
TitleText = 255 255 255
Window = 255 255 255
WindowFrame = 0 0 0
WindowText = 0 0 0


You can download the Windows 2003 Resource Kit from Microsoft. This contains the RegINI application in it.

Then just run regini -m \\<> registry.key to correct the colors on any server you wish.

154 Comments:

At 2/23/2005 07:22:00 AM, Anonymous Anonymous said...

Thank you!

 
At 2/25/2005 09:52:00 AM, Anonymous Anonymous said...

Who did you call at MS to get this information?
And what if we only have one server?
Having the same issue on our server. Happened same as you said, after running out of disk space.
Can login and then it displays normally.
Can you manually edit the regkey? and if so, what is the key?
Thanks

 
At 2/25/2005 10:58:00 AM, Anonymous Anonymous said...

I posted the above.
On a single server, I found you can fix this by exporting the regkey for the default, and export the same key (with working color settings) for an existing user.
then edit the default .reg file and copy/paste the settings from the user's .reg file into the one for the default.
(or edit the key entry at the top of the user .reg file to point to the default path)
Then merge the default .reg file back into the registry.
worked like a charm.

 
At 2/28/2005 05:17:00 PM, Anonymous Anonymous said...

Thank You. What a life saver.

 
At 3/01/2005 11:46:00 AM, Anonymous Anonymous said...

You rock!

 
At 3/14/2005 08:32:00 AM, Anonymous Chris Hall said...

That fix worked perfectly thanks a lot

 
At 3/16/2005 05:31:00 PM, Anonymous Anonymous said...

I had the same problem and your solution worked perfectly fine. Thanks much.

Some additional information I found, if you dont have another similar machine, there are a lot of values (Background, Window, scrollbar etc) where you would need to change under the 'colors' key. A good hint to find out is to start with keys that have the value 0 0 0 (indicating black) but remember text is generally black and you probably dont want to change it.

Quick but not complete solution Change the following values
'Window' to 255 255 255(white)
'background' to 102 111 116 (dark gray)
'buttonface' to 212 208 200 (light Gray)

Hope this helps

 
At 3/22/2005 08:26:00 PM, Anonymous Anonymous said...

I dont know how you figured this out but you rock! I have been scratching my head over this for days and thought I would have to rebuild.

 
At 3/22/2005 08:32:00 PM, Anonymous Anonymous said...

for you one server peeps who cant export from a working server, cut and paste the following inbetween the ********* put into into notepad, save it, then change the file extention to .reg - then double click it on the bad server

**********************
Windows Registry Editor Version 5.00

[HKEY_USERS\.DEFAULT\Control Panel\Colors]
"ActiveBorder"="212 208 200"
"ActiveTitle"="10 36 106"
"AppWorkSpace"="128 128 128"
"Background"="102 111 116"
"ButtonAlternateFace"="181 181 181"
"ButtonDkShadow"="64 64 64"
"ButtonFace"="212 208 200"
"ButtonHilight"="255 255 255"
"ButtonLight"="212 208 200"
"ButtonShadow"="128 128 128"
"ButtonText"="0 0 0"
"GradientActiveTitle"="166 202 240"
"GradientInactiveTitle"="192 192 192"
"GrayText"="128 128 128"
"Hilight"="10 36 106"
"HilightText"="255 255 255"
"HotTrackingColor"="0 0 128"
"InactiveBorder"="212 208 200"
"InactiveTitle"="128 128 128"
"InactiveTitleText"="212 208 200"
"InfoText"="0 0 0"
"InfoWindow"="255 255 225"
"Menu"="212 208 200"
"MenuText"="0 0 0"
"Scrollbar"="212 208 200"
"TitleText"="255 255 255"
"Window"="255 255 255"
"WindowFrame"="0 0 0"
"WindowText"="0 0 0"
**********************

 
At 3/23/2005 09:04:00 AM, Blogger Kevin I. said...

I am glad that other people are getting some use out of this. It only took me about 4 months to get around to calling MS to try and fix the problem. Hopefully at some point they will get a KB article published that talks about this issue.

 
At 3/24/2005 11:13:00 AM, Anonymous Anonymous said...

You are the man for calling microsoft on this....

Thanks

 
At 3/24/2005 11:14:00 AM, Anonymous Anonymous said...

I've also been ignoring this issue for months (hey, it worked fine, right?) until the day it crashed hard. Instead of typing in my username and password, I entered my password in the "reason why the server came down hard" text box. (That info is published in the System Log.) Now I've finally fixed it with your help. Thank you for your diligence and for posting a solution to this issue.

 
At 3/31/2005 04:17:00 AM, Anonymous Anonymous said...

Same problem - now solved - thanks a million.
If this is not an issue, it soon will be!

 
At 4/06/2005 10:09:00 AM, Anonymous Anonymous said...

THANK YOU SO MUCH! First hit on google too for "windows login black" and man did I need this. I KISS YOU!

 
At 4/07/2005 02:45:00 PM, Anonymous Anonymous said...

I do have to say... the QA dept took a while to find a solution on TechNet, or the MS website... so I decided to just google it.. and theres your post.... Thanks! Worked perfectly... now its time to order more TS Cals.

 
At 4/14/2005 09:40:00 AM, Anonymous Anonymous said...

I had the same symptoms but could not get into the console regardless of blind keystroke attempts. A Google search lead me to this post and at first I thought I hit pay dirt but alas, my pet was a different beast.

Turns out my system hard drive was beginning to fail. The OS automatically regressed the interface from DMA 5 to PIO mode and the event logs showed a couple of system files taking 120 seconds to access.

The logon screen would come back after a cold re-boot and last for a couple of hours before losing its logon prompt. Scary thoughts of viruses and other maladies were beginning to creep into my brain. However I stuck with the facts and that lead me to realize it was pending hardware failure.

I imaged the drive to a brand new one and booted into safe mode. Once the OS detected the new drive I logged out and rebooted normally. Bingo! Worked like a charm, no event errors and the problem has not re-occurred.

Hope this helps someone else that stumbles across this post. It was the first one I found while searching.

 
At 4/26/2005 09:49:00 AM, Anonymous Anonymous said...

Very kool of you to have took one for us by calling Microsoft.

I had the same problem and now it's fixed thanks to you.

 
At 4/28/2005 08:37:00 AM, Anonymous Anonymous said...

Thank you!

 
At 5/09/2005 06:30:00 AM, Anonymous Anonymous said...

Sweet Lord - Thanks! :)

 
At 5/18/2005 03:24:00 PM, Anonymous Anonymous said...

One thing worth pointing out is that you'll need to reboot the machine after importing the good key. Don't hit the power button and go down hard (which might be tempting). Use something from the resource kit, or WMI to reboot the machine remotley, otherwise you'll be looking at a black screen on the consoel when it comes back up.

 
At 5/19/2005 11:22:00 AM, Anonymous Anonymous said...

I had the same problem and your fix worked fine!
I managed to log in on the black screen, changed the registry, logged out and it worked.
I didn't had to reboot the machine!!
Thanks

 
At 5/20/2005 01:38:00 PM, Anonymous Anonymous said...

Thanks so much, you saved my client a swak of cash, me not having to call MS.

 
At 5/23/2005 06:01:00 PM, Anonymous Anonymous said...

Thank you! I really appreciate that you share the solution

 
At 5/25/2005 11:03:00 AM, Anonymous Anonymous said...

I agree, thanks for the info. I just had this happen to one a production server (Thanks MSRS and your wicked logging - 33MB files every second will fill up a hd quick).

 
At 6/18/2005 12:04:00 PM, Anonymous Anonymous said...

Just for your information, the black screen still exists on the login screen only. This means it's a little unusual to log into the system, you basically have to tab through to the correct blanks. The first available is the user name, which should be administrator by default - just tab down to the next field and enter the password.

 
At 6/30/2005 09:23:00 PM, Anonymous Adam Weigert said...

Thanks so much! This was really annoying! :) We even called Microsoft before finding this, they were clueless for the most part.

 
At 7/08/2005 03:42:00 AM, Anonymous Anonymous said...

Hi,

thanks, worked liked a charme.

 
At 7/11/2005 06:36:00 AM, Anonymous Anonymous said...

Thanks. It worked in my case as well.

 
At 7/13/2005 11:31:00 AM, Anonymous Anonymous said...

Top bloke

 
At 7/18/2005 04:06:00 PM, Anonymous Anonymous said...

Thanks heaps Kevin,

I support an email server that supports 2 time zones, strangely enough 12 hours apart. I had to come in at 11pm to reboot a server that someone couldn't fix via remote-desktop.

I found your solution which saved-the-day.

:o)

 
At 8/03/2005 12:02:00 PM, Anonymous Anonymous said...

Right on the money! I searched for a few days trying to find the cause with no success. We did have a space problem on the server, but did not know that this problem was related. Thanks a million - I was dreading calling MS!

 
At 8/03/2005 02:33:00 PM, Anonymous Anonymous said...

Right on. I had this problem going on and had no idea how to fix it. Thanks for doing the legwork

 
At 8/23/2005 01:03:00 PM, Anonymous Anonymous said...

You did a solid by posting this. Way to go.....

 
At 9/14/2005 04:43:00 AM, Anonymous Anonymous said...

Thanks mate...that one was a beauty

 
At 9/15/2005 04:48:00 PM, Anonymous Anonymous said...

Men, Thaks, IT WORKS, just fine and I didn't have to reboot my Server (W2K3 SP1 on HP PROLIANT ML370).

 
At 10/21/2005 10:04:00 AM, Anonymous Anonymous said...

Thanx a lot man,.... youre a "life saver",..... this has been costing me serious over hours

 
At 11/16/2005 06:24:00 AM, Anonymous Anonymous said...

Thanks for this, you saved me from a world of pain. Can't believe this isn't a KB article.
Cheers,

 
At 12/13/2005 01:15:00 PM, Anonymous Anonymous said...

Add me to the list... I've been logging in with my eyes closed for well over a year now - ...told the client it was a security feature.

Maybe someone should forward this url to MS Support... looks like a few occurances (who bothered to comment here) every month...I'd say justifies an MS article!

Thanks!

 
At 12/16/2005 09:26:00 AM, Anonymous Anonymous said...

Thank you for saving someone's life! If I had to try loging in to that black screen one more time, I would have...

Thanks Many!

 
At 12/26/2005 05:30:00 PM, Anonymous mguzzy said...

It is now a MS Knowledge base Item:
http://support.microsoft.com/default.aspx?scid=kb;en-us;906510
to get around not having another server you can cut and paste the reg file to a text file as noted above or export the reg key from another user...
mguzzy

 
At 1/17/2006 05:00:00 PM, Anonymous Anonymous said...

like others have said before...

You rock!

 
At 2/01/2006 01:21:00 PM, Anonymous Anonymous said...

Thank you

 
At 2/06/2006 03:32:00 AM, Anonymous Anonymous said...

thanks for post this fix! fantastic

 
At 2/06/2006 04:57:00 PM, Anonymous Anonymous said...

Just adding the props for posting this fix. Real simple to fix just a pain to figure out what to do in the first place.
I made a .reg file and put it on the desktop just in case it happens again!

 
At 2/08/2006 02:53:00 PM, Anonymous Anonymous said...

I'll add my thanks and register another instance of this problem occurring. Microsoft, if you're listening, you need to make KB article 906510 a hit when searching for Windows 2003 Black Logon Screen.

 
At 2/09/2006 04:32:00 PM, Anonymous Jim Hall said...

Perfect; resolved the problem a treat! ;-)

 
At 2/13/2006 06:26:00 AM, Anonymous Tony Cheesbrough said...

This was brilliant - it was vital for us as it was a TS/Citrix server!!!! Thanks unlimited.

 
At 3/06/2006 05:52:00 PM, Anonymous Anonymous said...

this just totally saved me. thank you.

 
At 3/21/2006 01:27:00 PM, Anonymous Anonymous said...

Excelente resultado. Muchas gracias, hace meses que tenía este problema y no lo podía solucionar.

 
At 3/23/2006 05:46:00 PM, Anonymous Julian said...

I have been ignoring this poblem for months. It was annoying but I didnt use the server that often. Now that I have converted the server from its old hardware to a VMWARE image, I wanted to fix it. Thanks for your solution. Great help!

 
At 3/24/2006 01:12:00 PM, Anonymous Anonymous said...

Worked like a charm. Thanks very much for sharing that info!

 
At 3/25/2006 01:36:00 AM, Anonymous Anonymous said...

Thanks sooooo much
This makes me look real good with my team
I have already shared the info with our support team

 
At 4/18/2006 12:22:00 PM, Anonymous Anonymous said...

Thank You!
Had this exact problem and used the recommended solution....................Worked perfectly.

Cool!

 
At 5/31/2006 07:56:00 PM, Anonymous Anonymous said...

Awesome post! Thanks for all your help!! God bless you!

 
At 7/18/2006 05:06:00 AM, Blogger iaydin said...

We were even thinking of reinstalling the OS. Because previous shutdown was unexpected, we weren't able to logon the server ("Why did the computer shutdown unexpectedly?" question and the dropdown box below that message were invisible). After appliying your fix, we could see the message and logged on normally.

Thank you sooo much!

 
At 7/21/2006 12:35:00 PM, Anonymous Anonymous said...

Thanks for posting this info. Our drive filled up when another admin accidentally opened our server as an open relay. We fixed the problem as soon as we found out, but a few days of returned (failed to send spam) filled our drive and caused a number of problems including the black screen of death. This solution should be on knowledgebase. Anyhow, I just want to thank ou for posting this again.

 
At 7/25/2006 09:49:00 AM, Anonymous Anonymous said...

Microsoft can kiss my grits. Yay Flyhpr!

 
At 7/25/2006 05:18:00 PM, Anonymous Anonymous said...

Same issue:

Dell Server Citrix Metaframe XP

Didn't have to reboot at all.

THANKS! (yes, i'm yelling - grin)

 
At 7/28/2006 08:38:00 AM, Anonymous Anonymous said...

Thank you very much.

 
At 7/31/2006 11:17:00 AM, Anonymous Anonymous said...

I also had the same problem after running out of disk space. Your procedure fixed my problem. I did not have to reboot to make it take effect. Thanks!

 
At 8/02/2006 08:37:00 PM, Anonymous Anonymous said...

It seems I have the same problem except even when blindly logging in, don't get into the system. A computer icon appears on the black screen and it stays that way indefinitely. I can't log into safe mode or access the OS drive over the network because it is not shared. I can access the second partition. I would like to somehow access the C(windows) drive to delete some unnecessary files but the server has a RAID 1 array and I can't access them from DOS. Ugh. Any ideas?

 
At 8/07/2006 09:36:00 AM, Anonymous Anonymous said...

Just a heads up - this is a great fix! I was able to fix this in under a minute by opening regedit on a server that was OK and then using regedit to connect to the network registry of the machine having the problem. Then its just a drag and drop!

If I'd only found your fix 5 hours ago I'd be much happier. :)

Thanks!

 
At 8/12/2006 02:41:00 AM, Anonymous Anonymous said...

Hi this is dev, thanks alot this really help in solving my problem and i got a veryyyyyyy happy customer.

 
At 8/17/2006 05:31:00 AM, Anonymous Anonymous said...

Thanks!

 
At 8/17/2006 05:32:00 AM, Anonymous Anonymous said...

Thanks!

 
At 8/17/2006 01:14:00 PM, Anonymous Anonymous said...

You're a star for posting this up Kevin. We've been having this issue for weeks now and MS is no help as usual.
Thanks!
Lorinda

 
At 10/04/2006 03:30:00 PM, Anonymous Anonymous said...

Worked instantly! Thx!

 
At 10/04/2006 03:30:00 PM, Anonymous Anonymous said...

Worked instantly! Thx!

 
At 10/11/2006 03:58:00 AM, Anonymous Anonymous said...

Wow ! And : Thanks !

 
At 10/12/2006 02:39:00 PM, Anonymous Anonymous said...

Perfect!!! Thanks!!!

 
At 10/17/2006 01:07:00 AM, Anonymous Anonymous said...

LOL...
Are you aware of the amount of time I've just saved here :-)

when you come to Denmark there will be a cold beer waiting for you.

 
At 10/23/2006 09:57:00 AM, Anonymous Anonymous said...

Obrigado

 
At 10/26/2006 11:16:00 AM, Anonymous Anonymous said...

This is great information. Thank you. It save me a lot of time

 
At 10/27/2006 09:47:00 AM, Anonymous Anonymous said...

Thanks!

 
At 10/28/2006 11:20:00 AM, Anonymous Anonymous said...

o.k. I am number 76 but I really have to say thank you :-)

 
At 11/13/2006 08:42:00 AM, Anonymous Anonymous said...

Thanks Mate - You are a legend!!

 
At 11/14/2006 02:49:00 AM, Anonymous Anonymous said...

Excellent! Saved loads of time, many thanks.

 
At 11/21/2006 10:31:00 AM, Anonymous Anonymous said...

Your mother should be very proud of you!

 
At 11/24/2006 09:09:00 AM, Anonymous Anonymous said...

Thanks, saved our bacon big time.

 
At 12/02/2006 11:58:00 AM, Anonymous David Mackey said...

Thanks so much. That is a great help.

 
At 12/10/2006 08:55:00 AM, Anonymous Anonymous said...

This post has been removed by a blog administrator.

 
At 12/11/2006 09:10:00 PM, Anonymous Anonymous said...

Thanks also, very grateful for this one, saved my A..E!

 
At 12/22/2006 01:50:00 AM, Anonymous Anonymous said...

Thanks Kevin
It works like a charm. We struggle for a couple of days and when we got used to the blank screen, we decided to search for solution and vwallaaa, there is the solution.

Mokone Tsiloane

 
At 1/08/2007 09:03:00 AM, Anonymous Anonymous said...

thanks you kevin,
i live in lebanon and today i had the same problem with my server at work (my disk was full because of the symantec antivirus which write a huge log file)
many thanks
Nadeem kahwaji

 
At 1/10/2007 01:30:00 AM, Anonymous Anonymous said...

Let me be the 92nd person to thank you. This fixed 2 of our servers we were planning on rebuilding. You easily saved me 3-4 hours of work with one posting. Blogs are cool.

 
At 1/15/2007 08:21:00 AM, Anonymous Dawid said...

This was probably the best little bit of info and saved me lots of time.

Thanks

 
At 1/17/2007 03:18:00 PM, Anonymous Anonymous said...

94th in line...let's go for triple digits!

Muchos Gracias from Canada!

 
At 1/19/2007 02:14:00 PM, Anonymous Anonymous said...

Worked Great Dude, thanks!!!!

 
At 1/22/2007 01:59:00 PM, Blogger James said...

Worked for me. We want a KB!!!

 
At 1/25/2007 05:58:00 AM, Anonymous Anonymous said...

Most excellent! Thanks for posting this in a logical manner!

 
At 2/15/2007 01:05:00 AM, Anonymous Anonymous said...

Thanks a lot!!! works perfect now i used the regkeys that are posted above.

 
At 2/21/2007 02:58:00 AM, Anonymous Anonymous said...

You my friend are a saint. We though the server was seriously hosed after running out of disk space...

 
At 2/25/2007 09:13:00 PM, Anonymous Anonymous said...

From another Anonymous System Admin... THANKS!!!

 
At 2/26/2007 01:35:00 AM, Blogger SasukeKun said...

Our client was saying that we have a virus on the server, our 3rd level was saying that we should restage the VM, they got the backup team on the call to check the good backups, then i found this awesome fix.

Thank youuuuu Kevin!

 
At 2/28/2007 04:16:00 PM, Anonymous Anonymous said...

Great post, this one really threw me for a loop. Thanks!

 
At 3/08/2007 03:47:00 PM, Anonymous Anonymous said...

thank you.. i had that problem on one of my mission critical servers and was about to spend the night rebuilding it.. with your suggestion i fixed the video problem in 1 minute.

thanks again

 
At 4/05/2007 08:58:00 AM, Anonymous Anonymous said...

UffDa... It worked for us as well.

After a boot, we had a yellow triagle with a black exclamation point and couldn't see the login fields. If you press Enter to acknowledge the "!", then press CTRL-ALT-DEL, now enter your password. Server should operate somewhat normal.

 
At 4/05/2007 09:02:00 AM, Anonymous Anonymous said...

Microsoft has posted a KB now. Here it is:

http://support.microsoft.com/kb/906510

 
At 4/07/2007 09:20:00 AM, Anonymous Anonymous said...

Thanks guys, saved me a lot of time reinstalling the whole machine.

Alex

 
At 4/14/2007 06:47:00 AM, Anonymous Anonymous said...

Hi Guys,

you saved me a lot of time :-)
I never thought that this would be such a simple reason ...

Hardy -> Van der CHEIB

 
At 4/18/2007 11:19:00 PM, Anonymous Anonymous said...

Thank you very much guys it worked for me.

 
At 4/25/2007 11:01:00 PM, Anonymous Anonymous said...

yeah boy! worked a treat

 
At 5/03/2007 11:05:00 PM, Anonymous Anonymous said...

Thanks! Never thought I would find a way to get rid of that annoying screen.

 
At 5/14/2007 07:47:00 AM, Anonymous Anonymous said...

Good job, thanks for the resolution and fix.

We had a drive run out of space from a runaway application.

Woot!

 
At 5/17/2007 08:27:00 AM, Anonymous Oreo said...

Thanks!! This helped me out a lot.

 
At 6/04/2007 11:25:00 AM, Anonymous Anonymous said...

You rock and you saved me rear.

 
At 7/02/2007 10:51:00 AM, Anonymous Anonymous said...

Life saver!! Why don't MS post this kind of stuff, I spent ages looking for this. Thanks.

 
At 7/13/2007 10:43:00 AM, Anonymous Anonymous said...

Super !!!
Thank

 
At 7/23/2007 09:51:00 AM, Anonymous Anonymous said...

It fixed my problem, thanks!

 
At 7/26/2007 04:31:00 AM, Anonymous Tom Revell said...

Hi, another person with a great big THANKS - someone had filled the print spool directory with a 4Gb spool file - server bluescreened and when it came back up was all black. Thanks to you, it was fixed in minutes. What a cool solution!!

Tom

 
At 7/26/2007 12:15:00 PM, Anonymous Adam said...

HOLY CRAP!!! This was bugging me for about a week. Thank you so much

 
At 7/30/2007 06:22:00 PM, Anonymous RunPCRun said...

Thanks fella. Worked a treat and got me out of what was looking like a more serious error than it was.

Also thanks to the guy that posted the reg text file. (it just made it that bit easier)

 
At 8/06/2007 01:09:00 PM, Anonymous Anonymous said...

Man, I'm glad I found this.
It works superb.

 
At 8/06/2007 02:53:00 PM, Anonymous Dave said...

I had this problem on our exchange server and I thought it was a system failure or was in the verge of failing. This would have left me with a huge headache trying to figure this one out! Now all I can say is dood, you rock!!!

 
At 8/09/2007 11:39:00 AM, Anonymous Anonymous said...

Thanks dude! Worked like a charm!

 
At 8/13/2007 02:49:00 PM, Anonymous Anonymous said...

Thank-you! This saved me alot of time and headaches!

 
At 8/23/2007 03:36:00 AM, Anonymous Dirk-Jan said...

Thanx Kevin and the others!!!
It worked fine! Just exporting the key from a working 2003 server end importing it in the faulty one.

(Ofcourse I had to "blind" log on into the problemserver but the cursor is standard at the Password field, just fill in blind your admin pwd..)
This server did need a reboot, just logoff/logon.
Again: many thanx, greetings from the Netherlands.. DJ

 
At 9/04/2007 11:55:00 AM, Anonymous <a href="http://buy-levitra--ooz.blogspot.com">buy Levitra Online</a> said...

This post has been removed by a blog administrator.

 
At 9/09/2007 02:56:00 PM, Anonymous <a href="http://search.cnn.com/search?query=site:m1.aol.com/phentermine4">Anonimous</a> said...

Nice! Nice site! Good resources here. I will bookmark!

 
At 9/10/2007 12:48:00 AM, Anonymous <a href="http://courses.cvcc.vccs.edu/ENG112_GROSS/_Chat_Room/000008fd.htm">Anonimous</a> said...

Excellent website. Good work. Very useful. I will bookmark!

 
At 9/10/2007 12:53:00 AM, Anonymous <a href="http://m2.aol.com/LorenLynn03/index8.html">Maxwells</a> said...

I see first time your site guys. I like you :)

 
At 9/18/2007 10:49:00 AM, Anonymous Dennis said...

I have had this issue on a machine for months with no idea how to fix it. It showed up yesterday on another. I googled it and found this fix 1st hit.

I did as suggested, logged out and logged in (NO REBOOT) and this worked Flawless.

 
At 9/21/2007 01:35:00 PM, Anonymous Anonymous said...

Thank You! Thank You! Thank You!

 
At 10/09/2007 09:28:00 AM, Anonymous Anonymous said...

This post has been removed by a blog administrator.

 
At 10/25/2007 06:08:00 AM, Anonymous Anonymous said...

Add me to the people who thank you, that's a great help.

 
At 11/05/2007 01:46:00 AM, Anonymous Anonymous said...

I love you and want to have your babies. Thanks dude.

 
At 11/06/2007 05:49:00 AM, Anonymous Anonymous said...

Many thanks for your help this just got me out of a major jam.

 
At 11/23/2007 08:45:00 AM, Anonymous Anonymous said...

Thanks alot!!!! It worked for me too!

 
At