Hi all,

Really hoping someone else has seen this before.  This started out affecting only one or two users and now is effecting everyone.  It started in the last few weeks.  Thought it was maybe a microsoft update that had messed something up but I've rolled back and its still broke.

when our users try to upload to document libraries they're getting either:

----

Form validation error: web server is busy.

or

Form validation error: The url 'document name' 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

----

The system is windows 2003, SQL 2005, SPS 2003 with SP2 and WSS version 2 with SP2 installed.

• Theres no quota lock on SQL databases (including tempdb)
• SQL databases are all set to 80 compatability
• Theres no quota lock on the site collection
• Theres no special characters in the document names being uploaded
• The files are well below the file upload max (which sits at 90MB at the moment)
• The disk drives where sharepoint and the sql databases reside are not full (the databases sit on a san with literally gigs of free space).
• Theres nothing in the application error logs (on the server).

I've searched microsoft technet, googled it and searched microsofts  knowledge base and drew a blank.  Most of the posts I've seen related to this refer either to special characters or the sql database being limited - neither apply in this case..

I'm wondering if a backup/restore would sort it?  need to sort this before I can migrate to 2007.

many thanks in advance

hey all,

ok made some progress.  Did a full restore of the site and still getting the same errors but I have noticed something

User goes to upload document.  Gets 'Form validation error' message.  Nothing appears in the document library.

however if you go into the explorer view of the document library - the files there!

So somewhere between the upload and the response from the server somethings screwing up.

Is there any way to trace this? if not will I have to repair the content database and how?

hey all,

this ended up working for us:

uninstalled SPS 2003 and WSS.

reinstalled WSS and SPS (with relevant service packs)

installed the hotfix 918743 - this adds a command to stsadm to allow database repair of the content database (it checks for orphaned links etc.)

after running the command stsadm -o databaserepair -url <servername> -databasename <database>

then restart the server and lo and behold both errors seems to have dissappeared.

hope this helps someone.

We are trying this as a solution.  Did you find it necessary to uninstall first?  Could just updating to the current sp do the same thing?

Thanks,

Dave