My 2003 server downloaded (w/in the last few days) an update for Windows Sharepoint Services 3.1 (KB932091). I ran the install and it seemed to lock up before completing the install. I ended up having to reset the server and I ran the update again after the restart. It completed with no problem. However now I cannot access the pages I've created on Sharepoint nor the Central Administration Site. I'm prompted for credentials when I try to browse to it but get 404 Not found error on my workstation and Http/1.1 404 Connection Close error when trying to browse through IIS on the server (also prompted for credentials there).
I'm hoping someone more knowledgeable than me experienced this after the Auto Update and can help out.
I have the same exact problem. WSS 3 on SBS 2003. Haven't been able to fix it either. Even tried to restore last night''s backups of the SQL STS config,admincontent,and site content dbs. No dice.
One additional note. When getting the 404 error, windows event log gives me these errors:
For my intranet site: The database STS_iron_427867325_2196 on IRON\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.
For central admin site: The database SharePoint_AdminContent_52effa5e-c1f9-4fa2-aac9- bc90ffc21099 on IRON\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.
I am getting the exact same errors after having the exact same problem with the update. It froze, I had to restart, then the 404 errors started occuring with the same Event information posted above. Please help!
There are already other posts on this exact issue. I called PSS (800) 936-4900. Have been on hold (still on hold as I type) for 3 hours 45 minutes. It is a free support call based on the issue.
I will post the results as soon as I get it fixed. May not be until tomorrow as I MUST leave work in 1 1/2 hours.
> My 2003 server downloaded (w/in the last few days) an update for > Windows Sharepoint Services 3.1 (KB932091). I ran the install and it > seemed to lock up before completing the install. I ended up having to > reset the server and I ran the update again after the restart. It > completed with no problem. > However now I cannot access the pages I've created on Sharepoint nor > the Central Administration Site. I'm prompted for credentials when I > try to browse to it but get 404 Not found error on my workstation and > Http/1.1 404 Connection Close error when trying to browse through IIS > on the server (also prompted for credentials there).
> I'm hoping someone more knowledgeable than me experienced this after > the Auto Update and can help out.
FWIW, things i've tried so far to fix this that didn't work, so any of you don't waste your time.
1. Restoring all SQL 2005 DBs from backup (including master) [sql 2005 management studio/sqlcmd] 2. Repairing WSS 3.0 [add/remove programs] 3. Repairing .NET 3.0 [add/remove programs] 4. Restoring my IIS web directories (e.g. C:\inetpub) from backup [xopy] 5. Fake-uninstalling the KB (by means of registry modifications) and attempting to reinstall it again. [regedit] 6. Restoring the WSS site from a "stsadm -o backup -url" backup [stsadm -r restore]
I'm tapped, short of removing all of WSS, reinstalling, and restoring last night's DBs (and even that may not work i suspect).
I had the same problem. and i fixed it by going here http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E... download the file that matches your OS. ie x32 or x64 If you try to run the file it will tell you the patch is already installed. but run the file with "/extract" extrace the file to someware and run "dw20w.msp" Let it do its thing. It takes a while......Then presto. well as least for me.
> I had the same problem. and i fixed it by going here > http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E... > download the file that matches your OS. ie x32 or x64 > If you try to run the file it will tell you the patch is already > installed. > but run the file with "/extract" extrace the file to someware and run > "dw20w.msp" > Let it do its thing. It takes a while......Then presto. well as least for > me.
> > This is the update that seemed to cause my problems.
> > Whenever I navigate to one of our sharepoint 3.0 sites in a browser we > > get a message like this.
> > "HTTP/1.1 404 Connection: close Date: Thu, 29 Mar 2007 10:31:42 GMT > > Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET > > MicrosoftSharePointTeamServices: 12.0.0.4518"
> > We're using Small Bssiness Server 2003 RS Premium. Are you guys using > > Windows 2003 Server?
> > Robin
I'm up again! Same fix as above. Glad y'all said to let it run for a while as I think mine took about an hour. Which makes me wonder if I hosed it up by not letting it run long enough the first time. Did all (or any) of you cancel or try to stop the original install?
Also - Andrew> how did you find the KB article (fix). I searched a fair bit yesterday and couldn't find anything on it. Not that I would have thought of running it again - but I should have at least stumbled across that page.
> I had the same problem. and i fixed it by going here > http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E... > download the file that matches your OS. ie x32 or x64 > If you try to run the file it will tell you the patch is already > installed. > but run the file with "/extract" extrace the file to someware and run > "dw20w.msp" > Let it do its thing. It takes a while......Then presto. well as least for > me.
On Mar 28, 9:16 pm, "Andrew Paternoster" <and...@gpk.net.au> wrote:
> Hi Guys
> I had the same problem. and i fixed it by going herehttp://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E... > download the file that matches your OS. ie x32 or x64 > If you try to run the file it will tell you the patch is already installed. > but run the file with "/extract" extrace the file to someware and run > "dw20w.msp" > Let it do its thing. It takes a while......Then presto. well as least for > me.
> Let me know how you guys go with it.
Yes! That is EXACTLY the solution for the same problem that was vexing us.
Our system kept telling us "the patch is already installed" so we tried the "/extract" trick you mentioned to run "dw20w.msp" and we let it run. It appeared to be hanging almost indefinitely about half way through, but it took about 4 hours to completely run but it ran successfully and solved the problem. Thank you for your help!
By the way, our server is Microsoft 2003 Standard edition on a Raid 5 (Dell Poweredge 2600) with Sharepoint 2007.
I rebooted, ran dw20w.msp again. This time I let it run to completion. Took about 1:20. I then had to reboot twice before I was able to access the site.
"Steve Gould" <steve.gould(at)apawood.org> wrote in message
>> I had the same problem. and i fixed it by going here >> http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E... >> download the file that matches your OS. ie x32 or x64 >> If you try to run the file it will tell you the patch is already >> installed. >> but run the file with "/extract" extrace the file to someware and run >> "dw20w.msp" >> Let it do its thing. It takes a while......Then presto. well as least for >> me.
I followed your instructions to run the dw20w.msp file and my sharepoint sites are back!!. It took about 1.5 hours to install.
As a result I've switched off auto approval of security and critical updates to our small business server and will control the patching from now on.
For anyone who may need to know we were running Windows Small Business Server 2003 R2 Premium Edition with Sharepoint 3.0 alongside Sharepoint 2.0 and reinstalling the update worked just need to be patient.
i have the same problem, but the instruction with the dw20w.msp doesn't work. after the installation which tooks one hour only the administration page could be connect.
:-(
On 30 Mrz., 10:47, robin.shaw...@googlemail.com wrote:
> I followed your instructions to run the dw20w.msp file and my > sharepoint sites are back!!. It took about 1.5 hours to install.
> As a result I've switched off auto approval of security and critical > updates to our small business server and will control the patching > from now on.
> For anyone who may need to know we were running Windows Small Business > Server 2003 R2 Premium Edition with Sharepoint 3.0 alongside > Sharepoint 2.0 and reinstalling the update worked just need to be > patient.
> I had the same problem. and i fixed it by going here > http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E... > download the file that matches your OS. ie x32 or x64 > If you try to run the file it will tell you the patch is already installed. > but run the file with "/extract" extrace the file to someware and run > "dw20w.msp" > Let it do its thing. It takes a while......Then presto. well as least for > me.
Doesn't work so well for me. I have tried running the dw20w.msp and it finished successfully. Or I should say it finished without throwing up an error. But I still cannot access the SharePoint site or the administration side. 404 errors. However, it is a different 404 error than if I were to request a specific page (default.aspx for example). The root requests generates a detailed 404 error, whereas the page requests generates the generic which IE dumbs down for me (I compared the source so I know they're different). I don't know if this makes any difference or not. One other thing I've also tried is the SharePoint Configuration Wizard. It will not successfully run either. This is very frustrating! You don't expect patches to break things, especially critical patches deployed via Windows Update...
Along with the KB932091 update, our windows update applied SP 2 and four other updates all at the same time. Now, my Sharepoint site is inaccesible. I have tried to rerun the KB932091 update by extracting it, and it run only for about min and poops... installation windows disappears. I have tried to access SharePoint Products and Technologies Configuration Wizard and it pops an error described below.
Is there any way to get this back up or do I have to start all over with my Sharepoint site?
Thanks in advance..
:-Uday
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text ************** System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchem aCompatibility() at Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) at Microsoft.SharePoint.SPWeb.InitializeSPRequest() at Microsoft.SharePoint.SPWeb.EnsureSPRequest() at Microsoft.SharePoint.SPWeb.get_Request() at Microsoft.SharePoint.SPWeb.InitWeb() at Microsoft.SharePoint.SPWeb.get_WebTemplate() at Microsoft.SharePoint.SPEvaluatorModeProvisioning.TryGetIsSiteProvisioned(St ring template, String relativePath, Nullable`1 port, SPSite& provisionedSite, SPWeb& provisionedWeb, Uri& provisionedUri) at Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.ShowNextFormForServ erRoleSingleServer() at Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.PsconfigBaseFormNex tButtonClickedEventHandler(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
|
