views:

165

answers:

5

Title says it all.

Everything works fine for most accounts 100% of the time but here and there some users who are able to access a subsite fine one day are greeted with a standard 404 the next. This can last for an hour or two days, it's really inconsistent.

I check the iis logs and it says the status is also a 404 for these requests, nothing else looks unusual. Sharepoint logs have nothing for the timestamps either.

Correct me if I am wrong but if it was a permission issue an access denied message would be shown.

It is not the individual computer because when a user is having this problem and I can log in with their account and I also get the 404 error although I am on the exact site with another account in another browser at exactly the same time, and it works perfect.

Any suggestions would be greatly appreciated, I've done a fair amount of searching but can not find a similar situation or help anywhere.

A: 

This seems like a longshot, but... could those SharePoint sites be throwing a 404 HttpException? It seems like you'd see that in the SharePoint logs, too, so it's even more unlikely.

At any rate, is your SharePoint logging level set to an appropriately verbose level to debug weird stuff like this?

Chris Farmer
It was set at default levels, I tried setting it to verbose but the file grew to about 90megs in under 10 minutes so I obviously can't leave it like that. There is a ton of spam saying connection to database established, connection string is ... ectAny suggestions on which types of settings I should set verbose on?
savageguy
A: 

Are people checking in & publishing master page changes when new CSS files and/or other includes (script files, etc.) are not yet published at all? I've seen this cause a 404 a few times when users forget to check before they publish.

Greg Hurlman
No new files have been added, or even modified for that matter, in the last month that would be included with the master page or page templates.
savageguy
A: 

Since the information is very strict at the moment, I will throw a few questions that might lead you towards the problem.

  • Are we on a loading balance setup? The intermittent 404 might be cause by one of the servers Web FrontEnds not correctly serving requests.
  • Are we running out of disk space in the SQL Server machine? This might cause it
  • Are the blogcache or site caches enabled? Some routines may break them
  • Do we have Anti-Virus on the server? (it HAS to be asked :p)
  • We get very high packet loss between the servers? (The error would be different though)

Something that might occur very often is when you have, say, custom code a DLL on the GAC or the bin folder, and since you could be on loading balance the second server does not have this DLL in its own GAC or BIN folder. Sharepoint usually raises 404s when assemblies are not found too, not only requests.

F.Aquino
No load balancing but there are two applications, one extended from the other. One is for internal office use, the other is accessible via the internet using alternative access mappings. The majority of reports I get are from people connecting externally but this also occurs to local users, I assume because there are much less local users so I hear much less about it.Disk space is fine, site cache is enabled - is disabling it something to try? Forefront is running on the server along with semantic. I have not seen any packet loss.I am able to see the 404 status in the iis log files but not
savageguy
in the sharepoint logs, there is nothing besides the useless messages
savageguy
A: 

I have had to write custom code within a SharePoint context and I had those 404 errors as well. The solution, in my case, was to ensure that the block of code executing had these 2 conditions met:

1) Run with elevated privileges, regardless of the fact that it is a 404 this was part of the solution.

2) web.AllowUnsafeUpdates = true; This line of code needed to be added even though it was wrapped within an elevated privileges block.

Once these were added the issue did not occur. This was happening on both load and non-load balanced environments.

Woot4Moo
the only custom code running on these pages is the navigation control I overwrote to display links in a normal, non complete mess in order to style properly. This control has been working fine for the last 6 months and pre-dates these issues by a far amount so I really don't think this is the problem.
savageguy
did you recently upgrade the service pack?
Woot4Moo
A: 

This reminds me of a strange asp.net bug that I had a few months back. It was caused by a patch that had been applied (to the framework if I remember correctly)

try downloading this Windows update list tool and have a look at what has changed since the problem started.

I concede that if there was a problem with a patch then its more likely that it would be a consistent error, but it's worth a look.

Matt Joslin