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?
Thanks
Lystra
Hello Everyone,
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!!!
Can anyone help me with this?
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?
View 1 Replies View RelatedI 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
View 3 Replies View Related
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)
INSTALLSQLDIR="D:Program FilesMicrosoft SQL Server"
And then using command prompt I did the following:
"start /wait setup.exe /qn myini.ini"
and it still doesn't work.
Am using Windows Server 2008R2,In this Server C:/ drive space is getting increase day by day as per my knowledge i have to format that system.If is there any other chances to get space and remove unwanted things from my Server.
View 7 Replies View RelatedI got a space issue on F drive
Total drive capacity 581 GB
Now free space is 4.4 GB ONLY
F:MSSQLDATA..NDF---163072128(163 GB)
F:MSSQLDATA...MDF--441785344(441 GB)
I am trying to shrink the database to get some free space on F: drive but "USSVC_LADadmin" is executing delete statement on this database. so I could not perform any activity at this time
Please suggest how to proceed further?
Hey - I know that I can find space information about SQL Server. Allocated space, free space, used space, data space, etc... BUT is there a way that I can query how much total/available space is on the actual drive? For example, let's say that I have SQL installed on the D drive of a Server; i also have another application on that drive. I know that I can query how much room SQL Server is using, but can i query how much total/available space is on the drive? Any help appreciated.
View 1 Replies View RelatedI'm running a security application that generates a lot of events. I have gone in over the past couple days and deleted large numbers of old events in an effort to reclaim space on the D: drive where the SQL DB for this app resides. I did this throught the app itself... through its GUI front end.
I'm not having any impact. There is not a file on the same drive where the deleted events are being directed to. If all these events are going away, why does my used space on the drive not shrink? I came at it from another tack, creating sql queries to delete old events from the same app. I did this through queries in the SQL mgmt studio. The tasks (multiple) completed successfully, and the report on the # of rows 'affected' showed that it was a substantial number. No decrease in the windows drive space being used. Any tips?
I have a SQL 2005 server I am working on for a client and the issue is this. The original install was put on the servers c: partition. When they ran out of space they moved all of the databases to a different drive. They still run into problems when they run maintenance plans. Half of them fail as drive c: runs out of space.
Is there a temp directory or file that needs to be moved and if so how do I do this? Do SQL system databases grow when a maintenance plan is run? Do the system databases need to be moved as well? I assume that these changes will require down time but I would like to avoid that if possible.
I am new to SQL and I have looked everywhere but have found no solutions. I would think there must be a temp directory where data is stored during the job.
Any help would be appreciated. Thanks.
Steve
Hello all
as indicated by my stupid question, I am very new to sql. our vrsion is 2000 and I'm talking about in enterprise manager, the database that was created is not showing up in the list of db. Although I can see the file in explorer.
The problem I€™m having is when I try to attach the database €œmailarchive3Q2007_data.mdf€? it is also looking for the log file €œmailarchive3Q2007_log.ldf€? . The log file was removed by someone else off our system. I have a backup of the file but it is too large to restore now (160 gig) when the system was first set up the recovery model was not set to simple so the log just grew till it filled up our drive. I no longer have the drive space necessary to restore the log file and shrink it. So what do I do now? I need some kind of €œmailarchive3Q2007_log.ldf€? file to attach the database in enterprise manager.
Hope sombody can help.
thanks
Mike
In our SQL Server database we will have a table that will be populated with about 2000 recordsper day. That is 2000 records per day for 5 days per week. Currently the computer we are using has about 50 gigabytesof available hard drive space on it. We are concerned that maybe we will need a bigger hard drive,based solely on the number of records entered into this table per day. The problem is I don'tknow how to calculate how much hard drive space we need. I think I read that using varchar,sql server 2005 really optimizes a database. Here is a typical example of data in ourdatabase. I put dots on three lines between the first and last sample record to justillustrate that there are many records in between.
Basically we only need 8 months of data at a time in the table and then we can purgerecords older than 8 months.Can someone help me approximate how much hard drive space I might need for 8 months of data,given the following sample record in the database?
Sample: -->34.5 4.08 10.6 .0012
Sample Table in my DB just for illustration:
(PPsquare inch) (Diameter) (Weight gm) (coeffOfSatFriction)
34.5 4.08 10.6 .0012...21.7 3.54 6.22 .019
I am amazed to see this morning that log file consuming whole disk space even though the database is in simple recovery mode.
What could be the reasons to fill in the space even in simple recovery mode??
I have a database which has log file size 300 GB. As the drive is filling up i need to clear the space on the drive, for that i have to shrink the log file.Â
Unfortunately i dont have option to take backup of the database.And i am not able to shrink the file now. Is there any way to shrink the log file with out taking backup of it ?
Is it possible to find out available free space from a mounted / network drive using tsql query? I am using sql server 2008 R2.
View 5 Replies View RelatedWe 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.
Thanks.
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?
View 3 Replies View RelatedWhen I ran the install for MSDE, it installed the DB server and the databases onto my C: drive and under program files...
The instructions I followed were listed here:
http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1
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?
Thanks,
LD.....
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.
Thank you all very much
Merry Christmas!
Hi,
View 12 Replies View RelatedMicrosoft says that a single PC upgrade needs "one and one-half times the amount of disk space in use by the SQL Server 6.x databases."
Can anyone tell me if "space in use" is allocated db space, or space actually used by the db through data and logs? I'd rather not go through a manual database shrink for each of our dbs to be converted to 7.0 unless there is really a need. We have several production dbs with a lot of room to grow that I would need to shrink if the answer is that we need to have 1.5 times the allocated db space.
Thanks for nay help or experiences with this topic.
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?
Thanks,
Rick
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.
Hi
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.
Has anyone run into this?
How do you compare SAN drive vs local drive on a 32 bit server?
Is it good idea to move my DB files to a SAN instead of local?
Canada DBA
Server: SQL 2008 R2
 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
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
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform
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). :(
The error I got is:
Hotfix.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
EventType : sqlsesetup P1 : sysdbupg.sql P2 : 0x7361
P3 : odbcstatement__execute_batch@sysdbupg.sql@3 P4 : 0x7361
P5 : lib_odbc_statement.h@91 P6 : unknown P7 : sql9 P8 : hotfix@
P9 : x86 P10 : 3042
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.
Thanks a lot,
Rex
I have never installed sql server before and I didnt know if I just take the sql server 2005 standard edition media and boot off it and do a fresh install that way or do I have to install Windows server
View 3 Replies View RelatedHi,
I am trying to do this:
UPDATE Users SET uniqueurl = replaceAllEmptySpacesInUniqueURL('uniqueurl')
What would be the syntax.
Any help appreciated.
Thanks
I am generating a Report from Sql Data Source in Sql Server 2005 and viewing the Report in Report viewer control of Visual Studio 2005.
The data in the Data Source contains string with multiple spaces (for example €œ Test String €œ) but when they get rendered in Report viewer control, multiple spaces gets converted to single space €? Test String €œ.
I tried following solutions
1) Replacing spaces with €œ €?
2) Inserting <pre> tag before the string and </pre> tag after the string (Also tried <Pre> instead of <pre>)
But in all the cases result is same. The Report Viewer control is showing €œ €? instead of space and €œ<Pre>€? tag instead of preserving spaces.
Please provide me a solution so that spaces can be preserved in Report Viewer.