Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

An error occurred accessing your Windows SharePoint Services files 1

Status
Not open for further replies.

marko2002

Technical User
Dec 16, 2003
61
GB
Guys, first off if the answer to this is on the site somewhere I apologise, though have searched with no luck!.

The problem is this - I have 1 main web server which is also my domain controller and after installing Windows 2003 Service Pack 1 I noticed I was having great difficulty in uploading my web sites or any changes using FrontPage 2003. I always had used FP2003 previously without any problems at all, though after SP1 it was so frustrating trying to upload I actually went to the trouble of rebuilding the entire domain from the ground up!.

The error message was as follows . . .
"An error occurred accessing your Windows SharePoint Services 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."

After rebuilding the server and NOT applying SP1, it began allowing me to upload my web site again, though half way through the upload it displayed the same error again!. The pattern is that it shows you this error, hit OK to rid it, try uploading again then same error again, hit OK to rid it and then publish again only to get so far and then the error appears again.

If I stick with it, I can sometimes eventually get the whole site uploaded, but then when I make ammendments to the site and have to upload again it starts all over again!!. I've heard that uninstalling SP1 solves the problem, but it didn't for me (and there are no clue's in the event log either!!). Stranger still, I am not using SharePoint nor is SharePoint services installed, though I do see a "Microsoft SharePoint Administration" site underneath my "Default Web Site".

Any help on this one greatly received.
Cheers
Marko
 
For anyone intersted, I totally demolished the domain after backup and rebuilt the entire thing from the ground up once more. I didn't apply SP1 but instead closed down all ports from the router and gradually applied each patch to the server one by one. I was previously getting a shutdown message from the "lsass.exe" service, though after closing down all ports from the router this message dissapeared. Once I had fully patched the system I opened up all the ports again and hey presto - was able to upload my web site once again without those annoying errors!!!. So, I guess it's obviously just a matter of SP1 for Windows 2003 screwing something up!.

Thanks to all who looked at the post though.
Marko
 
Question: I am getting the same error, exact same problem and have looked for a solution all over the net without great result. The only solution I have seen that worked is to remove SP1. My question is if anyone attempted to remove SP1 on a live site without creating major problems.
 
arlems, I wouldn't to be honest - unless someone else can advise you otherwise I had major problems with both IIS and exchange webmail once I removed SP1 - however, I recently took the plunge again and decided to implement SP1 as the risks to me personally were greater than the inconvenience this issue was causing.

Having said that, I did remove SP1 previously and it didn't seem to make a difference to my problem, therefore it would seem that once you have SP1 installed that's it - no going back, even after uninstalling it!.

On a slightly more optimistic note, I have noticed that recently I have not been having as great an issue with uploading as I did previously. It would appear now that on attempting an upload I will get the error message now and again, though after the first message the upload ALWAYS goes ahead without a problem the second time!. Not too sure whether MS have fixed this prob or not, though haven't yet had the time to inspect their patches to see if one of them indeed has fixed this prob!. May be worth investigating. My advice is to fully update your server with the latest patches, reboot and give it another shot (unless you already are patched!).

Most annoying thing about this problem is the lack of acknowledgement from Microsoft themselves.

Good luck
Marko
 
Thank you for your answer. I didn't think about getting the latest patches from Microsoft. Will Do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top