In an isolated dev environment set up to enable Kerberos in SharePoint 2007 and SQL Server 2005, a single VM Server for the DC, one for the SQL Server and one for the SharePoint Web Front End, developers were unable to create custom databases in the SQL Server instance and use SQL Server local logins to connect to those databases with ODBC.
Tests with generic UDL shortcuts (ODBC) failed with the error “Login failed for user “<username>”. The user is not associated with a trusted SQL Server connection.” upon clicking “Test Connection” button.
Carried out the following tests:
Made sure we had the right password for the testing account. If needed, can change passwords this way.
Made sure that SQL @@servername was correct (select @@servername executed as a query helps with this. Google can help provide more details).
Checked SQL Logs for more information (found Error 18452 after each connection failure)
The term “trusted connection” suggested that the issue might be with Kerberos even though we were using local accounts, so I also checked for the “Integrated Security” connection string value per discussion here.
Finally went through the UDL shortcut configuration again, and found an interesting phenomenon. If you click the “Test Connection” button you get the generic trusted connection error. But, if you click the drop-down list for selecting the database you want to connect to, you get a very applicable error message.
The fix for this problem is to go back into the SQL Server Management Studio, edit the properties for the local user and first enable “Enforce Password Policy” for the user, THEN uncheck all of the options including “Enforce password expiration” AND “User must change password at next login”.
The picture is not entirely complete here, but I made a lot of progress with this as an open (now closed) troubleshooting ticket with Microsoft.
The short summary is that using a Microsoft whitepaper (linked to below), I could get Windows XP SP2 workstations to work properly opening an Explorer View to a SharePoint 2007 farm’s document library, I had a bunch of other problems to surmount when trying to get a Windows Server 2003 SP2 system to do the same. The rest of this post is about other methods for troubleshooting and fixing the situation.
Recently we had cause to do a whole lot of research ourselves and end up calling Microsoft to get our implementation vetted and troubleshot (it was not working – all or almost all connections that should have been Kerberos connections were degrading back to NTLM).
Here are the salient notes and facts about troubleshooting and achieving the ultimate goal (having Kerberos working with our systems).
I don’t like to do exactly the same blog entry that someone else did, but the other blog entry was from 2007 and I just encountered the problem myself. Thank g-d for Google.
Anyhow, if you have a web application with no site at the root managed path, adding a best bet to a site collection on some other managed path will pop up a window that says,
The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.
The way to fix it is to create a site collection at the root managed path. Or probably upgrade to SP1.
Yes, I know the error is completely unhelpful. I found it so as well.
Creating a Search Center as a subsite Search Center for a Team Site site collection didn’t seem to create or properly hook up a People Search Results page within that Search Center for the People Search Scope. Doing a People search after having ONLY created a Search Center and set the Site Collection to use it for “richer results” comes up with an HTTP 404 error on the People Search results page.
Here’s how to create that full functional pipeline WITHOUT SharePoint Designer (to create the people search results page where SharePoint’s expecting it to be), thank you very much.
This may help you with defining additional site scopes and dedicated landing pages for their results too, assuming you also have a Search Center deployed.
WARNING: If you do this, you will end up renaming the Home tab in your horizontal nav bar to whatever your top level site’s name is, and the only way to get it back (short of SharePoint Designer) will be to disable the Office SharePoint Server Publishing Infrastructure feature at the Site Collection level. This may be okay with you and your users or not, depending on how much tweaking you intend to do through that feature/interface.
(Optional) Create Site Collection with Team Site top level site. Do this if you just want to proof it out. Otherwise, if you already have a site collection you want to do this with, start at steps 2 or 3 below, depending on what you’re starting with.
Do this operation in the Application Management tab of Central Administration.
Under the SharePoint Site Management section, click the “Create site collection” link and follow the prompts from there.
(Optional) Create Search Center Subsite (w/o Tabs). This assumes you haven’t already got a Search Center subsite or site collection to work with.
Do this operation within the top level site you just created. This may work in other contexts too, but I have not tested those.
Choose the “Search Center” option under the Enterprise tab when choosing a site definition.
I chose not to list the subsite in the Quick Launch, but I did choose to list it in horizontal navigation and to use the parent site’s horizontal navigation. If you choose different settings, know these may affect your site collection’s behavior.
Assign Search Center as Search Center target for top level site.
Do this operation within the top level site you just created.
Go to Site Actions -> Site Settings, then click Search settings under the Site Collection Administration section all the way to the right.
Provide the path starting with the end of the FQDN to the search center’s simple URL (e.g. if the top level site iat http://example.com/sites/tls/sc, then input /sites/tls/sc into the textbox.
Click OK button.
NOTE: If you’re starting with the same assumptions I am and you test the People search scope now, you should receive a 404 error, regardless of whether your crawls are working. This indicates the lack of a proper results web part page for the results to go into.
Enable Office SharePoint Server Publishing Infrastructure Feature and Office SharePoint Search Web Parts Feature (not entirely sure this is required) on Site Collection.Â (Enabling the first feature here will change your Home Tab in horizontal navigation to the Top Level site name.)
From top level site, choose Site Actions -> Site Settings.
In Site Collection Administration section, click the “Site collection features” link.
Click “Activate” button to right of Office SharePoint Server Publishing Infrastructure Feature item.
Click “Activate” button to right of Office SharePoint Server Search Web Parts Feature item.
(Optional) If you don’t want the potentially confusing changes to the Site Actions menu to impact the top level site, immediately disable the Office SharePoint Server Publishing Feature on the top level site.
In the top level site, go to Site Actions->Site Settings->Modify All Site Settings.
Under the Site Administration (NOT the Site Collection Administration) section, click the “Site Features” link.
Click the “Deactivate” button to the right of the Office SharePoint Server Publishing Feature item.
(Optional) Enable Office SharePoint Server Publishing Feature on Search Center Site. You may not have to do this, as it may be auto-enabled when the Site Collection Features are enabled. An easy way to tell whether this feature is activated on a site or subsite is by looking at the Site Actions menu. If it’s just 2 or 3 items (depending on the page you access it from): Create, sometimes Edit Page, and Site Settings, then you know this feature is not enabled. If instead it’s a huge menu with multiple fly-out submenus, then you know the feature is already enabled on that site.
Go to Search Center site.
Click Site Actions -> Site Settings and in Site Administration section, click Site features link.
Click “Activate” button to right of Office SharePoint Server Publishing Feature.
Create new page in Search Center for People Search Results.
Click Site Actions -> Create Page
Create a page called peoplesearchresults.aspx. Save it where the dialogue lets you save it. Probably Pages/*.aspx.
Choose the “(Welcome Page) Blank Web Part Page” Page Layout.
Click “Create” button.
Add appropriate People Search result web parts to new page.
On created page, if not already in page edit mode, choose Site Actions -> Edit Page
Add appropriate web parts, put them on the page in appropriate places and modify their web part settings to suit. I chose:
Header: People Search Box
Center: Search Statistics, Search Paging , Search High Confidence Results, People Search Core Results, Search Paging 
Center Right: Search Best Bets
Click Publish button to finalize edits to web part page.
Edit Search Scopes on Site Collection.
Go to your top level site.
Choose Site Actions -> Site Settings.
In the Site Collection Administration section, click “Search scopes” link.
Copy “People” Search Scope (default) to a copy for the Site Collection.
Use drop-down menu on “People” Search Scope and choose “Make Copy”
Edit the “Copy of People” Search Scope to set proper results page URL and change name (can’t just be “People” as that name’s already taken).
Use drop-down menu on Copy of People and choose “Edit Properties”.
Click “Change scope settings” link on next page.
Change Title to something descriptive that isn’t “People”.
Enable or Disable the Display groups you want for this scope.
Specify the target results page you just created. Start relative url at the search center’s root. So if, for example, the search center is at http://example.com/sites/tls/sc/ and your results page ias at http://example.com/sites/tls/sc/Pages/peoplesearchresults.aspx, use the value “/Pages/peoplesearchresults.aspx” in the Target results page textbox.
Click the “OK” button.
Remove default “People” Search Scope from Site’s selectable scopes.
Go to the Search Scopes settings page in the top level site (Site Actions -> Site Settings -> Site Collection Administration -> Search Scopes)
If you’re using default Display Groups, you should have “Search Dropdown” and “Advanced Search”
For each display group click the hyperlinked name of the group in the grey bar, labelled “Display Group” (e.g. for Search Dropdown, click the hyperlinked Search Dropdown in the phrase “Display Group: Search Dropdown (3)” (or some other number) in the grey title bar just above the list of scopes active for that display group).
In the Edit Scope Display group page, uncheck the Display checkbox to the left of the People scope name.
Click the OK button.
Repeat this for any other applicable Display Group you have in Search Scopes.
Let your crawls happen. The settings you made won’t be reflected in your sites until after the next crawl. If you have access to the SSP, you can reinitiate crawls to try to rush the process and make it happen immediately.
Retest. Hopefully you’re all hooked up now.
If everything is hooked up and you don’t want the publishing infrastructure and you want your Home tab back, you can now disable the Site Collection feature.
Go to your top level site. Go to site settings (Site Actions -> Site Settings).
Under the Site Collection Administration section, click the “Site collection features” link.
Click the “Deactivate” button to the right of the Office SharePoint Server Publishing Infrastructure Feature.
If not, don’t come crying to me!
Actually, I’ll be happy to try to help, but keep in mind that I don’t have a lot of spare time.
So before I enabled the Publishing Infrastructure feature, the top nav bar tabs showed the leftmost tab reading “Home”. After enabling it and later disabling it, the leftmost tab read as the site title (as set in the site settings). Great but all my functional tests are written to search for the tab reading “Home”. So I tried to edit that Global Navigation header in the Navigation settings in Site settings and the Edit… option is not available for that heading.
We set our upload size limit to 40,000 megabytes on our Virtual Server settings.
You access this setting in Windows SharePoint Services Central Administration -> Configure Virtual Server Settings -> [Select Virtual Server] -> Virtual server general settings -> the setting is in Maximum Upload Size. (default is 50 megabytes)
This was very bad. Apparently if the setting is set too high, it’s essentially interpreted to be zero by the application.
Once this happened, not only did we get the upload size error, “The form submission could not be processed because it exceeded the maximum length allowed by the Web administrator.” for any size file, but also, we got the Explorer View error, “Explorer View requires Internet Explorer 5.0 or greater and Web Folders.”
A better really huge setting that ended up working for us was 10,000 megabytes.
If you are playing with Approval workflows, and you find that your workflows are erroring out even when you think it should have completed successfully, make sure you aren’t in a situation where you’re updating the approval status without having the approval functionality of your document or workflow library enabled.
It’s all built-in, but it doesn’t all automatically enable itself on need.
I ultimately found my answer on SharePoint Blogs, but my discovery route was circuitous.
First, the Unknown Error statuses on my workflow status page for the workflow. These workflows would error out and require termination from the workflow status page so they’d stop contributing to my active workflow counts. Searching around, I found out (look at Eilene Hao’s response to Misha) that you can get more info about these by going to where your Diagnostic Logs are kept. Find out where those logs are kept by going to SharePoint Central Administration, Operations page/tab, then under the Logging and Reporting section, click the link to Diagnostic Logging. On the next page, you’ll find out where those logs are under Trace Log.
Go to that directory in your front end web server(s) and use a decent directory search/grep (I used Textpad I have installed in portable mode on a USB key) to find log files with the word “workflow”. Upon doing that, I found the string/error, “System.ArgumentNullException: Value cannot be null. Parameter name: name”. Googling eventually led me back to the SharePoint Blogs post above.
So the fix is that if you’re going to use an ootb (out of the box) builtin workflow that updates the approval status of an item, you should also enable the “Require content approval for submitted items?” option in Versioning Settings for the list settings. This will do a lot of things automatically for you:
When a list item is changed, the approval status for the item gets automatically changed back to “Pending”.
When a person with the permission level to approve items looks at the list, they get a special view option called “Approve/reject Items”. (So they can bypass the approval workflow)
The workflow that updates approval status stops erroring out.
It’s all pretty cool, but you have to know how it all hooks together.