I have sql server 2005 express and toolkits installed. However, I only see Report Server projects in my Visual Studio 2005 when I choose a Business Intelligence project.
Will someone please help me download the right file to start using SSIS designer?
Is it necessary to install SSRS and SSAS to see the designers in Visual Studio 2005? That would mean installing some parts of a SQL Server 2005 installation on my Vista SP1 machine, or just the BIDS.But i've tried the latter to no avail (it hangs), and the former doesn't make sense because i think the SQL engine would be needed, and doesn't that require a server OS? I'd just like to see the report and cube designers in VS2005. How do i do that? Does it have anything to do with running SQLServer setup? TIA!!
I have a script which grabs data from a source server. The problem is I have over 50 source servers, so I have to make a script for each one.. EXACTLY the same code but different linked server address.
So I was wondering if i can put the server name into a variable so I only need to make one script. Is that possible?
When I drop a new component onto the design surface, it appears with dotted lines around it, as it is selected.
But, the F2 key (the hotkey for rename) does not work.
I have to click on some other component, and then back on the new component, and then the F2 key works.
I remember reporting this bug back in the beta cycle, but it is still present even in the release -- I actually think Ã?'m using the SP1 version of 2005, but see version info below to be sure:
Remote terminal services broke my copy buffer again, as is so often does, so pasting in the version info failed -- falling back to manual typing -- SSIS 9.00.2047.00.
I am executing a single package that references 180 other packages , after executing the first 90-100 packages , SSIS designer completely freezes and then i have to kill the session using Task Manager . Is this a limitation of SSIS or is it a system constraint ?
If you have any suggestions or workarounds for de same plz do reply
When I installed SP1 on my SQL Server 2005, the performance of the package designer dropped enormously. I have to wait like 30 seconds after I drag-and-drop a datasource from the toolbox to the design area. Also it takes a very long time to run the very simple package. Not to mention opening some complicated package that was done before applying SP1. The package scheduled in SQL Agent went from 3-4min to 5-6min.
Can anyone address this issue? Maybe there's something I did wrong?
While installing SP1 I ecountered strange behaviour (some messages about file locking, rebooting and stuff), but in the end it said that it was successful
Our Visual Studio installation suddenly starting producing the error below upon trying to open any .dtsx package; although by "suddenly" I'm sure it was due to some Windows update or other program install, update, or uninstall. I've spent two days uninstalling, reinstalling, and repairing everything that is seemingly related to VS, but no luck. I've searched the forums and could not find this specific error mentioned, although I have tried some of the suggestions to fix possibly related 'class not registered' errors, but again no luck.
=================================== There was an error displaying the layout. (Microsoft Visual Studio) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.762&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=DDSErrorDeserializeDiagram&LinkId=20476 =================================== Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)) (msddsp) ------------------------------ Program Location: at MSDDS.IDdsDiagram.CreateShape(String ProgID, Boolean Visible, Int32 X, Int32 Y) at Microsoft.DataWarehouse.Controls.Interop.AxMSDDS.CreateShape(String progID, Boolean visible, Int32 x, Int32 y) at Microsoft.DataWarehouse.Design.ComponentDiagram.OnCreateShape(Object logicalObject, Int32 x, Int32 y, Boolean visible) at Microsoft.DataTransformationServices.Design.DtsComponentDiagram.OnCreateShape(Object component, Int32 x, Int32 y, Boolean visible) at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateShape(Object logicalObject, Int32 x, Int32 y) at Microsoft.DataTransformationServices.Design.DtrControlFlowDiagram.CreateExecutableShape(DtsContainer dtsContainer, Int32 x, Int32 y, Int32 width, Int32 height) at Microsoft.DataTransformationServices.Design.DtrControlFlowDiagram.RefreshSequenceExecutables(IDTSSequence sequence) at Microsoft.DataTransformationServices.Design.DtrControlFlowDiagram.AfterDeserialize()
If you try to "enable memory restriction" from the Lookup component GUI you need to input both 32 and 64 bit size of maximum memory. However when clicking "OK" on the editor you get a message like :
TITLE: Microsoft Visual Studio ------------------------------
Error at Update Execution Logs [Lookup folder path 1 [4429]]: Failed to set property "MaxMemoryUsage64" on "component "Lookup folder path 1" (4429)".
Ok, I am stumped. On a clean Windows Server 2003 machine we installed SQL Server 2005 Enterprise edition. We then installed all of the components, including BIDS. however, there is no option to start BIDS and I see devenv.exe does not exist.
Do I need VS installed in order to run BIDS and SSIS?
I have installed SQL Server 2005 but Integration Services is just not there. I have uninstalled and reinstalled several times and in the process uninstalled an old version of Visual Studio.NET (manually because it wouldn't uninstall automatically) and Visual Web Developer, just in case they were interfering with Integration Services. No luck, in fact it got worse, now Analysis Services also does not work because it can't find devenv.exe!
I have installed exactly this same software on another clean PC (ie. no previous Visual Studio variants on it) and it installs perfectly.
There seems to be some kind of clash between old versions of Visual Studio and SQL Server 2005 that prevents SQL Server from properly installing products like Integration Services that use the Visual Studio interface (ie. devenv.exe).
I now can't even reinstall the old version of Visual Studio.NET, and devenv.exe is nowhere to be found on my PC although it is referenced throughout the registry.
Has anyone got any suggestions, all I am after if a full and clean install of SQL Server 2005 so I can develop against it using Visual Web Developer.
I've gone through Add/Remove programs, and attempted to update SQL Server 2005 but cannot seem to find the correct components to add, and since I cannot see the SSIS name in my Services panel, i assume it hasn't been installed.
I note that I can install SSIS on a client box not just a server. What is the advantage (expect maybe if the client is a portable computer) to installing SSIS on a client box? I would normally expect to find it running on the server side of the house.
I have used above the DTSInstall.exe to Install my DTS Package in SQL Server 2005. An entry is created in the sysdtspackages90 table. 2 Questions: 1)Where in SQL Server 2005 should I be able to see the Package itself? If I look in Maintenace Plans I see nothing. 2) If I want to run it manually, when I double click on the dtsx file on the Database Server I get a message asking me what program I want to open it with? Why is this? Do I need to have SQL Management Studio Installed?
How can we install the SSIS runtime components alone.
We are calling SSIS packages from .NET code. We would like to know what are the minimum components we need to install in the machine in which the .NET code is running.
I've already read many topics that was asked about SSIS runtime, but for my purposes I didn't find satisfied answer
Our clients don't use SQL Server for their data. But we anyway used DTS packages for transfering data between client DBes. Only thing that we needed to install was DTS dlls.
What will I need to do now to use old DTS and new SSIS packages on these clients?
I'm trying to reinstall SQL Server 2005 STD but I cannot get Setup to install Integration Services or Notification Services. I looked in the log and this is what I found. Needless to say, it makes no sense to me. It seems that Setup is trying to find a missing source list for a certain product. I have no clue what that product is. I've spent endless hours trying to figure it out and I'm still drawing a blank. This is a printout of the log.
Integration services - ---------------------- MSI (s) (F0:B0) [02:33:01:437]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (F0:B0) [02:33:02:188]: End dialog not enabled MSI (s) (F0:B0) [02:33:02:188]: Original package ==> G:ServersSetupSqlRun_DTS.msi MSI (s) (F0:B0) [02:33:02:188]: Package we're running from ==> C:WINDOWSInstaller188966.msi MSI (s) (F0:B0) [02:33:02:339]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'. MSI (s) (F0:B0) [02:33:02:339]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (F0:B0) [02:33:02:339]: MSCOREE already loaded, using loaded copy MSI (s) (F0:B0) [02:33:02:379]: Couldn't find local patch ''. Looking for it at its source. MSI (s) (F0:B0) [02:33:02:379]: Resolving Patch source. MSI (s) (F0:B0) [02:33:02:379]: User policy value 'SearchOrder' is 'nmu' MSI (s) (F0:B0) [02:33:02:379]: User policy value 'DisableMedia' is 0 MSI (s) (F0:B0) [02:33:02:379]: Machine policy value 'AllowLockdownMedia' is 0 MSI (s) (F0:B0) [02:33:02:379]: SOURCEMGMT: Media enabled only if package is safe. MSI (s) (F0:B0) [02:33:02:379]: SOURCEMGMT: Looking for sourcelist for product {8B7E2749-624E-4C61-92FC-2BC18307FF24} MSI (s) (F0:B0) [02:33:02:379]: Note: 1: 1706 2: {8B7E2749-624E-4C61-92FC-2BC18307FF24} 3: MSI (s) (F0:B0) [02:33:02:379]: SOURCEMGMT: Failed to resolve source MSI (s) (F0:B0) [02:33:02:399]: Note: 1: 1708 MSI (s) (F0:B0) [02:33:02:399]: Note: 1: 2729 MSI (s) (F0:B0) [02:33:02:409]: Note: 1: 2729 MSI (s) (F0:B0) [02:33:02:409]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.
MSI (s) (F0:B0) [02:33:02:439]: MainEngineThread is returning 1612 The installation source for this product is not available. Verify that the source exists and that you can access it. G:ServersSetupSqlRun_DTS.msi MSI (c) (B8:88) [02:33:02:439]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (B8:88) [02:33:02:439]: MainEngineThread is returning 1612 === Verbose logging stopped: 5/19/2006 2:33:02 ===
----------------------- Notification services - ----------------------- MSI (s) (F0:30) [02:33:07:566]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (F0:30) [02:33:08:087]: End dialog not enabled MSI (s) (F0:30) [02:33:08:087]: Original package ==> G:ServersSetupSqlRun_NS.msi MSI (s) (F0:30) [02:33:08:087]: Package we're running from ==> C:WINDOWSInstaller18898f.msi MSI (s) (F0:30) [02:33:08:167]: APPCOMPAT: looking for appcompat database entry with ProductCode '{37E9AD9F-3217-4229-B5A5-7A0C82364C6C}'. MSI (s) (F0:30) [02:33:08:167]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (F0:30) [02:33:08:167]: MSCOREE already loaded, using loaded copy MSI (s) (F0:30) [02:33:08:187]: Couldn't find local patch ''. Looking for it at its source. MSI (s) (F0:30) [02:33:08:187]: Resolving Patch source. MSI (s) (F0:30) [02:33:08:187]: User policy value 'SearchOrder' is 'nmu' MSI (s) (F0:30) [02:33:08:187]: User policy value 'DisableMedia' is 0 MSI (s) (F0:30) [02:33:08:187]: Machine policy value 'AllowLockdownMedia' is 0 MSI (s) (F0:30) [02:33:08:187]: SOURCEMGMT: Media enabled only if package is safe. MSI (s) (F0:30) [02:33:08:187]: SOURCEMGMT: Looking for sourcelist for product {65A498A6-83B9-4B91-99EA-1BA88D73F0AA} MSI (s) (F0:30) [02:33:08:187]: Note: 1: 1706 2: {65A498A6-83B9-4B91-99EA-1BA88D73F0AA} 3: MSI (s) (F0:30) [02:33:08:187]: SOURCEMGMT: Failed to resolve source MSI (s) (F0:30) [02:33:08:187]: Note: 1: 1708 MSI (s) (F0:30) [02:33:08:187]: Note: 1: 2729 MSI (s) (F0:30) [02:33:08:187]: Note: 1: 2729 MSI (s) (F0:30) [02:33:08:187]: Product: Microsoft SQL Server 2005 Notification Services -- Installation failed.
MSI (s) (F0:30) [02:33:08:197]: MainEngineThread is returning 1612 The installation source for this product is not available. Verify that the source exists and that you can access it. G:ServersSetupSqlRun_NS.msi MSI (c) (B8:DC) [02:33:08:207]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (B8:DC) [02:33:08:207]: MainEngineThread is returning 1612
We just moved from SQL 2000 to SQL 2005 Ent. To use SSIS service, I need install this package on client side. But when I install the 2005 on my PC(Win XP Prof), I did not find any place I can include it. Anyone has similar experience or know how to do it?
Trying to install SQL Server 2005 Express and can't get SSIS to install - I keep getting message that IIS is not installed or enabled, however IIS 7.0 is installed and all features are enabled. I'm running VISTA home premium. Is this the problem?
We are installing 2 instances of sql server in cluster env.
When intalling "Default" instance, I m getting Notification services, Integration, reporting services for default instance.
My question is : When we intall second named instance on cluster, will named instance share Notification services, Integration, reporting services with default instace.
So if above is yes, do I have to install Notification services, Integration, reporting services on C: drive of cluster nodes, so that it is shared by all the instances on the cluster nodes.
I am trying to migrate our processing from command line based scripts and foxpro to SQL so I need to run the SSIS packages using dtexec. I copied the dtexec file and a few dll's that are missing to our production servers but i cant execute the packages. I dont want to install the full client tools (particularly managment/business inteligence studio) on our production servers due to the overhead and limited system disk space.
Can somebody tell me what the minimum install would be so I would be able to run SSIS packages using the dtexec or dtexecui tools? I would also like to install some of the other command line client tools like osql etc.
I have done a full Sql Server install on a server and the SSIS service is not available. Normally when I load Sql Server I get €œSQL Server Integration Services" as a service that I can start. On this machine it is not listed after the install. I don't get any errors through out the install.
Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Found patch located at: D:Hotfix_2175x86hotfixasfilessqlrun_as.msp Attempting to repair the local cache for PatchCode "{731AC539-10A2-4073-ADD2-49F74ED65EE6}" No action can be taken as the patch has not been applied on the local machine.
Found patch located at: D:Hotfix_2175x86hotfixdtsfilessqlrun_dts.msp Attempting to repair the local cache for PatchCode "{8B7E2749-624E-4C61-92FC-2BC18307FF24}" D:Hotfix_2175x86RepairMSPSource.js(159, 17) Msi API Error: PatchProperty,Property
Time: 03/29/2007 10:54:04.278 KB Number: KB921896 Machine: BPATLQQDW OS Version: Microsoft Windows Server 2003 family, Standard Edition Service Pack 1 (Build 3790) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x86 Database Services (ATLQQDW01) ENU SP2 2005.090.3042.00 x86 STANDARD Analysis Services (ATLQQDW01) ENU SP2 2005.090.3042.00 x86 STANDARD Reporting Services (ATLQQDW01) ENU SP2 9.00.3042.00 x86 STANDARD Notification Services ENU SP1 9.00.2047.00 x86 ENTERPRISE Integration Services ENU SP1 9.00.2047.00 x86 ENTERPRISE SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU SP2 9.2.3042 x86 STANDARD MSXML 6.0 Parser ENU 6.10.1129.0 x86 SQLXML4 ENU 9.00.3042.00 x86 Backward Compatibility ENU 8.05.2004 x86 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x86
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (ATLQQDW01) Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Analysis Services (ATLQQDW01) Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Reporting Services (ATLQQDW01) Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Number : 0 Error Description : ---------------------------------------------------------------------------------- Product : Notification Services Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log Error Number : 1612 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log Error Number : 1612 Error Description : Unable to install Windows Installer MSP file ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 1129 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 2004 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 1612
Hope this helps someone. My experience is that an interrupted install of SP2 screws things royally, despite signifying success.
My initial attempt at installing SQL Server 2005 SP2 (64-bit) on our dev server resulted in massive corruption of at least one SSIS solution. Without the option to uninstall the SP2, the prospect of a complete reinstall/recovery totally ruined my day.
When I loaded the SSIS solution, all packages returned the following connection based errors "connection manager will not acquire a connection because the package OffLineMode property is TRUE". OffLineMode property was in fact set to the default "False" for all packages. Individual tasks were broken also. I did not search all packages, but FTP and File System tasks were all corrupted. Nor could I successfully create these tasks in a new packages, even within a new solution.
During the install I recived the following error: Error Log: Product : Database Services (MSSQLSERVER) Product Version (Previous): 2153 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user xxxxx. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
The SP2 install continued and with the exception of database Services, all other components were installed successfully.
A very helpful person had posted this solution:
The problem is that there exists a file in this Data directory that the user running SP1 does not have permissions to modify. The workaround is to figure out which file this is (typically a user created DB or some backup program files) and to temporarily assign permission to that file(s). You can revert back to the intended permissions after running SP1.
Sure enough, there was a data and a log file with permission restricted to a single user. Granting permission to the account doing the install worked.
I ran the SP2 again and the database Services component "succeeded". In fact, as outlined, my SSIS packages were unusable.
I re-ran the SP2 install. No components were selected for update, so I manually rechecked each component and executed. This time the install completed successfully for all components, and much to my relief, SSIS functionality was restored.
Pretty scrappy install package IMHO. There are obviously dependencies between the different components being updated, but if these dependencies, and therefore integrity of the update, are broken, the installer nevertheless reports success.
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). :(