• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 987
  • Last Modified:

Unable to upload or save documents to MOSS 2007

Hi
I have a MOSS 2007 with a large content DB, around 96GB. Single WFE (win2k3R2) and single banckend SQL 2005 (win2k3R2). Both are x86 server with 4GB RAM. MOSS has SP1 installed and runs Forefront for SharePoint with SP1.

Recently we started receiving messages that users were unable to upload files or save any files opened from MOSS back on to the doc libraries. I suspected this to be something to do with Forefront as it had done so in the past. The AV settings were to scan the file when uploaded or downloaded. I removed scan from downloading files but no avail.

I tried various other things such as reset iis, and reset search index as event log was full of error message 4127. Eventually resetting w3wp seemed to do the trick and system was able to upload and save docs.

But then it broke again and no amount of tricks seem to get it back to normal. The error message is "The URL ' IT Documentation/IT Reports/ ITC Reports/ Weekly Report.docx' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web."

In the SharePoint log I also get the following mesasage" w3wp.exe (0x79D4)                             0x3980      Windows SharePoint Services         General                             8kh7      High          The URL ' IT Documentation/SharePoint action plan.doc' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web."

 MOSS 2007 has not been updated to SP2 but has had some updates such as .NET 3.5 installed.
Any thoughts....
0
newstarter
Asked:
newstarter
  • 5
  • 4
1 Solution
 
GeorgeGerguesCommented:
do you see any issues on the application log (event viewer ) when this happens ?
0
 
newstarterAuthor Commented:
I dont see anything that indicates why there was a failure. Having said that, there are couple of entries that may help to decipher the cause. These do not appear when document upload fails. They just regularly appear.

Event Type:      Error
Event Source:      Office SharePoint Server
Event Category:      User Profiles
Event ID:      5555
Description:
Failure trying to synch web application f8a7b7d6-6a46-4166-a7a9-1aad4b977aeb, ContentDB 2166821b-e906-4478-aa9f-2296ef03713f  Exception message was A duplicate site ID b164106d-70bc-4763-ae8b-d17c8dd57fa1(http://planet) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.

Event Type:      Error
Event Source:      Office SharePoint Server
Event Category:      Office Server General
Event ID:      7888
Date:            23/03/2011
Time:            03:00:02
User:            N/A
Computer:      GDC1-MOSS1
Description:
A runtime exception was detected. Details follow.
Message: A duplicate site ID d4cabae9-584d-4660-bb08-b37d694e5f34(http://planet/sites/ISLoB) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
****
The above error refers to my main web collection. The database may have been restored in 2009 but the problem started occuring only this month.
*****
Techinal Details:
Microsoft.Office.Server.UserProfiles.ProfileSynchronizationDuplicateSiteIDException: A duplicate site ID d4cabae9-584d-4660-bb08-b37d694e5f34(http://planet/sites/ISLoB) was found. This might be caused by restoring a content database from one server farm into a different server farm without first removing the original database and then running stsadm -o preparetomove. If this is the cause, the stsadm -o preparetomove command can be used with the -OldContentDB command line option to resolve this issue.
   at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.RegisterSitesForSynch(Guid[] rgGuid, Int32 nGuids, Object dummy)
   at Microsoft.Office.Server.UserProfiles.SynchCollection`2.FlushAdds()
   at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.AddRemoveSites(String strFirstChangeToken, SPChangeToken lastChangeToken)
   at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer.SynchContentDB()
   at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)
******
This error refers tothe second site collection in the farm. But this is not in use generally.
0
 
newstarterAuthor Commented:
OK Just now I tried to upload a document and it worked. It appears that overnight something happens that either makes it work or breaks it. I know the Application Pool is set to recycle at 01:28 at night. Under the web garden settings two worker process threads have been allocated. Request queue limit is set to 1000. Pinging is enabled under Health ckeck and rapid failover protection is enabled. The identity is set to farm admin account.

I suspect the culprit may be w3wp but how can I know for sure?
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
GeorgeGerguesCommented:
well , that might be your problem

On the sharepoint applications all pools must be single threaded.

Can you set the Threads on your garden to 1

that is the problem for sure


Here is a simple test to re-simulate your problem ,

try to do the same function ( upload the same file to the same library at the same time) from 2 different workstations


that should break it.


Again the recommendation is a single thread per pool.

Best of luck.
0
 
newstarterAuthor Commented:
Hi
It is certainly worth a try. I have changed the app pool to be single threaded and done an iisreset. All looks good as we are able to upload docs and save to SharePoint.

I will wait for 24 hours before considering this resolved.

Many thanks for your suggestion. I would not have suspected app pool to the the root of the problem.
0
 
newstarterAuthor Commented:
Yes the problem certainly seems to be with App Pool. I have now set it to be single threaded but still it failed.

There are 6 App pools and three of them are set to recycle at certain times (this is a departure from default config).
80 AppPool ------------------Recycle at 01:28
Shared Services -----------Recycle at 01:18
Intranet Shared Services--Recycle at 01:30
Central Admin V3-----------Recycle at 01:06

Could this be causing the problem? Resetting them when we have problem makes everything work again.
0
 
GeorgeGerguesCommented:
do you have more than one web server for this farm ?
0
 
newstarterAuthor Commented:
There is only one WFE and one SQL. I am now installing Windows updates and will follow that with MOSS2007SP2. The hope is that updates will resolve the issue.

Would you recommend setting max virtual memory and max used memory for the app pool?
0
 
GeorgeGerguesCommented:
I would not put a cap on memory no the application pool.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now