We susccessfully installed and configed the above instance on a single win 2008 running SQL Server 2008,; everything was fine till I checked the central Admin site a couple days ago and it's nowunreachable with a generic 500 browser Error. No obvious related error in event logs or WSS log. We used Network Service as the Central Admin app pool account per MS's recommendation for stand-alone installs. Tried server re-boot and re-running WSS cofig wizard: no luck. Any tips or ideas greatly appreciated!! Thanks Many are clever; few are wise

Hi, for more details http://support.microsoft.com/default.aspx/kb/841216 Windows SharePoint Services 3.0 Click Start, click Run, type cmd in the Open box, and then click OK. At the command prompt, type the following lines, and then press ENTER after each line: cd /d %commonprogramfiles%\Microsoft Shared\web server extensions\12\BINstsadm -o upgrade -forceupgrade Type exit to exit Command Prompt. Note If you run the Stsadm.exe command to manually force an upgrade of a Windows SharePoint Services installation, you may receive the following error message: The current user or the application pool identity of the virtual server is not the owner of the database '<sts_servername_1>' on server '"server_name\share_point"' You receive this error message because Windows SharePoint Services requires that the database owner (DBO) is one of the following: The account that the SharePoint Central Administration virtual server application pool is running as for Microsoft Windows authentication The SQL Server account that Windows SharePoint Services is connecting as for SQL Server authentication If you are using Windows authentication, you must change the database ownership and permissions for the databases to grant permissions to the application pool accounts. If you are using SQL Server authentication, you must change the database ownership and permissions for the databases to grant permissions to the SQL Server account. To change the database ownership and permissions, use Microsoft SQL Query Analyzer.You must change the DBO to be the Windows account or the SQL Server account that Windows SharePoint Services is running as. However, if for any reason you cannot make the change immediately, there is a temporary workaround. You can designate the Windows account or the SQL Server account that Windows SharePoint Services is running as to be the System Administrator in SQL Server. Then, you can continue running the stsadm o upgrade command.Note If your application pool account is running as Network Service and if you are using Windows authentication, you will not be able to designate Network Service as the DBO. Instead, you can grant System Administrators permissions in SQL Server to the Network Service group. For installations that use Windows authentication where Network Service is used as the application pool account that Windows SharePoint Services is running as, do not use the following procedure.To change the DBO to be the Windows account or the SQL Server account that Windows SharePoint Services is running as, follow these steps: Change the database ownership and permissions for the configuration database. To do this, follow these steps: On the computer that is running SQL Server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer. In the Connect to SQL Server dialog box, type the server name in the SQL Server box, and then click OK. On the Query menu, click Change Database. In the Select Database of server_name box, click the configuration database (sts_config), and then click OK. In the Query pane, type the following appropriate query, depending on whether you are using Windows authentication or SQL Server authentication.If you are using Windows authentication, type the following query. DECLARE @AdminVSAccount nvarchar(255) DECLARE @ContentVSAccount nvarchar(255) SET @ContentVSAccount = N'domain\contentaccount'; SET @AdminVSAccount = N'domain\adminaccount'; EXEC sp_grantlogin @ContentVSAccount; EXEC sp_changedbowner @AdminVSAccount; IF NOT EXISTS (SELECT * FROM sysusers WHERE name=@ContentVSAccount) EXEC sp_grantdbaccess @ContentVSAccount; EXEC sp_addrolemember 'db_owner', @ContentVSAccount; EXEC sp_addsrvrolemember @AdminVSAccount, 'dbcreator' EXEC sp_addsrvrolemember @AdminVSAccount, 'securityadmin' Note In lines 3 and 4, replace domain\contentaccount and domain\adminaccount with the domain account for the content virtual server and the domain account for the SharePoint Central Administration virtual server. If the accounts are the same, SQL Query Analyzer will display an error message, but the process will still succeed.If you are using SQL Server authentication, type the following query. DECLARE @SQLAccount nvarchar(255) SET @SQLAccount = N'sql_user_account'; EXEC sp_changedbowner @SQLAccount; EXEC sp_addsrvrolemember @SQLAccount, 'dbcreator' EXEC sp_addsrvrolemember @SQLAccount, 'securityadmin' Note In line 2, replace sql_user_account with the name of the SQL Server account that Windows SharePoint Services is configured to use to connect to the computer that is running SQL Server. This must be an existing SQL Server account. Click Execute Query to update the database. Change the database ownership and permissions for the content databases. To do this, follow these steps: On the computer that is running SQL Server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer. In the Connect to SQL Server dialog box, type the server name in the SQL Server box, and then click OK. On the Query menu, click Change Database. In the Select Database of server_name box, click the content database you want to update, and then click OK. In the Query pane, type the following appropriate query, depending on whether you are using Windows authentication or SQL Server authentication.If you are using Windows authentication, type the following query. DECLARE @AdminVSAccount nvarchar(255) DECLARE @ContentVSAccount nvarchar(255) SET @ContentVSAccount = N'domain\contentaccount'; SET @AdminVSAccount = N'domain\adminaccount'; EXEC sp_grantlogin @ContentVSAccount; EXEC sp_grantlogin @AdminVSAccount; EXEC sp_changedbowner @AdminVSAccount; IF NOT EXISTS (SELECT * FROM sysusers WHERE name=@ContentVSAccount) EXEC sp_grantdbaccess @ContentVSAccount; EXEC sp_addrolemember 'db_owner', @ContentVSAccount; Note In lines 3 and 4, replace domain\contentaccount and domain\adminaccount with the domain account for the content virtual server and the domain account for the SharePoint Central Administration virtual server. If the accounts are the same, SQL Query Analyzer will display an error message, but the process will still succeed. If you are using SQL Server authentication, in lines 3 and 4, replace domain\contentaccount and domain\adminaccount with the SQL Server account name.If you are using SQL Server authentication, type the following query. DECLARE @SQLAccount nvarchar(255) SET @SQLAccount = N'sql_user_account'; EXEC sp_changedbowner @SQLAccount; Note In line 2, replace sql_user_account with the name of the SQL Server account that Windows SharePoint Services is configured to use to connect to the computer that is running SQL Server. This must be an existing SQL Server account. Click Execute Query to update the database. Repeat the previous steps for each additional content database. Verify that setting the DBO and the appropriate permissions was successful. To do this, follow these steps: On the computer that is running SQL Server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager. Under Databases, locate the configuration database, right-click the configuration database, and then click Properties. On the General tab, verify that the owner is the account that you specified in the queries. For SQL Server authentication, the owner is the SQL Server account. For Windows authentication, the owner is the application pool account that the SharePoint Central Administration virtual server is running as. Repeat these steps for each of the other content databases Best Regards, Ammar MCT

Amar, thanks for the kind response!I pointedour network admin to both your post and the referencedMS KBlink. He says he followedthe procedures, including giving NS account sys admin on the sharepoint sql server instance, and still no luck; 500 error remains upon central admin site access attempts. Any other avenues to pursue? I was especially wondering about provisioning a non-built-in domain account as the farm credentials account - more like in a farm install - instead of using network service; worth trying? Thanks in advance!Many are clever; few are wise

Hi,Please check the following http://support.microsoft.com/kb/949350it is about IIS 7 on Windows 2008Best Regards, Ammar MCT

Hi, Which version is your WSS 3.0 SP? What action did you perform recently? For example, install update or change password? Check whether your accounts meet Office SharePoint Server Security Account Requirements, please refer to (http://go.microsoft.com/fwlink/?LinkID=92883&clcid=0x409). As of Windows SharePoint Services 3.0 Service Pack 1 (SP1), you can now install Windows SharePoint Services 3.0 on Windows Server 2008. You cannot install Windows SharePoint Services 3.0 without service packs on Windows Server 2008. So please check whether you use Windows SharePoint Services 3.0 Service Pack 1? If not, try to uninstall WSS 3.0 and reinstall WSS 3.0 SP1. Do not add any server roles in Windows Server 2008 Server Manager before setup for Windows SharePoint Services 3.0 is complete. If you add a server role, the setup process will fail, and you will need to uninstall and reinstall Windows SharePoint Services 3.0. If your WSS 3.0 include SP1, please enable ULS logging, and reproduce the issue, send the error information into the forum. For more information about how to enable ULS logging, please look into the following link Configure diagnostic logging settings http://technet.microsoft.com/en-us/library/cc262714.aspx For more information about how to uninstall WSS V3, please refer to the following articles: http://www.howtonetworking.com/msapps/wss14.htm For detailed information about Install a stand-alone server on Windows Server 2008 (Windows SharePoint Services), please refer to the following article: http://technet.microsoft.com/en-us/library/cc287813.aspx For more information about "HTTP 500 - Internal server error", please refer to the following article: Error message when you try to connect to a site in a Windows SharePoint Services 3.0 site collection: "HTTP 500 - Internal server error" http://support.microsoft.com/kb/937038 Important Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. Hope it helps. Rock WangRock Wang MSFT

I also have this problem: I've installed a SQL 2008 Express (x64) on Win2008 Standard (x64), then install WSS 3.0 with sp2 (x64). Everything seems find during the installation and configuration wizard, but after the wizard and prompt out the IE, it show the HTTP 500 internal server error. I've tried the above solution, also tried to apply WSS hotfix, install language pack, etc. but still don't work. any other advise and solution? it really make me crazy.....