Post by mike68883 on Dec 17, 2008 11:04:34 GMT -6
Running MOSS 2007 Enterprise on Windows Server 2003 Std R2 - fully patched.
===============
I did a complete uninstall/reinstall of MOSS today die to some unrelated
issues. I selected Complete for the setup, despite using just a single
server; I may add one more in the mid-range timeframe. Applied SP1 for WSS
3.0 and MOSS 2007, and the the Infrastructure Updates from August. All went
well during setup and configuration, but ran SP BPA anyway to see if I
missed something.
I got a single error, Priority 1; "The SharePoint 3.0 Central Administration
Web Application account and the Windows SharePoint Services Timer Service
account must be the same."
I went into IIS and checked the identity of the app pool and saw I had used
the wrong account. The Timer Service was correct. Couldn't find a way in
Central Administration to change the account the site was running under, so
I used the Configure button in IIS > Application Pool > Central
Administration > Properties >Identity to change the account to the correct
one. Restarted IIS, but am getting the same error in SP BPA.
I'm a relative newbie, so I need some help finding where I went wrong.
Many thanks in advance!
--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a conservation non-profit (501 (c)(3)) organization
Wood River, NE