Confluence SharePoint Connector 1.3 : Tracing the SharePoint Feature
This page last changed on Mar 29, 2010 by smaddox.
To troubleshoot or debug the SharePoint feature you can enable tracing and then view the trace with a tool such as DebugView. Enabling TracingTo enable tracing, you will need to add a node to the web.config file for your SharePoint web application:
Problems with Flushing Trace OutputIn some cases, the trace output does not flush properly. If you think this is the case for you, you can try tracing to a particular file and making sure the trace is flushed regularly. Here is an example of how to do this. Note that with this approach the trace file will continue to get larger over time. You can uncomment the <remove name="Default" /> by simply removing the leading <!-- and traling --> portions if you want traces to only go to the file and not make them available to DebugView. web.config snippet with autoflush Tracing the Confluence Search Administration PagesNote that if you want to trace the custom Confluence search administration pages, you need to enable tracing for the web.config used for your SSP web application. This is typically not the '80' directory as used in the example above nor is it the same directory/web application for SharePoint Central Administration.
Viewing the TraceThe easiest way to view the trace is to download DebugView onto your SharePoint web server. When using this tool, make sure you go to the 'Capture' menu and choose 'Capture Win32'. After you have updated your web.config, performed an IISRESET and started DebugView, you can navigate to pages within SharePoint and you should see trace messages related to the SharePoint Connector for Confluence. |
![]() |
Document generated by Confluence on Feb 20, 2011 21:50 |