Specific Error:
An error occurred accessing your Windows SharePoint Services site files.
Authors - if authoring against a Web server, please contact the Webmaster for this server's Web
site. WebMasters - please see the server's application event log for more details.
Resolutions:
Only "good" resolution seems to be a wipe-out of the web site on the server and a re-setup along with a wipe out of the local site and a re-import locally with a new publish up to the server.
However, since that is not something we admins like to here, so start banging your head and offer a quick prayer:
1. Some posts indicate a corrupted cache and the use of FP2003 using HTTP 1.1.
First, turn off HTTP 1.1 support in IE (Tools --> Internet Options - Advanced)
Second, delete all caches, history, including offline files.
2. Check for a limit on file size upload to the server. The FP client may be trying to upload a large file during publishing. According to the message boards (ref. 814332) a MS security update added a default limit of 50mb some time in the past.
3. Check and see if a database file is being uploaded. When SharePoint services is loaded -- it probably is since that's how the server installs itself -- MDB files are prohibited from being uploaded.
4. If IIS 4 or 5 or loaded, it could be due to the fact the the Isolation mode for the site is too high. In other words, the fix to is to put it to low and potentially have one site's naughty code transfer to all the others. Oh happy thought.
5. Publishing to a "SharePoint" enabled web site appears to use a "manifest.xml". (I'm familiar with this with Java-based Eclipse update sites) However, with this one from MS, it seems to die if there are two many files. The work around is to reduce the number of files in a single web site.
previous page
|