Configuration Database

1. Go to the “Operations” tab
2. Click “Servers in Farm”
3. Under “Farm Information” see the following items:
   1. Configuration database server
   2. Configuration database name

Central Administration Content Database

1. Go to the “Application Management” tab
2. Click “Web application list”
3. Click “SharePoint Central Administration v3″
4. Under “SharePoint Site Management”, click “Site collection list”
5. Under the root “/” site, look in the information table for the “Database Name” value

General Usage Content Databases

1. Go to the “Application Management” tab
2. Click “Web application list”
3. For each web application listed other than “SharePoint Central Administration v3″ (see above), perform the following:
   1. Click the web application name
   2. Under “SharePoint Site Management”, click “Site collection list”
   3. For each listed site collection (by URL):
      1. Click the URL of the site collection
      2. In the information table, look for the “Database Name” value

Search Database

1. Go to the “Operations” tab
2. Under “Topology and Services”, click “Services on server”
3. Click the text “Windows SharePoint Services Help Search”
4. Under “Search Database”, look for the values:
   • Database Server
   • Database Name

I was disappointed to see VirtualPC is no longer supported for Home versions of Windows. I was also disappointed to see the free VMware Server equivalent of VirtualPC had disappeared.

However, I just discovered the free VMware Player now not only runs VMs, as it always has, but also allows you to create them! You can also create and run 64-bit guest VM’s if you have the appropriate hardware, which I do. VirtualPC can’t do that. Sweet!

Update: A co-worker (thanks Shane!) mentioned to me the free VMware Server is still available. I’m going to try out Player, hoping it is more light-weight, and see how it goes first.

“A Time for Choosing” by Ronald Reagan

“Translation: If your company is deemed “critical,” a new set of regulations kick in involving who you can hire, what information you must disclose, and when the government would exercise control over your computers or network.”

Yikes.

It appears most modern browsers are susceptible to a simple man-in-the-middle attack on SSL certificates, meaning your encrypted browsing sessions can be intercepted.

The article lists Firefox 3.5 as the only modern browser not affected by the attack.

I’m running into a problem with the Delicious Toolbar 1.12.273.0 causing IE8 to hang on Windows XP SP3. It is super annoying, as I would like to use the Favorite Tags functionality on this machine.

worksforme – On Vista

I have the Delicious Toolbar running with IE8 on Vista with no problems. However for some reason the other computer I use running WinXP is choking on the Delicious addon.

Issue

After I install the Delicious Toolbar, I can open IE8 for one session. After closing the browser, the IE window disappears like everything is normal. When I try to open IE again, the chrome starts to load, but the window hangs. My home page doesn’t open, and the IE functions are frozen.

Behind the scenes, there are two iexplorer.exe processes, and one DeliciousManager.exe process still running. IE8 becomes responsive again once I kill the DeliciousManager.exe process in the Task Manager. Once I kill the DeliciousManager.exe process, the iexplorer.exe processes are freed up and end normally. Then I can start a new web browser session, until I run into the issue again when I close IE.

Attempt 1 – Disable potential conflicts

I tried disabling all other IE addons, setting exclusions in antivirus for real-time scans on the Delicious Toolbar data directories, and disabling the firewall. The DeliciousManager.exe task would still hang IE8.

Any Ideas?

Does anyone out there have any other ideas? If I find a solution, I will post a follow-up here.

We ran into an issue on one of our SPS 2003 installations where the team site information was not searchable at the team site level. We could successfully search all content at the portal/area level, but no results would come back when we performed the same search inside of a team site.

After some troubleshooting with our DBA and Microsoft Support (mostly our DBA), we realized that a required column by SharePoint for indexing the team site content was missing. The column name was Extension.

The resolution for this problem ended up being fairly simple once we figured it out:

1. Open SharePoint Central Administration on the front-end server
2. In the left-hand navigation, click “Windows SharePoint Services”
3. Under “Component Configuration”, click “Configure full-text search”
4. Uncheck “Enable full-text search and index component”
5. Click OK
6. Under “Component Configuration”, click “Configure full-text search”
7. Now re-check “Enable full-text search and index component”
8. Click OK
9. At this point the required column “Extension” should be recreated in the SQL database
10. Force a re-index or wait for the next schedule
11. Test

This fixed the issue for us, and we were able to bring back search results at both the portal and team site level again.