Very Urgent problem with Sharepoint 2001

[raetser]

Dear Friends,

We have a very serious problem with a customer where we have implemented a Sharepoint 2001 since 2 years now. All over sudden, since last week, they receive nothing but script execution errors, and we don't know what is wrong.

These are the errors we find:

System webparts like Subscription, Categories, Search and Document Library webparts are giving problems

Subscription Summary
Error: Failed to get subscription results for

Categories
Error: Script Execution Error: Invalid query.

Document Library
Folder Information: Script Execution Error: Microsoft JScript runtime error 'strRootDocLibLabel' is undefined line = 1, col = 0 (line is offset from the start of the script block). Error returned from property or method call.

Documents
Script Execution Error: Object required

Search
Matching Categories: XML Load Error: Invalid at the top level of the document.

Pls help us to resolve this issue.

Thanks a lot in advance,

Erwin

 

[pxbenl]

Hi Erwin,

We experience the same problem and so far, we did not have ANY luck discovering the source of the problem.

The things we have tried so far:
- Installing servicepacks for Win2K / SPS
- Updating MS scripting host
- Isolating applications (stopping web sites)

The thing we see happening is that STORE.EXE claims an awful lot of memory (1,6 of 2,0Gb available). We consider that to be the cause of the errors, but what causes STORE.EXE to grow that big (and fast!).

I would very much appreciate your comment if you can trace the source of our common problem!

Has ANYONE as yet have an answer? By now, we have to reboot IIS 3-8 times a day.......

Any help is much appreciated.

Ben.

 

[raetser]

Hi Ben,
Jeee, I am also still working on it. Something must be wrong when using serverXMLHTTP, I have written some code to test it, and it fails on the server where we have the problem, and it works on a working sharepoint 2001 implementation.

It is in TahoeUtils.asp, in the function StartQueryEx I think. There is also a function WaitForQueryResponse, and that is where he throws the Invalid Query error.
If in the first function, you replace the serverxmlhttp with xmlhttp, and you put the code in the last function in comment, then the subscriptions work again.
Now for the really funnyt stuff, if you revert back to serverxmlhttp in the first function, and uncomment the second, then the document library works! At least, for 5 minutes, because then it starts giving the errors again...very strange.
Anyways, if I can come up with a solution I will surely post it here!

 

[pxbenl]

Is there anyone who has discovered the cause of the Script Execution Errors? We are running out of options fast and the problem is becoming increasingly annoying.

We have tried adding extra memory (3Gb) with no succes.
Our supplier is constructing tools to either reboot the server or restart IIS in case the error occurs, much to my dismay, as I feel much more for finding the CAUSE of the problem.

Can anyone help us with tips/suggestions?

If all else failes, we are planning to deploy seperate servers for our applications (i.e. 2x SharePoint Portals, 1x Dedicated application).

 

[raetser]

Well Folks, we got it solved, but it was not that we pinpointed the culprit and resolved it, no. There obviously was a problem with the webstore. xmlhttp worked, serverxmlhttp didn't (against the webstore, because using serverxmlhttp for another purpose worked well). So after a lot of testing and the aid of Microsoft Product Support (they were reading the whitepapers slower than we did, because they always came with an idea that we tried the day before) we decided to update Sharepoint to Service Pack 3, taking the risk that everything would be ruined, because we were running version 1 of the Service Pack.
So very much to our surprise, the portal worked after the upgrade, just some minor customisations that we made to TahoeUtils needed to be added again, but for the rest the subscriptions where still there, the layout, the webparts,...
So the problem lies within the webstor, probably, if you would do a repair of SP1 you will solve the problem as well, but it looks like SP3 is a better option (or should be...)

Erwin