If some of you have come across this error and don't know how to fix it, I have found 2 possible fixes.
1, Recreate the site collection
2, Webtempcustom.xml file in the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\1033\XML directory was corrupt and it was causing the problem.
You can try to fix the xml file, but much easier just to re-create the site collection.
Fadi
Subscribe to:
Post Comments (Atom)
9 comments:
Hi, I am trying to manage a share point site for keeping track of projects of my department. I get the same error while trying to create an alert for a project list. Can you please clarify what you mean by "Recreate site collection"?
There's 2 things to try.
1, Do a STSADM backup, delete the web application. Create a new one and restore to it.
2, If the problem still is happening, follow these steps:
Export (using stsadm -o export) the entire application by running stsadm -o export -url http://web -filename c\:web.bak.
Create a new web application on the same server easy through central administration and create a new web application and site collection.
Create all of the sites and sub sites for the structure to be in place, so if there's 10 subsites in your app, simply create the ten.
When you create the new site, use the same template as the original.
Import the application if you're lucky it will import all of the subsites as well. If it errors there should be a log written somewhere stating what went wrong.
Once the app is up and running, then add all of the users back in. Since SP is in AD Creation mode, you cannot select existing users in the domain.
Let me know if you have any problems.
I had the same issue and couldnt believe tha ti would have to delete/restore my entire application.
For me, I go the error when i clicked a link to an application page. I looked and realized that one of the items the application page was dependant on had been deleted. Like if you are using hte Knowledge Manager Application and had deleted the KnowledgeBase.
See if that is the case for you... what does the page/link you are going to when you get the error reference. It may not always be as obvious as it was for me but I believe this will be the case for others as well.
I received the DISP_E_EXCEPTION while trying to set an alert on a view with four filter clauses (a=b and c=d and...). By changing the view to use just three filter clauses, the error went away and I was able to create the alert. Re-adding the fourth clause to the view after creating the alert didn't seem to work.
Fix found.
We uncovered the same issue and have now resolved it, without having to start over. We posted a more complete note on our Facebook page:
javascript:void(0)
Dave,
I went to your Facebook link and I do not see where the fix you indicated can be found. Please clarify.
My apologies, seems I did not post a direct link to the post, just the NetIQ page.
Please try: http://www.facebook.com/note.php?note_id=34932302116&id=17480979358&ref=share
I had this error happen to me this morning. Applying the following two Service Packs fixed the issue on my local instance:
WSS
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ef93e453-75f1-45df-8c6f-4565e8549c2a
MOSS
http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
If you have change somewhere in your web part that you dispose the SPSite or SPWeb, remove it. It would surely work. :)
Post a Comment