Thursday, December 29, 2005

The Perils of JavaSchools - Joel on Software

Once more, I feel good that I didn't waste more time in college. Joel roasts the dumbing down of Computer Science via Java (Ones? Zeroes? I only had undecided quanta!)

Thursday, December 22, 2005

Error 28704. Unable to connect to the Analysis server when upgrading to Team Foundation Server Beta 3 Refresh on SQL Server Standard Edition.

Error 28704. Unable to connect to the Analysis server when upgrading to Team Foundation Server Beta 3 Refresh on SQL Server Standard Edition. If you are upgrading a Team Foundation Server to Beta 3 Refresh on a Data Tier that has SQL Server Standard Edition then you will get this error:

Errors in the metadata manager. An error occurred when loading the Code Churn perspective, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Team System.1.cub\Code Churn.1.persp.xml'.
due to the fact that nothing cleans up the old Analysis Server's TFSWarehouse database. You can't do it inside any of the GUI managers because the Analysis Services service will not start up correctly (nice one!).

BUT THERE IS A WORK-AROUND.

When this error appears on-screen do this:
  1. Control Panel/Administrative Tools/Services.
  2. Stop the SQL Server Analysis Services service.
  3. Navigate in Explorer to the database directory where the Analysis Services databases are stored (usually C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data).
  4. Delete the file TFSWarehouse.0.db.xml and the directory TFSWarehouse.0.db
  5. Start the SQL Server Analysis Services service.
  6. See if you can now connect to the Analysis Services in SQL Server Management Studio (Object Explorer/Connect/Analysis Services/your server name). Typically there will be no Databases listed at this point.
  7. Click the Retry button on the setup screen.
This essentially eliminates the database that Team Foundation Server is going to setup anyway... so it should work fine.

Saturday, December 03, 2005

Google Sitemaps for ASP.NET 2.0

This is really cool! Google has long let you expose your site's "logical sitemap" structure so the crawler can better understand the site, details here. With ASP.Net 2.0, you can create an XML sitemap file that acts as a DataSource for the various Menu and MenuPath controls. Betrand Le Roy has done the cool work of mapping the ASP.Net sitemap file to an HTTP handler that will expose it in a format for Google to consume. Details here.