Hello,
if I do a unattended installation using this command
setup.exe /qb ADDLOCAL=Client_Components,Tools_Legacy,Connectivity SECURITYMODE=SQL SAPWD=xxx INSTALLSQLDATADIR=C:\
sqldmo.dll is not installed, although "Tools_Legacy" should do this.
What am I doing wrong
SQL Server 2005 Installation does not install sqldmo.dll
BillW
Saratoga
I have a few questions for you:
1) What platform are you installing on (e.g. a 32-bit OS or a 64-Bit OS)
2) Why do you think that sqldmo.dll is not installed (e.g. you searched the entire drive for it and couldn't find it)
Based on your install string, sqldmo.dll will be installed under C:\Program Files\Microsoft SQL Server\80\Tools\binn
3) If you go to the Control Panel and launch "Add or Remove Programs" do you see an entry titled: "Microsoft SQL Server 2005 Backward compatibility"
Cheers,
Dan
Billaboard
Alias
You need to check out the log file for the backward compat installation. Look for %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\SQLSetup####_*_BackwardsCompat_#.log. Open the log file in notepad and search for "Value 3" - this is a Windows Installer return code. 10 lines above and below this entry should give you some clue as to why the installation failed. If you can't determine the failure, go ahead and post the snippet from the log file.
Cheers,
Dan
MRMIKE
1) Windows XP with SP 2, 32 Bit. I'm trying to install the Standard Edition of SQLServer 2005 (German).
2) Yes I searched the entire drive.
In the meantime I have tried a clean installation with only
setup /qb ADDLOCAL=Tools_Legacy
Afterwards I find in "C:\Program Files\Microsoft SQL Server\80\Tools\binn" only some ATL-, MFC- and MSVC-DLLs.
3) No, only "Microsoft SQL Server 2005" and "Microsoft SQL Server Native Client".
mik_mihai
Well, I now have tried it with
setup.exe /qb ADDLOCAL=Client_Components,Tools_Legacy,TOOLS_BC_DEP
and it works! sqldmo.dll is there!
I really, really hate these incomplete Microsoft documentations!!!
Athan
Go ahead an zip up the log file directory and send it to me. If it turns out to be a real problem, rather than an anomoly, I'll file a bug.
Cheers,
Dan
dan.jones@microsoft.com
tomatgdd
Hello Dan,
there is no such file in this directory. I only have these files:
808.570 sqlsetup0001_psctest_.net framework 2.0 langpack.log
4.605.940 sqlsetup0001_psctest_.net framework 2.0.log
17.397 SQLSetup0001_PSCTEST_Core(Local).log
2.158 SQLSetup0001_PSCTEST_Core.log
40.533 SQLSetup0001_PSCTEST_SCC.log
285.120 SQLSetup0001_PSCTEST_SNAC.log
210.124 SQLSetup0001_PSCTEST_SQLNCLI_1.log
382.330 SQLSetup0001_PSCTEST_SQLSupport_1.log
915.448 SQLSetup0001_PSCTEST_Support.log
10.697.696 SQLSetup0001_PSCTEST_Tools.log
If I install it manually I get these additional files:
1.771.448 SQLSetup0001_PSCTEST_BackwardsCompat_1.log
894.946 SQLSetup0001_PSCTEST_OWC11_1.log
2.616.342 SQLSetup0001_PSCTEST_WI.log
I found some differences in "SQLSetup0001_PSCTEST_Core(Local).log" between unattended and manual installation (output of diff):
78a79,81
> <Func Name='DisplaySCCWizard'>
> CSetupBootstrapWizard returned 1
> <EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
115c118
< Client_Components = -1
---
> Client_Components = 3
122c125
< TOOLS_BC_DEP = -1
---
> TOOLS_BC_DEP = 3
222,224c225,227
< Skipped: InstallToolsAction.18
< Skipped: Action "InstallToolsAction.18" was not run. Information reported during analysis:
< No install request found for package: "owc11", referred by package: "tools", install will be skipped as a result.
---
> Running: InstallToolsAction.18 at: 2006/0/26 9:44:8
> Installing: owc11 on target: PSCTEST
> Complete: InstallToolsAction.18 at: 2006/0/26 9:44:22, returned true
228,230c231,233
< Skipped: InstallToolsAction.22
< Skipped: Action "InstallToolsAction.22" was not run. Information reported during analysis:
< No install request found for package: "bcRedist", referred by package: "tools", install will be skipped as a result.
---
> Running: InstallToolsAction.22 at: 2006/0/26 9:44:22
> Installing: bcRedist on target: PSCTEST
> Complete: InstallToolsAction.22 at: 2006/0/26 9:44:53, returned true
May this be the reason Do I have to add the undocumented "TOOLS_BC_DEP" to ADDLOCAL
Utsav Kedia
Oops; I was sure that I had tried that also without success.
O.K., it works here. Thank you.
Priyanga Karunathilake