Debugging and Trouble Shooting in WSS3.0 and MOSS

-
The followings are a few things that you can use to debug and trouble shoot your custom code in MOSS development environment.


  • Out-Of-The-Box (OOTB) SharePoint logs: The log can be located @ C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS. The detail level of the information can be setup in the Central Administrator. There are a lot of information in those log files. Fortunately, there are tools out there to help you parse and filter the logs (i.e. SpsDev.com ULS Log Reader).
  • Sometimes you'll get unexpected error has occurred on a web page and there is no other information to help you debugging this issue. There is a great post that shows you how you can get rid of the useless unexpected error page and get the standard ASP.net error page for debugging.

Change the following line in the web.config

<SafeMode MaxControls=“200“ CallStack=“false“…

to

<SafeMode MaxControls=“200“ CallStack=“true“…

and you'll also need to set custom errors to 'Off'

<customErrors mode=“Off“>

  • One more thing that you can do for custom code is to step through the code. For me, I have a hard time figure which w3p.exe to attach. I usually attach all of w3p.exe that I can find and that usually helps. However, I still haven't find a way to step through my feature receiver code. If I ever find a way, I'll updated this post.

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 App Details Page Error

-
Image
Out of no where, the app details page started throwing out error for all apps. ULS log entries System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'prc_CountAppInstanceData', database 'UsageAndHealth_Logging_DB', schema 'dbo'.     at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)     at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)     at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()     at System.Data.SqlClient.SqlDataReader.get_MetaData()     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBe
Read more

SharePoint 2013 - Working with Display Template for Content Search Web Part

-
Image
To create a custom display template, the best approach is to copy an existing one from Out-Of-Box display templates.  You can try each one and find the one that is closest to what you want to do. All the display templates are in the master page gallery.  To access it, Site Settings -> Master pages and page layouts -> Display Templates The Content Web Parts folder contains the display templates for content search web part and Search folder contains the display templates for the search results web parts. The easiest way to take a look at the display templates is to open the list in windows explorer.  On the ribbon, click on Open with Explorer option. You'll see a lot of html and js files in Content Web Parts folder.  The HTML files are the ones that you'll need to take a look.  The .js files are auto-generated when you add a new HTML file or update an existing one. For every content search web part, you usually have to specify two display template, Control a
Read more

SharePoint 2013 Features Information List

-
I find this information is so useful.  I used to get my information from, http://blogs.msdn.com/b/razi/archive/2013/10/28/listing-all-sharepoint-2013-features-including-name-title-scope-id-and-description.aspx. But in case the site is down later, I retrieve them using server code (SPFeatureDefinition) on SharePoint 2013 environment.  You can get the feature ID and description below. There is some more information is you're interested. SharePoint Server 2013 Features Display Name (Title) Scope ID Description PublishingStapling(Publishing Features Stapling) Farm 001f4bd7-746d-403b-aa09-a6cc43de7942 Staple Publishing features SiteStatusBar(Site status bar) Farm 001f4bd7-746d-403b-aa09-a6cc43de7999 Creates a Microsoft OneNote 2010 notebook in the Shared Documents library and places a link to it on the Quick Launch. This feature requires a properly configured WOPI application server to create OneNote 2010 notebooks. BasicWebParts(Basic Web Parts) Site 00bfea71-1c
Read more