Installing without AD? Using ADAM? (Error 32000)

Locked Installing without AD? Using ADAM? (Error 32000)

  • lunes, 06 de junio de 2005 16:49
     
     

    I followed the instructions for installing TS to the letter, but when I try to install it on the application server, I get the error:

    Error 32000. The commandline "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "SERVERNAME" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolodated.xml" -a "DOMAIN\TFSSERVICE" -v -l "..local..\Temp\SetupWarehouse.log"" returned non-zro value: 3.

    If I check the LogFile, it says:

    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 [SERVER1\TFSSERVICE]
    System.Data.SqlClient.SqlException: Windows NT user or group 'SERVER1\TFSSERVICE' not found. Check the name again.

    This tells me it's trying to use the username of SERVER1\TFSSERVICE on my DATABASE1 machine, which of course won't work - but I'm not sure, without a domain, how to use ADAM to solve the problem, since I can't even connect to the ADAM service (I've tried putting in the ADAM instance name and it says it can't be found).

    So my question is this: must I install Active Directory on my Application tier machine before I install TS?  Should ADAM work?  Do I need to do some custom configurations in my ADAP before I install the TS app?  How can I connect to the ADAM installation?
    What's the best configuration for this with only 2 hosting machines and no domain?

    Thanks!

Todas las respuestas

  • martes, 07 de junio de 2005 3:46
     
     Respondida
    You must have a domain already in your setup for Beta2.  You cannot use local accounts.  This will change for RTM as we will support workgroups

    Thanks

    Bruce
  • martes, 07 de junio de 2005 4:55
     
     
    I understand, but I'm becoming more and more disappointed with Microsoft and their bloatware products.  Team Server is an utter *** to install; it shouldn't be.  In addition, a BETA is exactly that - feature complete - BETA.  It's ridiculous that TS doesn't support the Workgroup environment in BETA 2 if they're going to support it for release.  When will it be tested?

    Microsoft preaches best development practices, yet doesn't follow them.  I've wasted roughly 6-8 hours trying to get Team Server installed, and I don't recall seeing anywhere that AD is REQUIRED, plus why on earth is ADAM installed if AD is required?

    Plain ridiculous.
  • martes, 07 de junio de 2005 5:50
     
     Respondida
    We appreciate your comments & feedback.  We continue to look for ways to improve Team System, which includes the setup experience. 

    Yes, this is a Beta - in fact, it is Team Foundation's first Beta.  We've gotten tremendous feedback from folks like, those willing to take the time to install and use Team Foundation.  We are using this information to make improvements.  So, thank you.

    FWIW, The requirement on AD is somewhat subtle.  Team Foundation doesn't specifically use AD rather it, for the beta, depended on domain based accounts for configuring the system.  This requirement is what brings AD into the discussion.  Workgroup support not being available in this beta was an conscience decision on our part.  We felt there was insufficient testing, not to mention a bug or two, to release it for use.

    AD/AM is no longer used by Team Foundation - post Beta 2.

    Again, thank you