SSIS Unable To Parse ADO.NET Query
Mar 29, 2007
Although I am able to connect to a SQL 2005 server (both through the SQL Management Studio and through the connection wizard in Visual Studio 2005), I am unable to parse a query if I use a connection set up as ADO.NET. When I use OLE-DB, it works properly. When I attempt to execute a SQL task (comprised of a single SELECT statement), I get "Failed to acquire connection 'servernamegoeshere'. Connection may not be configured correctly or you may not have the right permissions on this connection." How can this be if I'm able to parse data from this connection through other means? This happens both locally and remotely.
View 17 Replies
ADVERTISEMENT
Apr 5, 2006
i am executing an sql statement in sql server 2005 express edition. It says it is unable to parse the query then automatically re-arranges the sql text and then it is able to parse it and return me the result. my query is this: What am I doing wrong?
IF NOT EXISTS (SELECT MemberID, HotelID FROM tblHotels_Reviews WHERE MemberID = 3 AND HotelID = 3) BEGIN INSERT INTO tblHotels_Reviews(MemberID, HotelID, ReviewTitle, StayMonth, StayYear, Satisfaction, PricePerNight, ValueForMoney, CheckIn, FoodDining, BusinessFacilities, SafetySecurity, Rooms, StaffService, HotelFacilities, CheckOut, SuitableFor, Atmosphere, DoYouRecommend, Review, Anonymous, HasPhotos, ReviewDate, ReviewLanguage, PublishStatus)VALUES (6, 3, 'hello', 'January', 2002, 5, 234, 5, 5, 5, 5, 5, 5, 5, 5, 5, 'Singles,Couples', 0, 1, 'helloo', 0, 0, '06/04/2006', 'EN', 0) SELECT 1 AS RESULT END ELSE BEGIN SELECT 0 AS RESULT END
View 3 Replies
View Related
Feb 26, 2008
SELECT SID, SAmAccountName, DOMAIN, EmployeeID, CustAtr, DisplayName, UPN, Date, flag, Date_Mod, Date_Exp, IsActive, OU, Description, IDType
FROM dbo.CORP_EMP_IDS as corp_emp_ids
WHERE (EmployeeID BETWEEN 'A' AND 'Z') AND (IsActive = 1) AND (EmployeeID NOT IN ('gen', 'G', 'M', 'S', 'T', 'TT', 'AdminAcct', 'TestAcct', 'ConfRoom', 'AcctAdmin')) AND (Date_Exp > GETDATE() OR
Date_Exp = '') AND (SAmAccountName NOT LIKE '%$%')
UNION
SELECT SID, SAmAccountName, DOMAIN, EmployeeID, CustAtr, DisplayName, UPN, Date, flag, Date_Mod, Date_Exp, IsActive, OU, Description, IDType
FROM dbo.CORP_EMP_IDS AS CORP_EMP_IDS_1
WHERE (CustAtr BETWEEN 'A' AND 'Z') AND (IsActive = 1) AND (CustAtr NOT IN ('gen', 'G', 'M', 'S', 'T', 'TT', 'AdminAcct', 'TestAcct', 'ConfRoom', 'AcctAdmin','AdminAccts')) AND (Date_Exp > GETDATE() OR
Date_Exp = '') AND (SAmAccountName NOT LIKE '%$%')
ORDER BY EmployeeID
View 11 Replies
View Related
May 18, 2006
I've got some machines that output text files after each shot of parts. I'd like to take the data in those files and parse it and insert it into a SQL Server database for future massaging. The text files look like the example I've posted below. Can SSIS parse out the set points and actual values even though the file isn't CSV or tab delimited and the data is kind of 'strewn' all over the report? Each report does have the exact same format so the report format doesn't change from report to report, just the data. Thanks in advance.
Ernie
WP4.57 C Y C L E P R O T O C O L
Order data 18.05.06 11:27:57
Order number : 2006 Recipe no. : 15761
Machine number : 7 Recipe name : Stabilizer Bar Innsulator
Machine Operator: 1257 Art.descrip.: Stabilizer Bar Grommet
Shot Volume : 285.8
Part quantity : 100096 Type of mat.: M370-34
Shot quantity : 782 Batch number: 20124-125
-------------------------------------------------------------------------------
Temperatures in øC
Set Act Set Act
Fixed heat.platen right 182 182 Tempering screw 83 83
middle 180 180 Tempering inject.cylinder 85 85
left 182 182 Tempering circuit 3 90 91
Tempering circuit 4 0 39
Movab.heat.platen right 182 182 Tempering circuit 5 0 39
middle 180 180
left 182 182 Mould temperature 1 0 39
Mould temperature 2 0 39
Third heat.platen right 0 39 Mould temperature 3 0 39
middle 0 39 Mould temperature 4 0 39
left 0 39 Mould temperature 5 0 39
Mould heating circuit 6 0 39 Compound temp.after screw 104 104
Mould heating circuit 7 0 39 Compound temp.after nozzle 0 39
Mould heating circuit 8 0 39
Mould heating circuit 9 0 39
Mould heating circuit 10 0 39
---------------------------------------------------------------------------
Times in sec
Injection time 51.20 Transfer time 1 2.00
Internal mould press.time 0.00 Transfer time 2 2.00
Dwell pressure time 7.00 Transfer time 3 2.00
Controlled cure time 180.00 Transfer time 4 2.00
Calculated cure time 0.00 Transfer time 5 2.00
last cycle time 276
last opening time 25
---------------------------------------------------------------------------
Measure when injecting Measure at injection end
max. injection speed mm/s 11.9 Injection length mm 2.0
Injection energy kNm 247.2 Injection time sec 51.20
max. int.mould pres. bar 2 Hydraulic pressure bar 190
max. dwell pressure bar 192 Internal mould pressure bar 0
Pad mm 0.4
---------------------------------------------------------------------------
Stock Temperatures and Pressures During Metering
Stock Temperatures(C) Set Actual Metering Pressures(bar) Set Actual
Temperature 1st Step 105 106 Pressure 1st Step 135 131
Temperature 2nd Step 105 106 Pressure 2nd Step 135 129
Temperature 3rd Step 105 105 Pressure 3rd Step 135 122
Temperature 4th Step 105 106 Pressure 4th Step 135 135
Temperature 5th Step 105 109 Pressure 5th Step 135 137
Protocol Complete
View 1 Replies
View Related
Jun 7, 2002
I create a Execute SQL Task and Load a stored procedure into the "SQL Statement" box. This stored procedure has many 'go' words and many commented lines either with '--' mark or '/*' or '*/' mark.
When Parse Query, get Package Error "Deferred prepare could not be completed. Statements could not be prepared".
But I could run the same proc under the isql/w with no problem.
How could I deal with this error? Though it looks the execution of the package still run successful. The Parsing just create uncertainty.
thanks
David
View 2 Replies
View Related
Feb 11, 2008
I am getting a pain in the butt error in DTS.
If I use and Execute SQL Task like this ...
------------------------------------
DECLARE @VAR
SET @VAR = ?
EXEC sp_Test @VAR
------------------------------------
and then click parse query I get an error "Syntax error or Access violation"
However; if I use it this way
------------------------------------
EXEC sp_Test ?
------------------------------------
it works.
Now here is the odd thing. If I put in a DECLARE statement and a global parameter "?" I get the syntax error.
But .... If I use a disconnected edit and use DECLARE and "?" then task will run properly. So the problem seems to be with the query parser.
The problem is I don't have the time to edit everything in a disconnected manner. Is there a way or update that will allow me to use DECLARE and "?". I have tried many hotfixes but none have worked.
View 2 Replies
View Related
Nov 24, 2014
I have a table that is something like this:
Animal | Count
Dog |10
Dog |5
Dog |16
Dog |2
Cat |1
Cat |12
Cat |14
Cat |7
I need to write a query that will return something like this:
Dog_Count| Cat_ Count
10 |10
5 |5
16 |16
2 |2
View 4 Replies
View Related
Nov 13, 2007
Receive this error msg when trying to parse a SQL Query
.Net SqlClient Data Provider: Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
I have just finished going thru a long process getting SP2 CU3 patch installed.
The first file microsoft sent was corrupted and in turn corrupted my .NET Framework, had to run repair on the Framework before installing CU3.
I am now on version 9.0.3186. I have two other boxes with the same version and do not have this problem
My understanding is that all of the patches/hotfixes since SP,1 that this problem was resolved
Any help will be greatly appreciated as I am in a very heavy development stage on this box.
Thanks
Greg
View 1 Replies
View Related
Feb 2, 2006
I have a table where different types of values are stored in one field, but I need to seperate them into different fields based on a value in another field.
For (hypothetical) example:
There is an existing table with following info in three columns:
userid record recordtag
1 joe 1
1 j 2
1 jr 3
2 bob 1
2 a 2
2 sr 3
where recordtag indicates (1 for first name, 2 for middle initial, 3 for suffix)
I need to query these records for a report so it the output is:
userID firstname middleinitial suffix
1 joe j jr
2 bob a sr
What's the most efficient approach to create a query that will give me desired results? I have managed to create a very complex query that derives tables for each column I want to create and queries off of that derived table for the 'record' value based on the 'recordtag' values for a given 'userid'. The query is extremely slow, so I know there's some better way out there to get the results I want. Any help would be greatly appreciated. Thanks.
View 3 Replies
View Related
Sep 14, 2007
Hi
I am having a huge xml file with nested section.
i also have a xsd file for that xml.
i have a destination table where the data from the xml should be loaded into.
i am using the xml source transformation. But o get all the data i need to use multiple merje joins to get the data in a single row which i can insert into the destination.i was not quiet convinced with using so many joins.
so i tried using the script source transformation where i am using xml objects to get the node and dynamically construction the data row. and the output is then inserted into the destination.
on comparing the two approach the one using the script source is working much faster than the xml source transformation.
i wanted to know is there any limitaion using the script source to parse through xml files.
also i would like to know any other better way of getting the data from xml source without using the joins.
Hari
View 7 Replies
View Related
May 20, 2008
HI,
I am unable to connect SSIS using Sql Server Management Studio.The fallowing error is getting.
TITLE: Connect to Server
------------------------------
Cannot connect to GDC-101.
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine "GDC-101" failed:
The specified service does not exist as an installed service.
.
------------------------------
Connect to SSIS Service on machine "GDC-101" failed:
The specified service does not exist as an installed service.
.
------------------------------
BUTTONS:
OK
------------------------------
Can Any one help me.
Regards
Sith.
View 3 Replies
View Related
Aug 27, 2007
I (actually my DBA did it) have created an SSIS package in MS SQL Server 2005. It can be found under Integration Services under:
Stored Packages
MSDB
VisBridges
ExportTime
Using the Execute Package Utility, it runs perfectly.
I used the article at http://msdn2.microsoft.com/en-us/library/ms403355.aspx to build an application to run it.
My code includes the following (written in VB.Net):
a Web Service Function called LaunchPackage:
Public Function LaunchPackage(ByVal sourceType As String, _
ByVal sourceLocation As String, _
ByVal packageName As String) As Integer ' DTSExecResult
Dim packagePath As String
Dim myPackage As New Package()
Dim integrationServices As New Application
' combine path and file name
packagePath = Path.Combine(sourceLocation, packageName)
Select Case sourceType
Case "file"
' package is stored as a file.
' add extension if not present.
If String.IsNullOrEmpty(Path.GetExtension(packageName)) Then
packagePath = String.Concat(packagePath, ".dtsx")
End If
If File.Exists(packagePath) Then
myPackage = integrationServices.LoadPackage(packagePath, Nothing)
Else
Throw New ApplicationException("Invalid file location: " & packagePath)
End If
Case "sql"
' Package stored in MSDB.
' Combine logical path and package name.
If integrationServices.ExistsOnSqlServer(packagePath, <servername>, <UserID>, <password>) Then
myPackage = integrationServices.LoadFromSqlServer(packageName, <servername>, <UserID>, <password>, Nothing)
Else
Throw New ApplicationException("Invalid package name or location: " & packagePath)
End If
Case "dts"
' package is managed by SSIS Package Store.
' Default logical paths are File System and MSDB.
If integrationServices.FolderExistsOnDtsServer(packagePath, <servername>) Then
myPackage = integrationServices.LoadFromDtsServer(packagePath, <servername>, Nothing)
Else
Throw New ApplicationException("Invalid package name or location: " & packagePath)
End If
Case Else
Throw New ApplicationException("Invalid sourceType argument: valid values are 'file', 'sql', and 'dts'.")
End Select
Return myPackage.Execute()
End Function
My TestPage includes the following:
Protected Sub btnSubmit_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles btnSubmit.Click
Dim launchPackageService As New LaunchSSISPackageService
Dim packageResult As Integer
Dim sourceType As String = "dts"
'Dim sourceLocation As String = "M:mssqlssiconfig" ' for "file"
'Dim sourceLocation As String = "MSDBVisBridges" ' for "sql"
Dim sourceLocation As String = "VisBridges" ' for "sql & dts"
'Dim sourceLocation As String = "MSDB"
If rdoCreateTimeTrans.Checked Then
Try
packageResult = launchPackageService.LaunchPackage(sourceType, sourceLocation, "ExportTime")
Catch ex As Exception
Response.Write("The following exception occurred: " & ex.Message)
End Try
End If
End Sub
I've tried both "sql" and "dts" with all the various permutations that are listed (and commented out) above. I either get an error that says:
The top level folder "VisBridges" is not found. ("dts" "VisBridges") -- or --
Invalid package name or location: MSDBVisBridgesExportTime ("dts" "MSDBVisBridges") -- or --
Cannot find folder "MSDBVisBridgesExportTime" ("sql" "MSDBVisBridges") -- or --
The specified package could not be loaded from the SQL Server database ("sql" "VisBridges")
Any assistance would be greatly appreciated.
Many thanks,
Michell
View 6 Replies
View Related
Aug 1, 2006
Hi,
I've created a new SSIS package and am trying to run it as a sqlagent job. If I 'Run as' the 'SQLSERVER AGENT' account I get 'Executed as user: domainadministrator. The package execution failed. The step failed'. If I change this to 'Run as' 'sql agent service account' I get the following message 'Executed as user: [[servername]SYSTEM. The package execution failed'. The step failed.
I can successfully run the package in visual studio, management studio and via the command prompt.
Presumably it is a permissions problem?? I've tried setting up the logging but nothing was written to the log when I run the job, there is otherwise(via Visual studio). I've also tried the following http://support.microsoft.com/kb/918760, but it made no difference.
Anybody else experienced anything similar?
Thanks,
Paul
View 3 Replies
View Related
Oct 10, 2007
Hi,
I get the following error opening an existing (or working) ssis package on my new server.
Error loading 'TestExecutionFromScript.dtsx' : Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}' failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))..
I found in a blog that this is caused due to a dll which is not registered ("DTS.dll")
Can anyone try to explain the exact reason for this? I am not even able to execute a package from the command prompt using the dtexec utility. I have "Microsoft SQL Server Analysis Services Designer Version 9.00.3042.00" on my server. My other machine which executed this package successfully was running "Microsoft SQL Server Analysis Services Designer Version 9.00.1399.00".
Thanks very much for any kind of help.
View 3 Replies
View Related
May 21, 2008
I am trying to access Cube through SSIS and have been unable to set SSIS package with the work around provided here (https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=219068). On pasting the MDX query using the openrowset command on the OLEDB source editor, I get a pop up window with error 0x08000405 and the message that says 'syntax used for openrowset is incorrect'
I also tried running this on SQL Management studio but, get the following error.
OLE DB provider "MSOLAP" for linked server "(null)" returned message "An error was encountered in the transport layer.".
OLE DB provider "MSOLAP" for linked server "(null)" returned message "The peer prematurely closed the connection.".
Msg 7303, Level 16, State 1, Line 3
Cannot initialize the data source object of OLE DB provider "MSOLAP" for linked server "(null)".
The server where the cube resides is on 64bit machine and I have 32-bit..could this be the reason for the issue?
I found this article on microsoft support website (http://support.microsoft.com/kb/947512 ) which describes the possible symptoms and causes for connectivity issues But, couldn't find a work around for it.
Here is the syntax of the query I am using in SSIS and query analyser
SELECT * FROM
OPENROWSET('MSOLAP', 'Integrated Security=SSPI;Persist Security Info=True;Data Source=<SERVERNAME>; Initial Catalog=<Catalog name>;'
,
'MDX Query') AS Rowset_1
Any help with this issue is appreciated!
Thanks,
View 1 Replies
View Related
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
Apr 16, 2007
Hi all,
I have created an SSIS package with protection level - EncryptSensitiveWithUserKey. It is running alright from Visual Studio Environment but i need to call the package from an application, so i created a stored proc to call it, but getting the following error while running the stored proc:
Error: 2007-04-16 17:55:05.78
Code: 0xC0016016
Source:
Description: Failed to decrypt protected XML node "DTSassword" 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
any solution?
View 1 Replies
View Related
Mar 14, 2007
Hi,
I€™m using a Script Component in SSIS to call a Web Service. The web service is wrapped, using the wsdl tool. The package works, on my local enviroment. Script component calls the web service and returns the data. I€™ll move the web service to another server, web service as Anonymous access is enable. Deployed the Package on a SQL server. But, when excuting the package I get the below error. I can view and invoke the web method and see data even. SSIS is running under a NT AUTHORITYNetworkService account. I know that the problem is permission, but how would I resolve the issue.
Error:
OnInformation,SERVER,DOMAINSqlAdmin,MISPackage,{190832FB-4FF1-4ECD-BF53-4A49864089B4},{D7BF27CD-BDF1-418A-ABFE-BA0A24B921FB},3/14/2007 10:59:11 AM,3/14/2007 10:59:11 AM,0,0x,System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at ScriptComponent_6386cd9eab6a49e7b1a90f69dcc24beb.Service.GetMISAccounts()
at ScriptComponent_6386cd9eab6a49e7b1a90f69dcc24beb.ScriptMain.CreateNewOutputRows()
Any Help will be appreciated
View 1 Replies
View Related
Mar 15, 2006
I have developed a SSIS dts package, its running fine from my computer, but the problem is when I am deploying it on actual server then giving me error for connection
scenario,
development env: dev006
three servers: srv01 (64bit), srv02 (32bit), srv03 (32bit)
in development environment, same package is getting data from srv01 and pushing it to srv02 and srv03, but when i am deploying it on srv01 then it fails to establish connection with srv01. If I have a Business Intelligence Studio on 64bit then I will check it but that Studio is available for 64bit environments.
View 1 Replies
View Related
Mar 24, 2008
I am receiving the following error when attempting to create a new package in SSIS 2005. I have completeley re-installed, and even had our support folks re-image my pc, but no luck. Works fine on my laptop, and others are not having any issues.
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.
Any help would be greatly appreciated. Thanks, Bryan
View 6 Replies
View Related
Nov 3, 2015
I am trying to connect to a Web page from SSIS and I've tried both http connection manager and a Script Task but none of them seems to be working.
I get the following errors:
Through Script Component: Exception has been thrown by the target of an invocation.
Through http connection manager: The remote server returned an error: (503) Server Unavailable.
Here is one of the VB code I've tried:
Public Sub Main()
Dim MyWebClient As New System.Net.WebClient()
Dim proxyObject As New System.Net.WebProxy("BANANA:8080", True)
MyWebClient.Proxy = proxyObject
[Code] ....
And, here is one of the C# codes I've tried:
public void Main()
{
Variables varCollection = null;
Dts.VariableDispenser.LockForRead("User::RemoteUri");
Dts.VariableDispenser.LockForRead("User::LocalFolder");
Dts.VariableDispenser.GetVariables(ref varCollection);
varCollection.Unlock();
[Code] ...
I could open the same web page mentioned in the code manually in all my browsers (IE, Firefox, Chrome).
I am using SQL Server 2014.
View 18 Replies
View Related
May 16, 2008
I've created a SSIS package with a DataReaderDestination and a SSRS report that points to it.
I referenced these links during development and I have everything working as expected locally. **I changed the config files as stated on both my local machine and our server. My config matches the example exactly.
http://msdn.microsoft.com/en-us/library/ms345250.aspx
http://msdn.microsoft.com/en-us/library/ms159215.aspx
When I attempt to deploy my report project to the server I get this error message:
"An attempt has been made to use a data extension 'SSIS' that is not registered for this report server."
In the report manager data source properties page it reads:
"The data processing extension used for this report is not available. It has either been uninstalled, or it is not configured correctly."
In SQL Server Management Studio data source properties page SSIS is not a data source type option.
I've tried restarting both the Reporting Services and Integration Services on the server to no avail.
Any suggests? My problem is I can't get the SSIS to be recognized source on the server.
View 1 Replies
View Related
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
Apr 22, 2015
I have a little problem with my IS Server.I am using IS 9.0.1399 (SSIS 2005).I have one instance for databases.I am able to connect to Integration Services just with the Servername (no Instance Name) and I see the folders in there.When I try to open the MSDB Folder (under "Stored Packages") I get the following exeption:
"Login timeout expired/An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.SQL Network Interfaces: Connection string is not valid [87]."
View 3 Replies
View Related
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
View Related
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
Oct 24, 2007
Hi,
I am using SQL Server Destinations in my data flow tasks. I'm running this package in the server until i encountered this error:
OnError,,,LOAD AND UPDATE Dimension Tables,,,10/24/2007 1:22:23 PM,10/24/2007 1:22:23 PM,-1071636367,0x,Unable to prepare the SSIS bulk insert for data insertion.
OnError,,,Load Dimensions,,,10/24/2007 1:22:23 PM,10/24/2007 1:22:23 PM,-1071636367,0x,Unable to prepare the SSIS bulk insert for data insertion.
OnError,,,Discount Reason, ISIS Condition, ISIS Defect, ISIS Repair, ISIS Section, ISIS Symptom, Job Status, Parts, Purchase SubOrder Type, Service Contract, Service Reason, Service Type, TechServiceGrp, WarrantyType, Branch, Wastage Reason,,,10/24/2007 1:22:23 PM,10/24/2007 1:22:23 PM,-1073450974,0x,SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Dim_T_ISISDefect" (56280) failed with error code 0xC0202071. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
What could be the reason for this? I don't usually have an error.
cherriesh
View 6 Replies
View Related
Jul 17, 2006
We are trying to import data from a .csv file which sits on shared location. This package runs fine when we run it from designer. but we are having problem when we do it at run time (accessing it through a service). Same package runs fine if that file is on same server.
Is any one gone through this issue before? i appreciate any help in resolving this issue.
--------Log----
#Fields: event,computer,operator,source,sourceid,executionid,starttime,endtime,datacode,databytes,message
OnPreValidate,SMSPAD1125M,RFCGKommar1,GIRI_ETL_XREF,{4D456D56-B35F-4FCC-8A89-2D03AC545C76},{5395DAA0-DB96-49CA-BDE7-0DA5C623A2B0},7/17/2006 10:46:42 AM,7/17/2006 10:46:42 AM,0,0x,(null)
OnError,SMSPAD1125M,RFCGKommar1,GIRI_ETL_XREF,{4D456D56-B35F-4FCC-8A89-2D03AC545C76},{5395DAA0-DB96-49CA-BDE7-0DA5C623A2B0},7/17/2006 10:46:42 AM,7/17/2006 10:46:42 AM,-1073659875,0x,Connection "FlatFile" failed validation.
---------------------------------
Thanks,
-G
View 3 Replies
View Related
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
Oct 4, 2006
When I open up my existing SSIS project, I always get this error. Does anyone know what was wrong ?
TITLE: Microsoft Visual Studio
------------------------------
Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.IObjectWithSite'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{FC4801A3-2BA9-11CF-A229-00AA003D7352}' failed due to the following error: The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD)).
View 32 Replies
View Related
Jan 15, 2008
Having searched the forum, this one clearly has form... However beyond assisting those who have fallen at the first hurdle (i.e. forgetting/not knowing that they cannot execute the package remotely to the instance of SQL Server into which they are inserting), the issues raised by others have not been addressed. Thus I am bringing nothing new to the table here - just providing an executive summary of problems which others have run into, written about, but not received answers for.
First the complete error:
Description: Unable to prepare the SSIS bulk insert for data insertion. End Error Error: 2008-01-15 04:55:27.58 Code: 0xC004701A Source: <xxx> DTS.Pipeline Description: component "<xxx> failed the pre-execute phase and returned error code 0xC0202071. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:53:34 AM Finished: 5:00:00 AM Elapsed: 385.384 seconds. The package execution failed. The step failed.
Important points
It mostly works - It produces no error more than 9 times out of 10.
It fails on random dataflows - My package has several dataflows, (mostly) executing concurrently. Where the error occurs it does not do so on the same dataflow each time: on one run it'll fail on dataflow A whilst B,C,D and E succeed, then A-E will all succeed (and continue doing so for the next ten runs thereafter), and then the error recurs for dataflow D, with A,B,C and E all succeeding.
Hope someone has something interesting to say,
Tamim.
View 10 Replies
View Related
Jun 11, 2015
We are executing a SSIS package using a xp_cmdshell command in a SP as shown below. This package does consumes time to execute almost 90 minutes and does get executed successfully too. But the strange thing is we don't get the result in @result variable just because somehow the next sql statement after the below highlighted statement doesn't get executed at all. Â After checking execution stats for the SP using the query attached below we observed that somehow the SP vanishes out of the execution stats for the server.
 SELECT @cmd = 'dtexec /FILE "D:Program FilesMicrosoft SQL Server100DTSPackages.....PopulateReport.dtsx"'     Â
 SELECT @cmd = @cmd + ' /Decrypt T@!0er '     Â
 SELECT @cmd = @cmd + ' /set package.variables[vAppID].Value;' + CONVERT(VARCHAR(10),@appId)     Â
 SELECT @cmd = @cmd + ' /set package.variables[vDBName].Value;' + '"' + @db + '"'     Â
 SELECT @cmd = @cmd + ' /set package.variables[vBuildMFF].Value;' + CONVERT(VARCHAR(10),@BuildMFF)     Â
Â
[code]....
View 6 Replies
View Related
Apr 18, 2008
This is a simple problem. I just don't know how to fix it.
I want to print out the item that I am fetching in my cursor. look at line 12 below. My value is not being printed out. Does anyone know why?
1 DECLARE @mycur1 CURSOR2. DECLARE @InMarketId INT3. SET @InMarketId=5754. DECLARE @test VARCHAR(10)5. SET @mycur1 = CURSOR
6. FOR7. SELECT SubDivisionId FROM SubDivision WHERE MarketId=@InMarketId8. OPEN @mycur19. FETCH NEXT FROM @mycur1 INTO @test10. WHILE @@FETCH_STATUS = 0 11. BEGIN -- Delete from SubDivivisionSubMarket where SubDivisionId=@test12. PRINT @test 13. FETCH NEXT FROM @mycur1 INTO @test14. END15. DEALLOCATE @mycur1
View 1 Replies
View Related
