FSIS – Crawling and Troubleshooting in Real Time

When you’re configuring crawling for FSIS it can take some time if you’re a newbie.

The crawler config is not for the faint of heart.

The simplest way I’ve found to monitor the crawling whilst initially configuring it is to just open up a fiddler (www.fiddler2.com) session from the box that is doing the crawling.

Yes it will slow down crawling slightly – and yes you will need to keep an eye on memory usage if you’re crawling many pages per second.

However, it will be a valuable tool in your arsenal to monitor the crawling quickly and drill into any authentication issues and notice 404 errors coming through.

How To: Find All ContentByQuery Web Parts for a Farm?

Question: How to find all ContentByQuery web parts for a Farm?

Answer:

  1. Run this command: stsadm -o enumallwebs -includewebparts > D:\Data\enumwebs.txt
  2. Open up the enumwebs.txt file just created, and then search for “ContentByQueryWebPart” and take note of the URLs
  3. Open up IE, then navigate to each URL and add on ?Contents=1 to determine the title of the web part
  4. (Optional) Export the web part if you want to take a closer look

Fixing A Broken Page – Tip #1

If you add a web part to a page and it wasn’t written correctly you may experience an issue where the whole page doesn’t load.

When this happens, the simplest way to solve the issue is to perform the following steps:

  1. Add the string ?contents=1 to the URL of the broken page – e.g. http://intranet/pages/default.aspx?contents=1
  2. This will take you to the Web Part Maintenance page.  Once the page has loaded, look for the web part that you think is causing the error.  In most cases, it will actually display Error in the web part name.
  3. Check the box next to the web part and click the Delete button
  4. Navigate back to the page

Fixing A Broken SharePoint Site

If you’re ever working with a site that just won’t load and you don’t know it’s structure, you can (if it isn’t severely busted) still attempt to access other pages by manually navigating to the “View All Site Content” page, by adding  _layouts/viewlsts.aspx to the end of the site URL.

E.g. http://intranet/_layouts/viewlsts.aspx

If you still have troubles with the site, then you can attempt to navigate to the site settings page and modify the settings that might be causing the issue by adding _layouts/viewlsts.aspx to the end of the site URL:

E.g. http://intranet/_layouts/settings.aspx

FAST Search for SharePoint 2010 – Get All Results Back

On FAST ESP, there used to be a technique to get back all documents in your index – enter the minus character, followed by a term that wouldn’t be in your index.

For example: -394kidfdkadkfl2k2

This would bring back all documents.

In FAST Search for SharePoint 2010, this does not work.

The trick instead, is to simply enter the hash character ( # ) by itself / without the parenthesis in the search query textbox.

How To Remove InfoPath Branding

Have you ever wanted to remove the annoying “Powered by InfoPath” logo that users see when accessing InfoPath forms in the browser?

The good news is that this is pretty straightforward.  Just follow these simple steps:

  1. Log on to one of the servers in the SharePoint farm (e.g. an App Server)
  2. Run the following command:  stsadm -o setformsserviceproperty -pn AllowBranding -pv false

Enjoy!

How To Delete the SSP on SP2007

On SharePoint 2007 every now and then you may have a need to delete the SSP so that you can then recreate it.

The trouble is that deleting it through the UI isn’t very reliable.  However, it is reasonably straightforward to do so using stsadm, using the following command line syntax:  stsadm -o deletessp -title “[SSP Title]” -force -deletedatabases

For example: stsadm -o deletessp -title “SSP01″ -force -deletedatabases

SharePoint Installation with SQL Alias

As a best practice, SharePoint should be installed using a SQL alias.

Think of a SQL alias like a DNS record, but also being able to refer to a specific SQL instance name.

If you need to upgrade database servers in the future, you will usually be keeping the existing DB server in place, and creating a separate DB server environment (e.g. SQL 2005 vs SQL 2008). If you had your SharePoint installation configured with the server name details of the SQL 2005 environment, then now you have to undertake a long and arduous process to move to 2008.

If you configured the environment with a SQL alias – then you can just go and update the alias on each of the SharePoint servers to point at the new SQL 2008 environment. Much simpler!!

Note: When installing SharePoint with a SQL alias, you need to make sure that you set up the alias on EACH and EVERY SharePoint server.  Miss one and the box won’t be able to connect to the required database server(s).

The command to bring up the SQL Alias Client Config Utility is: cliconfg