Server 2012 R2 - critical app - server manager, any mmc, event viewer etc will not run UNLESS there is a dirty shut-down

mark denton 1 Reputation point
2022-03-21T18:23:24.893+00:00

If I restart the server gracefully (via OS or vSphere) then server manager does not start, you can't run any mmc, sql does not start, application services do not start. This is since applying a patch to the critical dotnet application that effectively removes the 32-bit version and installs a 64-bit version. This was Sandboxed and tested OK. If I abrupt power off the server and it recovers from a dirty shutdown then all applications and services start OK. This is a 2012-R2 server running a critical application with an SQL back-end that is very expensive to migrate to a fresh installation. On the other hand if it's half broken and I proceed to just run every tool I can think of just keep buttoning it off I run the possibility of it not working at all and then I have a whole department not working and we would be waiting for availability of a consultant to migrate /rebuild on a new server. If I sanbox the server (+plus DC + client etc) then I cannot recreate the problem.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,178 questions
Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
421 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2022-03-21T18:38:22.907+00:00

    I'd check the system event log for clues.

    0 comments
  2. mark denton 1 Reputation point
    2022-03-22T10:59:38.26+00:00

    Thanks for your comment! Of course..
    There is allot going on in event viewer on a problematic boot, however the first error that always occurs is the following one. If this error does not occur.. seemingly because we have had a dirty shutdown, then everything follows OK. I'm very sceptical about whether there is actually an issue with availability or responsiveness of our domain controllers (no other servers are affected by this issue) so am trying to think of what happens on the client side that may trigger this and what the difference would be (dirty not dirty).

    https://kb.eventtracker.com/evtpass/evtpages/EventId_1055_Microsoft-Windows-GroupPolicy_64856.asp

    Error code 1355 (The specified domain either does not exist or could not be contacted)
    This error code might indicate a fault or improper configuration with name resolution (DNS). Use nslookup to confirm you can resolve addresses of the domain controllers in the user domain. Use Networking troubleshooting procedures to further diagnose the problem.

    0 comments
  3. Dave Patrick 426.1K Reputation points MVP
    2022-03-22T12:21:45.427+00:00

    I'd check the domain controller and problem member both have the static address of DC listed for DNS and no others such as router or public DNS.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments