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 RepliesI made an analysis services project but I can't deploy it because it can't find the server
I search for the analysis service in the Service Control Manager but I can't find it.
Is it possible to download and install it with this version of sql server (workgroup) ?
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 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.
I have a VERY Legitmate use to install sql 4 workgroups on a pc without licensing it. I am making a disk image for MANY pcs to be imaged and load licensing after the imaging is completed.
I have been able to do this with Windows XP Professional, MS Office 2003 and a couple non-Ms programs. The information for MS software even came from their KB, so I know what I am doing is legit. I just can't find any information on doing this for my sql app.
Any suggestions??
Respectfully,
Frustrated
"Frustrated"
Hi,
View 12 Replies View RelatedI am using SQL Server 2005 Express Edition. I am planning on upgrading to either Workgroup or Standard edition. While working with Express Edition I did find out that this version does not support backup to a network drive.
My question is:
Is it possible to backup directly to a network drive using a Workgroup/ Standard edition of SQL Server rather than backing up to a local drive and then 'copy and paste' to a network drive like the Express Edition.My other question is :
Given a database limit of 50GB, which one of the editions, Workgroup or Standard, will be appropriate for use.Thank you for your time and patience.
Regards
Berly Sam
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
HI All,
After i installed SQL Server 2005 workgroups edition to my Laptop, P4 and 1 Giga memory. I had a problem.
my problem is: when i start my laptop need 4 minutes to start the windows xp pro edition.
then I format my laptop and install the windows again, and every thing works fine, but I installed the SQL again and i had same problem with windows startup, there is nothing related to SQL in ;msconfig utilities.
do you have any tip about this problem ?
Thank You
Good day,
We have developed an application using VS 2005 and SQL Server 2005 Developer Edition.
Currently, our client is asking if they could buy the SQL Server 2005 Workgroup Edition.
Is it ok? I'm afraid that the SP we made using CLR and any other functionality might not work.
We are suggesting our client to use the SQL Server 2005 Standard Edition instead. But for them to save money, can they use the Workgroup Edition instead?
I would really appreciate your help.
Thanks and more power,
Arthur
Hi all,
I am trying to install the workgroup edition on Windows SBS 2003 R2. After the removal of an unwanted
SQL Express Edition installation - the standard install of SQL 2005 from CD hangs during setup.
In the log file _WI.log is:
...
MSI (s) (B0:2C) [23:01:14:968]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (B0:2C) [23:01:14:968]: MsiProvideAssembly is returning: 1607
MSI (s) (B0:2C) [23:01:14:968]: No System Restore sequence number for this installation.
MSI (s) (B0:2C) [23:01:14:968]: Unlocking Server
MSI (s) (B0:2C) [23:01:14:968]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (B0:2C) [23:01:15:015]: MainEngineThread is returning 1603
MSI (s) (B0:A0) [23:01:15:109]: Destroying RemoteAPI object.
MSI (s) (B0:80) [23:01:15:109]: Custom Action Manager thread ending.
MSI (c) (B4:54) [23:01:15:125]: Back from server. Return value: 1603
MSI (c) (B4:54) [23:01:15:125]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B4:54) [23:01:15:125]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'.
Aktion beendet um 23:01:15: ExecuteAction. Rückgabewert 3.
MSI (c) (B4:54) [23:01:15:125]: Skipping action: FatalError (condition is false)
Aktion beendet um 23:01:15: INSTALL. Rückgabewert 3.
Any advice would be great!
THufschmidt
Can any one tell me what I should do with following error :
I'm working with sql server 2005 workgroup and I installed SP2.
When I make a maintenance plan voor backup the databases (full) then at the end I got the following error !
save maintenance plan failed
One or more arguments are invalid.
I red this problem already on forums but I didn't get it resolved.
When I use sql server 2005 developer It worked fine !
Geert
i have SQL Server 2005 Workgroup Edition
how to connect to it from vb.net 2005 because i try but no use
thanks in advance.
Hi
I've recently gone through installing and setting up merge replication on Server 2005 Standard. All working.
I am now setting up a different box with SQL 2005 Workgroup with SP2. When I go to the Replication tab in Management Studio there is only Local Subscriptions - No Local Publications.
I've re-run the installation but I can't see how Publications is not getting installed orwhy it is missing.
Any ideas much appreciated.
Thanks
Alistair
Does SQL Server 2005 Workgroup Edition have a limit to the number of user logins I can make?
View 1 Replies View RelatedHi,
I am new to SQL Server and I am trying to install SQL Server 2005 Express or Stnadard Edition on a computer runing XP pro on a XP's workgroup network using a router. Can I access the the database from another computer running XP pro on the same network? If I can, what setting do I need when installing SQL 2005 in order to do this?
Any help is appricated.
We have only a small busines and haven't got too much experience with servers and now have a proliant server coming in with SBS 2003 R2 Premium with the 4 GB max memory that SBS 2003 can handle according to the specs.
We weren't planning on using the SQL 2005 worlgroup edition up till now, but now we might. According to the specs of SQL server 2005 workgroup edition however, it has a max RAM of 3GB!
Is this going to be a problem and should we keep using our previous DB, or can we migrate toward SQL server with the 4 GB of RAM?
I have an SBS 2003 server that is running SQL 2000 standard edition which was recently upgraded to Small Business Server 2003 R2.
I have installed SQL 2005 workgroup edition on the SBS 2003 R2 server which acts both as an AD server and Exchange server. I installed SQL 2005 for the purpose of using SQL 2005 for my sharepoint services on the Small Business Server R2.
Now I have SQL 2000 and SQL 2005 workgroup edition installed, but I'm unsure whether I can uninstall the SQL 2000 and how to know whether the sharepoint instance is running in SQL 2005 or SQL 2000?
Additionally, I have some MSDE's running for WSUS and Server Reporting which are installed by the Small Business Server installation.
Which tools should I use to become familiar with identifying the databases and which version of the database engine is used for which database regardless of whether it is a SQL instance or a MSDE instance.
How can I identify which SQL versions are not in use and whether I can uninstall if not needed.
Thanks!!
In MSDE sql server 2000 dtsrun was available to execute the dts packages but now with sql server 2005 express edition integration service is not part of express/workgroup edition and the dtsexec run time is also not available.
View 6 Replies View RelatedI've heard that the Standard version supports the use of CommandNotification and that the Express version does not. What about the Workgroup edition?
The reason I'm asking is because there is a substantial monthly difference in cost between the two versions if I were to have my site hosted. I've been developing with MS SQL 2005 Express so obviously I have not tested this caching feature. Are command notifications reliable? On paper, it sounds impressive and extremely efficient especially if a site is to have heavy traffic and you can't afford the overhead of heavy database processing that is useless if the data is unchanged.
Does the Workgroup edition support automatic change notifications? Have automatic notifications been proven reliable and vastly more efficient than crude polling methods?
Thanks in advance.
Hi All,
A client of mine was using SQL Express and soon realised this doesn't meet his needs performance or database size wise. He also realised that SQL Server 2005 Workgroup came free with his R2 version of SBS.
So in essence, I have been trying to find the Microsoft recommended way to upgrade from Express to Workgroup. I have not been able to find a step-by-step guide and to add to my confusion, when I run the work-group installer it tells me to run the installer with a switch which I have gone ahead and done but when selecting components it has all of them defaulted to blanked out.
Surely the process for an in-place upgrade should not be so technical as I am finding it ? To my mind, the natural progression would be to upgrade express to a better capable version of 2005 and should be as easy as pie.
Anyway, I am basically looking for a step-by-step guide on how to upgrade to get it done right the first time as opposed to upgrading and than realised some remenants of Express are still larking about causing trouble.
Regards,
QS
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.
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!
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
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?
Why wont the installer for SQL Server let me install onto a drive other than the C drive? I am trying to install the Client tools only, but it insists on making me install to C. I need to install to a different drive for space reasons. I had SQL Server 2000 client installed, but I have since uninstalled it and tried the SQL 2005 install again and every time it wants to use the C drive.
If anyone knows a why to make this work I would greatly appreciate it.
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,
Jan J
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 RelatedTrying to install SQL Server 2005 beta version on partition disk drive sayF: (Other than local disk drive c:),Does anyone know how can I do this? During the installation, it never asksme on which drive it install to nor browse button is there to browse thedisk drive for installation...Any help???ThanksJ.
View 1 Replies View Related