We are currently having a "lively" discussion between our DBAs and Server Builders and I am interested in what others are doing. Our DBAs want to take the default SQL install into the C: drive, making sure that NO logs are written to C:. That way there is no chance for the C: drive to become full, crashing the box. Server guys are insisting that we install to a drive other than C:.
I would appreciate any discussion re: what others consider best practice , industry standard, if such a things esist.
Is there a way to install SQL 2005 Express on a different drive? The server that I want to use has 700MB availible on the C drive and 80 GB availible on the D drive. can I install SQL and all tools on the D drive?
I'd like to be able to install it to my D: drive. I've looked through all of the docs but I can't find any information on how to change the install path. Would anyone know how to do this?
We have purchased a new Server at my company. We previously had two servers. One was the NT file server and then we had another SQL Server. Well, we've bought one box to replace both old boxes. I have 3 18.2 GB SCSI drives running on a RAID-5 configuration. I've partitioned the C: drive as 2GB and it will only be used for NT files and NT Utility apps.
On the old system I had all my data files on one physical drive and all of my logs on a seperate physical drive. Now, with RAID, the three drives act like one big 36GB drive. Finally, my question...
How should I partition this drive? Should I put the SQL Server App, my data files and my logs all on one partition? Should they each have their own partition? Should it be a mix (App & Log, Data & Log, etc.). Also, how much space do I need just for the application if I put it in its own partition?
I've never installed SQL Server before, so if anyone has any other suggestions, tips, tricks, etc., I'd love to hear it. Either post here or e-mail me responses.
I wasn't able to find the answer to my question by searching the forum. I would very much appreciate if anyone would help me.
I need to install the SQL Server Workgroup trial. I wasn't able to find the workgroup trial so I was trying to install the enterprise instead. (If anyone knows how to get ahold of the workgroup trial that would be a help too)
I keep getting the following error when running the SQLEval.exe:
There is not enough space on drive C: to extract this package
I did an internet search on this error and it seems there is a bug that requires the amount of free space not be a multiple of 4. I currently have 13.2 GB free space and I have tried adding and removing files, to no avail. I have tried downloading the file in a few different versions in case the file was corrupted, and rebooting etc, but still I keep getting the same message. I only have one drive!!!
I created two partitions for my hard drive. The C drive which holds all of the Windows 2003 server operating system files and E drive which will be just for data and applications. The C drive is only 30GB while the E drive is 119GB. I need to be able to install in the application on the E drive. I already tried creating a folder on the E partition named program files with the sql2005 folder in it when I go through the installer package. SQL server still wants to be installed on the C drive. Is there anyway I can change this so it gets installed on the E partition. Thank You
I am trying to install the SQL Sever 2005 Workgroup Edition software that came with our Small Business Server 2003 R2 system. I would like to install to the d: drive because space on the c: drive is limited. Can I do that? If so, how?
I created two partitions for my hard drive. The C drive which holds all of the Windows 2003 server operating system files and E drive which will be just for data and applications. The C drive is only 30GB while the E drive is 119GB. I need to be able to install in the application on the E drive. I already tried creating a folder on the E partition named program files with the sql2005 folder in it when I go through the installer package. SQL server still wants to be installed on the C drive. Is there anyway I can change this so it gets installed on the E partition. Thank You
On the drive that SQL server is install on which is the C drive the amount of space is 495mb, can the amount of space be a potential problem, I am so used to looking at the drives that contains the data and log files and the backup.
So My question is should I also concern myself with the drive the sql server itself is installed on?
I am trying to install SQL Server 2005 Express Edition onto my PC on the D: drive. I do not have write privelleges to the C Drive. All I want to do is point the executable to install to another drive like D: or E: etc. Is this possible with SQL Server 2005 Express Edition setup executable file.
Just to let you know I have changed the template.ini file in the source folder to reflect the following (I tried both with and without quotes)
I have been trying to use openrowset with a shared drive, and even though the share has "full control" permissions granted to "everyone" and the accout that SQL runs under has been granted explicit full control permissions I am unable to open the file which itself has no security on it.
Can I not use a \ path and only use mapped drives?
Thanks
below works...
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=C:5People.xls', [Sheet1$])
below doesn't work...
SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0','Excel 8.0;Database=\cluster02FileManager5People.xls', [Sheet1$])
I am trying to move a log file from one drive to another.
What I have done is add another file to my file group. So now my log has a file on the 'e' drive and one on the 'f' drive. I now want to remove the file on the 'e' drive. I have emptied the file on the 'e' drive. When doing the command:
ALTER DATABASE Uniprodruntime REMOVE FILE m_rk_runtime_log
I get the following error message..
Server: Msg 5020, Level 16, State 1, Line 1 The primary data or log file cannot be removed from a database.
I have also gone into enterprise manager and tried to delete the file and it does nothing.
 1: TempDB keeps getting filled.  Restart of the server has not fixed it. I shrink it, but the space gets filled again. Now I can't even shrink it anymore 2: TempDB is at the wrong location. Its current location is this :C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLPROD6MSSQLDATA empdb
How do I change its location?Â
C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLPROD6MSSQLDATA empdb Correct location of TempDB should be: TempDB(T:) But its not there
Being a very novice SQL Server administrator, I need to ask the experts a question.
How do I go about moving a database from 1 drive to another? The source drive (C is local to the server, but the target drive (E is on a Storage Area Network (SAN), although it is still a local drive for the server. I want to move the database from C: to E:. Can someone provide me with instructions?
How to backup half of dbs from a server on C drive and the other half on D drive and vice versa, first half on D drive and other half On C drive using only one job and one stored procedure??
Using scheduling from job add 2 schedules to the job so first schedule backup first half to C and second half to D , the second schedule backup first half to D and second half to D.
I am currently running Windows XP Professional Service Pack2. It already has MSDE & SQL Server 2000 installed (although I just uninstalled MSDE in the vain hope that it might present the installer with a more straightforward upgrade).
I have tried installing with the default instance & a new instance (I don't really care - I just need to install the darn thing). I just want the basic database & Books On-line, nothing fancy.
Here is the Summary log, for what it's worth:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Tue Feb 06 16:45:14 2007
Machine : ANTHONYY1 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server Native Client Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : MSXML 6.0 Parser (KB927977) Product Version : 6.00.3890.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server Native Client Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BOL_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : MSXML 6.0 Parser (KB927977) Product Version : 6.00.3890.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : SQLXML4 Error : Setup is preparing to continue with the installation. --------------------------------------------------------------------------------
Here is the SQLSetup0011_ANTHONYY1_Core(Local).log
Microsoft SQL Server 2005 Setup beginning at Tue Feb 06 16:45:14 2007 Process ID : 2560 C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2007/1/6 16:45:14 Complete: LoadResourcesAction at: 2007/1/6 16:45:14, returned true Running: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14, returned true Running: ValidateWinNTAction at: 2007/1/6 16:45:14 Complete: ValidateWinNTAction at: 2007/1/6 16:45:14, returned true Running: ValidateMinOSAction at: 2007/1/6 16:45:14 Complete: ValidateMinOSAction at: 2007/1/6 16:45:14, returned true Running: PerformSCCAction at: 2007/1/6 16:45:14 Complete: PerformSCCAction at: 2007/1/6 16:45:14, returned true Running: ActivateLoggingAction at: 2007/1/6 16:45:14 Complete: ActivateLoggingAction at: 2007/1/6 16:45:14, returned true Running: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14 Complete: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__2560" returned false. Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions: Condition "Setup is running locally." returned true. Running: PerformDotNetCheck2 at: 2007/1/6 16:45:14 Complete: PerformDotNetCheck2 at: 2007/1/6 16:45:14, returned true Running: InvokeSqlSetupDllAction at: 2007/1/6 16:45:14 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0 <Func Name='DwLaunchMsiExec'> Examining 'sqlspars' globals to initialize 'SetupStateScope' Opening 'MachineConfigScope' for [ANTHONYY1] Trying to find Product Code from command line or passed transform If possible, determine install id and type Trying to find Instance Name from command line. No Instance Name provided on the command line If possible, determine action Machine = ANTHONYY1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceReadRegWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = XMLDomDocument, Result = 0 (0x0) Machine = ANTHONYY1, Article = Processor, Result = 0 (0x0) Machine = ANTHONYY1, Article = PhysicalMemory, Result = 0 (0x0) Machine = ANTHONYY1, Article = DiskFreeSpace, Result = 0 (0x0) Machine = ANTHONYY1, Article = OSVersion, Result = 0 (0x0) Machine = ANTHONYY1, Article = OSServicePack, Result = 0 (0x0) Machine = ANTHONYY1, Article = OSType, Result = 0 (0x0) Machine = ANTHONYY1, Article = iisDep, Result = 0 (0x0) Machine = ANTHONYY1, Article = AdminShare, Result = 0 (0x0) Machine = ANTHONYY1, Article = PendingReboot, Result = 70011 (0x1117b) Machine = ANTHONYY1, Article = PerfMon, Result = 0 (0x0) Machine = ANTHONYY1, Article = IEVersion, Result = 0 (0x0) Machine = ANTHONYY1, Article = DriveWriteAccess, Result = 0 (0x0) Machine = ANTHONYY1, Article = COMPlus, Result = 0 (0x0) Machine = ANTHONYY1, Article = ASPNETVersionRegistration, Result = 0 (0x0) Machine = ANTHONYY1, Article = MDAC25Version, Result = 0 (0x0) ******************************************* Setup Consistency Check Report for Machine: ANTHONYY1 ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: CheckPassed Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 0 <EndFunc Name='PerformDetections' Return='0' GetLastError='0'> <Func Name='DisplaySCCWizard'> CSetupBootstrapWizard returned 1 <EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'> Failed to find help file for LCID :2057 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 <EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'> Complete: InvokeSqlSetupDllAction at: 2007/1/6 16:49:35, returned true Running: SetPackageInstallStateAction at: 2007/1/6 16:49:35 Complete: SetPackageInstallStateAction at: 2007/1/6 16:49:36, returned true Running: DeterminePackageTransformsAction at: 2007/1/6 16:49:36 Complete: DeterminePackageTransformsAction at: 2007/1/6 16:49:47, returned true Running: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47 Complete: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47, returned true Running: OpenPipeAction at: 2007/1/6 16:49:47 Complete: OpenPipeAction at: 2007/1/6 16:49:47, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2007/1/6 16:49:47 Complete: CreatePipeAction at: 2007/1/6 16:49:47, returned false Error: Action "CreatePipeAction" failed during execution. Action "RunRemoteSetupAction" will be skipped due to the following restrictions: Condition "Action: CreatePipeAction has finished and passed." returned false. Running: PopulateMutatorDbAction at: 2007/1/6 16:49:47 Complete: PopulateMutatorDbAction at: 2007/1/6 16:49:47, returned true Running: GenerateRequestsAction at: 2007/1/6 16:49:47 SQL_Engine = 3 SQL_Data_Files = 3 SQL_Replication = 3 SQL_FullText = 3 SQL_SharedTools = 3 SQL_BC_DEP = 3 Analysis_Server = -1 AnalysisDataFiles = -1 AnalysisSharedTools = -1 RS_Server = -1 RS_Web_Interface = -1 RS_SharedTools = -1 Notification_Services = -1 NS_Engine = -1 NS_Client = -1 SQL_DTS = -1 Client_Components = 3 Connectivity = 3 SQL_Tools90 = 3 SQL_WarehouseDevWorkbench = 3 SDK = 3 SQLXML = 3 Tools_Legacy = 3 TOOLS_BC_DEP = 3 SQL_Documentation = 3 SQL_BooksOnline = 3 SQL_DatabaseSamples = -1 SQL_AdventureWorksSamples = -1 SQL_AdventureWorksDWSamples = -1 SQL_AdventureWorksASSamples = -1 SQL_Samples = -1 Complete: GenerateRequestsAction at: 2007/1/6 16:49:48, returned true Running: CreateProgressWindowAction at: 2007/1/6 16:49:48 Complete: CreateProgressWindowAction at: 2007/1/6 16:49:48, returned true Running: ScheduleActionAction at: 2007/1/6 16:49:48 Complete: ScheduleActionAction at: 2007/1/6 16:49:48, returned true Skipped: InstallASAction.11 Skipped: Action "InstallASAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.18 Skipped: Action "InstallASAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.22 Skipped: Action "InstallASAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.9 Skipped: Action "InstallASAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result. Skipped: InstallDTSAction Skipped: Action "InstallDTSAction" was not run. Information reported during analysis: No install request found for package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.11 Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.12 Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.18 Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.22 Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.9 Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result. Skipped: InstallNSAction Skipped: Action "InstallNSAction" was not run. Information reported during analysis: No install request found for package: "ns", install will be skipped as a result. Skipped: InstallNSAction.11 Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.12 Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.18 Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.22 Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.9 Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result. Skipped: InstallRSAction.11 Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.18 Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.22 Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result. Running: InstallSqlAction.11 at: 2007/1/6 16:49:48 Installing: sqlsupport on target: ANTHONYY1 Complete: InstallSqlAction.11 at: 2007/1/6 16:49:51, returned true Running: InstallSqlAction.12 at: 2007/1/6 16:49:51 Installing: sqlncli on target: ANTHONYY1 Complete: InstallSqlAction.12 at: 2007/1/6 16:49:55, returned true Running: InstallSqlAction.18 at: 2007/1/6 16:49:55 Installing: owc11 on target: ANTHONYY1 Complete: InstallSqlAction.18 at: 2007/1/6 16:49:56, returned true Running: InstallSqlAction.21 at: 2007/1/6 16:49:56 Installing: sqlwriter on target: ANTHONYY1 Complete: InstallSqlAction.21 at: 2007/1/6 16:49:58, returned true Running: InstallSqlAction.22 at: 2007/1/6 16:49:58 Installing: bcRedist on target: ANTHONYY1 Complete: InstallSqlAction.22 at: 2007/1/6 16:50:0, returned true Running: InstallSqlAction.9 at: 2007/1/6 16:50:0 Installing: msxml6 on target: ANTHONYY1 Complete: InstallSqlAction.9 at: 2007/1/6 16:50:2, returned true Running: InstallToolsAction.11 at: 2007/1/6 16:50:2 Installing: sqlsupport on target: ANTHONYY1 Complete: InstallToolsAction.11 at: 2007/1/6 16:50:5, returned true Running: InstallToolsAction.12 at: 2007/1/6 16:50:5 Installing: sqlncli on target: ANTHONYY1 Complete: InstallToolsAction.12 at: 2007/1/6 16:50:8, returned true Skipped: InstallToolsAction.13 Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis: No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result. Running: InstallToolsAction.18 at: 2007/1/6 16:50:8 Installing: owc11 on target: ANTHONYY1 Complete: InstallToolsAction.18 at: 2007/1/6 16:50:10, returned true Running: InstallToolsAction.20 at: 2007/1/6 16:50:10 Installing: BOL on target: ANTHONYY1 Complete: InstallToolsAction.20 at: 2007/1/6 16:52:2, returned true Running: InstallToolsAction.22 at: 2007/1/6 16:52:2 Installing: bcRedist on target: ANTHONYY1 Complete: InstallToolsAction.22 at: 2007/1/6 16:52:4, returned true Running: InstallToolsAction.9 at: 2007/1/6 16:52:4 Installing: msxml6 on target: ANTHONYY1 Complete: InstallToolsAction.9 at: 2007/1/6 16:52:6, returned true Skipped: InstallNSAction.10 Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result. Running: InstallSqlAction at: 2007/1/6 16:52:7 Installing: sql on target: ANTHONYY1 Error: MsiOpenDatabase failed with 110 Failed to install package This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. Error: MsiOpenDatabase failed with 110 for MSI D:ServersSetupSqlRun_SQL.msi Setting package return code to: 1620 Complete: InstallSqlAction at: 2007/1/6 16:52:27, returned false Error: Action "InstallSqlAction" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Running: InstallToolsAction.10 at: 2007/1/6 16:52:27 Installing: sqlxml4 on target: ANTHONYY1 Error Code: 0x8007006e (110) Windows Error Text: The system cannot open the device or file specified.
Source File Name: sqlchainingminorbuildactionbehavior.cpp Compiler Timestamp: Mon Jun 13 14:30:04 2005 Function Name: sqls::MinorBuildActionBehavior::modifyRequest Source Line Number: 65
Complete: InstallToolsAction.10 at: 2007/1/6 16:55:59, returned false Error: Action "InstallToolsAction.10" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Action "InstallToolsAction" will return false due to the following preconditions: Condition "Action: InstallToolsAction.10 has finished and failed." returned true. Installation of package: "tools" failed due to a precondition. Step "InstallToolsAction" was not able to run. Skipped: InstallASAction Skipped: Action "InstallASAction" was not run. Information reported during analysis: No install request found for package: "as", install will be skipped as a result. Skipped: InstallRSAction Skipped: Action "InstallRSAction" was not run. Information reported during analysis: No install request found for package: "rs", install will be skipped as a result. Skipped: RepairForBackwardsCompatRedistAction Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis: Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run: Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchMSDE2000" failed due to a precondition. Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run: Action: "UninstallForSQLAction" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchLibertySql" failed due to a precondition. Skipped: UninstallForRS2000Action Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis: Action: "UninstallForRS2000Action" will be skipped due to the following condition: Condition "Action: InstallRSAction was skipped." returned true. Running: ReportChainingResults at: 2007/1/6 16:55:59 Error: Action "ReportChainingResults" threw an exception during execution. One or more packages failed to install. Refer to logs for error details. : 1620 Error Code: 0x80070654 (1620) Windows Error Text: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Thu Sep 1 22:23:05 2005 Function Name: sqls::ReportChainingResults::perform Source Line Number: 3097
---- Context ----------------------------------------------- sqls::HostSetupPackageInstallerSynch::postCommit sqls::HighlyAvailablePackage::preInstall led due to cancel code received from cancel source: 29539
...and here is the SQLSetup0011_ANTHONYY1_SQL.log:
=== Verbose logging started: 06/02/2007 16:52:14 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe === MSI (c) (00:54) [16:52:14:284]: Resetting cached policy values MSI (c) (00:54) [16:52:14:284]: Machine policy value 'Debug' is 0 MSI (c) (00:54) [16:52:14:284]: ******* RunEngine: ******* Product: D:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (c) (00:54) [16:52:14:284]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (00:54) [16:52:14:284]: Grabbed execution mutex. MSI (c) (00:54) [16:52:14:299]: Cloaking enabled. MSI (c) (00:54) [16:52:14:299]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (00:54) [16:52:14:299]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (A4:98) [16:52:14:299]: Grabbed execution mutex. MSI (s) (A4:00) [16:52:14:299]: Resetting cached policy values MSI (s) (A4:00) [16:52:14:299]: Machine policy value 'Debug' is 0 MSI (s) (A4:00) [16:52:14:299]: ******* RunEngine: ******* Product: D:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (s) (A4:00) [16:52:21:080]: Note: 1: 2203 2: D:ServersSetupSqlRun_SQL.msi 3: -2147024873 MSI (s) (A4:00) [16:52:21:080]: MainEngineThread is returning 1620 MSI (c) (00:54) [16:52:21:080]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (00:54) [16:52:21:080]: MainEngineThread is returning 1620 === Verbose logging stopped: 06/02/2007 16:52:21 ===
I suppose an error dialog (or log message) that actually told you what is wrong and then what to do is too much to ask for. (Or an installer than just copied all the files into place). :(
Log Location: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
I tried to search internet, however, I couldn't get solution.
My SQL server 2005 is standard version, OS Windows server 2003 sp2, I am using Administrator account to install it.
I have compile my application into a Smart Device CAB and also including SQLCE CAB file for SQL.
I have users who choose to install SQLCE into Storage Cards instead and causes the application not to function, when asked which destination to install.
I've done some search and found out about "wceload.exe /noaskdest" but I'm using NSIS to compile into a single .exe file, and its calling "CEAppMgr.exe"
How can I force SQLCE to install into its default directory without asking user?
Win XP Pro SP2IIS 5.1SQL 2005 SP1 (Developer edition)VS 2005 SP1.Net 2.0IE7 (didn't work on IE 6 either)Latest updates from Windows updateI have set up SSRS successfully on several machines. But on a new machine with standard install I have the out of the box SSRS report manager running with issues and would like to resolve them. Report Manager will serve image files from my project. But it won't render deployed reports, not even one which has no data sources. From within VS 2005 the same reports render, no problems. The same reports published to another SSRS machine render fine.The browser erorr message is "Value does no fall within the expected range".Any ideas? Thanks in advance.
Hi,Is it possible to install Enterprise Manager without to install theserver ?Thanks !--J-L M. (Alphomega)ICQ: 149635116Pour m'écrire, cliquer le lien ci-dessoushttp://cerbermail.com/?G5iYdBb2Ce
I've tried looking for a solution in other threads but I couldn't find anything that was completely the same as my situation. I got a new pc at work and I've tried installing SQL Server 2005 on it but everytime I try to install it, regardless of services included or excluded with the install, I cannot get through the install without this error. Below is the excerpt from the Summary.txt log file.
Error Code: -2147024894 MSI (s) (74!98) [17:10:55:858]: Product: Microsoft SQL Server 2005 Tools -- Error 29549. Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Error 29549. Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='203'> Doing Action: Do_sqlAssemblyRegSvcs PerfTime Start: Do_sqlAssemblyRegSvcs : Mon Nov 12 17:10:55 2007 <Func Name='Do_sqlAssemblyRegSvcs'> Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: 2147942402 Error message: The system cannot find the file specified. Error descrition: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Error Code: -2147024894 Windows Error Text: The system cannot find the file specified. Source File Name: sqlcasqlassembly.cpp Compiler Timestamp: Thu Aug 11 01:12:01 2005 Function Name: Do_sqlAssemblyRegSvcs Source Line Number: 155
I've searched for and found similar problems that deal with the microsoft.sqlserver.notificationservices.dll not being found but I haven't found a fix that worked for me. These are the fixes I've refered to thus far.
The answer that seems to fix this problem for everyone is to set the MSDTC service login as the NT AUTHORITYNetworkService account. The problem for me is that this is already set to this profile and I've tried resetting the services and rebooting the machine. I did not have a problem with my old machine, which as far as I can tell, is the same configuration, so I know this install should work.
I'm running Windows XP SP2. This is not the upgrade to SQL Server 2005 SP2, this is the original disk that came with Visual Studio 2005.
Has anyone else faced this issue where changing the MSDTC login wasn't the solution? Also, this is my first post, so I apologize if I've left anything out. Just let me know if you want any other information.
I never installed previous beta versions on my computer before. But now I have some serious problem after an incomplete de-install and a re-install of SQL server 2005 express advanced. I hope anybody can help me to solve this. Because the first installation eas not succesfull I had to do an de-install. I have tried to unstall through start/control panel/ add-remove programms and even there not all programs were removed. And that caused the problem. After that I wanted to re-install again but an msi file was missing. So I did a de-install agian. Tried to re-install again but with a lot of errors. After looking at the library I found a program: Windows Install CleanUp. I installed it and that even gives an error for all programs installed with SQL 2005. After that I ran a program called MsiInv to clean but without any succes because this program reported a run-tim error. I have all reports on my computer but don't know how to attach them. If you think you can help me I could send you all the reports. Regards,
I am installing the X86 Executable version of SQL Server. I copied it to my desktop and clicked RUN. It extracts the files and then the Install Wizard tells me there is not enough space on the C Drive to load the program. I have 23 gigabits of free space and the program only takes about 900 megabits.
Hi I have a database(CEB) and my CEB.mdf is on D Drive and CEB.LDF is on G DRIVE ...NOw I want to move the CEB.LDF on to the different drive .. can any one suggest me the way and will I have any effect on the database. It is kind of urgent.
I have a shared drive mapped to the h: drive letter on my sql server and I want to create new databases on that drive. Is this at all possible? I try it and I couldn't see h: even if I typed it in.
What problems will I get if the hard drive for the transaction logs becomes defective? Will this affect transactions and/or backup? What should I do to fix this problem?
In reading material on the quorum drive on a sql server cluster in mentions this is the drive the logs are written to. Is this referring to sql log files that are dumped by a process or scheduled job, or some other log files?
