After applying January's WSUS patches on 2008 R2 server I had issues with the Server Service. 1st issue was the Server Service hung on restart Event ID 7022. 2nd issue was after another reboot the Server Service stated starting the eventually kicked into life. I want to reboot the server again and monitor what this service is doing as I fear it will either fail or hang. Can anyone recommend a tool to do this or give advice on previous experience of issues with this service?

1. Which update is causing problem? You can restore previous working status. 2. You can log booting process (choose F8 and appropriate item). Reveal logs here 3. How do behave clean and safe boots? 4. Yo may look for dependences of Server Service 5. You would not do a mistake,if you place the question into WSUS forum or/an WSUS server forum Regards Milos

Hi Milos I'm not sure which update is casuing the issue. I'm wanting a tool to monitor what the Server Service is doing the next time I reboot the server. Stephen

Hi, You may use Process Monitor to monitor the server. For more information regarding Process Monitor, please refer to the following Microsoft TechNet article and blog: Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645 Troubleshooting with Process Monitor http://blogs.technet.com/b/askperf/archive/2007/06/01/troubleshooting-with-process-monitor.aspx Based on the current situation, you may uninstall the reinstalled installed updates one by one to find out the root cause. Regards,Arthur Li TechNet Community Support

Please see if you have similar situation as mentioned in below thread. Server 2008 Server Service Hangs for approx. 16 minutes upon boot up, then starts http://social.technet.microsoft.com/Forums/en-US/winservercore/thread/dc68be06-cb81-4dcb-915c-2350e776cd31/~Santosh

Hi, You may use Process Monitor to monitor the server. For more information regarding Process Monitor, please refer to the following Microsoft TechNet article and blog: Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645 Troubleshooting with Process Monitor http://blogs.technet.com/b/askperf/archive/2007/06/01/troubleshooting-with-process-monitor.aspx Based on the current situation, you may uninstall the reinstalled installed updates one by one to find out the root cause. Regards,Arthur Li TechNet Community Support

Well Process Monitor in Boot Logging mode is making my server blue screen...

Hi, You may also analyze them with Debugging Tools by yourself. Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. 4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder". 5. Please send the ZIP file to us. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB article below: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Arthur Li TechNet Community Support

Hi, You may also analyze them with Debugging Tools by yourself. Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. 4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder". 5. Please send the ZIP file to us. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB article below: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Arthur Li TechNet Community Support