Sorry no screenshot of it, but we have all seen it.
Maybe I missed someone's hint or tip on this one but since it just happened, yet again, I want to find a better solution.
When upgrading servers to R8.x, and we do this remotely via Windows Remote Desktop for 95% of our clients, we have seen a problem.
After finished upgrading Domino it asks to restart the server, which I would do anyway and here starts the problem. I can not reconnect remotely to the server.
a)You might think the Windows patches are being loaded, that has been the case at times and for delays but it will always come back.
b)You could say I told it to shut down NOT restart, yep done that too a few times.
c)You might even think some DNS issue occurred or rename of the server at restart that you forgot about. Been there done that too!
d)You may even think there is a hardware failure or NIC burnout.
No, what I am talking about is Windows restarts fine, Domino runs fine. BUT in the Domino console is a line asking for someone to click Y or N to upgrade the templates on the server from R8.x to 8.0.2 in this case.
Why does this hold up Windows Remote Desktop?
Any ideas how to get around it?
In the end called the client, they validated this was the case and hit Y and all was well.
Normally if you are in front of the server you can just hit Y for yes and move on, but not so for working remotely. Yes I could possibly use Remote console if it was enabled.
Maybe VNC would get around this? But I hate VNC unless I must use it like on Windows 2000 servers.
Speaker, Blogger, Author. Posts about HCL Digital Solutions, HCL Software, Lotus, Management, Collaboration, Competitive Intelligence and Strategy, Productivity, CRM and B2B Marketing.
Keith,
ReplyDeleteTry using rdp in console mode:
http://support.microsoft.com/kb/278845
Try this http://dominounlimited.blogspot.com/2008/03/short-tip-connect-to-remote-windows.html
ReplyDeleteThis also will happen if the Domino Server is busy replaying transaction logs on restart after a crash or unclean shutdown. You won't be able to connect via rdp and in this senario even if you get physical access to the machine and login, all that you see is the windows banner that says applying computer settings. Once it is done replaying the logs and server is up you can login via rdp no problem..
ReplyDeleteStuart & Carlos, thanks but yes I know about the change. That isn't the problem.
ReplyDelete/Console allows for one to see the domino server console, I can not even get remote desktop to connect to the server.
It just says server is unavailable.
And for Chuck, I forgot about that, should have added it. thanks!
Stupid question. Have you tried running Domino with the Java console?
ReplyDeleteDoes it yield the same results?
I always make sure the -jc line in the Domino Service entry.
Keith,
ReplyDeleteI've had this problem before and resolved that type of issue:
"The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error message
http://support.microsoft.com/kb/323497
You might have to use remote registry, but this should work
To resolve this issue, follow these steps: 1. Start Registry Editor.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
3. Under this registry subkey, delete the following values: • Certificate
• X509 Certificate
• X509 Certificate ID
4. Quit Registry Editor, and then restart the server.
Also, if using XP and SP3 the /console switch is now /admin
HTH,
Tim E. Brown
I think this has to do with the order services get started in Windows. Because the Domino service never fully starts, the service manager in windows basically hangs and never starts the terminal services service. The only sure way to defeat this is set the Domino service to manual before you reboot, let windows come up then start the Domino service, and change the service back to automatic so the next time you reboot the server it starts automatically.
ReplyDeleteSome excellent ideas and points regarding the startup. My guess, like Brandon's was it just gets stuck. When i remember I will set it to manual start next time I update someone.
ReplyDeleteThe reg edit is a bit drastic, this isn't a encryption error, just a logon one.
And yes, /admin or /console are the choices but really isn't windows 2003 smart enough to let errors bypass and move on someone can administer the server?