bill2013
asked on
Cannot log on remotely to SBS 2008 server - "Console has stopped working"
Hi,
I just tried to log into an SBS 2008 server but cannot do so. I get msg "Windows 2008 console has stopped working" and get the choice of to close or check for a solution and close. Tried the latter and it says "An unauthorised change has been made".
Getting an 0xC004D401 file mismatch error.
Get this problem around every six weeks and this is overcome by a restart of the server, but because of public holidays no-one in the office until Tuesday.
Is there a way of restarting the server remotely without being logged in?
I know how to reboot the domain pc from the server, but not the other way around. That said, all the pcs are shutdown anyway, so it would need to be a command to the server directly.
I just tried to log into an SBS 2008 server but cannot do so. I get msg "Windows 2008 console has stopped working" and get the choice of to close or check for a solution and close. Tried the latter and it says "An unauthorised change has been made".
Getting an 0xC004D401 file mismatch error.
Get this problem around every six weeks and this is overcome by a restart of the server, but because of public holidays no-one in the office until Tuesday.
Is there a way of restarting the server remotely without being logged in?
I know how to reboot the domain pc from the server, but not the other way around. That said, all the pcs are shutdown anyway, so it would need to be a command to the server directly.
ASKER
Thanks Arnold, tried "mstsc /admin /v:myservername /public" but did not recognise the computer name. Definitely using the correct one??
Could not try the first suggestion as I cannot log into the server.
Could not try the first suggestion as I cannot log into the server.
ASKER
I managed to get to the logon with "mstsc /admin /v:mypublicIP /public" but get the same error and cannot open SBS.
More than likely the SBS Managment Console is corrupted and needs to be repaired. Because it is set to start automatically when you log onto your server it could cause you to not be able to connect remotely if it is damaged.
Unfortunately, fixing this remotely is difficult if it's a physical machine (definitely much easier if it is a virtual machine, since you can access it from another computer on the network in the Hyper-V or VSphere management console).
If you had something like LogMeIn Pro on the server you could also use that to boot into Safe Mode with Networking and LogMeIn enabled to provide access. Because booting into Safe Mode is what you need to do in order to repair the SBS Management Console.
Please see full instructions on repair from TechNet here:
https://technet.microsoft.com/en-us/library/dd430086(v=ws.10).aspx
Jeff
TechSoEasy
Unfortunately, fixing this remotely is difficult if it's a physical machine (definitely much easier if it is a virtual machine, since you can access it from another computer on the network in the Hyper-V or VSphere management console).
If you had something like LogMeIn Pro on the server you could also use that to boot into Safe Mode with Networking and LogMeIn enabled to provide access. Because booting into Safe Mode is what you need to do in order to repair the SBS Management Console.
Please see full instructions on repair from TechNet here:
https://technet.microsoft.com/en-us/library/dd430086(v=ws.10).aspx
Jeff
TechSoEasy
Oh, and that error you are getting? It is most likely caused by an incomparable app you've installed on the server (or worse, a virus).
Details about this are here: https://support.microsoft.com/en-us/kb/931699
(even though that article is written for Vista, it applies equally to Server 2008 which is essentially Vista anyhow).
Jeff
TechSoEasy
Details about this are here: https://support.microsoft.com/en-us/kb/931699
(even though that article is written for Vista, it applies equally to Server 2008 which is essentially Vista anyhow).
Jeff
TechSoEasy
ASKER
Thanks Jeff,
I will wait until someone can do an onsite reboot tomorrow.
I have to resolve this issue, but have been stuck on getting Exchange 2016/Outlook 2016 working together. Now that's done, I can spent some time on this, so I will check out your link.
I can't imagine putting the apps mentioned on a server, but could be something similar - will try the resolution tomorrow.
If it wasn't a server, I would run Combofix.
I will wait until someone can do an onsite reboot tomorrow.
I have to resolve this issue, but have been stuck on getting Exchange 2016/Outlook 2016 working together. Now that's done, I can spent some time on this, so I will check out your link.
I can't imagine putting the apps mentioned on a server, but could be something similar - will try the resolution tomorrow.
If it wasn't a server, I would run Combofix.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Jeff. I will try it tomorrow.
ASKER
thanks
Though it might be simpler to access service as administrator and connect to the SBS to restart the terminal server services to see if that resolves the issue. Try mstsc /admin /v:sbserver /public see if you get a different response. If this is a reoccurring basis something else is going on.