No luck in installing TFS in a more or less single server installation. Different Error 32000's...

Hi, I've been trying to get VSTF Beta 2 running for last 3 days with no luck.

Always ending with different Error 32000's
example:
Error 32000.The Commandline '"C:\Program Files\Microsoft Visual Studio Enterprise Server\widbloc.exe" -s hostname -d CurrituckDB' returned non-zero value: 1.

I have a Lab domain, consisting of 2 DC's running smoothly (and have been for well over a year now). No errors whatever if I use Netdiag or DCDIAG.

Now I have a virtual server where I'm trying to install a "single server installation" while using the present lab AD.
The virtual installation consist of the following:
W2003withSP1 (Slipstreamed)
IIS6 with ASP.Net enabled
SQL2005Beta 2 Full install (tried both April and June CTP versions, April version seem to require a regedit deletion according to lots of posts in the forums I've visited)
Creating a separate Application Pool for the Reports and ReportServer websites in the IIS
Installing Windows Sharepoint Services with SP1 and installed the Windows Update patch.
I have exluded the Reports and ReportServices vdirs from Sharepoint
I have verified that the Sharepoint site is working and that the Reports and ReportingServices works as well.
I've even tried to reboot after each step!
I login as TFSSETUP which is a domain admin in the lab domain (as well as TFSSERVICE)
I start installing the VSTF, giving the domain\tfsservice account (which is also a domain admin)
Then when the Application Tier is installing I receive the error 32000's.

Any help appreciated!

Best Regards
Mike

Answer this question

No luck in installing TFS in a more or less single server installation. Different Error 32000's...

Mukool
Thanks for the post.

I still haven't been able to achieve a successful install. I am currently re-starting a new virtual machine and am in the process of installing the O/S. I will give your approach a try.

Sarah
Bj&#248;rnar Sundsb&#248;
Frank/Sarah,

What version of Yukon are you using The version of Yukon which is supported for use with TFS Beta2 is 9.00.1116. There are known TFS issues with later Yukon builds (the "The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE or DELETE statements.
" is one of them).

You can run "select @@version" on the server to get the SQL Server version.

Thanks,
Amit
albator69
Ok Here's some more

go this when executing the SQL code above

Warning! The maximum key length is 900 bytes. The index 'xxUQ_xxTree__TreePath-B90FD6E4-0B1B-4675-B0C6-3C95B1CBA6F6' has maximum length of 904 bytes. For some combination of large values, the insert/update operation will fail.

Msg 1065, Level 15, State 1, Procedure ExecBigBatch, Line 89

The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE or DELETE statements.

ExecBigBatch is encrypted so i can't go any further.

Seems to be an index error before which might also be causing a misread on the error.
ravivarma
More info
Ran a trace on SQL Server and here is some output

SP:StmtCompleted .Net SqlClient Data Provider 784 9 CurrituckDB 24214  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:55.857 86306 313532612609 0 0 2005-06-12 04:20:55.857  0 0 -- Encrypted text 0 0 6464  3 6354  1218103380            8272 - P 9
SP:StmtStarting .Net SqlClient Data Provider 784 9 CurrituckDB 24215  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:55.857 86306 313532612609       -- Encrypted text   6988  3 6466  1218103380            8272 - P 9
Exception .Net SqlClient Data Provider 784 9 CurrituckDB 24216  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:55.857 86306 313532612609    1065   Error: 1065, Severity: 15, State: 1           1      15
User Error Message .Net SqlClient Data Provider 784 9 CurrituckDB 24217  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:55.857 86306 313532612609    1065   The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE or DELETE statements.           1      15
SP:Completed .Net SqlClient Data Provider 784 9 CurrituckDB 24218  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:54.917 86306 313532612609  940 2005-06-12 04:20:55.857   167 -- Encrypted text     3   1218103380 ExecBigBatch            8272 - P 9
SP:Completed .Net SqlClient Data Provider 784 9 CurrituckDB 24219  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:53.053 86306 313532612609  2804 2005-06-12 04:20:55.857   561 -- Encrypted text     2   1314103722 AlterUsedViews            8272 - P 9
SP:Completed .Net SqlClient Data Provider 784 9 CurrituckDB 24220  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:50.387 86306 313532612609  5486 2005-06-12 04:20:55.873   476 -- Encrypted text     1   2078630448 ApplyFieldChanges            8272 - P 9
SQL:BatchCompleted .Net SqlClient Data Provider 784 9 CurrituckDB 24221  server   DOMAIN\user 0X010500000000000515000000013A9C04FFAAB81B3BF220CF77040000 DOMAIN user 2 73 server DOMAIN\user 2005-06-12 04:20:49.920 86306 313532612609 875 5951 2005-06-12 04:20:55.873 1 - Error 19230 1304
                begin transaction
                   declare @now as datetime;
                   set @now = getutcdate();
               exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=24,@name='Assigned To';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-31,@name='AttachedFileCount';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-1,@name='Authorized As';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=58,@name='BIS Links';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=9,@name='Changed By';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=33,@name='Created By';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=32,@name='Created Date';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=52,@name='Description';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=35,@name='Escalation Flag';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-57,@name='ExternalLinkCount';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=54,@name='History';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-32,@name='HyperLinkCount';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-104,@name='IterationID';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-95,@name='Parent ID';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-90,@name='ParentChild';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-16,@name='ProjectID';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=22,@name='Reason';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=37,@name='Related Links';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=75,@name='RelatedLinkCount';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=2,@name='State';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=1,@name='Title';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-15,@name='Work Item Form';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=-14,@name='Work Item FormID';
exec dbo.ChangeField @changerID=0,@changeDate=@now,@fldid=25,@name='Work Item Type';

                exec dbo.ApplyFieldChanges 0,@now;

                commit 147
Paul Marangoni
Hey Sarah, this might save you some time in the future!

A tip is to make one OSImage installation under Virtual Server, Patch it the way you want it, then shut it down.
Save that Image on a network share and give it a descriptive name like Win2003SP1.vmc and .vhd.
Then just make a new copy of the Image.
Name that one the hostname of the Server you're gonna use.
Mount it under Virtual Server, and boot it.
The use Sysinternals excellent NewSID (http://www.sysinternals.com/Utilities/NewSid.html) to make it unique and give it the right hostname and reboot it.

With this method you can Deploy a new server in less than 10 minutes.
Paintshow
I had the same problem and I used the following solution:

Do the following from a command line whilst you have the error dialog up

rskeymgmt -d

Say yes to "delete all encrypted data from the report server database" question

then run this command

%ProgramFiles%\Visual Studio Enterprise Server\BISIISDIR\uninstall\createds "http://SERVER/ReportServer/ReportService.asmx TfsReportDS "Data Source="SERVER";initial catalog=BisDWDB" "DOMAIN\TFS_SERVICE_ACCOUNT_USER" "TFS_SERVICE_ACCOUNT_PASSWORD"

It should say "Data Source Created Successfully"

If it does click retry.
Edwar Smeathers
Hi!

Tried the above, but I get the same error as mentioned before.
Larry P
Thanks for the tip. I have been saving the .vmc and .vhd files as I go and when things don't work out I have been using them as restore points.

I am currently at the SQL Server install step. The last time I ran the install wizard, it froze completely at the last component (Books Online) to be installed. I am hoping it will go through this time, I will know in a few minutes - I'm close to the end.
L Zhou
tried it no luck for me
wavemill
Was the error message from SQL 2005 June CTP The Beta2 single server setup _ONLY_ work with the SQL 2005 April CTP.

Could you post the error msg from the setup using April CTP

Thanks,
Scott
Nitin Chintamani
My next try is to still to use Virtual Server (since I've read so many posts saying that it works) but to use a Win2003Std without SP1 since the Windows Firewall/ICS (Internet Connection Sharing might interupt with lots of things).

I've also read that to first install SQL2005 CTP (April or later, I'm using June right now), then install Sharepoint Services with SP1, then to Windows Update the Sharepoint Services, then to install Reporting Services after Sharepoint Services.

I'll keep you posted after I've tried this!
Handofphate
I have been encountering the exact same errors and it looks like we have identical setups. I have been working on the install for several days and I can't seem to get it working.

I have been following the guidelines to the letter except for the fact that I am using Virtual Server instead of a clean machine and I am using the present lab AD instead of setting the active directory on the virtual machine.

Do you think this could be the root of our problems

I have read all posts in regards to the 32000 error and I am now considering attempting a clean install. The set back is that this would require us to purchase a new PC which we are trying to avoid.

Please post if you get the install working and how.... I am going to continue trying.
Paul B - Miami
FYI i get the following exception when i run this same command {widbloc.exe } within a cmd window.

Thanx --

Localizing database CurrituckDB on server enterprise.

The DB has 24 fields which the tool will try to localize.
System.Exception: Trying to update the DB with the localized field names failed. ---> System.Data.SqlClient.SqlException: The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE or DELETE statements.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
   at Microsoft.VisualStudio.Currituck.WIDBLoc.WIDBLoc.LocalizeWITDB(String serverName, String dbName)
   --- End of inner exception stack trace ---
   at Microsoft.VisualStudio.Currituck.WIDBLoc.WIDBLoc.LocalizeWITDB(String serverName, String dbName)
   at Microsoft.VisualStudio.Currituck.WIDBLoc.WIDBLoc.Main(String[] args)
mike bel
Today it worked for some unknown reason!!!

I'll try to describe the steps I took to get it working!

I installed Win2003Std w SP1 Slipstreamed on a Virtual Server Instance.
Made it a member of my Lab domain (which is a Native 2003 domain)
Logged on as domain\administrator
Installed IIS with ASP.Net
Removed Internet Explorer Enhanced Security Configuration
Verified the IIS (http://localhost )
Installed SQL Server 2005 Beta April CTP Edition
-With All Components
-Used Built-in System Account and Checked the Auto-Start service
-Used Mixed Mode Authentication
Restarted the Server

Logged on as domain\administrator
Enabled the Windows Firewall
-Opening for HTTP and RemoteDesktop (Tcp Port 80 and TCP port 3389)
Configured the Reporting Services IIS Pool
-Start IIS Manager
-Under Server, Right click on Application Pool
-Create New Pool, name it "Reporting Services"
-Under Server/Web Sites/Default Web Site, Right click on Reports and change Application Pool to "Reporting Services"
-Under Server/Web Sites/Default Web Site, Right click on ReportServer and change Application Pool to "Reporting Services"
Then I restarted the IIS
-Start->Run->iisreset
Windows Sharepoint Services Installation (with SP1)
Run the STSV2.EXE
-Accept the License Agreement
-Select Server Farm
-Configure the Sharepoint Admin site and Default site using the hostname and domain\administrator account
-Choose Team Web Site Template
-Verify the Sharepoint site with http://localhost and it should be a default Team Web Site

And now to the fun part!
-Fix the ReportService.asmx error by replacing the <assemblies> section in the <system.web> section of the C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\web.config file:
<assemblies>
<clear />
<add assembly="ReportingServicesWebServer" />
<add assembly="mscorlib" />
<add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
<add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</assemblies>

You also have to config both web.config files for reportserver and reportmanager to have full access:
Change the following line in both web.config files:
<trust level="Full" originUrl="" />
Location: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer
and: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager

Also you will have to exclude the Reports and ReportServer virtual directories from Sharepoint
-C:\program files\common files\ microsoft shared\web server extensions\60\bin\stsadm -o addpath -url http://localhost/reports -type exclusion
-C:\program files\common files\ microsoft shared\web server extensions\60\bin\stsadm -o addpath -url http://localhost/reportserver -type exclusion

Windows Update
-Install the KB841876 update
-Start->Run->iisreset
-Verify the Reports Virtual Directory (http://locahost/reports, be patient this will take well over 20 seconds to show) and the Reportservice.asmx (http://localhost/reportServer/Reportservice.asmx)

After here I shut down the server, made a copy of the Virtual Server Image and the restarted it again.

Logged on as domain\tfssetup (which is a domain admin account)
Edited the c:\inetpub\wwwroot\web.config file
-Removed the remarks from: <add name="Session" type="System.Web.SessionState.SessionStateModule" />
-and change false to true in the enableSessionState Param. Should be like this: <pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false"
-Start->Run->iisreset

Start the Team Foundation Server
-Choose so that both Tiers are on the same machine
-Specify Service Logon Account to domain\tfsservice (which is a domain admin account as well)
-The setup should run fine without any errors!

Add the TFSService Account to Namespace Administrator group
-C:\program files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\SDK\BIN\gssutil /g+ adm: n:domain\tfsservice
-It should end with a Done.

Install Office 2003 (with SP1)
-Excel should be enough, make sure to Update it to SP1!

Do a Image Backup now (atleast restart the server) and everything should work fine from now on!
No luck in installing TFS in a more or less single server installation. Different Error 32000's...

Answer this question