Unable To Execute Multiple SSIS Packages From Windows Service

Aug 28, 2007

Need some help...
When we tried to run mulitple packages one after the other from a windows service, first one succeeds but later ones are throwing below error :
"The script threw an exception: The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there.
A deadlock was detected while trying to lock variable "System:ackageName, User::BusinessDate, User::Environment, User:ortfolioName" for read access. A lock could not be acquired after 16 attempts and timed out."

Later, we tried to create separate AppDomains for each package and execute via console application, but ended up with below error (The below expressions were defined in OnError Event) :
"The result of the expression "@[User::ReportErrorFrom]" on property "FromLine" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
The result of the expression ""Error At :" + @[System:ourceName] + "
" +
"Error Description : "+ @[System::ErrorDescription] + "
" " on property "MessageSource" cannot be written to the property. The expression was evaluated, but cannot be set on the property."

At last, we tried to span a separate process (System.Diagnostics.Process) for each package. this seems working but taking very long time:
A package that normally takes 2 min, is taking 60 min.

We also tried creating an SSIS Package that executes mulitple packages. But only first package is getting executed, and second one is throwing below error (Here the variable it is trying to lock is of first package):
"Failed to lock variable "UniqueInstrumentsQuery1" for read access with error 0xC0010001 "The variable cannot be found. This occurs when an attempt is made to retrieve a variable from the Variables collection on a container during execution of the package, and the variable is not there. The variable name may have changed or the variable is not being created.".

Please help us with some work around for this. Thanking you in advance,

View 17 Replies


ADVERTISEMENT

Walkthrough To Execute SSIS Packages Via Web Service

Aug 17, 2007

I am seeking a walkthrough for executing packages via a web service. All I have found so far are fragmented bits of information. This article is a good start but it leaves out some critical security setting information. http://msdn2.microsoft.com/en-us/library/ms403355.aspx#service.

Does anyone know of a good walkthrough that includes the security setup: Impersonation, Proxies, etc.?

View 6 Replies View Related

Remoting Timeout When Calling SSIS Package Execute From A Windows Service

Sep 12, 2007

When running an integration services package from a windows service I get the "Object ... has been disconnected or does not exist at the server." exception after aproximately six minutes of execution.

This is *not* my windows service failing. I can loop indefinately while tracing to a log file within the service and it will run forever. While calling the mypackage.execute(...) method however, after six minutes (give or take) the exception is thrown...

my code looks something like this:
<code>
dim foo as Microsoft.SqlServer.Dts.Runtime.Application
mypackage = foo..LoadPackage(strimportPkgFilename, pkgevents)
results = myPackage.Execute(Nothing, Nothing, pkgevents, Nothing, Nothing)
</code>

<error>
A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll
Exception in: frmMyForm.DoImports
Message: Object '/b76f98a0_5bd9_49d8_a524_eeb49d55b303/bqbhkjnaofq_ifr_cwz+srid_1.rem' has been disconnected or does not exist at the server.
</error>

oddly, this same code works perfectly if I run it within a windows form application no matter how long it takes.

It also runs fine if the package can complete in under six minutes.

Any suggestions?

Mark

View 2 Replies View Related

Integration Services :: SSIS Execute Multiple Packages Based On Conditional Split

Sep 4, 2015

We are building a dataload application where parameters are store in a table. And there are multiple packages for each load.There is a column IsChecked column if it is 1 then only the child package should execute.Created a master package. In which i have taken execute SQL task in that storing a results in variable and based on the result the child package should execute. But In executesql task i selected result set as full result set.  I am getting the below error.

[Execute SQL Task] Error: Executing the query "SELECT  isnull(ID ,0) AS ID FROM DataLoadParameter..." failed with the following error: "The type of the value (DBNull) being assigned to variable "User::LoadValue" differs from the current variable type (Int32). Variables may not change type during execution. Variable types are strict, except for variables of type Object.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

View 3 Replies View Related

Integration Services :: Remotely Execute Packages On SSIS Server - Packages Are Deployed In File System

Apr 22, 2015

We manage some SSIS servers, which has only SSIS and SSIS tools installed on them and not the sql server DB.

SSIS packages and configuration files are deployed on a NAS. We run the SSIS packages through DTEXEC by logging in to the server.

We want to allow developers to run their packages on their own on the server, but at the same time we dont want to give them physical access on the server i.e we do not want to add them into RDP users list on server properties. We want them to allow running their packages remotely on the server.

One way We could think of is by using powershell remoting and we are working on that. But is there any other way or any tool already present for the same.

View 4 Replies View Related

Cannot Execute Job With Multiple Packages

Mar 28, 2008

I have a schedule job that errors out on the first step when I attempt to run it. There are 3 packages that I created and I can run them all manually just fine.

I get this error when I try to run the job:
-----------------------------------------------


Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,
Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted

03/28/2008 13:49:22,ST Customer Data,Error,0,Server01,ST Customer Data,(Job outcome),,The job failed.

The Job was invoked by User sa.

The last step to run was step 1 (config 1).

The job was requested to start at step 1 (config 1).,00:00:01,0,0,,,,0


03/28/2008 13:49:22,ST Customer Data,Error,1,Server01,ST Customer Data,config 1,,

Executed as user: Server01SYSTEM. ...9.00.3042.00 for 32-bit

Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 1:49:23 PM Error: 2008-03-28 13:49:23.23
Code: 0xC0016016 Source:

Description: Failed to decrypt protected XML node "DTS:Password" with

error 0x8009000B "Key not valid for use in specified state.".

You may not be authorized to access this information.

This error occurs when there is a cryptographic error.
Verify that the correct key is available. End Error

Error: 2008-03-28 13:49:23.57 Code: 0xC0202009
Source: Config 1 Customer Data Connection manager "SourceConnectionOLEDB"
Description: SSIS Error Code DTS_E_OLEDBERROR.

An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available.
Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D
Description: "Communication link failure".

An OLE DB record is available.
Source: "Microsoft SQL Native Client"
Hresult: 0x80...
The package execution fa...
The step failed.,00:00:01,0,0,,,,0

-----------------------------------------------


Any ideas?

Thanks,

John

View 2 Replies View Related

Best Practices Question - How Do You Execute Multiple Packages?

Jan 26, 2006

I have 200+ plus packages that need to be flexible in how they are run. For example, an end user may choose to run packages 1,2,3 and the next end user may choose to run packages 2,3,7, etc. Prior ro running a package, I set an "instance id" inside the group of packages so I can tie them all together in the logfile - I know that packages 1,2,3 were all run as group and that's distinct from packages 2,3,7 that were run in a differnt group.

Initially I embarked on a scenario where I had a queue table that loaded up the packages to be run and then had a little c# app that read the queue, generated the "instance id" and ran all the packages (either thru dtexec.exe or the Microsoft.SqlServer.DTS.Runtime). But now I wonder if using a master package that uses the Execute Package Task is the way to go. My 200+ packages are all independent and run based on a single config file and it seems as though going the parent package route will destroy some of that independence because I'll now be relying on parent package variables.

Any comments or suggestions?

View 2 Replies View Related

How To Make SqlServer Agent Execute Windows Service

Mar 24, 2004

To run a remainder service that shoots a mail once everyday to all users of a subscribed service satisfying a pre-determined criteria, I'm planning to use a Sql Server Agent Job. In the first step of the Job, I'll have a stored procedure that gets all the records matching that criteria & store it in a table.

In the next step, I want a Windows Service (as there need not be any interface & my project requires easy deployment & minimal manual intervention) to fetch the records from the above table & shoot mails to users of the subscribed service. Several thousand mails may have to be sent this way. In order not to strain Sql server & also avoid extended stored procedures due to safety reasons, I'm considering using this windows service.

I want to know

1) how to make the Sql Server Agent execute the Windows service?

2) abt code or resources on how to write a vb.net Windows service that will work through a recordset & send mails.

3) from a perfomance point of view, if this method is feasible? If not, what are the other efficient alternatives.

View 1 Replies View Related

Integration Services :: How To Execute Multiple Packages In Parallel

Oct 14, 2008

I'm pretty new to SSIS but I've managed to cobble together a number of individual packages to refresh SQL tables from a 3rd-party database.
 
Now, what I'd like to do is have a single package that I can use to invoke each of the individual ones. Since it will run on a quad, I'd like to invoke them such they'll run in parallel.

View 2 Replies View Related

Execute SSIS Packages From Vb.net

Nov 8, 2007

Hi!

I was following this article http://www.codeproject.com/useritems/Execute_Package_by_C_.asp to execute list of SSIS packages via vb.net. I created a windows application in server A copied the exe file in server B. the SSIS package is in server B. I deployed the package and it runs file vis integration server. below are my codes. everytime i run the exe in server B. I can see the list of packages but when i hit execute button i get error msgs that says "failure" I am not sure how to get more error out of it. I am not sure whats causing this error.
----------------------------

Imports System.Data.SqlTypes

Imports System.Data.SqlClient

Imports Microsoft.SqlServer.Management.Smo

Imports Microsoft.SqlServer.Management.Smo.Agent

Imports Microsoft.SqlServer.Dts.Runtime

Imports Microsoft.SqlServer.Management.Common

Public Class Form1

Dim app As New Microsoft.SqlServer.Dts.Runtime.Application()

Dim pInfos As PackageInfos = app.GetPackageInfos("\", "SQLKEV", "", "")



Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

For Each pInfo As PackageInfo In pInfos

If pInfo.Name <> "Maintenance Plans" Then

ComboBox1.Items.Add(pInfo.Name)

End If

Next

End Sub



Private Sub btnExec_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnExec.Click

Dim app As Microsoft.SqlServer.Dts.Runtime.Application

app = New Microsoft.SqlServer.Dts.Runtime.Application()

Dim pkgResults_Sql As DTSExecResult

Dim pkgIn As New Package()

Try



pkgIn = app.LoadFromSqlServer("" + ComboBox1.SelectedItem.ToString().Trim(), "SQLKEV", "", "", Nothing)

pkgIn.PackagePassword = "password21"

pkgResults_Sql = pkgIn.Execute()

MessageBox.Show(pkgResults_Sql.ToString())

Catch ex As Exception

MsgBox("this is an exception" + ex.ToString)

End Try

End Sub



End Class
----------------------------



please help

View 9 Replies View Related

SSIS Packages Validating Before Execute

Feb 18, 2008

Hi

I have an SSIS package that wont run whne i try to run it in one go, but if i run it step by step it will succeed
as the reason its failing is in the 2nd step it references a table that doesn't exist (its created in the 1st step.

So at the start package is trying to validate, but it won't as the table is created in step 1.

So this is why it works if i execute this step by step, is there a way of turning off the pre run validation
on SSIS scripts ?

Thanks

View 1 Replies View Related

All SSIS Packages Failing After Windows Update!

Jul 23, 2007

Starting saturday all of our SSIS packages on a server (64-bit) starting failing (hundreds of them) the error is:



Precompiled script failed to load. Attempting to reload the script with updated data. For more information, see the Microsoft Knowledge Base article, KB931846 (http://go.microsoft.com/fwlink/?LinkId=81885).



That Knowledgebase link talks about SP2 fixing the issue but we have SP2 already on the server. The sysdtslog90 table is just packed with these as each script inside each package is getting the same error. Looking at the system log the following were installed as part of windows update shortly before the errors started occuring:



- Update for Windows Server 2003 x64 Edition (KB936357)

- Security Update for Windows Server 2003 x64 Edition (KB926122)

- Microsoft .NET Framework 3.0: x64 (KB928416)

- Security Update for Microsoft .NET Framework, Version 2.0 (KB928365)

- Security Update for Excel 2003 (KB936507)

- Update for Outlook 2003 Junk Email Filter (KB936557)



View 10 Replies View Related

For SSIS Dev Team: Is It Possible To Execute Packages Asynchronously?

Mar 28, 2007

Question is in the subject.



The reason I'm asking is because I want a workaround to a problem that a guy is having here:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1404349&SiteID=1



-Jamie

View 1 Replies View Related

Unable To Open Windows Service Identity Panel In Reporting Services Configuration Manager

Jul 4, 2007

Hi,



I've a slight problem with configuring my Report Server. I have set up everything apart from the initialisation and and the Windows Service Identity, however when I select the panel for the latter I am presented with a message box displaying the following:



" Reporting Services Configuration Manager:



There was an error while switching panels. The most likely cause is an error retreiving WMI properties. The exception details are:



InvalidArgument=Value of '1' is not valid for 'SelectedIndex'.

Parameter name: SelectedIndex "



I have tried re-installing the entire SQL server setup and this made no difference, I followed this by removing then reinstalling just the Report Service. Still nothing.



Any ideas as to what it is doing and how I should go about fixing it?



Sim

View 4 Replies View Related

Unable To Edit Or Create SSIS Packages Or Maintenance Plans

Oct 30, 2007

Hi,

I am running SQL 2005 Enterprise with SP2. In the past I have been able to successfully create SSIS packages using the BIDS and also Maintenance Plans from within Management Studio.

Today I tried to edit a maintenance plan and got the following error message:-

TITLE: Microsoft SQL Server Management Studio
------------------------------
Retrieving the COM class factory for component with CLSID {0BE35203-8F91-11CE-9DE3-00AA004BB851} failed due to the following error: 80040154. (Microsoft.DataWarehouse)
------------------------------
BUTTONS:
OK
------------------------------

This error also occurs if I try to create a new Maintenance Plan.

I then tried opening an existing SSIS package in BIDS and got the following error:-

------------------------------------------------------------------------------------------
Microsoft Visual Studio is unable to load this document
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
------------------------------------------------------------------------------------------

These errors only occur on my PC so I know that the problem is with my PC. I have totally uninstalled SQL 2005 components from my PC and reinstalled them with no luck.

To my knowledge, I haven't installed any other programs since creating these packages, although there's a possiblilty my PC may have had some patches applied through SMS.

I am running Windows 2000 Professional.

Can anyone help me resolve this problem?

Thanks.

Martin

View 6 Replies View Related

Unable To Create A SSIS Deployment Utility For A Solution Which Are Having 2 Packages

Dec 28, 2007

Hi All,

I have created a solution which contains only 2 packages say Package1.dtsx and Pakage2.dtsx. I want to create a deployment utility to deploy onto other developers machince. I changed the project properties "CreateDeploymentUtility" to TRUE. When I do the build it is not creating the files in "Deployment" folder. It is saying Rebuild All Failed but the error is not showing.

For more information the 2 packages have 4 indirect configurations from environment variables which are storing the actual config file path.

Am I missing something here?

Thanks.
Venkat.

View 8 Replies View Related

Remote Execution Of SSIS Packages Via Web Service

May 30, 2006

Is anyone executing SSIS packages using a web service similar to the example in http://msdn2.microsoft.com/en-us/ms403355(SQL.90).aspx

From what I've read, there is a new HTTP server embeded in SQL Server (so we don't have to have IIS) that this could be done from??







View 2 Replies View Related

How Do I Do A Minimal Client Tool Install To Execute SSIS Packages

Jun 15, 2006

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.

View 8 Replies View Related

Calling SSIS Packages From A Service Broker Queue

Feb 26, 2007

I would like to call an SSIS package from a Service Broker Queue.

There is one way that I am aware of -

Using xp_cmdshell from within an activation stored procedure and using DTEXEC.

Is there a more elegant way of executing an SSIS package from within SSB?

Also, I am not interested in writing a .NET external activator to process my messages in the queue. I would like this operation to be strictly database oriented. Having said this, I am also trying to avoid triggers processing the messages in the queue.

Thank you!

View 6 Replies View Related

Integration Services :: How To Run All SSIS Packages In A Folder Using Execute Package Task

Jun 26, 2015

I have created for each container to call all the packages in a folder like below, also created a variable.

Then I add execute package task inside of foreach container and selected file system in a location and in connection called currently creating package name finally in connection properties i added variable in expression which i created and mapped into for each loop container. I referred below link 

[URL] ....

All the packages are running but its not ending once all the packages executed its re run and continue the running process, how to stop once all the packages execute. 

View 24 Replies View Related

2k5 SP-2 : Unable To Install Windows Installer MSP File (SSIS &&amp; SSNS)

Mar 29, 2007

New thread.

I tried following/have info on prior long thread on issue ...


> Extracted SP-1
> Ran JS script (info below)
> Re-ran SP-2, failed. (info below)
> (DTS9_Hotfix_KB921896_sqlrun_dts.msp.log info below)



JS script OUTPUT BELOW
=====================================================================

D:Hotfix_2175x86>cscript RepairMSPSource.js "D:Hotfix_2175x86"

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




Summary.txt OUTPUT BELOW
=====================================================================

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

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
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



HotFix.log OUTPUT BELOW
=====================================================================


03/29/2007 10:15:12.964 ================================================================================
03/29/2007 10:15:12.964 Hotfix package launched
03/29/2007 10:15:12.996 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:12.996 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:15:12.996 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:12.996 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:15:12.996 Local Computer:
03/29/2007 10:15:12.996 Target Details: BPATLQQDW
03/29/2007 10:15:12.996 commonfilesdir = C:Program FilesCommon Files
03/29/2007 10:15:12.996 lcidsupportdir = D:Installs1033
03/29/2007 10:15:12.996 programfilesdir = C:Program Files
03/29/2007 10:15:12.996 programfilesdir_wow = C:Program Files
03/29/2007 10:15:12.996 supportdir = D:Installs
03/29/2007 10:15:12.996 supportdirlocal = D:Installs
03/29/2007 10:15:12.996 windir = C:WINDOWS
03/29/2007 10:15:13.011 winsysdir = C:WINDOWSsystem32
03/29/2007 10:15:13.011 winsysdir_wow = C:WINDOWSSysWOW64
03/29/2007 10:15:13.011
03/29/2007 10:15:13.011 Enumerating applicable products for this patch
03/29/2007 10:15:13.027 Found Redist 2005 product definition
03/29/2007 10:15:13.043 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:13.043 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:15:13.043 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:13.043 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:15:13.683 Found Redist 2005 product definition
03/29/2007 10:15:13.699 Found Redist 2005 product definition
03/29/2007 10:15:13.730 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:13.730 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:15:13.730 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:13.730 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:15:13.996 Found SQL 2005 product definition
03/29/2007 10:15:20.886 Enumeration: Determining QFE level for product instance ATLQQDW01
03/29/2007 10:15:20.886 Enumeration: Associated hotfix build information not found for the following file: D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
03/29/2007 10:15:20.886 Enumeration: Found following QFE level for product instance ATLQQDW01: 3042
03/29/2007 10:15:20.902 Enumeration: Determining GDR branching Hotfix for product instance ATLQQDW01
03/29/2007 10:15:20.902 Enumeration: Associated hotfix build information not found for the following file: D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
03/29/2007 10:15:20.902 Enumeration: No GDR branch Hotfix found for product instance ATLQQDW01
03/29/2007 10:15:20.917 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:20.917 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:15:20.917 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:20.917 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:15:20.917 Product discovery completed during the install process for ATLQQDW01
03/29/2007 10:15:20.917 SP Level check completed during the install process for ATLQQDW01
03/29/2007 10:15:20.917 Product language check completed during the install process for ATLQQDW01
03/29/2007 10:15:20.917 Product version check completed during the install process for ATLQQDW01
03/29/2007 10:15:20.917 Command-line instance name check completed during the install process
03/29/2007 10:15:20.917 SKU check completed during the install process for ATLQQDW01
03/29/2007 10:15:20.917 Baseline build check completed during the install process
03/29/2007 10:15:20.933 Found OLAP Server 2005 product definition
03/29/2007 10:15:43.214 Enumeration: Determining QFE level for product instance ATLQQDW01
03/29/2007 10:15:43.230 Enumeration: Associated hotfix build information not found for the following file: D:Program FilesMicrosoft SQL ServerMSSQL.2OLAP\Binmsmdsrv.exe
03/29/2007 10:15:43.230 Enumeration: Found following QFE level for product instance ATLQQDW01: 3042
03/29/2007 10:15:43.230 Enumeration: Determining GDR branching Hotfix for product instance ATLQQDW01
03/29/2007 10:15:43.230 Enumeration: Associated hotfix build information not found for the following file: D:Program FilesMicrosoft SQL ServerMSSQL.2OLAP\Binmsmdsrv.exe
03/29/2007 10:15:43.230 Enumeration: No GDR branch Hotfix found for product instance ATLQQDW01
03/29/2007 10:15:43.230 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:43.245 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:15:43.245 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:15:43.245 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:15:43.245 Product discovery completed during the install process for ATLQQDW01
03/29/2007 10:15:43.245 SP Level check completed during the install process for ATLQQDW01
03/29/2007 10:15:43.245 Product language check completed during the install process for ATLQQDW01
03/29/2007 10:15:43.245 Product version check completed during the install process for ATLQQDW01
03/29/2007 10:15:43.245 Command-line instance name check completed during the install process
03/29/2007 10:15:43.245 Baseline build check completed during the install process
03/29/2007 10:15:43.261 Found Notification Services 2005 product definition
03/29/2007 10:16:05.558 Enumeration: Determining QFE level for product instance
03/29/2007 10:16:05.589 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242\Binsservice.exe
03/29/2007 10:16:05.636 Enumeration: Found following QFE level for product instance : 2047
03/29/2007 10:16:05.636 Enumeration: Determining GDR branching Hotfix for product instance
03/29/2007 10:16:05.651 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242\Binsservice.exe
03/29/2007 10:16:05.651 Enumeration: No GDR branch Hotfix found for product instance
03/29/2007 10:16:05.776 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:05.792 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:05.792 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:05.792 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:05.808 Product discovery completed during the install process for NS
03/29/2007 10:16:05.808 SP Level check completed during the install process for NS
03/29/2007 10:16:05.808 Product language check completed during the install process for NS
03/29/2007 10:16:05.808 Product version check completed during the install process for NS
03/29/2007 10:16:05.808 Baseline build check completed during the installation process for NS
03/29/2007 10:16:05.808 Baseline build check completed during the install process
03/29/2007 10:16:05.823 Found Report Server 2005 product definition
03/29/2007 10:16:12.354 Enumeration: Determining QFE level for product instance ATLQQDW01
03/29/2007 10:16:12.354 Enumeration: Associated hotfix build information not found for the following file: D:Program FilesMicrosoft SQL ServerMSSQL.3Reporting Services\ReportServerinReportingServicesService.exe
03/29/2007 10:16:12.370 Enumeration: Found following QFE level for product instance ATLQQDW01: 3042
03/29/2007 10:16:12.370 Enumeration: Determining GDR branching Hotfix for product instance ATLQQDW01
03/29/2007 10:16:12.370 Enumeration: Associated hotfix build information not found for the following file: D:Program FilesMicrosoft SQL ServerMSSQL.3Reporting Services\ReportServerinReportingServicesService.exe
03/29/2007 10:16:12.370 Enumeration: No GDR branch Hotfix found for product instance ATLQQDW01
03/29/2007 10:16:12.370 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:12.370 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:12.370 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:12.386 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:12.386 Product discovery completed during the install process for ATLQQDW01
03/29/2007 10:16:12.386 SP Level check completed during the install process for ATLQQDW01
03/29/2007 10:16:12.386 Product language check completed during the install process for ATLQQDW01
03/29/2007 10:16:12.386 Product version check completed during the install process for ATLQQDW01
03/29/2007 10:16:12.386 Command-line instance name check completed during the install process
03/29/2007 10:16:12.386 SKU check completed during the install process for ATLQQDW01
03/29/2007 10:16:12.386 Baseline build check completed during the install process
03/29/2007 10:16:12.386 Found DTS 2005 product definition
03/29/2007 10:16:34.463 Enumeration: Determining QFE level for product instance
03/29/2007 10:16:34.463 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90DTS\Binnmsdtssrvr.exe
03/29/2007 10:16:34.495 Enumeration: Found following QFE level for product instance : 2047
03/29/2007 10:16:34.495 Enumeration: Determining GDR branching Hotfix for product instance
03/29/2007 10:16:34.495 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90DTS\Binnmsdtssrvr.exe
03/29/2007 10:16:34.495 Enumeration: No GDR branch Hotfix found for product instance
03/29/2007 10:16:34.495 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:34.495 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:34.510 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:34.510 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:34.510 Product discovery completed during the install process for Integration Services
03/29/2007 10:16:34.510 SP Level check completed during the install process for Integration Services
03/29/2007 10:16:34.510 Product language check completed during the install process for Integration Services
03/29/2007 10:16:34.510 Product version check completed during the install process for Integration Services
03/29/2007 10:16:34.510 Baseline build check completed during the installation process for Integration Services
03/29/2007 10:16:34.510 Baseline build check completed during the install process
03/29/2007 10:16:34.510 Found SQL 2005 Tools product definition
03/29/2007 10:16:56.666 Enumeration: Determining GDR branching Hotfix for product instance
03/29/2007 10:16:56.682 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
03/29/2007 10:16:56.682 Enumeration: No GDR branch Hotfix found for product instance
03/29/2007 10:16:56.697 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:56.697 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:56.697 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:56.697 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:56.697 Product discovery completed during the install process for SQL Tools
03/29/2007 10:16:56.697 SP Level check completed during the install process for SQL Tools
03/29/2007 10:16:56.697 Product language check completed during the install process for SQL Tools
03/29/2007 10:16:56.697 Product version check completed during the install process for SQL Tools
03/29/2007 10:16:56.697 SKU check completed during the install process for SQL Tools
03/29/2007 10:16:56.697 Baseline build check completed during the install process
03/29/2007 10:16:56.713 Found Redist 2005 product definition
03/29/2007 10:16:56.713 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:56.713 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:56.729 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:56.729 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:57.119 Found Redist 2005 product definition
03/29/2007 10:16:57.135 Found Redist 2005 product definition
03/29/2007 10:16:57.151 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:57.151 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:57.151 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:57.151 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:57.479 Found Redist 2005 product definition
03/29/2007 10:16:57.494 Found Redist 2005 product definition
03/29/2007 10:16:57.510 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:57.510 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:57.526 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:57.526 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:58.244 Found Redist 2005 product definition
03/29/2007 10:16:58.260 Found Redist 2005 product definition
03/29/2007 10:16:58.276 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:58.276 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/29/2007 10:16:58.291 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/29/2007 10:16:58.291 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/29/2007 10:16:58.619 Found Redist 2005 product definition
03/29/2007 10:16:58.729 Product Enumeration Results:
03/29/2007 10:16:58.729 INF File Name: D:InstallsHotFixSqlncli.inf
03/29/2007 10:16:58.729 baselinebuild = 1399
03/29/2007 10:16:58.729 build = 3042
03/29/2007 10:16:58.729 description = SQL Server Native Client
03/29/2007 10:16:58.744 details = Service Pack for Microsoft SQL Server Native Client.
03/29/2007 10:16:58.744 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.744 kbarticle = KB921896
03/29/2007 10:16:58.744 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.744 lcid = 1033
03/29/2007 10:16:58.744 legalproductname = Microsoft SQL Native Client
03/29/2007 10:16:58.744 machinetype = x86
03/29/2007 10:16:58.744 package = HotFixSqlncli
03/29/2007 10:16:58.744 packagetype = Hotfix
03/29/2007 10:16:58.744 productcode = {F9B3DD02-B0B3-42E9-8650-030DFF0D133D}
03/29/2007 10:16:58.744 productname = Redist9
03/29/2007 10:16:58.744 recommendinstall = 1
03/29/2007 10:16:58.744 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.744 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.744 splevel = 2
03/29/2007 10:16:58.744 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.744 supportdir = D:Installs
03/29/2007 10:16:58.744 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
03/29/2007 10:16:58.744 version = 9
03/29/2007 10:16:58.744
03/29/2007 10:16:58.744 File Group Details: MSI
03/29/2007 10:16:58.744 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:58.744 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.760 File Details: sqlncli.msi
03/29/2007 10:16:58.760
03/29/2007 10:16:58.760 Instance Details: SQL Server Native Client
03/29/2007 10:16:58.760 fullversion = 9.00.3042.00
03/29/2007 10:16:58.760 lcid = 1033
03/29/2007 10:16:58.760 productcode = {F9B3DD02-B0B3-42E9-8650-030DFF0D133D}
03/29/2007 10:16:58.760 qfelevel = 3042
03/29/2007 10:16:58.760 sp = -1
03/29/2007 10:16:58.760
03/29/2007 10:16:58.760 Product Enumeration Results:
03/29/2007 10:16:58.760 INF File Name: D:InstallsHotFixSqlncli_x64.inf
03/29/2007 10:16:58.760 baselinebuild = 1399
03/29/2007 10:16:58.760 build = 3042
03/29/2007 10:16:58.760 description = SQL Server Native Client
03/29/2007 10:16:58.760 details = Service Pack for Microsoft SQL Server Native Client.
03/29/2007 10:16:58.760 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.760 kbarticle = KB921896
03/29/2007 10:16:58.760 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.760 lcid = 1033
03/29/2007 10:16:58.760 legalproductname = Microsoft SQL Native Client (64-bit)
03/29/2007 10:16:58.760 machinetype = x64
03/29/2007 10:16:58.760 package = HotFixSqlncli_x64
03/29/2007 10:16:58.760 packagetype = Hotfix
03/29/2007 10:16:58.776 productname = Redist9
03/29/2007 10:16:58.776 recommendinstall = 1
03/29/2007 10:16:58.776 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.776 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.776 splevel = 2
03/29/2007 10:16:58.776 supportdir = D:Installs
03/29/2007 10:16:58.776 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
03/29/2007 10:16:58.776 version = 9
03/29/2007 10:16:58.776
03/29/2007 10:16:58.776 File Group Details: MSI
03/29/2007 10:16:58.776 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:58.776 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.776 File Details: sqlncli_x64.msi
03/29/2007 10:16:58.776
03/29/2007 10:16:58.776 Product Enumeration Results:
03/29/2007 10:16:58.776 INF File Name: D:InstallsHotFixSqlSupport.inf
03/29/2007 10:16:58.776 alwaysinstall = 1
03/29/2007 10:16:58.776 baselinebuild = 1399
03/29/2007 10:16:58.776 build = 3042
03/29/2007 10:16:58.776 description = Setup Support Files
03/29/2007 10:16:58.776 details = Service Pack for the SQL Server support files.
03/29/2007 10:16:58.776 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.791 kbarticle = KB921896
03/29/2007 10:16:58.791 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.791 keyqualifier = 1
03/29/2007 10:16:58.791 lcid = 1033
03/29/2007 10:16:58.791 legalproductname = SQL Server 2005 Setup Support Files
03/29/2007 10:16:58.791 machinetype = x86
03/29/2007 10:16:58.791 package = HotFixSqlSupport
03/29/2007 10:16:58.791 packagetype = Hotfix
03/29/2007 10:16:58.791 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
03/29/2007 10:16:58.791 productname = Redist9
03/29/2007 10:16:58.791 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.791 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.791 splevel = 2
03/29/2007 10:16:58.791 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.791 supportdir = D:Installs
03/29/2007 10:16:58.791 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
03/29/2007 10:16:58.791 version = 9
03/29/2007 10:16:58.791
03/29/2007 10:16:58.791 File Group Details: MSI
03/29/2007 10:16:58.791 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
03/29/2007 10:16:58.791 parameters = REINSTALL=ALL
03/29/2007 10:16:58.791 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.807 File Details: SqlSupport.msi
03/29/2007 10:16:58.807
03/29/2007 10:16:58.807 Instance Details: Setup Support Files
03/29/2007 10:16:58.807 fullversion = 9.2.3042
03/29/2007 10:16:58.807 lcid = 1033
03/29/2007 10:16:58.807 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
03/29/2007 10:16:58.807 qfelevel = 3042
03/29/2007 10:16:58.807 sp = -1
03/29/2007 10:16:58.807
03/29/2007 10:16:58.807 Product Enumeration Results:
03/29/2007 10:16:58.807 INF File Name: D:InstallsHotFixSQL.inf
03/29/2007 10:16:58.807 baselinebuild = 1399
03/29/2007 10:16:58.807 baselinebuildmax = 3042
03/29/2007 10:16:58.807 build = 3042
03/29/2007 10:16:58.807 description = Database Services
03/29/2007 10:16:58.807 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
03/29/2007 10:16:58.807 installer = Hotfix
03/29/2007 10:16:58.807 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.807 kbarticle = KB921896
03/29/2007 10:16:58.807 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.807 lcid = 1033
03/29/2007 10:16:58.807 legalproductname = SQL Server Database Services 2005
03/29/2007 10:16:58.807 machinetype = x86
03/29/2007 10:16:58.822 package = HotFixSQL
03/29/2007 10:16:58.822 packagetype = Hotfix
03/29/2007 10:16:58.822 productname = SQL9
03/29/2007 10:16:58.822 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.822 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.822 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/29/2007 10:16:58.822 splevel = 2
03/29/2007 10:16:58.822 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.822 sqlutility = sqlcmd.exe
03/29/2007 10:16:58.822 supportdir = D:Installs
03/29/2007 10:16:58.822 validateauthentication = true
03/29/2007 10:16:58.822 version = 9
03/29/2007 10:16:58.822
03/29/2007 10:16:58.822 File Group Details: MSP
03/29/2007 10:16:58.822 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/29/2007 10:16:58.822 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.822 File Details: sqlrun_sql.msp
03/29/2007 10:16:58.822
03/29/2007 10:16:58.822 Instance Details: ATLQQDW01
03/29/2007 10:16:58.822 agentservicename = SQLAgent$ATLQQDW01
03/29/2007 10:16:58.822 associatedhotfixbuild = 1520
03/29/2007 10:16:58.822 clustername =
03/29/2007 10:16:58.822 ftsservicename = MSFTESQL$ATLQQDW01
03/29/2007 10:16:58.838 fullversion = 2005.090.3042.00
03/29/2007 10:16:58.838 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
03/29/2007 10:16:58.838 id = MSSQL.1
03/29/2007 10:16:58.838 installsqldatadir = D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
03/29/2007 10:16:58.838 installsqldir = D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
03/29/2007 10:16:58.838 lcid = 1033
03/29/2007 10:16:58.838 name = ATLQQDW01
03/29/2007 10:16:58.838 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
03/29/2007 10:16:58.838 qfelevel = 3042
03/29/2007 10:16:58.838 servicename = MSSQL$ATLQQDW01
03/29/2007 10:16:58.838 sku = STANDARD
03/29/2007 10:16:58.838 sp = 2
03/29/2007 10:16:58.838 type = SQL Server Standalone Product
03/29/2007 10:16:58.838 vermajbld = 3042
03/29/2007 10:16:58.838 version = 9
03/29/2007 10:16:58.838
03/29/2007 10:16:58.838 Product Enumeration Results:
03/29/2007 10:16:58.838 INF File Name: D:InstallsHotFixAS.inf
03/29/2007 10:16:58.838 baselinebuild = 1399
03/29/2007 10:16:58.838 baselinebuildmax = 3042
03/29/2007 10:16:58.838 build = 3042
03/29/2007 10:16:58.838 description = Analysis Services
03/29/2007 10:16:58.838 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
03/29/2007 10:16:58.854 installer = Hotfix
03/29/2007 10:16:58.854 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.854 kbarticle = KB921896
03/29/2007 10:16:58.854 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.854 lcid = 1033
03/29/2007 10:16:58.854 legalproductname = SQL Server Analysis Services 2005
03/29/2007 10:16:58.854 machinetype = x86
03/29/2007 10:16:58.854 package = HotFixAS
03/29/2007 10:16:58.854 packagetype = Hotfix
03/29/2007 10:16:58.854 productname = OLAP9
03/29/2007 10:16:58.854 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.854 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.854 splevel = 2
03/29/2007 10:16:58.854 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.854 supportdir = D:Installs
03/29/2007 10:16:58.854 version = 9
03/29/2007 10:16:58.854
03/29/2007 10:16:58.854 File Group Details: MSP
03/29/2007 10:16:58.854 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/29/2007 10:16:58.854 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.854 File Details: sqlrun_as.msp
03/29/2007 10:16:58.854
03/29/2007 10:16:58.854 Instance Details: ATLQQDW01
03/29/2007 10:16:58.869 associatedhotfixbuild = 1520
03/29/2007 10:16:58.869 clustername =
03/29/2007 10:16:58.869 fullversion = 2005.090.3042.00
03/29/2007 10:16:58.869 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.2
03/29/2007 10:16:58.869 id = MSSQL.2
03/29/2007 10:16:58.869 installsqldatadir = D:Program FilesMicrosoft SQL Server
03/29/2007 10:16:58.869 installsqldir = D:Program FilesMicrosoft SQL ServerMSSQL.2OLAP
03/29/2007 10:16:58.869 lcid = 1033
03/29/2007 10:16:58.869 name = ATLQQDW01
03/29/2007 10:16:58.869 olapservicename = MSOLAP$ATLQQDW01
03/29/2007 10:16:58.869 productcode = {8ABF8FEB-ABB0-40DC-9945-85AF36EF30A9}
03/29/2007 10:16:58.869 qfelevel = 3042
03/29/2007 10:16:58.869 servicename = MSOLAP$ATLQQDW01
03/29/2007 10:16:58.869 sku = STANDARD
03/29/2007 10:16:58.869 sp = 2
03/29/2007 10:16:58.869 type = Olap Standalone Product
03/29/2007 10:16:58.869 vermajbld = 3042
03/29/2007 10:16:58.869 version = 9
03/29/2007 10:16:58.869
03/29/2007 10:16:58.869 Product Enumeration Results:
03/29/2007 10:16:58.869 INF File Name: D:InstallsHotFixNS.inf
03/29/2007 10:16:58.869 baselinebuild = 1399
03/29/2007 10:16:58.869 baselinebuildmax = 3042
03/29/2007 10:16:58.885 build = 3042
03/29/2007 10:16:58.885 description = Notification Services
03/29/2007 10:16:58.885 details = Service Pack for Notification Services, a platform for developing and deploying applications that send personalized, timely notifications to a variety of devices or applications.
03/29/2007 10:16:58.885 installer = Hotfix
03/29/2007 10:16:58.885 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.885 kbarticle = KB921896
03/29/2007 10:16:58.885 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.885 lcid = 1033
03/29/2007 10:16:58.885 legalproductname = SQL Server Notification Services 2005 instances
03/29/2007 10:16:58.885 machinetype = x86
03/29/2007 10:16:58.885 package = HotFixNS
03/29/2007 10:16:58.885 packagetype = Hotfix
03/29/2007 10:16:58.885 productname = NS9
03/29/2007 10:16:58.885 recommendinstall = 1
03/29/2007 10:16:58.885 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.885 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.885 splevel = 2
03/29/2007 10:16:58.885 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.885 supportdir = D:Installs
03/29/2007 10:16:58.885 version = 9
03/29/2007 10:16:58.885
03/29/2007 10:16:58.885 File Group Details: MSP
03/29/2007 10:16:58.885 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/29/2007 10:16:58.901 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.901 File Details: sqlrun_ns.msp
03/29/2007 10:16:58.901
03/29/2007 10:16:58.901 Instance Details: NS
03/29/2007 10:16:58.901 associatedhotfixbuild = 0
03/29/2007 10:16:58.901 clustername =
03/29/2007 10:16:58.901 fullversion = 9.00.2047.00
03/29/2007 10:16:58.901 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90NS
03/29/2007 10:16:58.901 id =
03/29/2007 10:16:58.901 installsqldatadir =
03/29/2007 10:16:58.901 installsqldir = C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242
03/29/2007 10:16:58.901 lcid = 1033
03/29/2007 10:16:58.901 name =
03/29/2007 10:16:58.901 productcode = {C0B81E26-F7D0-4E84-941A-21C438BC586D}
03/29/2007 10:16:58.901 qfelevel = 2047
03/29/2007 10:16:58.901 sku = ENTERPRISE
03/29/2007 10:16:58.901 sp = 1
03/29/2007 10:16:58.901 type = Tools Only
03/29/2007 10:16:58.901 vermajbld = 2047
03/29/2007 10:16:58.901 version = 9
03/29/2007 10:16:58.901
03/29/2007 10:16:58.901 Product Enumeration Results:
03/29/2007 10:16:58.901 INF File Name: D:InstallsHotFixRS.inf
03/29/2007 10:16:58.916 baselinebuild = 1399
03/29/2007 10:16:58.916 baselinebuildmax = 3042
03/29/2007 10:16:58.916 build = 3042
03/29/2007 10:16:58.916 description = Reporting Services
03/29/2007 10:16:58.916 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
03/29/2007 10:16:58.916 installer = Hotfix
03/29/2007 10:16:58.916 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.916 kbarticle = KB921896
03/29/2007 10:16:58.916 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.916 lcid = 1033
03/29/2007 10:16:58.916 legalproductname = SQL Server Reporting Services 2005
03/29/2007 10:16:58.916 machinetype = x86
03/29/2007 10:16:58.916 package = HotFixRS
03/29/2007 10:16:58.916 packagetype = Hotfix
03/29/2007 10:16:58.916 productname = RS9
03/29/2007 10:16:58.916 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.916 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.916 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/29/2007 10:16:58.916 splevel = 2
03/29/2007 10:16:58.916 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.916 sqlutility = sqlcmd.exe
03/29/2007 10:16:58.916 supportdir = D:Installs
03/29/2007 10:16:58.916 validateauthentication = 1
03/29/2007 10:16:58.932 version = 9
03/29/2007 10:16:58.932
03/29/2007 10:16:58.932 File Group Details: MSP
03/29/2007 10:16:58.932 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/29/2007 10:16:58.932 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.932 File Details: sqlrun_rs.msp
03/29/2007 10:16:58.932
03/29/2007 10:16:58.932 Instance Details: ATLQQDW01
03/29/2007 10:16:58.932 associatedhotfixbuild = 1520
03/29/2007 10:16:58.932 clustername =
03/29/2007 10:16:58.932 fullversion = 9.00.3042.00
03/29/2007 10:16:58.932 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.3
03/29/2007 10:16:58.932 id = MSSQL.3
03/29/2007 10:16:58.932 installsqldatadir =
03/29/2007 10:16:58.932 installsqldir = D:Program FilesMicrosoft SQL ServerMSSQL.3Reporting Services
03/29/2007 10:16:58.932 lcid = 1033
03/29/2007 10:16:58.932 name = ATLQQDW01
03/29/2007 10:16:58.932 productcode = {E930E839-998E-42F9-97E2-71FC960DB1B7}
03/29/2007 10:16:58.932 qfelevel = 3042
03/29/2007 10:16:58.932 rsservicename = ReportServer$ATLQQDW01
03/29/2007 10:16:58.932 servicename = ReportServer$ATLQQDW01
03/29/2007 10:16:58.932 sku = STANDARD
03/29/2007 10:16:58.932 sp = 2
03/29/2007 10:16:58.947 type = Report Server Standalone Product
03/29/2007 10:16:58.947 vermajbld = 3042
03/29/2007 10:16:58.947 version = 9
03/29/2007 10:16:58.947
03/29/2007 10:16:58.947 Product Enumeration Results:
03/29/2007 10:16:58.947 INF File Name: D:InstallsHotFixDTS.inf
03/29/2007 10:16:58.947 baselinebuild = 1399
03/29/2007 10:16:58.947 baselinebuildmax = 3042
03/29/2007 10:16:58.947 build = 3042
03/29/2007 10:16:58.947 description = Integration Services
03/29/2007 10:16:58.947 details = Service Pack for Integration Services, a set of tools and programmable objects used to create and manage packages that extract, transform, and load data, as well as perform tasks.
03/29/2007 10:16:58.947 installer = Hotfix
03/29/2007 10:16:58.947 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.947 kbarticle = KB921896
03/29/2007 10:16:58.947 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.947 lcid = 1033
03/29/2007 10:16:58.947 legalproductname = SQL Server Integration Services 2005
03/29/2007 10:16:58.947 machinetype = x86
03/29/2007 10:16:58.947 package = HotFixDTS
03/29/2007 10:16:58.947 packagetype = Hotfix
03/29/2007 10:16:58.947 productname = DTS9
03/29/2007 10:16:58.947 recommendinstall = 1
03/29/2007 10:16:58.947 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.963 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.963 splevel = 2
03/29/2007 10:16:58.963 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.963 supportdir = D:Installs
03/29/2007 10:16:58.963 version = 9
03/29/2007 10:16:58.963
03/29/2007 10:16:58.963 File Group Details: MSP
03/29/2007 10:16:58.963 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/29/2007 10:16:58.963 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.963 File Details: sqlrun_dts.msp
03/29/2007 10:16:58.963
03/29/2007 10:16:58.963 Instance Details: Integration Services
03/29/2007 10:16:58.963 associatedhotfixbuild = 0
03/29/2007 10:16:58.963 clustername =
03/29/2007 10:16:58.963 dtsservicename = MsDtsServer
03/29/2007 10:16:58.963 fullversion = 9.00.2047.00
03/29/2007 10:16:58.963 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90DTS
03/29/2007 10:16:58.963 id =
03/29/2007 10:16:58.963 installsqldatadir =
03/29/2007 10:16:58.963 installsqldir = C:Program FilesMicrosoft SQL Server90DTS
03/29/2007 10:16:58.963 lcid = 1033
03/29/2007 10:16:58.963 name =
03/29/2007 10:16:58.963 productcode = {8E408A85-E0E5-4094-903F-8675707AC313}
03/29/2007 10:16:58.963 qfelevel = 2047
03/29/2007 10:16:58.979 servicename = MsDtsServer
03/29/2007 10:16:58.979 sku = ENTERPRISE
03/29/2007 10:16:58.979 sp = 1
03/29/2007 10:16:58.979 type = Tools Only
03/29/2007 10:16:58.979 vermajbld = 2047
03/29/2007 10:16:58.979 version = 9
03/29/2007 10:16:58.979
03/29/2007 10:16:58.979 Product Enumeration Results:
03/29/2007 10:16:58.979 INF File Name: D:InstallsHotFixTools.inf
03/29/2007 10:16:58.979 baselinebuild = 1399
03/29/2007 10:16:58.979 baselinebuildmax = 3042
03/29/2007 10:16:58.979 build = 3042
03/29/2007 10:16:58.979 description = Client Components
03/29/2007 10:16:58.979 details = Service Pack for the interactive management tools for running SQL Server, including SQL Server Configuration Manager, SQL Server Management Studio, SQL Profiler, and Replication Monitor.
03/29/2007 10:16:58.979 installer = Hotfix
03/29/2007 10:16:58.979 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:58.979 kbarticle = KB921896
03/29/2007 10:16:58.979 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:58.979 lcid = 1033
03/29/2007 10:16:58.979 legalproductname = SQL Server Tools and Workstation Components 2005
03/29/2007 10:16:58.979 machinetype = x86
03/29/2007 10:16:58.979 package = HotFixTools
03/29/2007 10:16:58.979 packagetype = Hotfix
03/29/2007 10:16:58.994 productname = SQLTools9
03/29/2007 10:16:58.994 recommendinstall = 1
03/29/2007 10:16:58.994 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:58.994 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:58.994 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/29/2007 10:16:58.994 splevel = 2
03/29/2007 10:16:58.994 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:58.994 supportdir = D:Installs
03/29/2007 10:16:58.994 version = 9
03/29/2007 10:16:58.994
03/29/2007 10:16:58.994 File Group Details: MSP
03/29/2007 10:16:58.994 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/29/2007 10:16:58.994 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:58.994 File Details: sqlrun_tools.msp
03/29/2007 10:16:58.994
03/29/2007 10:16:58.994 Instance Details: SQL Tools
03/29/2007 10:16:58.994 associatedhotfixbuild = 1520
03/29/2007 10:16:58.994 clustername =
03/29/2007 10:16:58.994 fullversion = 9.2.3042
03/29/2007 10:16:58.994 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
03/29/2007 10:16:58.994 id =
03/29/2007 10:16:58.994 installsqldatadir =
03/29/2007 10:16:58.994 installsqldir = C:Program FilesMicrosoft SQL Server90Tools
03/29/2007 10:16:59.010 lcid = 1033
03/29/2007 10:16:59.010 name =
03/29/2007 10:16:59.010 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
03/29/2007 10:16:59.010 qfelevel = 3042
03/29/2007 10:16:59.010 sku = STANDARD
03/29/2007 10:16:59.010 sp = 2
03/29/2007 10:16:59.010 type = Tools Only
03/29/2007 10:16:59.010 vermajbld = 3042
03/29/2007 10:16:59.010 version = 9
03/29/2007 10:16:59.010
03/29/2007 10:16:59.010 Product Enumeration Results:
03/29/2007 10:16:59.010 INF File Name: D:InstallsHotFixMsxml6.inf
03/29/2007 10:16:59.010 baselinebuild = 1399
03/29/2007 10:16:59.010 build = 6.10.1129.0
03/29/2007 10:16:59.010 description = MSXML 6.0 Parser
03/29/2007 10:16:59.010 details = Service Pack for Microsoft XML 6.0 Parser.
03/29/2007 10:16:59.010 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.010 kbarticle = KB921896
03/29/2007 10:16:59.010 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.010 lcid = 1033
03/29/2007 10:16:59.010 legalproductname = MSXML 6.0 Parser
03/29/2007 10:16:59.010 machinetype = x86
03/29/2007 10:16:59.010 package = HotFixMsxml6
03/29/2007 10:16:59.026 packagetype = Hotfix
03/29/2007 10:16:59.026 productcode = {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}
03/29/2007 10:16:59.026 productname = Redist9
03/29/2007 10:16:59.026 recommendinstall = 1
03/29/2007 10:16:59.026 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.026 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.026 splevel = 2
03/29/2007 10:16:59.026 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:59.026 supportdir = D:Installs
03/29/2007 10:16:59.026 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
03/29/2007 10:16:59.026 version = 9
03/29/2007 10:16:59.026
03/29/2007 10:16:59.026 File Group Details: MSI
03/29/2007 10:16:59.026 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.026 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.026 File Details: msxml6.msi
03/29/2007 10:16:59.026
03/29/2007 10:16:59.026 Instance Details: MSXML 6.0 Parser
03/29/2007 10:16:59.026 fullversion = 6.10.1129.0
03/29/2007 10:16:59.026 lcid = 1033
03/29/2007 10:16:59.026 productcode = {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}
03/29/2007 10:16:59.026 qfelevel = 1129
03/29/2007 10:16:59.026 sp = -1
03/29/2007 10:16:59.041
03/29/2007 10:16:59.041 Product Enumeration Results:
03/29/2007 10:16:59.041 INF File Name: D:InstallsHotFixMsxml6_x64.inf
03/29/2007 10:16:59.041 baselinebuild = 1399
03/29/2007 10:16:59.041 build = 6.10.1129.0
03/29/2007 10:16:59.041 description = MSXML 6.0 Parser
03/29/2007 10:16:59.041 details = Service Pack for Microsoft XML 6.0 Parser.
03/29/2007 10:16:59.041 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.041 kbarticle = KB921896
03/29/2007 10:16:59.041 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.041 lcid = 1033
03/29/2007 10:16:59.041 legalproductname = MSXML 6.0 Parser (64-bit)
03/29/2007 10:16:59.041 machinetype = x64
03/29/2007 10:16:59.041 package = HotFixMsxml6_x64
03/29/2007 10:16:59.041 packagetype = Hotfix
03/29/2007 10:16:59.041 productname = Redist9
03/29/2007 10:16:59.041 recommendinstall = 1
03/29/2007 10:16:59.041 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.041 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.041 splevel = 2
03/29/2007 10:16:59.041 supportdir = D:Installs
03/29/2007 10:16:59.041 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
03/29/2007 10:16:59.041 version = 9
03/29/2007 10:16:59.057
03/29/2007 10:16:59.057 File Group Details: MSI
03/29/2007 10:16:59.057 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.057 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.057 File Details: msxml6_x64.msi
03/29/2007 10:16:59.057
03/29/2007 10:16:59.057 Product Enumeration Results:
03/29/2007 10:16:59.057 INF File Name: D:InstallsHotFixSqlxml4.inf
03/29/2007 10:16:59.057 baselinebuild = 1399
03/29/2007 10:16:59.057 build = 3042
03/29/2007 10:16:59.057 description = SQLXML4
03/29/2007 10:16:59.057 details = Service Pack for Microsoft SQLXML 4.0.
03/29/2007 10:16:59.057 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.057 kbarticle = KB921896
03/29/2007 10:16:59.057 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.057 lcid = 1033
03/29/2007 10:16:59.057 legalproductname = SQLXML4
03/29/2007 10:16:59.057 machinetype = x86
03/29/2007 10:16:59.057 package = HotFixSqlxml4
03/29/2007 10:16:59.057 packagetype = Hotfix
03/29/2007 10:16:59.057 productcode = {36DD7006-7BFE-4E3D-AF6E-FA734BC879B7}
03/29/2007 10:16:59.057 productname = Redist9
03/29/2007 10:16:59.057 recommendinstall = 1
03/29/2007 10:16:59.057 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.072 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.072 splevel = 2
03/29/2007 10:16:59.072 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:59.072 supportdir = D:Installs
03/29/2007 10:16:59.072 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
03/29/2007 10:16:59.072 version = 9
03/29/2007 10:16:59.072
03/29/2007 10:16:59.072 File Group Details: MSI
03/29/2007 10:16:59.072 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.072 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.072 File Details: sqlxml4.msi
03/29/2007 10:16:59.072
03/29/2007 10:16:59.072 Instance Details: SQLXML4
03/29/2007 10:16:59.072 fullversion = 9.00.3042.00
03/29/2007 10:16:59.072 lcid = 1033
03/29/2007 10:16:59.072 productcode = {36DD7006-7BFE-4E3D-AF6E-FA734BC879B7}
03/29/2007 10:16:59.072 qfelevel = 3042
03/29/2007 10:16:59.072 sp = -1
03/29/2007 10:16:59.072
03/29/2007 10:16:59.072 Product Enumeration Results:
03/29/2007 10:16:59.072 INF File Name: D:InstallsHotFixSqlxml4_x64.inf
03/29/2007 10:16:59.072 baselinebuild = 1399
03/29/2007 10:16:59.072 build = 3042
03/29/2007 10:16:59.088 description = SQLXML4
03/29/2007 10:16:59.088 details = Service Pack for Microsoft SQLXML 4.0.
03/29/2007 10:16:59.088 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.088 kbarticle = KB921896
03/29/2007 10:16:59.088 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.088 lcid = 1033
03/29/2007 10:16:59.088 legalproductname = SQLXML4 (64-bit)
03/29/2007 10:16:59.088 machinetype = x64
03/29/2007 10:16:59.088 package = HotFixSqlxml4_x64
03/29/2007 10:16:59.088 packagetype = Hotfix
03/29/2007 10:16:59.088 productname = Redist9
03/29/2007 10:16:59.088 recommendinstall = 1
03/29/2007 10:16:59.088 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.088 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.088 splevel = 2
03/29/2007 10:16:59.088 supportdir = D:Installs
03/29/2007 10:16:59.088 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
03/29/2007 10:16:59.088 version = 9
03/29/2007 10:16:59.088
03/29/2007 10:16:59.088 File Group Details: MSI
03/29/2007 10:16:59.088 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.088 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.088 File Details: sqlxml4_x64.msi
03/29/2007 10:16:59.104
03/29/2007 10:16:59.104 Product Enumeration Results:
03/29/2007 10:16:59.104 INF File Name: D:InstallsHotFixSQLServer2005_BC.inf
03/29/2007 10:16:59.104 baselinebuild = 1399
03/29/2007 10:16:59.104 build = 2004
03/29/2007 10:16:59.104 description = Backward Compatibility
03/29/2007 10:16:59.104 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
03/29/2007 10:16:59.104 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.104 kbarticle = KB921896
03/29/2007 10:16:59.104 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.104 lcid = 1033
03/29/2007 10:16:59.104 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
03/29/2007 10:16:59.104 machinetype = x86
03/29/2007 10:16:59.104 package = HotFixSQLServer2005_BC
03/29/2007 10:16:59.104 packagetype = Hotfix
03/29/2007 10:16:59.104 productcode = {69880C00-08DD-4385-B752-9C62656F6D1E}
03/29/2007 10:16:59.104 productname = Redist9
03/29/2007 10:16:59.104 recommendinstall = 1
03/29/2007 10:16:59.104 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.104 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.104 splevel = 2
03/29/2007 10:16:59.104 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:59.104 supportdir = D:Installs
03/29/2007 10:16:59.119 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
03/29/2007 10:16:59.119 version = 9
03/29/2007 10:16:59.119
03/29/2007 10:16:59.119 File Group Details: MSI
03/29/2007 10:16:59.119 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.119 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.119 File Details: SQLServer2005_BC.msi
03/29/2007 10:16:59.119
03/29/2007 10:16:59.119 Instance Details: Backward Compatibility
03/29/2007 10:16:59.119 fullversion = 8.05.2004
03/29/2007 10:16:59.119 lcid = 1033
03/29/2007 10:16:59.119 productcode = {69880C00-08DD-4385-B752-9C62656F6D1E}
03/29/2007 10:16:59.119 qfelevel = 2004
03/29/2007 10:16:59.119 sp = -1
03/29/2007 10:16:59.119
03/29/2007 10:16:59.119 Product Enumeration Results:
03/29/2007 10:16:59.119 INF File Name: D:InstallsHotFixSQLServer2005_BC_x64.inf
03/29/2007 10:16:59.119 baselinebuild = 1399
03/29/2007 10:16:59.119 build = 2004
03/29/2007 10:16:59.119 description = Backward Compatibility
03/29/2007 10:16:59.119 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
03/29/2007 10:16:59.119 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.135 kbarticle = KB921896
03/29/2007 10:16:59.135 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.135 lcid = 1033
03/29/2007 10:16:59.135 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
03/29/2007 10:16:59.135 machinetype = x64
03/29/2007 10:16:59.135 package = HotFixSQLServer2005_BC_x64
03/29/2007 10:16:59.135 packagetype = Hotfix
03/29/2007 10:16:59.135 productname = Redist9
03/29/2007 10:16:59.135 recommendinstall = 1
03/29/2007 10:16:59.135 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.135 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.135 splevel = 2
03/29/2007 10:16:59.135 supportdir = D:Installs
03/29/2007 10:16:59.135 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
03/29/2007 10:16:59.135 version = 9
03/29/2007 10:16:59.135
03/29/2007 10:16:59.135 File Group Details: MSI
03/29/2007 10:16:59.135 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.135 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.135 File Details: SQLServer2005_BC_x64.msi
03/29/2007 10:16:59.135
03/29/2007 10:16:59.135 Product Enumeration Results:
03/29/2007 10:16:59.135 INF File Name: D:InstallsHotFixSqlWriter.inf
03/29/2007 10:16:59.135 baselinebuild = 1399
03/29/2007 10:16:59.151 build = 3042
03/29/2007 10:16:59.151 description = Microsoft SQL Server VSS Writer
03/29/2007 10:16:59.151 details = Service Pack for Microsoft SQL Server VSS Writer.
03/29/2007 10:16:59.151 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.151 kbarticle = KB921896
03/29/2007 10:16:59.151 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.151 lcid = 1033
03/29/2007 10:16:59.151 legalproductname = Microsoft SQL Server VSS Writer
03/29/2007 10:16:59.151 machinetype = x86
03/29/2007 10:16:59.151 package = HotFixSqlWriter
03/29/2007 10:16:59.151 packagetype = Hotfix
03/29/2007 10:16:59.151 productcode = {E9F44C98-B8B6-480F-AF7B-E42A0A46F4E3}
03/29/2007 10:16:59.151 productname = Redist9
03/29/2007 10:16:59.151 recommendinstall = 1
03/29/2007 10:16:59.151 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.151 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.151 splevel = 2
03/29/2007 10:16:59.151 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/29/2007 10:16:59.151 supportdir = D:Installs
03/29/2007 10:16:59.151 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
03/29/2007 10:16:59.151 version = 9
03/29/2007 10:16:59.151
03/29/2007 10:16:59.151 File Group Details: MSI
03/29/2007 10:16:59.166 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.166 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.166 File Details: SqlWriter.msi
03/29/2007 10:16:59.166
03/29/2007 10:16:59.166 Instance Details: Microsoft SQL Server VSS Writer
03/29/2007 10:16:59.166 fullversion = 9.00.3042.00
03/29/2007 10:16:59.166 lcid = 1033
03/29/2007 10:16:59.166 productcode = {E9F44C98-B8B6-480F-AF7B-E42A0A46F4E3}
03/29/2007 10:16:59.166 qfelevel = 3042
03/29/2007 10:16:59.166 sp = -1
03/29/2007 10:16:59.166
03/29/2007 10:16:59.166 Product Enumeration Results:
03/29/2007 10:16:59.166 INF File Name: D:InstallsHotFixSqlWriter_x64.inf
03/29/2007 10:16:59.166 baselinebuild = 1399
03/29/2007 10:16:59.166 build = 3042
03/29/2007 10:16:59.166 description = Microsoft SQL Server VSS Writer
03/29/2007 10:16:59.166 details = Service Pack for Microsoft SQL Server VSS Writer.
03/29/2007 10:16:59.166 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/29/2007 10:16:59.166 kbarticle = KB921896
03/29/2007 10:16:59.166 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/29/2007 10:16:59.166 lcid = 1033
03/29/2007 10:16:59.166 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
03/29/2007 10:16:59.166 machinetype = x64
03/29/2007 10:16:59.182 package = HotFixSqlWriter_x64
03/29/2007 10:16:59.182 packagetype = Hotfix
03/29/2007 10:16:59.182 productname = Redist9
03/29/2007 10:16:59.182 recommendinstall = 1
03/29/2007 10:16:59.182 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/29/2007 10:16:59.182 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/29/2007 10:16:59.182 splevel = 2
03/29/2007 10:16:59.182 supportdir = D:Installs
03/29/2007 10:16:59.182 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
03/29/2007 10:16:59.182 version = 9
03/29/2007 10:16:59.182
03/29/2007 10:16:59.182 File Group Details: MSI
03/29/2007 10:16:59.182 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/29/2007 10:16:59.182 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/29/2007 10:16:59.182 File Details: SqlWriter_x64.msi
03/29/2007 10:16:59.182
03/29/2007 10:17:27.916 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
03/29/2007 10:17:27.916 Registry: Cannot read registry key value "PendingFileRenameOperations"
03/29/2007 10:17:27.931 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
03/29/2007 10:17:27.947 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
03/29/2007 10:17:41.838 Registry: Set registry key value "EnableErrorReporting", DWORD value = 1
03/29/2007 10:17:41.838 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
03/29/2007 10:17:41.884 Locked file: Checking for locked files
03/29/2007 10:17:45.744 Locked file: C:Program Filesmicrosoft sql server90dtsinnmsdtssrvr.exe (MsDtsServer [MsDtsSrvr.exe] - 8060)
03/29/2007 10:53:18.873 Locked file: Checking for locked files
03/29/2007 10:53:26.482 Attempting to pause the 32 bit ngen queue
03/29/2007 10:53:27.294 Installing product: NS9
03/29/2007 10:53:27.294 Installing instance: NS
03/29/2007 10:53:27.310 Installing target: BPATLQQDW
03/29/2007 10:53:27.310 Installing file: sqlrun_ns.msp
03/29/2007 10:53:27.326 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixNS9_Hotfix_KB921896_sqlrun_ns.msp.log
03/29/2007 10:53:27.326 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
03/29/2007 10:53:27.326 Registry: Cannot read registry key value "Debug"
03/29/2007 10:53:27.873 MSP returned 1612: The installation source for this product is not available. Verify that the source exists and that you can access it.
03/29/2007 10:53:27.873 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
03/29/2007 10:53:27.873 Registry: Cannot read registry key value "Debug"
03/29/2007 10:53:27.888 Copy Engine: Error, unable to install MSP file: D:InstallsHotFixNSFilessqlrun_ns.msp
03/29/2007 10:53:27.888 The following exception occurred: Unable to install Windows Installer MSP file Date: 03/29/2007 10:53:27.888 File: depotsqlvaultstablesetupmainl1setupsqlsesql

View 1 Replies View Related

Am Unable To Access SSIS Even Though The Service Is Up And Running.

Nov 13, 2007

I've lost access to SSIS and BIDS.

I'm a SQL 2005 developer DBA with a 1.5 years experience with SQL Server 2005. It has been a while since I needed to use SSIS. I used it with no problems earlier this year when I was managing the team conversion to SQL Server 2005. Now it no longer appears on my START > Programs > SQL Server 2005 menus. I had to reinstall SQL Server 2005 and Visual Studio 2005 months ago and must have lost it then some how.

How do I get access to BIDS and SSIS again?

SQL Server Integrated Services shows up in my Services list as running.
I've already tried Add/Remove Programs to drop that component from SQL Server 2005, reboot, Add it back, reboot. Still does not show up in my menus and the Service is running. The Setup Bootstraplog summary for this effort shows no failures and shows this:

Product : Microsoft SQL Server 2005 Integration Services
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0021_xxxx-xxxx_DTS.log


My SQL Server level is 9.0.3054. The About Info is:

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600


My Visual Studio About Info is:
Microsoft Visual Studio 2005
Version 8.0.50727.762 (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0096213-41845
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0096213-41845
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0096213-41845
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0096213-41845
Microsoft Visual J# 2005
Microsoft Visual Web Developer 2005 77626-009-0096213-41845
Microsoft Visual Web Developer 2005
Microsoft Web Application Projects 2005 77626-009-0096213-41845
Microsoft Web Application Projects 2005
Version 8.0.50727.762
Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1 (KB926601)
Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB937061)

Also, in case it is relevant, I've NEVER installed SQL Server Express or had it installed.
When I reinstalled, I installed SQL Server 2005 before VS 2005 since I know that has caused problems with some people.

Please help me get SSIS and BIDS access again.

Thanks,
Paul

View 6 Replies View Related

Executing Multiple SSIS Packages

Apr 24, 2008

I am trying to execute around 3 SSIS packages using Execute package task by having all the 3 in one SSIS package,
I am getting the below error:
Error: Error 0xC001000A while preparing to load the package.
The specified package could not be loaded from the SQL Server database. .

Can I use Execute package task for this purpose??

Thanks!!

View 4 Replies View Related

Run Multiple SSIS Packages In Order

Sep 21, 2006

I built 3 diffrent packages and i want to be executed in order. The first one is exporting some tables to another database and the other two packages are based on the database built in the first package.

Any suggestions?

Thank you in advance:)

View 6 Replies View Related

Executing Multiple SSIS Packages

Apr 24, 2008

I am trying to execute around 3 SSIS packages using Execute package task by having all the 3 in one SSIS package,
I am getting the below error:
Error: Error 0xC001000A while preparing to load the package.
The specified package could not be loaded from the SQL Server database. .
Then I did the following:
1. Right click on MSDB
2. Import package
Inside Import package window:
Package location: SQL Server
Server: servername
authentication: windows authen
Package path: \serverC$folder1SSIS Packagesfolder2
Import package as:
Package name: package.dtsx
Below is the error I am getting:
TITLE: Import Package
------------------------------
Cannot find folder "\serverC$folder1SSIS Packagesfolder2".
Can I use Execute package task for this purpose??
Thanks!!

View 12 Replies View Related

SSIS Script For Windows Service Monitoring

May 24, 2006

Hi

I would like to use SSIS Script for Monitoring Windows Service...

If Windows Service Up / Down. I should be able to Notified by

Using SSIS Script(SQL SERVER 2005).

Please Help me

Thanks & Regards
Deepu M.I

View 1 Replies View Related

SSIS Script For Monitoring Windows Service

May 25, 2006

I would like to use SSIS Script for Monitoring Windows Service...

If Windows Service Up / Down. I should be able to Notified by

Using SSIS Script(SQL SERVER 2005).

Please Help me

View 5 Replies View Related

Execute SSIS Package Through ASP.NET Web Service - Different Problem

Aug 22, 2007

Hi all,

There was already several posts about executing packages programmatically from the context of Web Services. I have decided to follow Web Service approach because we were already calling packages programmatically through .NET. So far I have been able to clear all security configuration obstacles as I am able to load package and call Execute but mysteriously package doesn€™t execute. I am reading StopTime, StartTime and ExecutionDuration properties after call to Execute and evidently package doesn€™t execute because StartTime and EndTime are identical and ExecutionDuration is 0 but no error is raised or logged anywhere but package return status is failure)!

We are using SQL Server 2005 with Service Pack 2 on Windows 2003 R2 Enterprise, .NET Framework 2.0. The Domain Account that has Admin privileges on both servers is calling Web Service. DefaultAppPool uses Network Service and Anonymous access is enabled. Network Service is also member of the sysadmin role.

I am sure root of the problem is still in the Security but I am not getting any clue because of lack of any error. Does anyone has any suggestion? Thanks in advance.

Sinisa Catic

View 4 Replies View Related

Execute A Stored Procedure Which Calls SSIS Packages Using A Proxy Account For Non Sysadmins In Sql Server 2005

Sep 18, 2007



Hi all,
I have a problem while i create a proxy account.The situation is like this...There is a user who has an login in to the server.He has a stored procedure which calls some on the SSIS packages and XP_cmdshell...so this stored procedure basically load some data in to the tables .So for the login in order to execute the stored procedure as he is not a Sys admin I have created a proxy account in my account as Iam an SA and then in the proxies and in principals I selected his login name and this way I have created a credential and a proxy account.

Now the problem is if he logins with his id and password and try to execute the stored procedure it gives an error message

Server: Msg 15153, Level 16, State 1, Procedure xp_cmdshell, Line 1
The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '##xp_cmdshell_proxy_account##' credential exists and contains valid information.


....so this mean the login is not able to see the proxy account.So what I did is I created a job and then in the job owner tab I have selected his login and then created a step with the type operating system (CmdExec) as I need to just execute the stored procedure and used the proxy account that I have created.

so I gave the command -- exec <stored procedure> --.
But this job fails and gives the error message as
[298] SQLServer Error: 536, Invalid length parameter passed to the SUBSTRING function. [SQLSTATE 42000]....

So now ....first My question is am I doing in a right way....if its right then why Iam not able to execute the stored procedure.

If there is any other way through which I can execute the stored procedure using a proxy account for the logins who are not sys admins....please do let me know.....

Thanks
Raja.V

View 2 Replies View Related

SSIS SQL 2005 Script Task For Windows Monitoring Service

May 26, 2006

Hi

Does any body knows how to convert this VBScript Code to VBDotNet (SQL SERVER 2005 INTEGERATION). Below Codes Returns a list of all the services installed on a computer, and indicates their current status (typically, running or not running).Its in VBScript Format.


strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\" & strComputer & "
ootcimv2")

Set colRunningServices = objWMIService.ExecQuery("Select * from Win32_Service")

For Each objService in colRunningServices
Wscript.Echo objService.DisplayName & VbTab & objService.State
Next


Regards
Deepu M.I

View 4 Replies View Related

How To Execute Multiple Queries In Ssis?

Jan 26, 2007

Hi there,

I am new to ssis.I need to execute multiple queries to update number of tables in sqlserver.Pleasesuggest me the right way to do this.



Thanks in Advance.

Regards

Vinod

View 4 Replies View Related

How To Change Windows Auth. To SQL Server Auth. In SSIS Packages

Apr 30, 2007

I had a few packages created with Windows Authentication which now needs to be migrated to run with SQL Server Authentication. I tried changing it in the connection managers but the packages failed to validate at the SCD transformations.For a few packages I had Configuration files for these packages where i tried to do it but it dint run giving the following Error Message:
[Connection manager "Target"] Error: An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user <<with my network id>>.".

[Execute SQL Task] Error: Failed to acquire connection "Target". Connection may not be configured correctly or you may not have the right permissions on this connection.

Target was the name of my connection.

View 1 Replies View Related

Unable To Connect To SQL SERVER 2005 Database Engine Using Windows Authentication Under Windows Vista...

Mar 26, 2008

Hallo there,

I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.

My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.

I enabled all the protocols and all the ports
I disabled windows firewall and antivirus (eset nod32)
I installed all service packs available
I have also installed Visual Studio 2005 without installing sqlexpress

But nothing happens!

Please i am very desperate, any information will be gratefully accepted.

This is my installation Information



Code Snippet

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.6001.18000
Microsoft .NET Framework 2.0.50727.1434
Operating System 6.0.6001


Thank you in advance,
Patonios


View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved