Personal website of Dave Hope » SQL Server

Deleting the TFS workspace for a missing account fails (TF50605)

Dave — Thu, 13 May 2010 14:24:40 +0000

Having decommissioned a few legacy AD DS domains over the last year or so we’ve had a few references in TFS to missing accounts. When attempting to delete the workspace you get the following error:

TF50605: There was an error looking up the SID for OLD-DOMAIN\CCNETNIGHTLYBUILD.

In order to delete the workspace, we need to remap it to a valid user account. Here’s the process to do just that.

Firstly, we should list the workspaces on this computer we’re having problems with (in this case, BUILDSERVER01).

C:\>tf workspaces /owner:* /server:http://tfs-server:8080 | findstr BUILDSERVER01
Workspace		Owner				Computer	Comment
----------------------- ------------------------------- --------------- -------------------------------
BUILDSERVER01		saCCNetNightly			BUILDSERVER01	Temporary CruiseControl.NET Wo
BUILDSERVER01		OLD-DOMAIN\CCNETNIGHTLYBUILD	BUILDSERVER01 	Temporary CruiseControl.NET Wo
BUILDSERVER01		saCCNetNightly			BUILDSERVER01

We may as well attempt to delete the workspace, though the process is likely to fail as it wont be able to resolve the SID if the domain is no longer available.

C:\>tf workspace /delete /server:http://tfs-server:8080 BUILDSERVER01;OLD-DOMAIN\CCNETNIGHTLYBUILD
TF50605: There was an error looking up the SID for OLD-DOMAI\CCNETNIGHTLYBUILD.

At this point, we need to open up the TfsVersionControl table and manually point the workspaces to a valid identity. The first stage is to identify the ID of the missing account:

SELECT IdentityId FROM tfsVersionControl.tbl_Identity WHERE (DisplayName LIKE 'OLD-DOMAIN\CCNETNIGHTLYBUILD')

Now that we have the ID, we can locate the workspaces the owner has on the server we’re having problems with.

SELECT WorkspaceId, OwnerId, WorkspaceName FROM tfsVersionControl.tbl_Workspace WHERE (OwnerId = 311) AND (Computer = 'BUILDSERVER01')

We should now update the tfsVersionControl.tbl_Workspace table with a valid IdentityId from the tfsVersionControl.tbl_Identity table. Once that’s done, try the delete command again:

C:\>tf workspace /delete /server:http://tfs-server:8080 "BUILDSERVER01;Dave Hope"
A deleted workspace cannot be recovered.
Workspace 'BUILDSERVER01;Dave Hope' on server 'http://tfs-server:8080' has 0 pending change(s).
Are you sure you want to delete the workspace? (Yes/No) Yes

And hey presto, the workspace is gone.

Security update for SQL Server KB970892 fails to install

Dave — Tue, 20 Oct 2009 08:26:49 +0000

Over the last few days KB970892 has consitently failed to install on our SQL Servers via Windows Update. The following instructions will get it working.

Once the update fails to install, you’ll likely have to reboot as the system will be flagged as pending a reboot. Once rebooted we need to attempt to complete the SQL Server installation:

Open up Add or Remove Programs, select Microsoft SQL Server 2005 and click Change
On the Component Selection screen, choose Database Engine under SQL Server 2005 Instances and click Next
On the Feature Maintenance screen, choose Database Engine and click Next
Go through the setup wizard until the Change or Remove Instance screen. Then click Complete the suspended installation.
Follow through the wizard, if you get a prompt for the files point it at your SQL SP3 installation media and continue.

If you’re using SQL Server 2005 Express you can extract SQLEXPR32.EXE with the /x switch.

The installation will likely fail with the following error:

SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is too short.. To continue, correct the problem, and then run SQL Server Setup again.

Edit C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\sqlagent90_msdb_upgrade.sql with notepad or similar.

Change password on line 30683 to something more complex, from:
encryption by password = 'Yukon90_'
To (for example):
encryption by password = 'Yukon90_23423ASDzz}{'

Then further down, change line 30977 to reflect the same value:

From
set @exec_str = N'add signature to ' + @sp + N' by certificate [##MS_AgentSigningCertificate##] with password = ''Yukon90_'''

To
set @exec_str = N'add signature to ' + @sp + N' by certificate [##MS_AgentSigningCertificate##] with password = ''Yukon90_23423ASDzz}{'''

Cancel out of setup. Back in Add or Remove Programs choose Change again for Microsoft SQL Server 2005 continuing through the wizard as before. This time, you wont get the error and the upgrade will complete.

SQL Server 2008 RTM

Dave — Thu, 07 Aug 2008 06:42:04 +0000

As Neil points out in his blog, SQL 2008 RTM’d and is available on Technet / MSDN. Typical, I only setup 2005 Enterprise for SCCM in my lab environment yesterday.

Time to take this for a spin. Keep an eye on Neil’s blog, he has more SQL2008 goodness planned.

Deploying SQL Server with Microsoft Deployment

Dave — Sun, 16 Dec 2007 13:07:50 +0000

This guide focuses on VS2005 Express Edition with advanced services, though this applies to any version of SQL2005.

The first thing you’ll need to do is copy the install files to your distribution share via the Deployment Workbench. Be sure to choose a directory structure without spaces as this seems to cause problems during setup.

Once you’ve got your Application folder setup, create a file called ‘template.ini’ in the same directory and add the following contents:
[Options] ADDLOCAL=All INSTANCENAME=MSSQLSERVER SQLBROWSERACCOUNT="NT AUTHORITY\NETWORK SERVICE" SQLACCOUNT="NT AUTHORITY\NETWORK SERVICE" AGTACCOUNT="NT AUTHORITY\NETWORK SERVICE" ASACCOUNT="NT AUTHORITY\NETWORK SERVICE" RSACCOUNT="NT AUTHORITY\NETWORK SERVICE" SQLBROWSERAUTOSTART=1 SQLAUTOSTART=1 AGTAUTOSTART=0 ASAUTOSTART=0 RSAUTOSTART=0 SECURITYMODE=SQL SAPWD=9C1_GM3Z@U*+ DISABLENETWORKPROTOCOLS=0 ERRORREPORTING=0 SQMREPORTING=0

That will install all components, and set the local SA password to ’9C1_GM3Z@U*+’. This needs to be a complex password, or setup will fail.

Once that’s in place, save the file and use the following quiet install command:

setup.exe /qn /settings \\london.nwtraders.msft\Distribution$\Applications\Microsoft_SQL2005_Express\template.ini

If you haven’t already got them added, you’ll need to add in dependencies for the .Net Framework 2.0 and Windows Installer 3.1

For .Net 2.0 extract dotnetfx.exe, add to your applications distribution folder via the Deployment Workbench and use the following quiet install command install.exe /q

For Windows Installer 3.1 (if required) download, add to your applications distribution folder in the normal mannger and use WindowsInstaller-KB893803-v2-x86.exe /quiet as the quiet install command.

You should only need Windows Installer 3.1 if you plan on deploying it to Windows XP, so add a platform restriction (not sure what the official naming is) but choose ‘This can run only on the specified client platforms’ but on the ‘Details’ tab.

Moving a WSUS 3.0 Database

Dave — Thu, 14 Jun 2007 08:41:44 +0000

Due to seemingly non-existant documentation on moving a WSUS 3.0 database to a new server, I figured i’d write up my experience.

Database configuration is all stored in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UpdateServices\Server\Setup
The keys you’re interested in are SqlServerName and SqlInstanceIsRemote. Microsoft only officially support Windows authentication, so that’s what i’ll cover here.

You’ll be able to connect the the Windows Internal Database using Microsoft SQL Server management studio Express (a free download), detach the database and re-attach on your new SQL server.

Once that’s done, add the computer account of the WSUS server as a database login (e.g. nwtraders\LONDON$) and give it the dbowner role on the SUSDB.

The last step is to set the SqlServerName and SqlIsRemote values as mentioned earlier. Once done, restart IIS and the UpdateServices service. Job done.

Compacting all MSSQL databases

Dave — Fri, 06 Apr 2007 12:07:40 +0000

Now that my hangover has just about worn off from a rough night out, I thought i’d post something useful. Below is a quick and (very) dirty way of clearing down the log and shrinking MSSQL datbases. Something useful for people who want to keep their Windows systems/networks tidy.
-- DECLARE STUFF. DECLARE @rowCount int DECLARE @rowCurrent int DECLARE @rowData table (dbID int IDENTITY (1, 1), dbName varchar(50)) DECLARE @dbName varchar(50) SET @rowCurrent = 0 -- Populate @rowData with list of databases on server. INSERT INTO @rowData(dbName) SELECT name FROM sysdatabases -- Number of rows in @rowData. SELECT @rowCount = COUNT(*) FROM @rowData -- Itherate through rows. WHILE @rowCurrent < @rowCount BEGIN SELECT @dbName = dbName FROM @rowData WHERE dbID = @rowCurrent PRINT @dbName BACKUP LOG @dbName WITH NO_LOG DBCC SHRINKDATABASE (@dbName) SET @rowCurrent = @rowCurrent + 1 END
If anyone has some suggestions, feel free to let me know.

The Technology Specialist MCTS certifications help IT professionals to obtain the knowledge of specific technologies. MCTS is the 2nd most important Microsoft’s certification. The candidates are required to pass the mcts 70-529 Microsoft .NET Framework 2.0, mcts 70-620 Windows Vista, Configuring, mcts 70-630 Microsoft Office SharePoint Server 2007,mcts 70-640 Windows Server 2008 AD and Microsoft mcts 70-642 exam.