Don't forget spcontnt is your key for 'web part' error resolution
Submitted By: Riwut Libinuko, Plasmedia
Posted On: 1/13/2005
Overall Rating: 3 (1 ratings, 1 comments)
Description:
Eventough webpart is very powerfull, but debuging web part is painfull. For example, you forget to put try-catch block in your code - and one day you get error without any clue to edit. Or imagine, you're creating on-the-fly graph web part, and send wrong HTML header to the page. Causing Sharepoint page shows image only and no interface to access.
What should we do ?
Remember that Sharepoint has spcontnt.aspx - an interface to edit web farm content,
http://[YOURSITES/_layouts/1033/spcontnt.aspx?&url=[FULLYENCODED_WEBFARMPAGE]
Change [YOURSITES] to url of your site, and [FULLYENCODED_WEBFARMPAGE] to url to your web farm.aspx page.
Then, close the offending web part.
Subscribe to:
Post Comments (Atom)
-
The problem was that the remote connection needed to utilize Named Pipes, but in order to utilize Named Pipes both the machine hosting the i...
-
How to clear SharePoint People Picker suggestion cache If you have been SharePoint Site owner long enough, you would have definitely ...
-
Getting the following error (Figure 1): Server Error in '/' Application. ID4014: A SecurityTokenHandler is not registered to ...
2 comments:
Here is a shotcut
http://[Your_Site]/[Your_Page]?contents=1
This can help you enter spcontnt.aspx directly.
Post a Comment