I'm hoping someone more knowledgeable than me experienced this after
the Auto Update and can help out.
thanks
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.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Date: 28/03/2007
Time: 21:01:50
User: N/A
Computer: SBS001
Description:
The database SharePoint_AdminContent_87e28dcd-3e40-4d34-b88c-
de20bbfc9507 on SERVER\Microsoft##SSEE is not accessible to missing
Windows Internal Database signatures.
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.
<mattp...@gmail.com> wrote in message
news:1175109161.6...@n76g2000hsh.googlegroups.com...
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).
-Tony
I had the same problem. and i fixed it by going here
http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93EF-4423-BD0B-06B1B331C7AC&displaylang=en
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.
Thanks for your reply. This solved my problem!!!
I extract the update and started the dw20w.msp. I took about 45 minutes when
it was finished, but then everything worked fine!
Thanks again!
Marco.
"Andrew Paternoster" <and...@gpk.net.au> wrote in message
news:uWvo8Aac...@TK2MSFTNGP03.phx.gbl...
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 use Windows Server 2003 and WSS3.0. The solution of Andrew solved my
problem.
I think, an installation on SBS2003 will also work with this solution.
Regards,
Marco.
<robin....@googlemail.com> wrote in message
news:1175164764.6...@n59g2000hsh.googlegroups.com...
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.
"Andrew Paternoster" <and...@gpk.net.au> wrote in message
news:uWvo8Aac...@TK2MSFTNGP03.phx.gbl...
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.
"Steve Gould" <steve.gould(at)apawood.org> wrote in message
news:exBo1Lh...@TK2MSFTNGP05.phx.gbl...
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 tried to repair the Sharepoint Installation, but the wizard has
a JIT error and I have yet to try and ignore it to press on.
This is a real shame to have a client starting to be happy with
Sharepoint, only to have a Microsoft patch screw it up.
I really don't want to lose that Sharepoint site.
Andrew Paternoster schrieb:
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.ValidateDatabaseSchemaCompatibility()
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(String
template, String relativePath, Nullable`1 port, SPSite&
provisionedSite, SPWeb& provisionedWeb, Uri& provisionedUri)
at
Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.ShowNextFormForServerRoleSingleServer()
at
Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.PsconfigBaseFormNextButtonClickedEventHandler(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)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
psconfigUI
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase: file:///C:/Program%20Files/Common%20Files/Microsoft%20Shared/web%20server%20extensions/12/BIN/psconfigui.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.SharePoint
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.dll
----------------------------------------
Microsoft.SharePoint.SetupConfiguration.Intl
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.SetupConfiguration.intl/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.SetupConfiguration.intl.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
Microsoft.SharePoint.Security
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.Security/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.Security.dll
----------------------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
Microsoft.SharePoint.Search
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1015
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SharePoint.Search/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.Search.dll
----------------------------------------
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD/msvcm80.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.210 (QFE.050727-2100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Microsoft.SharePoint.AdministrationOperation
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.AdministrationOperation/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.AdministrationOperation.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.DirectoryServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
----------------------------------------
Microsoft.SharePoint.Library
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.Library/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.Library.dll
----------------------------------------
Microsoft.SharePoint.intl
Assembly Version: 12.0.0.0
Win32 Version: 12.0.4518.1016
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.intl/12.0.0.0__71e9bce111e9429c/Microsoft.SharePoint.intl.dll
----------------------------------------
************** 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.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
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.