error 32000

Question

Team Foundation Server Dual-Server Deployment ,while install Application Tier get the error: Error 32000.Failed to get CustomActionData.

here is log file info:
vs70uimgr: DisplayMessage_START:Error 32000.The Commandline '"Z:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\widbloc.exe" -s datasvr -d

CurrituckDB' returned non-zero value: 1.
[06/16/05,23:57:14] vs70uimgr: DisplayMessage_END:Error 32000.The Commandline '"Z:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\widbloc.exe" -s datasvr -d

CurrituckDB' returned non-zero value: 1.
[06/16/05,23:57:14] Setup.exe: AddGlobalCustomProperty
[06/16/05,23:57:14] Visual Studio 2005 Team Foundation Application Tier Beta 2 (English): ***ERRORLOG EVENT*** : ERROR:Error 32000.The Commandline '"Z:\Program

Files\Microsoft Visual Studio 2005 Enterprise Server\widbloc.exe" -s datasvr -d CurrituckDB' returned non-zero value: 1.
[06/16/05,23:57:17] vs70uimgr: Entering DisplayMessage() method.

Answer 1

Sorry ,VSTS June must use April SQL 2005 .But I got the same error 3200.
setupwarehouse.log:
If exists(select name from Sysdatabases where name='BisDWDB') begin exec ('alter database [BisDWDB] set read_only with rollback immediate') waitfor delay '000:0:15' exec ('drop database BisDWDB') end
create database [BisDWDB]

exec sp_grantlogin [MYBETA\tfsservice]

exec sp_grantlogin [MYBETA\tfssetup]

exec sp_grantdbaccess [MYBETA\tfsservice]
exec sp_addrolemember 'db_owner', 'MYBETA\tfsservice'

exec sp_addRole TfsWarehouseDataReader

exec sp_grantdbaccess [MYBETA\tfssetup]
exec sp_addrolemember 'TfsWarehouseDataReader', 'MYBETA\tfssetup'

System.Data.SqlClient.SqlException: The login already has an account under a different user name.
User or role 'MYBETA\tfssetup' does not exist in this database.
   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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.VisualStudio.Bis.Warehouse.MetaData.WarehouseSchemaCreator.SqlExecuteNonQuery(SqlConnection cn, SqlTransaction tr, String sqlStmt)
   at Microsoft.VisualStudio.Bis.Warehouse.MetaData.WarehouseSchemaCreator.GrantAccess(String accessUser, String dataReaderAccount)
   at Microsoft.VisualStudio.Bis.Warehouse.MetaData.WarehouseSchemaCreator.CreateWarehouseDatabase(String accessUser, String dataReaderAccount)
   at Microsoft.VisualStudio.Bis.Tools.WarehouseSetup.SetupWarehouse()

Answer 2

This is a dual-server install of the June CTP of Team Foundation Server using the SQL Server 2005 April CTP?

Answer 3

I used SQL Server 2005 April CTP .
Data tier: member server.
App tier : DC
Logon user :tfssetup
tfs service account:tfsservice
Access report service :tfssetup

Answer 4

Jackie,

I got the same error when doing a single server install. What ended up happening to me was that there was an error with asp.net 2.0 beta 2.

When I tried to browse to http://localhost/ReportServer/ReportService.asmx

It did not work.

So i had to change the .net version in IIS Admin to be 2.0.????

Then i verified the above address would work and hit retry and it worked

I hope this helps.

Ryan

Answer 5

Ryan Kelley ,try exclude SQL Server Reporting Services from Windows SharePoint Services management

1. Open a Command Prompt and change directory to the %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\60\BIN directory.

2. Run the following commands to exclude the SQL Server Reporting Services Web applications:

   STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion

   STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion

3. Restart Windows.

Answer 6

Are you still having issues, or have you rectified the problem?

Answer 7

Now I am getting the issue again. The message box says "failed to get CustomActionData" And i think it must be somehow tied to the following.

When I start the installation for TFS - Single Server, it will not let me continue if i do NOT go, uninstall .net Framework 2.0 so that the TFS installer can install it. If .net Framwork 2.0 is installed it will not ever finish the setup process.

Any ideas? - I am beginning to wonder if this really works or not. LOL

Answer 8

Rob Caron MSFT wrote:

Are you still having issues, or have you rectified the problem?

yes,I still having the issues

Answer 9

In any "CustomData" Error, we need to log information from the VSMSI*.  This is a generic error and without the information, we don't know what to look for.

Open the file, and then look for the custom error information and send it to us please.

Thanks

Answer 10

Ryan Kelley wrote:

When I start the installation for TFS - Single Server, it will not let me continue if i do NOT go, uninstall .net Framework 2.0 so that the TFS installer can install it. If .net Framwork 2.0 is installed it will not ever finish the setup process.

This sounds like you might be using the wrong release of SQL Server. Are you installing with SQL Server 2005 April CTP, or the June CTP? Single-server will only working for Beta 2 of Team Foundation Server with the April CTP of SQL.

Answer 11

I get the same error during VS 2005 Team Foundation Application Tier Beta 2 Setup.  I have already installed the April SQL 2005 CTP on the other server and run the Data Tier Setup there.  The error reads:

Error 32000.Failed to get CustomActionData

I copied the following lines from the VSMsiLog5D17.txt file.  I copied lines from the installation of ASP.NET on:
====================================


Finished installing ASP.NET (2.0.50601).
06/28/05 11:17:14 DDSet_Status: Process returned 0
06/28/05 11:17:14 DDSet_Status: Commandline '"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50601\aspnet_regiis.exe" -iru -enable' returned 0
06/28/05 11:17:14 DDSet_CARetVal: 0
06/28/05 11:17:14 DDSet_Status: QuietExec returned 0
MSI (s) (A0:B8) [11:17:14:007]: Executing op: ActionStart(Name=CA_QuietExec,,)
06/28/05 11:17:14 DDSet_Exit: QuietExec ended
MSI (s) (A0:B8) [11:17:14:007]: Executing op: CustomActionSchedule(Action=CA_QuietExec,ActionType=17409,Source=BinaryData,Target=QuietExec,CustomActionData="C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"|0|0|0|0|NULL)
MSI (s) (A0:60) [11:17:14:069]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICF.tmp, Entrypoint: QuietExec
06/28/05 11:17:14 DDSet_Status: LANGID: 1033
06/28/05 11:17:14 DDSet_Entry: QuietExec started
06/28/05 11:17:14 DDSet_Status: Commandline: "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"
06/28/05 11:17:14 DDSet_Status: IgnoreExitCode: 0
06/28/05 11:17:14 DDSet_Status: Silent: 0
06/28/05 11:17:14 DDSet_Status: ActionStart: 0
06/28/05 11:17:14 DDSet_Status: Cost: 0
06/28/05 11:17:14 DDSet_Status: WorkingDirectory:
06/28/05 11:17:14 DDSet_Status: Silent: 0
06/28/05 11:17:14 DDSet_Status: ActionStart: 0
06/28/05 11:17:14 DDSet_Status: Cost: 0
06/28/05 11:17:14 DDSet_Status: WorkingDirectory:
06/28/05 11:17:17 DDSet_Status: Process returned 3
06/28/05 11:17:17 DDSet_Error: The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"' returned non-zero value: 3.
MSI (s) (A0!EC) [13:11:34:762]: Product: Visual Studio 2005 Team Foundation Application Tier Beta 2 (English) -- Error 32000.Failed to get CustomActionData.

06/28/05 13:11:34 DDSet_Status: Commandline: "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"
06/28/05 13:11:34 DDSet_Status: IgnoreExitCode: 0
06/28/05 13:11:34 DDSet_Status: Silent: 0
06/28/05 13:11:34 DDSet_Status: ActionStart: 0
06/28/05 13:11:34 DDSet_Status: Cost: 0
06/28/05 13:11:34 DDSet_Status: WorkingDirectory:
06/28/05 13:11:34 DDSet_Status: Silent: 0
06/28/05 13:11:34 DDSet_Status: ActionStart: 0
06/28/05 13:11:34 DDSet_Status: Cost: 0
06/28/05 13:11:34 DDSet_Status: WorkingDirectory:
06/28/05 13:11:53 DDSet_Status: Process returned 3
06/28/05 13:11:53 DDSet_Error: The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"' returned non-zero value: 3.
MSI (s) (A0!EC) [13:15:46:285]: Product: Visual Studio 2005 Team Foundation Application Tier Beta 2 (English) -- Error 32000.Failed to get CustomActionData.

06/28/05 13:15:46 DDSet_Status: Commandline: "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"
06/28/05 13:15:46 DDSet_Status: IgnoreExitCode: 0
06/28/05 13:15:46 DDSet_Status: Silent: 0
06/28/05 13:15:46 DDSet_Status: ActionStart: 0
06/28/05 13:15:46 DDSet_Status: Cost: 0
06/28/05 13:15:46 DDSet_Status: WorkingDirectory:
06/28/05 13:15:46 DDSet_Status: Silent: 0
06/28/05 13:15:46 DDSet_Status: ActionStart: 0
06/28/05 13:15:46 DDSet_Status: Cost: 0
06/28/05 13:15:46 DDSet_Status: WorkingDirectory:
06/28/05 13:16:05 DDSet_Status: Process returned 3
06/28/05 13:16:05 DDSet_Error: The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "DatabaseSrvr" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -ra "Domain\myId" -a "Domain\svcAcct" -v -l "C:\DOCUME~1\myId\LOCALS~1\Temp\setupwarehouse.log"' returned non-zero value: 3.

Answer 12

I was able to resolve this issue by setting the Reports virtual folder and the ReportServer virtual folder in IIS to use ASP.net 2.0.  I also created a separate app pool, not sure if that matters.  Reports and ReportServer virtual directories should use .net framework 2.0.5601.

Tommy Goddard
netdialect.com

Answer 13

Tommy, I wonder if you are using a different configuration than I am.  When I installed the data tier, I started by installing the April SQL 2005 CTP.  I assigned the ReportServer virtual directory to its on app pool.  (The Reports virtual directory is still in the default app pool.)  The thing that makes me think we have a different setup is the version number for ASP.NET.  On the data tier, the SQL Reports directories are using ASP.NET 2.0.50215.0.  On the application tier, the version of ASP.NET is 2.0.5601.

Answer 14

So you are running two different versions of the CLR?  I wasn't ever able to get that going :)  I tried installing the app tier and it complained about my version of the framework b2, so I removed it.  Then when I installed vs.net 2005 june ctp it installed CLR 2.0.5601.  When I installed April SQL it installed the CLR 2.0.50215.  I actually had to remove 2.0.50215 in order to install TFS.  But now because of issues with analysis server running on the 2.0.5601 I had to remove and TFS and reinstall SQL with the CLR.  I'm stuck...

I installed in the same order as you except I am not able to get past the installation of the Foundation server after I removed it.  I get the CustomAction error message.  Maybe I'll just remove everything like I did before and start over.

Answer 15

I get this same error when attempting to do a single server install with SQL Server 2005 June CTP. I couldn't use the April CTP because Microsoft removed it from the MSDN subscriber downloads. Additionally the two SQL Server virtual directories were already configured to use ASP.NET 2.0.50215.

Answer 16

You cannot do single-server with the June CTP. See: http://blogs.msdn.com/robcaron/archive/2005/06/15/429278.aspx

The SQL Server 2005 April CTP is still there; it's alongside the Visual Studio 2005 Beta 2 downloads.

For help cleaning-up old installs, see:
http://blogs.msdn.com/astebner/archive/2005/04/30/413764.aspx

Answer 17

Jackie - any news on how your install is doing? Did any of these posts help you get unstuck?

Answer 18

Jeez, maybe they should have stated that in the release notes maybe?   I have griped a few times about the CTPs not having enough detail on which releases work with the software we are installing.  For example, when installing the WinFX SDK you are required to use VS.net Beta 2 (No CTP).  For June TFS CTP you are required to use April SQL but can not use June SQL and can only do a dual server install with April SQL.  Requires .net CLR 2.0.x  ... etc... you guys get the idea.  Please pass it along.

Thanks,
Tommy

Answer 19

I can't tell specifically, but be aware that the June CTP of Team Foundation REQUIRES that you install on 2 boxes.  This is a result of SQL and TFS being on different CLR versions (at the moment).  Using 'setup' you will not be able to get both CLRs successfully installed on one box.

And, TFS will attempt to install a build of the CLR which isn't the Beta 2 build.

Challenging to say the least ... but CTPs are a point in time and some of those times not everything is sync'd up.

Look at it this way -- we get to deal with the same challenges :)

Answer 20

My error  display:
System.Data.SqlClient.SqlException: The login already has an account under a different user name.User or role 'MYBETA\tfssetup' does not exist in this database.
So when prompted the tfs service and access reporting service account ,I inputed administrator as tfsservice account and tfssetup as  access reporting service account ,I successed.

Answer 21

I've had my say about CTPs before (http://blogs.msdn.com/robcaron/archive/2004/12/09/279257.aspx).

Okay, since we've heard back from Jackie, I'm going to close this thread and call it a day.