SQLServerFineBuild Forum Rss Feed

New Post: How to get finebuild to recognize SQLFineServer.bat /drv... settings

skinnerd3y — Mon, 27 Feb 2012 16:59:53 GMT

ah-ha, The line/character spacing was throwing it off thanks so much. will try again today.

New Post: How to get finebuild to recognize SQLFineServer.bat /drv... settings

EdVassie — Sat, 25 Feb 2012 08:27:16 GMT

Hi,

FineBuild was written before Powershell got installed everywhere, and still needs to comply with MS-Dos command line restrictions.

The ^ character is the MS-Dos command continuation character, and must be the last character in each line. If it is followed by even a single space character it will not be treated as a command continuation character and the following lines will be treated as separate commands.

If a line ends with a ^ and the following line is blank, then the command is treated as complete. In your example there is a blank line between the /SAPWD: and /DrvProg: parameters, which will mean that the /DrvProg: parameter will not be added to the FineBuild command line. Also, the last line of the command should not include the ^ character.

If a parameter contains spaces it must be delimited within double-quote characters ". (Do not use two single-quote characters.) If you have an opening quote you must also have a closing quote, otherwise the Dos command interpreter will treat everything else as part of the parameter value. In your example you have an opening quote for /SAPWD: but no closing quote.

There are some other restrictions that are on page 17 of the Reference Manual. Eventually this information will be moved to the Wiki but for now please see the Reference Manual.

Once you get past this, it is useful to know that FineBuild exploits VBScript Named Arguments. A Named Argument always starts with a / and ends with a : and the value of the argument must start immediately after the : character.

A Named Argument is not case sensitive, but the value given with the named argument is case-sensitive. For example, /SAPWD:MySAPassword /sapwd:MySAPassword /SaPwd:MySAPassword are all equivalent, but /SAPWD:MySAPassword and /SAPWD:mysapassword are NOT equivalent.

If you supply the same Named Argument more than once, FineBuild will only see the first value that you supplied. For Example, if you supply /DrvProg:E /DrvProg:H, then FineBuild will only see the value E for /DrvProg:.

The syntax %* near the beginning of the command file allows additional parameters to be given at run time. For example if you have a command file SQLFineServer that includes a parameter /DrvProg:E, you can type SQLFineServer /DrvProg:W to override the value given in the command file so that FineBuild uses the value /DrvProg:W

New Post: How to get finebuild to recognize SQLFineServer.bat /drv... settings

Skinnerd3y — Fri, 24 Feb 2012 20:39:44 GMT

I am trying to use the finebuild Server install option I have configured the sqlfineServer.bat as below but it continues to install everything to the C: drive what am I doing wrong:

REM Copyright © 2008, 2011 Edward Vassie. Distributed under Ms-Pl License
REM

CALL "SqlFineBuild.bat" %* /Type:Full /DEBUG:YES /IAcceptLicenseTerms ^
/SAPWD:"MySAPassword^

/DrvProg:E ^
/DrvBackup:I /DrvData:F /DrvDataFT:F /DrvLog:G /DrvTemp:T /DrvDBA:H ^

New Post: Installation Error @ 1BA

EdVassie — Thu, 23 Feb 2012 12:32:07 GMT

Hi Lorenzo,

FineBuild is trying to create a shortcut for the SQLDIAG tool at this stage. It is possible that the Performance Tools menu has a different name in the Italian Edition of SQL Server. You can restart FineBuild and add a /MenuPerfTools: parameter to supply the Italian name of this menu (put the menu name in quotes if the name includes any spaces), and tell FineBuild where to restart by adding a /restart:auto parameter.

There are other menus that may have language-specific names. The FineBuild Referance Manual has details of what parameters may need to be added in the section Non-English Versions of SQL Server on page 194.

The SQLDIAG shortcut is the last piece of work in 5FA. If you want to bypass this, restart FineBuild by adding a /restart:5fb parameter.

I am preparing a Win 7 guest machine for running a SQL 2008 R2 Express install, and if anything further is needed I'll let you know when the install is complete.

New Post: Install error object required: ...

EdVassie — Thu, 23 Feb 2012 12:06:33 GMT

Hi,

You need to run one of the files in the FineBuild folder, such as SQLFineWorkstation.

The files in the Build Scripts folder are not designed to run independantly of each other, they must be run in the sequence controlled by the SQLFineBuild.bat file. The SQLFineBuild.bat file itself needs specific parameters to tell it what to do, and these are supplied by files such as SQLFineWorkstation or SQLFineServer.

The QuickStart guide describes how to run a Workstation install. When you want to install to a multi-disk server or to a Windows Cluster, please see the Reference Manual for more details of this type of install.

New Post: Install error object required: ...

Skinnerd3y — Wed, 22 Feb 2012 23:49:38 GMT

I am trying to do a findbuild sql server2008r2 install on windows server 2008R2.

I rightclick the cmdHere.exe and run as admin
then I type in cscript FineBuild2InstallSQL.vbs and get the error below.
I've changed the path and put everything in the Build Scripts folder but get same error.
Any help would be appreciated.

C:\SQL2008R2-Std\FineBuild\Build Scripts>cscript FineBuild2InstallSQL.vbs
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
**************************************************
*
* Starting FineBuild2InstallSQL
*
**************************************************
C:\SQL2008R2-Std\FineBuild\Build Scripts\FineBuild2InstallSQL.vbs(113, 3) Micros
oft VBScript runtime error: Object required: 'objBuildFile.documentElement'

***** Error has occurred *****
Error code : 424
Source : Microsoft VBScript runtime error
Description: Object required: 'objBuildFile.documentElement'
SQL Server Base Install failed

New Post: Installation Error @ 1BA

penzo — Wed, 22 Feb 2012 13:48:54 GMT

This is feedback for 3.0.2 release

all seems ok, but it aborts somepoint @ configuration
now,sql files are OK, istance name and TCP port OK, FileStream OK

sa account disabled (and also if I set password and grant login it fails to login)... Maybe I forgot some option?

.Net 4 is OK as well as PS2 is OK (but this is by default on Win7)

Using:

Win7pro - italian sp1
SQL2008R2 Express ADV (ENU version)
Finebuild - 3.0.2
this Finebuildfile:

@ECHO OFF
REM Copyright � 2009, 2011 Edward Vassie.  Distributed under Ms-Pl License
REM
CALL "SQLFineBuild.bat" %*     /Type:Workstation             /IAcceptLicenseTerms          ^
 /InstNet4:Yes /InstPS2:Yes ^
 /Edition:Express ^
 /Instance:QUALIBUS   /TCPPort:9966 ^
 /FileStreamLevel:3   /FileStreamShareName:QUALIBUS ^
 /DrvProg:C ^
 /SAPWD:"Goodpa55!"

this is the log:

**************************************************
*
* Starting FineBuild Validation
*
**************************************************
Validation processing for FineBuild for SQL2008R2
FineBuild Execution Environment
 
 FineBuild Version          V3.0.2
 Operating System Name      Windows 7 Ultimate
 Operating System Level     
 Operating System Platform  X64
 SQL Server Version         SQL2008R2
 
Validation processing for build type WORKSTATION
 
/IAcceptLicenseTerms is present.
This means that you accept the license terms of FineBuild and the licence terms of all products that FineBuild installs
 
**************************************************
*
* Starting FineBuild1Preparation
*
**************************************************
Process Id 1: Starting Preparation processing (See 3.3) at 17:45:47
Process Id 1A: Setup FineBuild (See 3.x) at 17:45:47
Process Id 1AA: Setup Host (See 3.2.6) at 17:45:47
 Setup Host (See 3.2.6) complete
Process Id 1AZ: Finished SetupFineBuild at 17:45:47
Process Id 1B: Setup SQL Server folders (See 3.3.1, 3.3.2, 3.4.3) at 17:45:47
Process Id 1BA: Setup System drives at 17:45:47
 Setup C: drive for System
 Setup System drives complete
Process Id 1BB: Setup DBA drive at 17:45:50
 Setup DBA drive complete
Process Id 1BC: Setup SQL Server drives at 17:45:51
 Setup SQL Server drives complete
Process Id 1BE: Setup Temp drive (See 3.3.3) at 17:45:57
 Setup Temp folder Environment Variables on drive C
 Setup Temp drive (See 3.3.3) complete
Process Id 1BF: Temp Folder for User Accounts (See 3.3.4) at 17:45:59
 Temp Folder for User Accounts (See 3.3.4) complete
Process Id 1C: Setup local groups (See 3.4.4) at 17:46:00
 Setup local groups (See 3.4.4) complete
Process Id 1D: Setup Rights (See 3.4.5) at 17:46:01
Process Id 1DA: Setup Group Rights at 17:46:03
 Setup Group Rights complete
Process Id 1DB: Setup Account Rights at 17:46:03
 Setup Account Rights complete
Process Id 1E: Setup SQL Server Network (See 3.4.x) at 17:46:03
Process Id 1EA: Setup Firewall (See 3.4.6) at 17:46:03
 Setup Firewall (See 3.4.6) complete
Process Id 1EC: Run GPUpdate to apply permissions at 17:46:07
 Run GPUpdate to apply permissions complete
Process Id 1TZ: Finished Preparation processing at 17:46:07
**************************************************
*
* Starting User1Preparation
*
**************************************************
Process Id 1U: User Preparation processing at 17:46:10
Process Id 1ZZ: Completed User Preparation processing at 17:46:11
**************************************************
*
* Starting FineBuild2InstallSQL
*
**************************************************
Process Id 2: Starting SQL Install processing (See 4) at 17:46:13
Process Id 2A: Pre-requisite processing (See 4.2) at 17:46:13
Process Id 2AA: Build Slipstreamed SQL Install Media (See 4.2.1) at 17:46:13
 Extracting RTM media
 SP1 file not found: C:\Users\Lorenzo Faleschini\Desktop\SQL2008R2-Express\Service Packs\SP1\SQLServer2008R2SP1-KB2528583-x64-ENU.exe
 Build Slipstreamed SQL Install Media (See 4.2.1) complete
Process Id 2BA: SQL2008R2 install for build WORKSTATION (See 4.3.2) at 17:47:25
 SQL Server install command: "C:\Temp\SQLMediaPCU\Setup.exe" /QUIETSIMPLE    /FEATURES="SQLEngine,Replication,FullText,RS,CONN,BOL,BIDS,SSMS,ADV_SSMS,BC"  /INSTANCENAME="QUALIBUS"  /SAPWD="**********" /SQLSVCACCOUNT="NT AUTHORITY\SERVIZIO DI RETE"  /SQLSVCSTARTUPTYPE=AUTOMATIC /AGTSVCACCOUNT="NT AUTHORITY\SERVIZIO DI RETE" /AGTSVCSTARTUPTYPE=AUTOMATIC /FTSVCACCOUNT="NT AUTHORITY\SERVIZIO DI RETE" /SQLSYSADMINACCOUNTS="WIN7VM\Lorenzo Faleschini" "BUILTIN\ADMINISTRATORS" /SQLCOLLATION="Latin1_General_CI_AS" /FILESTREAMLEVEL=3 /FILESTREAMSHARENAME="QUALIBUS" /RSSVCACCOUNT="NT AUTHORITY\SERVIZIO DI RETE" /RSSVCSTARTUPTYPE=AUTOMATIC /RSINSTALLMODE="DefaultNativeMode" /ACTION="INSTALL"  /NPENABLED=1 /TCPENABLED=1 /ERRORREPORTING=0 /SQMREPORTING=0 /IAcceptSQLServerLicenseTerms /BROWSERSVCSTARTUPTYPE=MANUAL /BROWSERSVCUSERNAME="NT AUTHORITY\SERVIZIO DI RETE"  /INSTALLSQLDATADIR="C:\Program Files\Microsoft SQL Server" /SQLUSERDBDIR="C:\SQLFiles\MSSQL.QUALIBUS.Data" /SQLUSERDBLOGDIR="C:\SQLFiles\MSSQL.QUALIBUS.Log" /SQLTEMPDBDIR="C:\SQLFiles\MSSQL.QUALIBUS.Data\Tempdb" /SQLTEMPDBLOGDIR="C:\SQLFiles\MSSQL.QUALIBUS.Log" /SQLBACKUPDIR="C:\SQLFiles\MSSQL.QUALIBUS.Backup\AdHocBackup"  /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"  /INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"   /ENABLERANU=1  /TIMESTAMP=20120221_174725
 QUALIBUS 2BA SQL2008R2 install for build WORKSTATION (See 4.3.2) log files located in: SOFTWARE\Microsoft\Microsoft SQL Server\100\Bootstrap\\20120221_174725
 SQL2008R2 install for build WORKSTATION (See 4.3.2) complete
Process Id 2C: Setup SQL Server post-install tasks at 18:12:38
Process Id 2CA: Save installed SQL Edition data at 18:12:38
 Save installed SQL Edition data complete
Process Id 2CB: Reset DBA Permissions at 18:12:38
 Reset DBA Permissions complete
Process Id 2Z: Finished SQL Install processing at 18:13:03
**************************************************
*
* Starting FineBuild3InstallFixes
*
**************************************************
Process Id 3: Starting SQL Fixes processing (See 4.4) at 18:13:06
Process Id 3A: Install SQL Service Pack SP1 (See 4.4.1) at 18:13:06
 Install SQL Service Pack SP1 (See 4.4.1) bypassed
Process Id 3BA: Install SQL Cumulative Update SP1 CU3 (See 4.4.2) at 18:13:06
 Install SQL Cumulative Update SP1 CU3 (See 4.4.2) bypassed
Process Id 3BB: Install SQL Cumulative Update SP1 CU3 for SNAC (See 4.4.3) at 18:13:06
 Install SQL Cumulative Update SP1 CU3 for SNAC (See 4.4.3) bypassed
Process Id 3C: SQL BOL Update (See 4.4.4) at 18:13:06
 SQL BOL Update (See 4.4.4) bypassed
Process Id 3E: Run Update Scripts (See 4.4.5) at 18:13:06
 Checking if update scripts are complete.
 Run Update Scripts (See 4.4.5) complete
Process Id 3F: Backup system database files (See 4.4.6) at 18:13:26
 Backing up System Database files
 Checking if update scripts are complete.
 Backup system database files (See 4.4.6) complete
Process Id 3G: Get SQL patch level at 18:13:56
 Get SQL patch level complete
Process Id 3Z: Finished SQL Fixes processing at 18:13:56
**************************************************
*
* Starting FineBuild4InstallXtras
*
**************************************************
Process Id 4: Starting Xtras processing (See 5) at 18:13:58
 Checking if update scripts are complete.
Process Id 4A: Analysis Services Extras at 18:14:09
Process Id 4I: Integration Services Extras at 18:14:09
Process Id 4IB: Install DTS Designer at 18:14:09
 Install DTS Designer bypassed
Process Id 4IC: Install DTS Backup 2000 at 18:14:09
 Install DTS Backup 2000 bypassed
Process Id 4R: Report Services Extras at 18:14:09
Process Id 4RA: Install Taskpad View Report at 18:14:09
 Install Taskpad View Report bypassed
Process Id 4RB: Install Report Services Scripter at 18:14:09
 Install Report Services Scripter bypassed
Process Id 4RC: Install Linked Report Generator at 18:14:09
 Install Linked Report Generator bypassed
Process Id 4S: SQL Server Extras at 18:14:09
Process Id 4SD: Install SQL Cache Manager at 18:14:09
 Install SQL Cache Manager bypassed
Process Id 4SH: Install SQL System Views Map at 18:14:09
 Install SQL System Views Map bypassed
Process Id 4T: Tools Extras at 18:14:09
Process Id 4TA: Install Windows Access Based Enumeration at 18:14:09
 Install Windows Access Based Enumeration bypassed
Process Id 4TB: Install Extended Events Manager at 18:14:09
 Install Extended Events Manager bypassed
Process Id 4TC: Install PDF Reader at 18:14:09
 Install PDF Reader bypassed
Process Id 4TD: Install Process Explorer at 18:14:09
 Install Process Explorer bypassed
Process Id 4TE: Install Process Monitor at 18:14:09
 Install Process Monitor bypassed
Process Id 4TF: Install RML Tools at 18:14:09
 Install RML Tools bypassed
Process Id 4TG: Install SQL Nexus at 18:14:09
 Install SQL Nexus bypassed
Process Id 4TH: Install SQL troubleshooting Guide at 18:14:09
 Install SQL troubleshooting Guide complete
Process Id 4TI: Install XML Notepad at 18:14:09
 Install XML Notepad bypassed
Process Id 4X: Finished Xtras processing at 18:14:09
**************************************************
*
* Starting FineBuild5ConfigureSQL
*
**************************************************
Process Id 5: Starting SQL Configuration processing (See 6) at 18:14:11
 Checking if update scripts are complete.
Process Id 5A: Services configuration (See 6.2) at 18:14:21
Process Id 5AA: Network Protocols (See 6.2.1.2) at 18:14:21
 Network Protocols (See 6.2.1.2) complete
Process Id 5AB: Configure COM Security at 18:14:21
 Configure COM Security complete
Process Id 5AC: Configure SQL Startup Parameters at 18:14:21
 Configuring SQL Server parameters
 Checking if update scripts are complete.
 Configure SQL Startup Parameters complete
Process Id 5AE: Configure Service Startup Options at 18:14:41
 Starting Reporting Services
 Configure Service Startup Options complete
Process Id 5B: Instance configuration (See 6.3) at 18:14:47
Process Id 5BA: SQL Surface Area options (See 6.3.1.1) at 18:14:47
 Backup Service Master Key (See 6.3.1.3)
 SQL Surface Area options (See 6.3.1.1) complete
Process Id 5BD: SQL Instance properties (See 6.3.2) at 18:14:49
 SQL Instance properties (See 6.3.2) complete
Process Id 5C: Account configuration (See 6.4) at 18:14:50
Process Id 5CA: SQL standard accounts (See 6.4.1) at 18:14:50
 Add DB Owner account (See 6.4.2)
 Add User accounts (See 6.4.?)
 SQL standard accounts (See 6.4.1) complete
Process Id 5CB: SQL sysadmin accounts (See 6.4.3) at 18:14:50
 SQL sysadmin accounts (See 6.4.3) complete
Process Id 5CD: Rename and Disable sa account (See 6.4.5) at 18:14:51
 Rename and Disable sa account (See 6.4.5) complete
Process Id 5CF: Configure RS Accounts (See 6.4.7) at 18:14:51
Process Id 5CFA: Reporting Services Administration Accounts (See 6.4.7.1) at 18:14:51
 Reporting Services Administration Accounts (See 6.4.7.1) complete
Process Id 5CFB: Reporting Services Execution Account (See 6.4.7.2) at 18:14:56
Process Id 5CFC: Backup RS Encryption Key (See 6.4.7.3) at 18:14:56
 Backup RS Encryption Key (See 6.4.7.3) complete
Process Id 5D: Database configuration (See 6.5) at 18:14:57
Process Id 5DA: System database setup (See 6.5.1.2) at 18:14:57
 System database setup (See 6.5.1.2) complete
Process Id 5DB: System database move (See 6.5.1.2.4) at 18:15:00
 Copying Database files
 Making backup of system database files
 System database move (See 6.5.1.2.4) complete
Process Id 5DC: Restart SQL Server (See 6.5.1.3) at 18:15:12
 Checking if update scripts are complete.
 Starting Reporting Services
 Removing redundant database files
 Restart SQL Server (See 6.5.1.3) complete
Process Id 5DE: Configure Full Text Search (See 6.5.2) at 18:15:34
 Configure Full Text Search (See 6.5.2) complete
Process Id 5E: SQL Management configuration (See 6.6) at 18:15:35
Process Id 5EA: System DB Management (See 6.6.1) at 18:15:35
 System DB Management (See 6.6.1) complete
 System DB Management (See 6.6.1) complete
Process Id 5EB: Create DBA DB DBA_Data (See 6.6.2.1) at 18:15:38
 Create DBA DB DBA_Data (See 6.6.2.1) complete
Process Id 5EC: DBA Management Routines (See 6.6.2.2) at 18:15:38
 DBA Management Routines (See 6.6.2.2) complete
Process Id 5EG: Generic Maintenance setup (See 6.6.5) at 18:15:43
 Generic Maintenance setup (See 6.6.5) complete
Process Id 5EH: Apply standard DB options (See 6.6.6) at 18:15:49
 Apply standard DB options (See 6.6.6) complete
Process Id 5EI: Apply standard Job corrections (See 6.6.?) at 18:15:50
 Apply standard Job corrections (See 6.6.?) complete
Process Id 5F: Windows configuration (See 6.6.7) at 18:15:50
Process Id 5FA: SQL menu items (See 6.6.7.1) at 18:15:50
***** Error has occurred *****
 Process    : 5FA: SQL menu items (See 6.6.7.1)
 Error code : -2147024893
 Source     : WshShortcut.Save
 Description: Impossibile salvare il collegamento "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2008 R2\Performance Tools\SQLDiag.lnk".
 Last Action: SQLDIAG Shortcut
 Instance Configuration failed

New Post: Installation Error @ 1BA

EdVassie — Sat, 18 Feb 2012 12:30:06 GMT

Hi Penzo,

As discussed in direct emails, thanks very much for sending me a list of the problems you have had trying to install Italian language SQL Server with FineBuild. The problem you initialy reported should be fixed in the v3.0.2 release uploaded on 17 Feb, but the other issues with the Italian install need further changes to FineBuild, and I plan to fix these in the next version.

New Post: Installation Error @ 1BA

penzo — Thu, 16 Feb 2012 12:05:27 GMT

I replaced ntrights.exe with the one in win2003resource kit, and reg.exe with that in system32 folder ('cause I didn't find it under w2k3toolkit)...

but nothing changed. same error

New Post: Installation Error @ 1BA

penzo — Thu, 16 Feb 2012 11:27:41 GMT

Thanks for quick reply:

1- Can you rerun and add a parameter /debug:yes and send me the log file.

**************************************************
*
* Starting FineBuild Validation
*
**************************************************
Validation processing for FineBuild for SQL2008R2
Validation processing for build type WORKSTATION
  >Validation processing for all build types
  >Check available space on Drive A:
  >Check available space on Drive C:
  >Check available space on Drive D:
  >Validate License details
 
/IAcceptLicenseTerms is present.
This means that you accept the license terms of FineBuild and the licence terms of all products that FineBuild installs
 
**************************************************
*
* Starting FineBuild1Preparation
*
**************************************************
  >Get Cluster details
Process Id 1: Starting Preparation processing (See 3.3) at 12:17:33
  >Add Buildfile value ProcessId: 1
  >Add Buildfile value ProcessIdDesc: Starting Preparation processing (See 3.3)
  >Add Buildfile value ProcessIdTime: 12:17:33
Process Id 1A: Setup FineBuild (See 3.x) at 12:17:33
  >Add Buildfile value ProcessId: 1A
  >Add Buildfile value ProcessIdDesc: Setup FineBuild (See 3.x)
  >Add Buildfile value ProcessIdTime: 12:17:33
Process Id 1AA: Setup Host (See 3.2.6) at 12:17:33
  >Add Buildfile value ProcessId: 1AA
  >Add Buildfile value ProcessIdDesc: Setup Host (See 3.2.6)
  >Add Buildfile value ProcessIdTime: 12:17:33
 Setup Host (See 3.2.6) complete
  >Check CACLS.EXE exists in Windows folder
  >(1AA) Run CACLS /?
  >Check NTRIGHTS.EXE exists in Windows folder
  >(1AA) Run NTRIGHTS /?
  >Check REG.EXE exists in Windows folder
  >(1AA) Run REG /?
  >Add Buildfile value DrvDataAS: C
  >Add Buildfile value DrvLogAS: C
  >Add Buildfile value DrvData: C
  >Add Buildfile value DrvLog: C
  >Add Buildfile value DrvTemp: C
  >Add Buildfile value DrvLogTemp: C
  >Add Buildfile value DrvDBA: C
Process Id 1AZ: Finished SetupFineBuild at 12:17:34
  >Add Buildfile value ProcessId: 1AZ
  >Add Buildfile value ProcessIdDesc: Finished SetupFineBuild
  >Add Buildfile value ProcessIdTime: 12:17:34
Process Id 1B: Setup SQL Server folders (See 3.3.1, 3.3.2, 3.4.3) at 12:17:34
  >Add Buildfile value ProcessId: 1B
  >Add Buildfile value ProcessIdDesc: Setup SQL Server folders (See 3.3.1, 3.3.2, 3.4.3)
  >Add Buildfile value ProcessIdTime: 12:17:34
Process Id 1BA: Setup System drives at 12:17:34
  >Add Buildfile value ProcessId: 1BA
  >Add Buildfile value ProcessIdDesc: Setup System drives
  >Add Buildfile value ProcessIdTime: 12:17:34
  >Setup System drive
 Setup C: drive for System
  >Labelling drive C:
  >Clearing index attribute from drive C:
  >(1BA) Run Async ATTRIB +I C:\*.* /D /S
  >Creating share for drive C:\
  >Add Buildfile value DirProgSys: C:\Program Files
  >Add Buildfile value DirProgSysX86: C:\Program Files (x86)
  >Setup Program folder
  >ProcessFolderRights("NT AUTHORITY\SERVIZIO DI RETE","C:\Program Files")
  >Assign rights to folders
  >(1BA) Run %COMSPEC% /D /C Echo Y| cacls "C:\Program Files" /T /C /E /G "NT AUTHORITY\SERVIZIO DI RETE":F 
***** Error has occurred *****
 Process    : 1BA: Setup System drives
 Error code : 2
 Last Action: (1BA) Run %COMSPEC% /D /C Echo Y| cacls "C:\Program Files" /T /C /E /G "NT AUTHORITY\SERVIZIO DI RETE":F 
 SQL Server install preparation failed

2- Can you also confirm tht the folder name C:\Program Files does exist and is not given a different name on the Italian version of Windows.

In Windows explorer I see C:\Programmi but if I type C:\Program Files it goes to the right directory. In fact this is what is in cmd: I thiink the italian name is just a symbolic link or hard link as you prefer (or junction speaking windows)

C:\>dir / Il volume nell'unit� C � System Numero di serie del volume: 68A4-1CDD

Directory di C:\

25/11/2011  15:12 25/11/2011  15:07 14/07/2009  02:38 25/11/2011  15:07 14/07/2009  06:08 16/02/2012  10:35 14/07/2009  04:20 15/02/2012  18:15 15/02/2012  19:45 20/12/2011  17:41 25/11/2011  15:12 25/11/2011  15:12 16/02/2012  10:25 15/02/2012  16:27 25/11/2011  15:12 15/02/2012  19:45 3 File  2.147.342.922 byte 13 Directory  44.369.866.752 byte disponibili

a <DIR> $Recycle.Bin <DIR> Boot 383.562 bootmgr 8.192 BOOTSECT.BAK <JUNCTION> Documents and Settings [C:\Users] 2.146.951.168 pagefile.sys <DIR> PerfLogs <DIR> Program Files <DIR> Program Files (x86) <DIR> ProgramData <JUNCTION> Programmi [C:\Program Files] <DIR> Recovery <DIR> SQL2008R2-Express <DIR> System Volume Information <DIR> Users <DIR> Windows

3- Also, are you sure you are running with elevated authority... right-click on CmdHere.bat and select Run as Administrator.

yes from local admin account (this machine isn't in any domain, so WIN7VM\penzo is the admin user), I have no spaces in the username and the password is not containing any of these \/:;=,+?“‘[]<>|%

the only thing I miss is to replace NTRIGHTS.EXE and REG.EXE with those on win 2003 resource cd... that I'm now downloading from technet to test just in case.

thanks again Ed

New Post: Installation Error @ 1BA

EdVassie — Thu, 16 Feb 2012 10:45:58 GMT

Hi,

Can you rerun and add a parameter /debug:yes and send me the log file. Can you also confirm tht the folder name C:\Program Files does exist and is not given a different name on the Italian version of Windows. Also, are you sure you are running with elevated authority... right-click on CmdHere.bat and select Run as Administrator.

Many thanks

New Post: Installation Error @ 1BA

penzo — Wed, 15 Feb 2012 19:08:51 GMT

Hi,

I have a problem, I'm testing FineBuild 3.0.1 to automate my 2008R2 Express installs.

I have tested on Win 7 Ultimate x64 and I get an error that I cannot fix.. I don't understad where the problem is exactly, I guess by reading the reference that should be somewhere in System Drive permission settings... this is just a guess, cause it stops @ 1BA

I have enough disk space on this machine (it's a VMware Workstation 8 vm), more than 30 Gb on C:

can you help me?

HERE THE SCRIPT I EDITED (From SQLFineExpress):

@ECHO OFF
REM Copyright � 2009, 2011 Edward Vassie.  Distributed under Ms-Pl License
REM
CALL "SQLFineBuild.bat" %*     /Type:Workstation             /IAcceptLicenseTerms          ^
 /InstNet4:Yes /InstPS2:Yes ^
 /Edition:Express ^
 /Instance:QUALIBUS   /TCPPort:9966 ^
 /FileStreamLevel:3   /FileStreamShareName:QUALIBUS ^
 /DrvProg:C ^
 /SAPWD:"ggoooodpa55!"

HERE THE ERROR I GET (From Log):

HERE MY FOLDER CONTENTS (just to check if is a media preparation issue):

./Additional Components:
Windows6.0-KB968930-x64.msu
Windows6.0-KB968930-x86.msu
WindowsServer2003-KB933789-x86-ENU.exe
WindowsServer2003-KB937444-x86-ENU.exe
WindowsServer2003-KB968930-x64-ENG.exe
WindowsServer2003-KB968930-x86-ENG.exe
WindowsServer2003.WindowsXP-KB933789-x64-ENU.exe
WindowsServer2003.WindowsXP-KB937444-x64-ENU.exe
WindowsXP-KB968930-x86-ENG.exe

./Additional Components/Redist:
dotNetFx40_Full_x86_x64.exe
WindowsServer2003-KB942288-v4-x64.exe
Windows6.0-KB942288-v2-x64.msu
WindowsServer2003-KB942288-v4-x86.exe
Windows6.0-KB942288-v2-x86.msu
WindowsXP-KB942288-v3-x86.exe

./FineBuild:
All FineBuild Stuff here

./Service Packs:
Empty for now

./SQLMedia:
SQLEXPRADV_x64_ENU.exe
SQLEXPRADV_x86_ENU.exe

New Post: bug report

joshf — Wed, 07 Dec 2011 22:59:07 GMT

Hi Ed,

I just created an issue in the issue tracker but I don't see any other issues in there so I wasn't sure that was in use. Just wanted to call your attention to it.

- Josh

New Post: Installation using Mount Points

EdVassie — Thu, 13 Oct 2011 18:27:10 GMT

I have not done any testing with mount points. My understanding is that Microsoft recommend that you set up mount points to hold all the contents of a folder. This would mean that if you have folders E:\SQLFiles\Data and E:\SQLFiles\Log you could have a mount point to take everything that is put into E:\SQLFiles\Data and another mount point to take everything that is put in E:\SQLFiles\Log.

You can get FineBuild to create your folder structure and then stop so that you can set up your mount point. You can then restart FineBuild to carry on with the install.

To get FineBuild to stop after creating the folders, add a parameter /stopat:1z. When you restart FineBuild, remove the /stopat parameter and add a parameter /restart:auto.

If you can think of a way to supply mount point information as some new FineBuild parameters please let me know, and I will add it to a future version of FineBuild.

New Post: Installation using Mount Points

csorgenfrie — Thu, 13 Oct 2011 02:28:24 GMT

Reading through the documentation I see you can configure different drive letters for using the /drv parameter. We use a single mount point with individual LUN\Folders attached to the single drive letter. Is there anyway to configure the /drv:E\DATA so that it will use the DATA folder to do the installs inside of?

New Post: Install media and FineBuild scripts

edvassie — Fri, 09 Sep 2011 14:41:53 GMT

Hi Ajith,

FineBuild v3.0.0 documents a new way to set up the install media that exploits the parameters you asked for. One of the impacts is that it is now possible to get the Microsoft install media direct from the DVD drive. Thanks for making your suggestion, I think it has helped improve FineBuild.

New Post: SQLAccount

edvassie — Fri, 09 Sep 2011 14:33:40 GMT

FineBuild V3.0.0 should fix these problems. If you use /GroupDBA:"" then FineBuild will default to using the local Administrators group.

New Post: SQLAccount

bolivartech — Wed, 31 Aug 2011 21:41:58 GMT

I'm installing the 64-bit version on a 64-bit OS. I did comment out the calls to ResetDBARegPerm though to move on. Still having issues in other scripts, seems like anything that makes a call to the registry is having a problem.

I'm getting closer though, and even with errors I can get it to install and update to SP4 and can log in. So that's really all I'm going for.

New Post: SQLAccount

EdVassie — Wed, 31 Aug 2011 18:25:44 GMT

Are you installing a 32-bit version of SQL Server on a 64-bit OS? If so then FineBuild is using the wrong registry key, just delete the call to ResetDBARegPerm.

New Post: SQLAccount

bolivartech — Tue, 30 Aug 2011 13:05:17 GMT

Well turning off the UAC did not resolve the error I am getting. I will take a look to see what is happening in the script at that point and if I figure it out I will relay that back here.