J.R. Sitman
asked on
WSUS services stop off and on during the day
I get events that tell me the services related to WSUS or possibly IIS stop off and on. Like Client web, Reporting Web, Simple Auth, Server Synchronization, etc.
I don't know how to trouble shoot this. It's a 2008 std, DC
I don't know how to trouble shoot this. It's a 2008 std, DC
ASKER
just got back in the office I'll post later today
ASKER
Nothing in the security logs. Yes event 13042 is one of them. I'll reads the links you sent and post after.
ASKER
When I type cacls I get a message that it is now Icacls. When I type Icacls it asks for many parameters. I think icacls "name" /verify is correct, but I don't know what to use for the name
ASKER
Still need help with my last post
The cacls/icacls is meant to verify the permissions.
see if this is of more help
http://technet.microsoft.com/en-us/library/cc708545%28WS.10%29.aspx
see if this is of more help
http://technet.microsoft.com/en-us/library/cc708545%28WS.10%29.aspx
ASKER
The 2nd link 920659 seems like it could be very helpful but it applies to server 2003. The settings on server 2008 for IIS are "very' different. Can you find me an article that would apply to 2008 or translate the 2003 article for me. I'm really new to 2008. Still learning. Teaching myself. I'm the only Admin at the company.
Thanks
Thanks
ASKER
Ignore my last post. I figured it out. Didn't solve the problem. I'll read the other link, later
ASKER
I'm also getting this error. However, when I check the computers they don't show any failures. I'm hoping maybe this will help you help me trouble shoot.
Client computers are installing updates with a higher than 10 percent failure rate
Client computers are installing updates with a higher than 10 percent failure rate
Ok see if this is of more help
http://blogs.technet.com/asksbs/archive/2008/06/02/troubleshooting-multiple-errors-on-wsus-13042-13051-and-12032.aspx
http://blogs.technet.com/asksbs/archive/2008/06/02/troubleshooting-multiple-errors-on-wsus-13042-13051-and-12032.aspx
ASKER
sorry for taking so long to get to this. I'll try to read it today or tomorrow. Thanks for continuing to help.
ASKER
In the first section of the article it explains how to reset the passwords of the IUSR accounts. When I did this only 2 of my 3 servers were listed. The DC where WSUS is hosted (2008) is not there. Does 2008 not use this account? I also noticed in IIS mgr from the 2008 server the "IIS Manager permissions" portion is empty. Is that the way it should be?
Found this
http://learn.iis.net/page.aspx/140/understanding-built-in-user-and-group-accounts-in-iis-7/
Understanding the new IUSR account
As mentioned above, the IUSR account will replace the IUSR_MachineName account in IIS 7. The IUSR_MachineName account will still be created and used only when the FTP 6 compatible server included on the WIndows Server 2008 is installed. If the FTP Server included with Windows Server 2008 is not installed, then this account is never created.
http://learn.iis.net/page.aspx/140/understanding-built-in-user-and-group-accounts-in-iis-7/
Understanding the new IUSR account
As mentioned above, the IUSR account will replace the IUSR_MachineName account in IIS 7. The IUSR_MachineName account will still be created and used only when the FTP 6 compatible server included on the WIndows Server 2008 is installed. If the FTP Server included with Windows Server 2008 is not installed, then this account is never created.
ASKER
OK. I think my settings are good.. I've made the changes and will post later any results
ASKER
Nope still getting errors. What if I uninstall WSUS and reinstall it. Might be less frustrating than what we've gone through so far.
Yes, go ahead with uninstall/reinstall.
Follow this only if you have troubles removing
http://blogs.technet.com/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
In addition to the blog you may need to uninstall Windows Internal Database
To uninstall Windows Internal Database
Open a command shell.
Call msiexec with the correct key for the operating system platform.
On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-D E6C4F6AA8F B} callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-8 52E7FA64D0 1} callerid=ocsetup.exe
Follow this only if you have troubles removing
http://blogs.technet.com/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
In addition to the blog you may need to uninstall Windows Internal Database
To uninstall Windows Internal Database
Open a command shell.
Call msiexec with the correct key for the operating system platform.
On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-D
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-8
ASKER
Thanks. I'll post when I can.
ASKER
I uninstalled it today. When I tried to uninstall the database I got the attached error.
WSUS.png
WSUS.png
Ignore that, it's probably already uninstalled hence the error.
continue with the reinstall
continue with the reinstall
ASKER
I'll wait 1 day to see if I get any event errors.
Before reinstalling ? I dont see any reason to wait.
ASKER
ok. I'll do it today
ASKER
it's been installing for over 30 minutes. Task manager does show it not responding. Should I wait?
I'd kill it and try again, are there any events in eventvwr ?
ASKER
Somethings not right. I did the reinstall oh 3.0 SP1 and it said finished. Normally it would start so it can be configured. It didn't. I rebooted and it doesn't even show installed.
Install sp2, be sure to go over prereqiusites
http://www.microsoft.com/downloads/details.aspx?FamilyId=a206ae20-2695-436c-9578-3403a7d46e40&displaylang=en
hang in there, we'll get it
http://www.microsoft.com/downloads/details.aspx?FamilyId=a206ae20-2695-436c-9578-3403a7d46e40&displaylang=en
hang in there, we'll get it
ASKER
see error
wsus2.png
wsus2.png
ASKER
I'll be gone for a while
Check for the old .mdb and .ldb files
http://technet.microsoft.com/en-us/library/cc708610%28WS.10%29.aspx
The removal of the application may not remove the default .mdb and .ldb files, which will cause a subsequent WSUS 3.0 installation to fail. These files can be deleted from the %windir%\SYSMSI\SSEE directory.
Post the wsussetup.log if that doesnt resolve it.
http://technet.microsoft.com/en-us/library/cc708610%28WS.10%29.aspx
The removal of the application may not remove the default .mdb and .ldb files, which will cause a subsequent WSUS 3.0 installation to fail. These files can be deleted from the %windir%\SYSMSI\SSEE directory.
Post the wsussetup.log if that doesnt resolve it.
ASKER
iT'S STATES THE ACTION IS ONLY VALID FOR PRODUCTS INSTALLED
The wsussetup.log states this?
suggest you go over the Release notes
http://technet.microsoft.com/en-us/library/cc708491%28WS.10%29.aspx
http://technet.microsoft.com/en-us/library/cc708491%28WS.10%29.aspx
ASKER
I reviewed the release notes. Everything meets the requirements. I didn't finf any mdb of ldb files. only mdf and ldf. The last wsussetup.log on the server is 1/3/2010.
There's more than just requirements listed in the Release notes, there is also known problems/resolutions. Didn't need to know the date of the wsussetup.log...I needed to see it.
ASKER
Sorry I've been out of town. I'll be at the location tomorrow and get you the logs
ASKER
Thanks for your patience. Here is the log
WSUSSetup.log
WSUSSetup.log
ASKER
did you have time to review the log?
Yes, sorry been real busy....I would go over all the steps in a manual removal again. Then try again
ASKER
ok
ASKER
The server crashed (won't boot) today. I'm going to reinstall the OS. What do you suggest I do about this open question. I apologize that it didn't get fixed, but I greatly appreciate all your effort.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good info. Thanks again
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
take a look at the specific log files for WSUS, windows update.log, does it shed any light?