Message from discussion
404 and Page Not Found error on Sharepoint Site
Path: g2news1.google.com!postnews.google.com!l77g2000hsb.googlegroups.com!not-for-mail
From: sean.chees...@gmail.com
Newsgroups: microsoft.public.sharepoint.windowsservices
Subject: Re: 404 and Page Not Found error on Sharepoint Site
Date: 5 Apr 2007 13:10:03 -0700
Organization: http://groups.google.com
Lines: 13
Message-ID: <1175803803.688239.192070@l77g2000hsb.googlegroups.com>
References: <1175109161.699907.211080@n76g2000hsh.googlegroups.com>
<1175126418.340307.313140@r56g2000hsd.googlegroups.com>
<1175128364.197124.304220@n76g2000hsh.googlegroups.com>
<uWvo8AacHHA.2120@TK2MSFTNGP03.phx.gbl>
NNTP-Posting-Host: 68.57.217.39
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1175803804 1343 127.0.0.1 (5 Apr 2007 20:10:04 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 5 Apr 2007 20:10:04 +0000 (UTC)
In-Reply-To: <uWvo8AacHHA.2120@TK2MSFTNGP03.phx.gbl>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.04506.30),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: l77g2000hsb.googlegroups.com; posting-host=68.57.217.39;
posting-account=awK9zw0AAABEJjHwQpR5qUfvoDiKCIZr
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...