Use The Developer Debug in IE for Javascript January 7, 2012
Step through selecting item, finding the javascript and setting a break
FAST Debugging July 22, 2011
http://www.neilrichards.net/blog/?p=100
The FAST Query Game
Debugging queries in a production or UAT environment is a serious pain. This technique was taught to me by a FAST Ninja (thanks Torstein!) and is a bit bizarre. It involves running a query from SharePoint and then extracting the data passed to FAST out of a log file and manually resubmitting the query on the FAST server, all within 15 seconds.
This approach is necessary because along with your query, SharePoint sends FAST a user authorization token that is only valid for a short period of time.
Preparation:
- You must be logged into the FAST server
- Open Windows Explorer and navigate to <FASTInstallLocation>/var/logs/querylogs/. Find the most recently modified file.
- Open a copy of NotePad (or your favourite text editor)
- On the FAST server, open a web browser and navigate to the QR Server.
- Search for the term “test”
- Anywhere
- Open a web browser and navigate to the SharePoint search UI.
- At this stage you will have 1x Notepad, 1x Windows Explorer, 2x Web browsers
The rules:
- You must execute your queries from the SharePoint server, via the UI
- You have 15 seconds to complete the following process… or you die… probably.
So the approach per the linked article is to go to the log file and copy the queryvariable string and resubmit using the QServer FAST test page.
Following a successful round of the FAST Debugging game, you can investigate the results. I can’t possibly describe each element, but at a high-level:
- QUERYTRANSFORMS à Describes what was submitted through SharePoint. Refiner selections, user contexts, sorting selections will all appear here.
- NAVIGATION à Indicate what refinement data is being sent back to the server. Useful when the number of displayed refiners seems incorrect.
- RESULTSET à Includes all the search hits from the current “page”, including the value of every managed property (i.e. attributes of a document that FAST gives special treatment). While it doesn’t give you a way to interrogate every crawled property you also get to look at the rank of a document
- PAGENAVIGATION à If you work in Collaboration you’re smart enough to figure this out.
http://www.neilrichards.net/blog/?p=153
FFDumper
https://blogs.pointbridge.com/Blogs/tseng_william/Pages/Post.aspx?_ID=15
FFDumper and Log4Net and pipelineextensibility.
Go to \FASTSEARCH\data\ffd. Here you will find folders for each document processor you have running. Go into a folder and you will see multitudes of .ffd files, which can be opened in NotePad. I wrote a simple, probably slightly inefficient script to loop through the files and find the property name that I am looking for:
1: $items = Get-ChildItem -Path FULL PATH OF FFD FOLDER" 2: 3: # enumerate the items array 4: 5: foreach ($item in $items) 6: { 7: if (Get-Content $item | Select-String "
ows_ratevalue") 8: { 9: Write-Host "LOOK HERE!" $item 10: } 11: else 12: { 13: Write-Host "FALSE" $item 14: } 15: }
This finally gave me the correct camel case for my crawled property (ows_RateValue) after digging through the .ffd file that I pinpointed with my script; which I placed in my pipelineextensiblity.xml file.
1: <CrawledProperty propertySet="00130329-0000-0130-c000-000000131346" varType="31" propertyName="ows_RateValue" />
Internet Explorer 9 Developer Tool
http://www.sitepoint.com/debug-faster-with-f12-developer-tools-in-internet-explorer-9/
Once the Select element by click option is chosen, any item on the web page that you hover over will get a blue border (as seen on the SitePoint logo above). This allows you to specifically choose which area of the page you want to examine.
The DOM pane allows you to edit the HTML on the fly and see the changes in the window immediately. To do this, just click the Edit icon and edit the HTML as you would in a regular text editor. When you’re finished editing, depress the Edit button and the changes will be visible in the viewport.
Script Debugging and Using the Console
As is expected with any good developer tools, IE9 provides powerful client-side script debugging capabilities that help developers solve issues that might come up when dealing with complex code. To begin debugging scripts on your page, open the F12 Developer Tools and choose the Script tab.
From here, a number of options are available. A drop-down list allows you to select a particular script to work with
When the Console option is selected, you can execute statements on the fly by typing them into the console’s command line. The Console feature is new in IE9’s F12 Developer Tools, and provides a number of invaluable features to developers.
Visual Studio Enhanced Debugging December 16, 2010
http://msdn.microsoft.com/en-us/library/ee231550.aspx#Features
Debugging Feature Event Receivers
By default, when you run a Visual Studio SharePoint application, its features are automatically activated for you on the SharePoint server. However, this causes problems when you debug feature event receivers, because when a feature is activated by Visual Studio, it runs in a different process than the debugger. This means that some debugging functionality, such as breakpoints, will not work correctly.
To disable the automatic activation of the feature in SharePoint and allow proper debugging of Feature Event Receivers, set the value of the project’s Active Deployment Configuration property to No Activation before debugging. Then, after your Visual Studio SharePoint application is running, manually activate the feature in SharePoint. To do this, click Site Settings on the Site Actions menu in SharePoint, click the Manage Site Features link, and then click the Activate button next to the feature and resume debugging as normal.
Due to the sometimes complex interactions between the Visual Studio process (devenv.exe), the Visual Studio SharePoint host process (vssphost4.exe), SharePoint, and the WCF layer, diagnosing errors that occur while building, deploying, and so forth can be a challenge. To help you resolve such errors, you can enable enhanced debugging information. To do this, go to the following registry key in the Windows registry:
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\SharePointTools]
Change the “EnableDiagnostics” key value from “0″ to “1.”
Setting this key value to 1 causes stack trace information to appear in the Output window whenever project system errors occur while you are running in Visual Studio. To disable enhanced debugging information, set EnableDiagnostics back to 0.
User Profile Service Application Provisioning Sequence December 3, 2010
This is part two, which talks about the Details of setting up the User profile Service application along with details of events which happen under the hood on SharePoint & SQL servers.
Let’s get into the details of Setting up the User Profile Service Application
Start the “User Profile Service”
1) When we start the “User Profile Service” from the Central Administration UI, we first start with provisioning the User Profile Service instance.
Javascript Debugging April 28, 2010
Open Developer Tools -> Click Script Tab -> Set Breakpoints and Refresh the associated web page
Kerberos DelegConfig Tool For Debugging Problems April 5, 2010
http://blogs.iis.net/bretb/archive/2008/03/27/How-to-Use-DelegConfig.aspx
The Tool to Make Sense of it All
Brian Booth, a Support Escalation Engineer for IIS at Microsoft, created an ASP.NET Application that will run some key checks on the client, server, and back end server to identify problem areas for kerberos delegation. The following link will allow you to download the ASP.NET application that helps identify which common symptoms and Root causes you may be running into when attempting to configure an IIS Server to delegate credentials from the client to a back end server.
http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1434
