SQL Server 2005 Integration Services Installation Guide
Sep 8, 2006
Hi, all,
Thank you very much for your kind attention.
Would please any here give me any advices for where can I find the SQL Server 2005 Integration Services Installation Guide? The one I found online (http://msdn2.microsoft.com/en-us/library/ms143506.aspx) is just confused me, which is just about the installation of SQL Server 2005 different version.
Really need help for that.
With best regards,
Yours sincerely,
View 3 Replies
ADVERTISEMENT
Apr 11, 2006
All,
Is it advisible to install SQL Server Integration Services with SQL Server Database Services or is to good to install SQL Server Integration Servies separately.
Thanks & Regards
Shri.DBA
View 1 Replies
View Related
Aug 9, 2006
hi,
after installing sp1 for sql server 2005 the sql server integration services did not start. and i can`t start them manually. the installation succeeded without problems (both sql server and sp1)
the only problem was with installing sql server 2005. in the sql server configurations manager the following protocols were disabled:
- named pipes
- tcp/ip
- via
- shared memory was enabled
is this a problem. because in the "how to verify installation of sql server" is written, that tcp/ip has to be enabled. however i can manually enable it.
i can`t start the sql server integration services manually. so what can i do? i also tried reinstall sql server but i do get the same error.
hope somebody can help me!
View 1 Replies
View Related
Mar 20, 2008
Dear All,
please provide me the complete installation guide links like
on which operating system, which version can install like that...
i've searched in google, but i'm not satisfied. please provide the link from experts side....
thank you very much
Vinod
Even you learn 1%, Learn it with 100% confidence.
View 3 Replies
View Related
Sep 4, 2006
Trying to install SQL Server 2005 on my machine,I installed each part (engine, reporting services, integration services etc) seperately.
During the installation of Integration Services I got the following message
failed to install and configure assemblies D:Microsoft SQL Server 9090DTSTasksMicrosoft.Sqlserver.MSMQTasks.dll in the COM+ catalog. Error: -2146233087
ErrorMessage: Unknown Error 0x80131501
ErrorDescription: You must have administrative credentials to perform this task. Contact your system administrator for assistance
I am administrator of my machine an i tried to install SQL usign this account.
I selected IGNORE and the installation continued. Will I have any problem with Integration Services in the future because of this error?
What is the source of this problem? How could I solve this problem?
Thank You Very Much
View 5 Replies
View Related
Sep 7, 2007
Is it possible to parm in a value to a SSIS
in my SSIS i have a variable;
Name : FileName
Scope : PackageName
Type : String
Value : ""
I have tried adding the following code in my vb.net project ;
pkg.Variables("filename").Value = "C: emp estfile.001"
pkg.execute()
but come up with the following error
A first chance exception of type 'System.MissingMemberException' occurred in Microsoft.VisualBasic.dll
Public member 'Variables' on type 'IDTSPackage90' not found.
can anyone help ?
View 11 Replies
View Related
Jan 16, 2007
Hi All,
Parameter passing in SSIS 2005 sometimes appears to be a cumbursome task. I have been digging into this topic for quite some time and here i note down some simple steps to demonstrate parameter passing at Package level.
(1) Create a SSIS project using Business Intelligence 2005 Or VS 2005.
(2) Create datasource (.ds) and Data Source View as required.
(3) A default SSIS Package by the name Package.dtsx is created. Double click this and you are shown tabs for Control Flow, Data Flow, Event Handlers, Package Explorer. On the Control Flow, drap and drop Execute SQL Task from Control Flow Items in the toolbar.
(4) Lets now create a variable at Package level. Right click anywhere in the control flow box (not on the Task created in Step 3 above). Click on the Variables on the context menu displayed. Variables window appears on the left of the screen. Click the Add Variable box in this window to create a variable. Name it var1 (or whatever you may like), Scope as Package, DataType as String and Value as MyValue. This is only the default value.
(5) Now let us edit the SQL Task created in Step 3. Double on it, on the General tab you can change its Name, Description. Set ResultSet as None. We shall proceed to execute a stored procedure by name MySPName and pass it a parameter. Set ConnectionType as OLE DB. Select the connection you creates in step 2. Set SQLSourceType as Direct input. SQLStatement as MySPName ? . Note the ? mark after the name of the stored procedure. This is important to accept the variable value (var1) created in Step 4.
(6) Select Parameter Mapping tab now. Click on Add button. Select the Variable Name as User::var1. This is the user created variable of Step 4. Select Direction as Input, DataType as Varchar and Parameter Name as @var1. Click on OK now.
(7) This sets up the basic of parameter passing. Compile the project to verify everything works. Right Click on the SQL Task and select Execute Task. This will execute the package taking default value of the variable. This can be used along with dtexec command with /set option to pass the parameter at command prompt.
View 5 Replies
View Related
Nov 27, 2006
Setup: Windows server 2003 SP1, SQL 2005 SP2, Sharepoint Office server 2007, Report Services addin (CTP v9.00.3027).
Using the Report server configuration tool, setting Report Server Virtual directory, end up with RS Configuration tool crashing.
It appears to be happening on the task "Changing Secure connection level", & returns "System.NullReferenceException was unhandled
Message: Object reference not set to an instance of an object."
any ideas?
View 6 Replies
View Related
Nov 16, 2007
While installing SQL Server 2005 Enterprise Edition on Windows Vista Ultimate
the setup alerts me "there are known compatibility problems, please
install SP2 after this". So ok, all went nice and installed without error.
IIS 7 installed fully, so all green in setup display.
(But after installation i do not see any service which begins with SQL***...)
At the end, the setup wanted to start the administration Tool.
Ok, but my name was not listed, so i could not add me to the permitted users.
I can not use any tool, because i have no rights.
Some Ideas?
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services-Clienttools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 6.0.6000.16386 (vista_rtm.061101-2205)
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.6000.16546
Microsoft .NET Framework 2.0.50727.312
Betriebssystem 6.0.6000
thanks Frank
View 6 Replies
View Related
Nov 26, 2005
I tried removing and reinstalling SQL Server 2005 Developer Edition for three times, including "all-at-once" component installation and "component-by-component" and I just can't get Integration Services to install.
View 6 Replies
View Related
May 20, 2008
When I install SQL server 2005 and select the option to have Integration Services installed, I cannot see the templates in VS 2005. Is there a way to tell if they have been installed on the harddrive? Is there any way to install them manually?
Thanks,
Carey
View 7 Replies
View Related
Jan 29, 2007
How can we Integrate SQL server 2005 Report builder, Report designer in a custom .Net Application ? . Please Help me.
I want to provide Report Designer, Report builder and Query builder functionalities to my .Net application. How can I Integrate them in my application?
View 3 Replies
View Related
Jul 11, 2006
i have 4 different databases, in each one i have a table of customers i want to combine the 4 tables of customers from the 4 databases in a new table with eliminating similar records
View 5 Replies
View Related
Jul 14, 2007
Hello - We have been unable to successfully install Integration Services with an instance of SQL 2005 running on a Windows Small Business Server 2003. Installation proceeds with no errors, but when you attempt to connect to the Integrations Services and browse to where it apparently exists, the SQL Server Managment Studio returns the following error:
TITLE: Connect to Server
------------------------------
Cannot connect to ABDI04.
------------------------------
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 "ABDI04" failed:
The specified service does not exist as an installed service.
.
------------------------------
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
------------------------------
BUTTONS:
OK
------------------------------
We have tried uninstalling the Integration Services, then reinstalling it and again applying SP2 with the same results.
Thank you.
View 17 Replies
View Related
Jun 30, 2007
Hello Everyone,
I have been banging my head against the wall with trying to integrate SharePoint 2007 and SQL Reporting Services. I have been following these 2 websites down to the letter in trying to configure everything:
1. http://msdn2.microsoft.com/en-us/library/bb326356.aspx <---Microsoft's Steps
2. http://blogs.msdn.com/sharepoint/archive/2007/02/19/microsoft-sql-server-2005-sp2-reporting-services-integration-with- wss-3-0-and-moss-2007.aspx <---SharePoint Blog Group
Basically my setup is as follows:
Server 1 = SharePoint 2007
Server 2 = SQL Server Reporting Services SP2 / SharePoint 2007 services
Server 3 = Database
Server1 is setup and running SharePoint 2007 fine with no problems. It was installed under the complete option with its own server farm. Then with the Server2, SharePoint 2007 is installed again, also under the complete complete option, and configured to join Server1's server farm. In this way, Server2 is able to supply Server1 with services and it has been said that if you are using 2 different servers, one for SharePoint and one for Reporting Services, you need to have an instance of SharePoint on the reporting services box. With a SharePoint "front-end" the reporting-services now has a way to also join Server1s farm.
This is where the headache begins....the SharePoint install is successful on Server2 and the services are started as evident through the Central Administration page. The next task is to install SQL Server 2005 Reporting Services and then the SQL Server 2005 SP2 patch.
After installing SQL Server and the SP2 patch, you go into the SQL Reporting Services Configuration Manager and setup the Report Server, Database, and SharePoint integration. I configure everything to run under the "DefaultAppPool" under IIS, and I get green accepted checkboxes on everything.
Finally, the last step is to install Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies on Server1. This add-in actually allows the connection between SharePoint on Server1 to the Reporting Services on Server2. The install is successful and the extra options for reporting pop up under Central Administration page. When configuring the final connection under the Central Admin I referred to the following Microsoft Page:
http://msdn2.microsoft.com/en-us/library/bb326213.aspx
For the "manage integration settings", I set the report server to Server2 and use Windows Authentication. Then for the "grant database access" I use Server2 and login with my credentials...
PROBLEM: Then for the final step of setting the server defaults, I click on the link and get the following error:
"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. "
I have googled and tried installing/uninstalling several times, but it seems that I keep getting hung up here. When trying to access reports on the ReportServer, the same error message comes up.
If anyone is familiar with integration between SharePoint and SQL Reporting Services, and may have any ideas/comments/advice, I would greatly appreciate it. Thanks in advance! =)
--A4orce84
View 4 Replies
View Related
Nov 8, 2006
I created an SSIS package for a client that does data importing. When I run the pacakge from Visual Studio there is an error window showing all the errors and warnings. A good example of an error is if the import file is in the wrong format.When there is a error or warning can I write the error log to a file OR notify someone of the errors so they can make corrections and rerun the package OR any ideas that the client can find out what went wrong and then make corrections accordingly? Thanks
View 1 Replies
View Related
Jun 6, 2006
Hi
I am trying to Execute an SSIS Package from C# Dot Net.
Below the code i am using.
try
{
Application app = new Application();
Package package = app.LoadPackage("DTSPackage/WinServeMonitoring.dtsx", null);
DTSExecResult result = package.Execute();
label1.Text = "Package Execution " + result.ToString();
}
catch (Exception exp)
{
label1.Text = exp.Message.ToString();
}
I have added reffrence for DTS Run time (using Microsoft.SqlServer.Dts.Runtime;)
But I am getting an Error like this
Error 1 'Application' is an ambiguous reference between 'System.Windows.Forms.Application' and 'Microsoft.SqlServer.Dts.Runtime.Application' C:Documents and Settingsvahqmd10My DocumentsVisual Studio 2005ProjectsWindowsApplication1WindowsApplication1Form1.cs 23 17 WindowsApplication1
Error 2 'Application' is an ambiguous reference between 'System.Windows.Forms.Application' and 'Microsoft.SqlServer.Dts.Runtime.Application' C:Documents and Settingsvahqmd10My DocumentsVisual Studio 2005ProjectsWindowsApplication1WindowsApplication1Form1.cs 23 39 WindowsApplication1
Error 3 The type 'System.Windows.Forms.Application' has no constructors defined C:Documents and Settingsvahqmd10My DocumentsVisual Studio 2005ProjectsWindowsApplication1WindowsApplication1Form1.cs 23 35 WindowsApplication1
Can any one Help me !
Regards
Deepu M.I
View 9 Replies
View Related
Oct 30, 2006
Hello, I would love to know where people are discussing the book Microsoft SQL Server 2005 Integration Services book by Kirk Hasleden.
I'm on page 41 and I'm getting an error with the example in the "SELECT "2004" FROM Sales.vSalesPersonSalesByFiscalYears"
part because there is not a table called Sales.vSalesPersonSalesByFiscalYears in the AdventureWorks database.
Thank youo
View 3 Replies
View Related
Oct 2, 2006
Hi every one,
I'd like to install SQL SERVER 2005 Express Edition ,I begin to install it from DVD but during the installation it dosn't ask me about any instance and after installation there isn't SQLExpress service and I can't use sql server .(there are not MSSQL and Binn directory in sql server 2005) but when I install visual studio 2005 and after that I install sql server 2005 it ask me for name of instance and with this way every thing is ok and I use sql server completely.
I 'd like to know the complete installation of sql server 2005 is depend on installation of visual studio 2005 befor it ?if not how can I introduce any instance after installation of sel server 2005 .
View 11 Replies
View Related
Oct 12, 2006
I have a package that uses a connection defined in the package designer.I also hve some connections defined in the data sources with the same name.How can I change the connections in the package designer to use the connections in the datasources and make all processes use this data sources connection?Thanks
View 2 Replies
View Related
Mar 23, 2007
Hi,
I have just install SQL 2005 SP2 and trying to get Window SharePoint Services V3 integrated with SQL 2005 SP2 reporting services.
In SharePoint Central Administration, I select the Reporting Services Integration page and have setup the Report Server Web Service URL and Authentication Mode. I then goto Grant database access, specify the SQL server name, get promted for a username and password that has access SQL Reportserver and get the following error "The group name could not be found"
Does anyone have any ideas?
Thanks
View 5 Replies
View Related
Oct 11, 2007
Hello, I have a problem when trying to fully process an SSAS database using Integration Services "Analysis Services Processing Task" task. I have 2 of these tasks which are responsible for processing the Dimensions then the Cubes. When I run the package either via the BIDS environment or on the local server from the Integration Services engine, I will get an error after about 20 minutes stating:
"Error: Memory Error: Allocation failure. Not enough storage is available to process this command""Error: Errors in the metadata manager. An error occurred when loading the <cube name> cube from the file \?D:Program FilesMicrosoft SQL ServerMSSQL.2OLAPDataMyWarehouse<cube file>.xml"
The cube name is not specific, it will fail and any of my cubes could be in the error log
If I fully process the AS database using the AS engine (logon to local AS server, right-click AS database and click Process), I get no errors at all, it processes and completes fine. The processing options are identical when I run in AS or via the SSIS "Analysis Services Processing Task" task.
I've searched quite a lot online but no joy, the information I have gleaned from various sites does not directly link SSIS with SSAS processing problems.
When either the AS processing starts via SSAS or SSIS the memory usage of MSMDSRV.exe increases to around 1.4 / 1.5 GB but never goes to 2GB ever, even when the error appears.
I've done the following with no effect.
" Have run via AS and works fine
" No specific cube it fails on
" Have created a Dimension only package, same problem
" Changed the maxmemorylimit
" Changed the connections to localhost
" Memory DOES NOT max out on server
Server Specs:
Windows Server 2003 Standard + Service Pack 2
4GM ram, 2GB paging file
SQL Server 2005 + Service Pack 2
Can anyone help?
Andy
View 2 Replies
View Related
Jun 20, 2007
Hi,
I've encountered this error when opening up http://localhost/ReportServer/
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportServerRSReportServer.config' is denied.
Here is the log info:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>Pacific Daylight Time</TimeZone>
<Path>C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesLogFilesReportServerService__06_20_2007_10_08_12.log</Path>
<SystemName>CSD060266</SystemName>
<OSName>Microsoft Windows NT 5.1.2600 Service Pack 2</OSName>
<OSVersion>5.1.2600.131072</OSVersion>
</Header>
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
ReportingServicesService!library!9!6/20/2007-10:08:13:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
ReportingServicesService!resourceutilities!9!6/20/2007-10:08:13:: i INFO: Reporting Services starting SKU: Developer
ReportingServicesService!resourceutilities!9!6/20/2007-10:08:13:: i INFO: Evaluation copy: 0 days left
ReportingServicesService!runningjobs!9!6/20/2007-10:08:13:: i INFO: Database Cleanup (NT Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
ReportingServicesService!runningjobs!9!6/20/2007-10:08:13:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!9!6/20/2007-10:08:13:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!9!6/20/2007-10:08:13:: i INFO: Execution Log Entry Expiration timer enabled: Next Event: 57106 seconds. Cycle: 86400 seconds
ReportingServicesService!runningjobs!9!6/20/2007-10:08:13:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
ReportingServicesService!runningjobs!9!6/20/2007-10:08:13:: i INFO: SQM timer timer enabled: Next Event: 60706 seconds. Cycle: 86400 seconds
ReportingServicesService!library!e!6/20/2007-10:08:13:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., Cannont get edition information from catalog server;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.
ReportingServicesService!library!e!6/20/2007-10:08:44:: i INFO: Exception dumped to: C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesLogFiles flags= ReferencedMemory, AllThreads, SendToWatson
ReportingServicesService!library!e!6/20/2007-10:08:44:: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.
at Microsoft.ReportingServices.Diagnostics.Sku.EnsureCorrectEdition(SqlConnection sqlConn, String connectionString, Boolean checkRestrictedSkus)
at Microsoft.ReportingServices.Library.ConnectionManager.EnsureCorrectEdition()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread()
ReportingServicesService!library!e!6/20/2007-10:08:44:: Attempting to start service again...
I've been doing all I could think of: reinstall the whole SQL server and its services; stop and restart SQL server service and Reporting service.
It could be my SQL version has a problem...not sure....
I could not think of anything else.
If you have any thoughts about it, please do reply.
Any suggestion is highly appreciated. Thank you...
View 3 Replies
View Related
Sep 11, 2006
Hello,
I am trying to install SQL SERVER2005 on windows 2003 server.It is not installing SSIS designer.why is it so?
View 10 Replies
View Related
Sep 11, 2006
Hello,
I am trying to install SQL SERVER2005 on windows 2003 server.It is not installing SSIS designer.why is it so?
Regards
Kuldeep
View 1 Replies
View Related
May 21, 2007
Hi,
I created a package which passes some infornmations( through parameters) to its child package.
I need to do some processing in parent package based on execution status of child package.i.e.
if child fails then some operation and if child succeeds then other operation.
To determine the status of execution of child package I am using two differnt constraint ..one constraint is having value "Success" and other having value "Failure".
My problem is that when child packge is executed successfully the constraint with value = "Success" works properly but when child fails the constraint with value "Failure" does not work.
-Prashant
View 4 Replies
View Related
Nov 22, 2006
Hi All,
Does somebody know where can I find a guide or white paper regarding to the subject?
It should contain the procedures needed to recover Analisys, Reporting and Integration services as well.
Thanks,
Miska
View 1 Replies
View Related
Jul 23, 2005
I am trying to know how to read many XML files within one data flowtask. I have many many files that I would like to apply to with thesame data flow so I need to know how to read them in and what taskshould I use under SQL 2005 DTS/Integration services.Thanks for your help!JON
View 1 Replies
View Related
Sep 7, 2007
My client machine has VS Studio 2005 Professional installed. My server has SQL Server 2005 Enterprise with BIDS installed. I would prefer to do my task development on my client instead of the server. How do I get the Integration Services projects on my installation of VS 2005? I went so far as installing SQL Express and BIDS on my local machine, but the only Business Development projects I get are Report Server. Any assistance would be greatly appreciated.
Thanks,
Lee
View 4 Replies
View Related
Mar 15, 2007
I'm trying to install SP2 on a named instance of SQL 2005 running on Win2003 SP2. There's a named instance of SQL 2000 SP4 running on the same machine. SP2 upgrades everything but fails on the Integration Services. I get the following hotfix log:
03/15/2007 12:11:24.765 ================================================================================
03/15/2007 12:11:24.781 Hotfix package launched
03/15/2007 12:11:24.812 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:24.843 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:24.843 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:24.859 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:24.859 Local Computer:
03/15/2007 12:11:24.875 Target Details: DEVDB
03/15/2007 12:11:24.875 commonfilesdir = C:Program FilesCommon Files
03/15/2007 12:11:24.890 lcidsupportdir = d:62fd796336ff97e5e9fdd31033
03/15/2007 12:11:24.906 programfilesdir = C:Program Files
03/15/2007 12:11:24.906 programfilesdir_wow = C:Program Files
03/15/2007 12:11:24.921 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:24.921 supportdirlocal = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:24.937 windir = C:WINDOWS
03/15/2007 12:11:24.937 winsysdir = C:WINDOWSsystem32
03/15/2007 12:11:24.953 winsysdir_wow = C:WINDOWSSysWOW64
03/15/2007 12:11:24.953
03/15/2007 12:11:24.968 Enumerating applicable products for this patch
03/15/2007 12:11:24.968 Found Redist 2005 product definition
03/15/2007 12:11:25.000 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:25.031 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:25.031 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:25.046 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:25.359 Found Redist 2005 product definition
03/15/2007 12:11:25.390 Found Redist 2005 product definition
03/15/2007 12:11:25.390 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:25.406 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:25.406 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:25.421 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:25.562 Found SQL 2005 product definition
03/15/2007 12:11:27.187 Enumeration: Determining QFE level for product instance SQL2005
03/15/2007 12:11:27.218 Enumeration: Found following QFE level for product instance SQL2005: 3050
03/15/2007 12:11:27.218 Enumeration: Determining GDR branching Hotfix for product instance SQL2005
03/15/2007 12:11:27.234 Enumeration: Found following GDR branch hotfix for product instance SQL2005: 3152
03/15/2007 12:11:27.234 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:27.250 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:27.250 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:27.265 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:27.265 Product discovery completed during the install process for SQL2005
03/15/2007 12:11:27.281 SP Level check completed during the install process for SQL2005
03/15/2007 12:11:27.281 Product language check completed during the install process for SQL2005
03/15/2007 12:11:27.296 The product instance SQL2005 been patched with more recent updates.
03/15/2007 12:11:27.296 Command-line instance name check completed during the install process
03/15/2007 12:11:27.312 SKU check completed during the install process for SQL2005
03/15/2007 12:11:27.328 Baseline build check completed during the install process
03/15/2007 12:11:27.328 Found OLAP Server 2005 product definition
03/15/2007 12:11:28.281 Enumeration: Determining QFE level for product instance SQL2005
03/15/2007 12:11:28.281 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.2OLAP\Binmsmdsrv.exe
03/15/2007 12:11:28.281 Enumeration: Found following QFE level for product instance SQL2005: 3050
03/15/2007 12:11:28.296 Enumeration: Determining GDR branching Hotfix for product instance SQL2005
03/15/2007 12:11:28.312 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.2OLAP\Binmsmdsrv.exe
03/15/2007 12:11:28.312 Enumeration: No GDR branch Hotfix found for product instance SQL2005
03/15/2007 12:11:28.328 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:28.328 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:28.343 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:28.343 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:28.359 Product discovery completed during the install process for SQL2005
03/15/2007 12:11:28.359 SP Level check completed during the install process for SQL2005
03/15/2007 12:11:28.375 Product language check completed during the install process for SQL2005
03/15/2007 12:11:28.375 The product instance SQL2005 been patched with more recent updates.
03/15/2007 12:11:28.390 Command-line instance name check completed during the install process
03/15/2007 12:11:28.390 Baseline build check completed during the install process
03/15/2007 12:11:28.406 Found Notification Services 2005 product definition
03/15/2007 12:11:29.343 Enumeration: Determining QFE level for product instance
03/15/2007 12:11:29.406 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242\Binsservice.exe
03/15/2007 12:11:29.437 Enumeration: Found following QFE level for product instance : 3050
03/15/2007 12:11:29.468 Enumeration: Determining GDR branching Hotfix for product instance
03/15/2007 12:11:29.468 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242\Binsservice.exe
03/15/2007 12:11:29.484 Enumeration: Found following GDR branch hotfix for product instance : 3152
03/15/2007 12:11:29.484 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:29.500 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:29.515 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:29.515 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:29.531 Product discovery completed during the install process for NS
03/15/2007 12:11:29.531 SP Level check completed during the install process for NS
03/15/2007 12:11:29.546 Product language check completed during the install process for NS
03/15/2007 12:11:29.546 The product instance NS been patched with more recent updates.
03/15/2007 12:11:29.562 Baseline build check completed during the install process
03/15/2007 12:11:29.562 Found Report Server 2005 product definition
03/15/2007 12:11:30.515 Command-line instance name check completed during the install process
03/15/2007 12:11:30.515 Baseline build check completed during the install process
03/15/2007 12:11:30.531 Found DTS 2005 product definition
03/15/2007 12:11:31.453 Enumeration: Determining QFE level for product instance
03/15/2007 12:11:31.468 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90DTS\Binnmsdtssrvr.exe
03/15/2007 12:11:31.484 Enumeration: Found following QFE level for product instance : 1399
03/15/2007 12:11:31.484 Enumeration: Determining GDR branching Hotfix for product instance
03/15/2007 12:11:31.500 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90DTS\Binnmsdtssrvr.exe
03/15/2007 12:11:31.500 Enumeration: No GDR branch Hotfix found for product instance
03/15/2007 12:11:31.515 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:31.515 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:31.531 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:31.531 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:31.546 Product discovery completed during the install process for Integration Services
03/15/2007 12:11:31.546 SP Level check completed during the install process for Integration Services
03/15/2007 12:11:31.562 Product language check completed during the install process for Integration Services
03/15/2007 12:11:31.562 Product version check completed during the install process for Integration Services
03/15/2007 12:11:31.578 Baseline build check completed during the installation process for Integration Services
03/15/2007 12:11:31.593 Baseline build check completed during the install process
03/15/2007 12:11:31.593 Found SQL 2005 Tools product definition
03/15/2007 12:11:32.531 Enumeration: Determining GDR branching Hotfix for product instance
03/15/2007 12:11:32.546 Enumeration: Found following GDR branch hotfix for product instance : 3152
03/15/2007 12:11:32.562 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:32.562 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:32.578 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:32.578 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:32.593 Product discovery completed during the install process for SQL Tools
03/15/2007 12:11:32.593 SP Level check completed during the install process for SQL Tools
03/15/2007 12:11:32.609 Product language check completed during the install process for SQL Tools
03/15/2007 12:11:32.609 The product instance SQL Tools been patched with more recent updates.
03/15/2007 12:11:32.625 SKU check completed during the install process for SQL Tools
03/15/2007 12:11:32.625 Baseline build check completed during the install process
03/15/2007 12:11:32.640 Found Redist 2005 product definition
03/15/2007 12:11:32.656 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:32.656 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:32.671 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:32.671 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:32.921 Found Redist 2005 product definition
03/15/2007 12:11:32.953 Found Redist 2005 product definition
03/15/2007 12:11:32.968 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:32.968 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:32.984 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:32.984 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:33.140 Found Redist 2005 product definition
03/15/2007 12:11:33.171 Found Redist 2005 product definition
03/15/2007 12:11:33.171 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:33.187 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:33.187 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:33.203 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:33.437 Found Redist 2005 product definition
03/15/2007 12:11:33.453 Found Redist 2005 product definition
03/15/2007 12:11:33.468 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:33.468 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/15/2007 12:11:33.484 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/15/2007 12:11:33.484 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/15/2007 12:11:33.609 Found Redist 2005 product definition
03/15/2007 12:11:33.703 Product Enumeration Results:
03/15/2007 12:11:33.718 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlncli.inf
03/15/2007 12:11:33.734 baselinebuild = 1399
03/15/2007 12:11:33.734 build = 3042
03/15/2007 12:11:33.750 description = SQL Server Native Client
03/15/2007 12:11:33.750 details = Service Pack for Microsoft SQL Server Native Client.
03/15/2007 12:11:33.765 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:33.765 kbarticle = KB921896
03/15/2007 12:11:33.781 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:33.796 lcid = 1033
03/15/2007 12:11:33.796 legalproductname = Microsoft SQL Native Client
03/15/2007 12:11:33.812 machinetype = x86
03/15/2007 12:11:33.812 package = HotFixSqlncli
03/15/2007 12:11:33.828 packagetype = Hotfix
03/15/2007 12:11:33.828 productcode = {F9B3DD02-B0B3-42E9-8650-030DFF0D133D}
03/15/2007 12:11:33.843 productname = Redist9
03/15/2007 12:11:33.843 recommendinstall = 1
03/15/2007 12:11:33.859 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:33.859 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:33.875 splevel = 2
03/15/2007 12:11:33.875 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:33.890 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:33.890 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
03/15/2007 12:11:33.906 version = 9
03/15/2007 12:11:33.921
03/15/2007 12:11:33.921 File Group Details: MSI
03/15/2007 12:11:33.937 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:33.937 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:33.953 File Details: sqlncli.msi
03/15/2007 12:11:33.953
03/15/2007 12:11:33.968 Instance Details: SQL Server Native Client
03/15/2007 12:11:33.968 fullversion = 9.00.3042.00
03/15/2007 12:11:33.984 lcid = 1033
03/15/2007 12:11:33.984 productcode = {F9B3DD02-B0B3-42E9-8650-030DFF0D133D}
03/15/2007 12:11:34.000 qfelevel = 3042
03/15/2007 12:11:34.000 sp = -1
03/15/2007 12:11:34.015
03/15/2007 12:11:34.031 Product Enumeration Results:
03/15/2007 12:11:34.031 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlncli_x64.inf
03/15/2007 12:11:34.046 baselinebuild = 1399
03/15/2007 12:11:34.046 build = 3042
03/15/2007 12:11:34.062 description = SQL Server Native Client
03/15/2007 12:11:34.062 details = Service Pack for Microsoft SQL Server Native Client.
03/15/2007 12:11:34.078 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:34.078 kbarticle = KB921896
03/15/2007 12:11:34.093 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:34.093 lcid = 1033
03/15/2007 12:11:34.109 legalproductname = Microsoft SQL Native Client (64-bit)
03/15/2007 12:11:34.109 machinetype = x64
03/15/2007 12:11:34.125 package = HotFixSqlncli_x64
03/15/2007 12:11:34.125 packagetype = Hotfix
03/15/2007 12:11:34.140 productname = Redist9
03/15/2007 12:11:34.156 recommendinstall = 1
03/15/2007 12:11:34.156 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:34.171 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:34.171 splevel = 2
03/15/2007 12:11:34.187 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:34.187 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
03/15/2007 12:11:34.203 version = 9
03/15/2007 12:11:34.203
03/15/2007 12:11:34.218 File Group Details: MSI
03/15/2007 12:11:34.218 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:34.234 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:34.234 File Details: sqlncli_x64.msi
03/15/2007 12:11:34.250
03/15/2007 12:11:34.265 Product Enumeration Results:
03/15/2007 12:11:34.265 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlSupport.inf
03/15/2007 12:11:34.281 alwaysinstall = 1
03/15/2007 12:11:34.281 baselinebuild = 1399
03/15/2007 12:11:34.296 build = 3042
03/15/2007 12:11:34.296 description = Setup Support Files
03/15/2007 12:11:34.312 details = Service Pack for the SQL Server support files.
03/15/2007 12:11:34.312 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:34.328 kbarticle = KB921896
03/15/2007 12:11:34.328 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:34.343 keyqualifier = 1
03/15/2007 12:11:34.343 lcid = 1033
03/15/2007 12:11:34.359 legalproductname = SQL Server 2005 Setup Support Files
03/15/2007 12:11:34.359 machinetype = x86
03/15/2007 12:11:34.375 package = HotFixSqlSupport
03/15/2007 12:11:34.390 packagetype = Hotfix
03/15/2007 12:11:34.390 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
03/15/2007 12:11:34.406 productname = Redist9
03/15/2007 12:11:34.406 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:34.421 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:34.421 splevel = 2
03/15/2007 12:11:34.437 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:34.437 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:34.453 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
03/15/2007 12:11:34.453 version = 9
03/15/2007 12:11:34.468
03/15/2007 12:11:34.468 File Group Details: MSI
03/15/2007 12:11:34.484 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
03/15/2007 12:11:34.500 parameters = REINSTALL=ALL
03/15/2007 12:11:34.500 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:34.515 File Details: SqlSupport.msi
03/15/2007 12:11:34.515
03/15/2007 12:11:34.531 Instance Details: Setup Support Files
03/15/2007 12:11:34.531 fullversion = 9.2.3042
03/15/2007 12:11:34.546 lcid = 1033
03/15/2007 12:11:34.546 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
03/15/2007 12:11:34.562 qfelevel = 3042
03/15/2007 12:11:34.562 sp = -1
03/15/2007 12:11:34.578
03/15/2007 12:11:34.578 Product Enumeration Results:
03/15/2007 12:11:34.593 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSQL.inf
03/15/2007 12:11:34.593 baselinebuild = 1399
03/15/2007 12:11:34.609 baselinebuildmax = 3042
03/15/2007 12:11:34.625 build = 3042
03/15/2007 12:11:34.625 description = Database Services
03/15/2007 12:11:34.640 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
03/15/2007 12:11:34.640 installer = Hotfix
03/15/2007 12:11:34.656 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:34.656 kbarticle = KB921896
03/15/2007 12:11:34.671 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:34.671 lcid = 1033
03/15/2007 12:11:34.687 legalproductname = SQL Server Database Services 2005
03/15/2007 12:11:34.687 machinetype = x86
03/15/2007 12:11:34.703 package = HotFixSQL
03/15/2007 12:11:34.703 packagetype = Hotfix
03/15/2007 12:11:34.718 productname = SQL9
03/15/2007 12:11:34.718 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:34.734 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:34.750 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/15/2007 12:11:34.750 splevel = 2
03/15/2007 12:11:34.765 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:34.765 sqlutility = sqlcmd.exe
03/15/2007 12:11:34.781 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:34.781 validateauthentication = true
03/15/2007 12:11:34.796 version = 9
03/15/2007 12:11:34.796
03/15/2007 12:11:34.812 File Group Details: MSP
03/15/2007 12:11:34.812 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/15/2007 12:11:34.828 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:34.828 File Details: sqlrun_sql.msp
03/15/2007 12:11:34.843
03/15/2007 12:11:34.859 Instance Details: SQL2005
03/15/2007 12:11:34.859 agentservicename = SQLAgent$SQL2005
03/15/2007 12:11:34.875 associatedhotfixbuild = 3152
03/15/2007 12:11:34.875 clustername =
03/15/2007 12:11:34.890 details = The product instance SQL2005 been patched with more recent updates.
03/15/2007 12:11:34.890 ftsservicename = MSFTESQL$SQL2005
03/15/2007 12:11:34.906 fullversion = 2005.090.3050.00
03/15/2007 12:11:34.906 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
03/15/2007 12:11:34.921 id = MSSQL.1
03/15/2007 12:11:34.921 installsqldatadir = D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
03/15/2007 12:11:34.937 installsqldir = C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
03/15/2007 12:11:34.937 lcid = 1033
03/15/2007 12:11:34.953 name = SQL2005
03/15/2007 12:11:34.953 productcode = {EB76B218-8FC5-41DF-9F1F-7FF3E0448383}
03/15/2007 12:11:34.968 qfelevel = 3050
03/15/2007 12:11:34.984 servicename = MSSQL$SQL2005
03/15/2007 12:11:34.984 sku = ENTERPRISE
03/15/2007 12:11:35.000 sp = 2
03/15/2007 12:11:35.000 type = SQL Server Standalone Product
03/15/2007 12:11:35.015 vermajbld = 3042
03/15/2007 12:11:35.015 version = 9
03/15/2007 12:11:35.031
03/15/2007 12:11:35.031 Product Enumeration Results:
03/15/2007 12:11:35.046 INF File Name: d:62fd796336ff97e5e9fdd3HotFixAS.inf
03/15/2007 12:11:35.046 baselinebuild = 1399
03/15/2007 12:11:35.062 baselinebuildmax = 3042
03/15/2007 12:11:35.062 build = 3042
03/15/2007 12:11:35.078 description = Analysis Services
03/15/2007 12:11:35.093 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
03/15/2007 12:11:35.093 installer = Hotfix
03/15/2007 12:11:35.109 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:35.109 kbarticle = KB921896
03/15/2007 12:11:35.125 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:35.125 lcid = 1033
03/15/2007 12:11:35.140 legalproductname = SQL Server Analysis Services 2005
03/15/2007 12:11:35.140 machinetype = x86
03/15/2007 12:11:35.156 package = HotFixAS
03/15/2007 12:11:35.156 packagetype = Hotfix
03/15/2007 12:11:35.171 productname = OLAP9
03/15/2007 12:11:35.171 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:35.187 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:35.187 splevel = 2
03/15/2007 12:11:35.203 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:35.218 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:35.218 version = 9
03/15/2007 12:11:35.234
03/15/2007 12:11:35.234 File Group Details: MSP
03/15/2007 12:11:35.250 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/15/2007 12:11:35.250 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:35.265 File Details: sqlrun_as.msp
03/15/2007 12:11:35.265
03/15/2007 12:11:35.281 Instance Details: SQL2005
03/15/2007 12:11:35.281 associatedhotfixbuild = 1520
03/15/2007 12:11:35.296 clustername =
03/15/2007 12:11:35.296 details = The product instance SQL2005 been patched with more recent updates.
03/15/2007 12:11:35.312 fullversion = 2005.090.3050.00
03/15/2007 12:11:35.328 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.2
03/15/2007 12:11:35.328 id = MSSQL.2
03/15/2007 12:11:35.343 installsqldatadir = C:Program FilesMicrosoft SQL Server
03/15/2007 12:11:35.343 installsqldir = C:Program FilesMicrosoft SQL ServerMSSQL.2OLAP
03/15/2007 12:11:35.359 lcid = 1033
03/15/2007 12:11:35.359 name = SQL2005
03/15/2007 12:11:35.375 olapservicename = MSOLAP$SQL2005
03/15/2007 12:11:35.375 productcode = {52B0D62A-860D-4136-9A8A-9FD877E8EE89}
03/15/2007 12:11:35.390 qfelevel = 3050
03/15/2007 12:11:35.390 servicename = MSOLAP$SQL2005
03/15/2007 12:11:35.406 sku = ENTERPRISE
03/15/2007 12:11:35.406 sp = 2
03/15/2007 12:11:35.421 type = Olap Standalone Product
03/15/2007 12:11:35.421 vermajbld = 3042
03/15/2007 12:11:35.437 version = 9
03/15/2007 12:11:35.453
03/15/2007 12:11:35.453 Product Enumeration Results:
03/15/2007 12:11:35.468 INF File Name: d:62fd796336ff97e5e9fdd3HotFixNS.inf
03/15/2007 12:11:35.468 baselinebuild = 1399
03/15/2007 12:11:35.484 baselinebuildmax = 3042
03/15/2007 12:11:35.484 build = 3042
03/15/2007 12:11:35.500 description = Notification Services
03/15/2007 12:11:35.500 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/15/2007 12:11:35.515 installer = Hotfix
03/15/2007 12:11:35.515 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:35.531 kbarticle = KB921896
03/15/2007 12:11:35.531 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:35.546 lcid = 1033
03/15/2007 12:11:35.562 legalproductname = SQL Server Notification Services 2005 instances
03/15/2007 12:11:35.562 machinetype = x86
03/15/2007 12:11:35.578 package = HotFixNS
03/15/2007 12:11:35.578 packagetype = Hotfix
03/15/2007 12:11:35.593 productname = NS9
03/15/2007 12:11:35.593 recommendinstall = 1
03/15/2007 12:11:35.609 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:35.609 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:35.625 splevel = 2
03/15/2007 12:11:35.625 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:35.640 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:35.640 version = 9
03/15/2007 12:11:35.656
03/15/2007 12:11:35.656 File Group Details: MSP
03/15/2007 12:11:35.671 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/15/2007 12:11:35.687 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:35.687 File Details: sqlrun_ns.msp
03/15/2007 12:11:35.703
03/15/2007 12:11:35.703 Instance Details: NS
03/15/2007 12:11:35.718 associatedhotfixbuild = 3152
03/15/2007 12:11:35.718 clustername =
03/15/2007 12:11:35.734 details = The product instance NS been patched with more recent updates.
03/15/2007 12:11:35.734 fullversion = 9.00.3050.00
03/15/2007 12:11:35.750 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90NS
03/15/2007 12:11:35.750 id =
03/15/2007 12:11:35.765 installsqldatadir =
03/15/2007 12:11:35.765 installsqldir = C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242
03/15/2007 12:11:35.781 lcid = 1033
03/15/2007 12:11:35.796 name =
03/15/2007 12:11:35.796 productcode = {C0B81E26-F7D0-4E84-941A-21C438BC586D}
03/15/2007 12:11:35.812 qfelevel = 3050
03/15/2007 12:11:35.812 sku = ENTERPRISE
03/15/2007 12:11:35.828 sp = 2
03/15/2007 12:11:35.828 type = Tools Only
03/15/2007 12:11:35.843 vermajbld = 3042
03/15/2007 12:11:35.843 version = 9
03/15/2007 12:11:35.859
03/15/2007 12:11:35.859 Product Enumeration Results:
03/15/2007 12:11:35.875 INF File Name: d:62fd796336ff97e5e9fdd3HotFixRS.inf
03/15/2007 12:11:35.875 baselinebuild = 1399
03/15/2007 12:11:35.890 baselinebuildmax = 3042
03/15/2007 12:11:35.890 build = 3042
03/15/2007 12:11:35.906 description = Reporting Services
03/15/2007 12:11:35.921 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
03/15/2007 12:11:35.921 installer = Hotfix
03/15/2007 12:11:35.937 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:35.937 kbarticle = KB921896
03/15/2007 12:11:35.953 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:35.953 lcid = 1033
03/15/2007 12:11:35.968 legalproductname = SQL Server Reporting Services 2005
03/15/2007 12:11:35.968 machinetype = x86
03/15/2007 12:11:35.984 package = HotFixRS
03/15/2007 12:11:35.984 packagetype = Hotfix
03/15/2007 12:11:36.000 productname = RS9
03/15/2007 12:11:36.000 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:36.015 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:36.015 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/15/2007 12:11:36.031 splevel = 2
03/15/2007 12:11:36.046 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:36.046 sqlutility = sqlcmd.exe
03/15/2007 12:11:36.062 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:36.062 validateauthentication = 1
03/15/2007 12:11:36.078 version = 9
03/15/2007 12:11:36.078
03/15/2007 12:11:36.093 File Group Details: MSP
03/15/2007 12:11:36.093 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/15/2007 12:11:36.109 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:36.109 File Details: sqlrun_rs.msp
03/15/2007 12:11:36.125
03/15/2007 12:11:36.125 Product Enumeration Results:
03/15/2007 12:11:36.140 INF File Name: d:62fd796336ff97e5e9fdd3HotFixDTS.inf
03/15/2007 12:11:36.156 baselinebuild = 1399
03/15/2007 12:11:36.156 baselinebuildmax = 3042
03/15/2007 12:11:36.171 build = 3042
03/15/2007 12:11:36.171 description = Integration Services
03/15/2007 12:11:36.187 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/15/2007 12:11:36.187 installer = Hotfix
03/15/2007 12:11:36.203 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:36.203 kbarticle = KB921896
03/15/2007 12:11:36.218 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:36.218 lcid = 1033
03/15/2007 12:11:36.234 legalproductname = SQL Server Integration Services 2005
03/15/2007 12:11:36.234 machinetype = x86
03/15/2007 12:11:36.250 package = HotFixDTS
03/15/2007 12:11:36.250 packagetype = Hotfix
03/15/2007 12:11:36.265 productname = DTS9
03/15/2007 12:11:36.281 recommendinstall = 1
03/15/2007 12:11:36.281 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:36.296 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:36.296 splevel = 2
03/15/2007 12:11:36.312 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:36.312 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:36.328 version = 9
03/15/2007 12:11:36.328
03/15/2007 12:11:36.343 File Group Details: MSP
03/15/2007 12:11:36.343 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/15/2007 12:11:36.359 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:36.359 File Details: sqlrun_dts.msp
03/15/2007 12:11:36.375
03/15/2007 12:11:36.390 Instance Details: Integration Services
03/15/2007 12:11:36.390 clustername =
03/15/2007 12:11:36.406 dtsservicename = MsDtsServer
03/15/2007 12:11:36.406 fullversion = 9.00.1399.00
03/15/2007 12:11:36.421 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90DTS
03/15/2007 12:11:36.421 id =
03/15/2007 12:11:36.437 installsqldatadir =
03/15/2007 12:11:36.437 installsqldir = C:Program FilesMicrosoft SQL Server90DTS
03/15/2007 12:11:36.453 lcid = 1033
03/15/2007 12:11:36.453 name =
03/15/2007 12:11:36.468 productcode = {8E408A85-E0E5-4094-903F-8675707AC313}
03/15/2007 12:11:36.468 qfelevel = 1399
03/15/2007 12:11:36.484 servicename = MsDtsServer
03/15/2007 12:11:36.484 sku = ENTERPRISE
03/15/2007 12:11:36.500 sp = 0
03/15/2007 12:11:36.515 type = Tools Only
03/15/2007 12:11:36.515 vermajbld = 1399
03/15/2007 12:11:36.531 version = 9
03/15/2007 12:11:36.531
03/15/2007 12:11:36.546 Product Enumeration Results:
03/15/2007 12:11:36.546 INF File Name: d:62fd796336ff97e5e9fdd3HotFixTools.inf
03/15/2007 12:11:36.562 baselinebuild = 1399
03/15/2007 12:11:36.562 baselinebuildmax = 3042
03/15/2007 12:11:36.578 build = 3042
03/15/2007 12:11:36.578 description = Client Components
03/15/2007 12:11:36.593 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/15/2007 12:11:36.593 installer = Hotfix
03/15/2007 12:11:36.609 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:36.625 kbarticle = KB921896
03/15/2007 12:11:36.625 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:36.640 lcid = 1033
03/15/2007 12:11:36.640 legalproductname = SQL Server Tools and Workstation Components 2005
03/15/2007 12:11:36.656 machinetype = x86
03/15/2007 12:11:36.656 package = HotFixTools
03/15/2007 12:11:36.671 packagetype = Hotfix
03/15/2007 12:11:36.671 productname = SQLTools9
03/15/2007 12:11:36.687 recommendinstall = 1
03/15/2007 12:11:36.687 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:36.703 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:36.703 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/15/2007 12:11:36.718 splevel = 2
03/15/2007 12:11:36.718 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:36.734 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:36.750 version = 9
03/15/2007 12:11:36.750
03/15/2007 12:11:36.765 File Group Details: MSP
03/15/2007 12:11:36.765 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/15/2007 12:11:36.781 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:36.781 File Details: sqlrun_tools.msp
03/15/2007 12:11:36.796
03/15/2007 12:11:36.796 Instance Details: SQL Tools
03/15/2007 12:11:36.812 associatedhotfixbuild = 3152
03/15/2007 12:11:36.812 clustername =
03/15/2007 12:11:36.828 details = The product instance SQL Tools been patched with more recent updates.
03/15/2007 12:11:36.828 fullversion = 9.2.3050
03/15/2007 12:11:36.843 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
03/15/2007 12:11:36.859 id =
03/15/2007 12:11:36.859 installsqldatadir =
03/15/2007 12:11:36.875 installsqldir = C:Program FilesMicrosoft SQL Server90Tools
03/15/2007 12:11:36.937 lcid = 1033
03/15/2007 12:11:36.953 name =
03/15/2007 12:11:36.968 productcode = {4D2DFB70-AECB-47BF-A895-3B3AA544934F}
03/15/2007 12:11:36.968 qfelevel = 3050
03/15/2007 12:11:36.984 sku = ENTERPRISE
03/15/2007 12:11:36.984 sp = 2
03/15/2007 12:11:37.000 type = Tools Only
03/15/2007 12:11:37.000 vermajbld = 3042
03/15/2007 12:11:37.015 version = 9
03/15/2007 12:11:37.015
03/15/2007 12:11:37.031 Product Enumeration Results:
03/15/2007 12:11:37.031 INF File Name: d:62fd796336ff97e5e9fdd3HotFixMsxml6.inf
03/15/2007 12:11:37.046 baselinebuild = 1399
03/15/2007 12:11:37.046 build = 6.10.1129.0
03/15/2007 12:11:37.062 description = MSXML 6.0 Parser
03/15/2007 12:11:37.062 details = Service Pack for Microsoft XML 6.0 Parser.
03/15/2007 12:11:37.078 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:37.093 kbarticle = KB921896
03/15/2007 12:11:37.093 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:37.109 lcid = 1033
03/15/2007 12:11:37.109 legalproductname = MSXML 6.0 Parser
03/15/2007 12:11:37.125 machinetype = x86
03/15/2007 12:11:37.125 package = HotFixMsxml6
03/15/2007 12:11:37.140 packagetype = Hotfix
03/15/2007 12:11:37.140 productcode = {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}
03/15/2007 12:11:37.156 productname = Redist9
03/15/2007 12:11:37.156 recommendinstall = 1
03/15/2007 12:11:37.171 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:37.171 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:37.187 splevel = 2
03/15/2007 12:11:37.203 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:37.203 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:37.218 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
03/15/2007 12:11:37.218 version = 9
03/15/2007 12:11:37.234
03/15/2007 12:11:37.234 File Group Details: MSI
03/15/2007 12:11:37.250 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:37.250 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:37.265 File Details: msxml6.msi
03/15/2007 12:11:37.265
03/15/2007 12:11:37.281 Instance Details: MSXML 6.0 Parser
03/15/2007 12:11:37.281 fullversion = 6.10.1129.0
03/15/2007 12:11:37.296 lcid = 1033
03/15/2007 12:11:37.296 productcode = {A43BF6A5-D5F0-4AAA-BF41-65995063EC44}
03/15/2007 12:11:37.312 qfelevel = 1129
03/15/2007 12:11:37.328 sp = -1
03/15/2007 12:11:37.328
03/15/2007 12:11:37.343 Product Enumeration Results:
03/15/2007 12:11:37.343 INF File Name: d:62fd796336ff97e5e9fdd3HotFixMsxml6_x64.inf
03/15/2007 12:11:37.359 baselinebuild = 1399
03/15/2007 12:11:37.359 build = 6.10.1129.0
03/15/2007 12:11:37.375 description = MSXML 6.0 Parser
03/15/2007 12:11:37.375 details = Service Pack for Microsoft XML 6.0 Parser.
03/15/2007 12:11:37.390 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:37.390 kbarticle = KB921896
03/15/2007 12:11:37.406 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:37.406 lcid = 1033
03/15/2007 12:11:37.421 legalproductname = MSXML 6.0 Parser (64-bit)
03/15/2007 12:11:37.437 machinetype = x64
03/15/2007 12:11:37.437 package = HotFixMsxml6_x64
03/15/2007 12:11:37.453 packagetype = Hotfix
03/15/2007 12:11:37.453 productname = Redist9
03/15/2007 12:11:37.468 recommendinstall = 1
03/15/2007 12:11:37.468 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:37.484 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:37.484 splevel = 2
03/15/2007 12:11:37.500 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:37.500 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
03/15/2007 12:11:37.515 version = 9
03/15/2007 12:11:37.515
03/15/2007 12:11:37.531 File Group Details: MSI
03/15/2007 12:11:37.531 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:37.546 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:37.562 File Details: msxml6_x64.msi
03/15/2007 12:11:37.562
03/15/2007 12:11:37.578 Product Enumeration Results:
03/15/2007 12:11:37.578 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlxml4.inf
03/15/2007 12:11:37.593 baselinebuild = 1399
03/15/2007 12:11:37.593 build = 3042
03/15/2007 12:11:37.609 description = SQLXML4
03/15/2007 12:11:37.609 details = Service Pack for Microsoft SQLXML 4.0.
03/15/2007 12:11:37.625 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:37.625 kbarticle = KB921896
03/15/2007 12:11:37.640 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:37.640 lcid = 1033
03/15/2007 12:11:37.656 legalproductname = SQLXML4
03/15/2007 12:11:37.671 machinetype = x86
03/15/2007 12:11:37.671 package = HotFixSqlxml4
03/15/2007 12:11:37.687 packagetype = Hotfix
03/15/2007 12:11:37.687 productcode = {36DD7006-7BFE-4E3D-AF6E-FA734BC879B7}
03/15/2007 12:11:37.703 productname = Redist9
03/15/2007 12:11:37.703 recommendinstall = 1
03/15/2007 12:11:37.718 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:37.718 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:37.734 splevel = 2
03/15/2007 12:11:37.734 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:37.750 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:37.750 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
03/15/2007 12:11:37.765 version = 9
03/15/2007 12:11:37.765
03/15/2007 12:11:37.781 File Group Details: MSI
03/15/2007 12:11:37.796 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:37.796 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:37.812 File Details: sqlxml4.msi
03/15/2007 12:11:37.812
03/15/2007 12:11:37.828 Instance Details: SQLXML4
03/15/2007 12:11:37.828 fullversion = 9.00.3042.00
03/15/2007 12:11:37.843 lcid = 1033
03/15/2007 12:11:37.843 productcode = {36DD7006-7BFE-4E3D-AF6E-FA734BC879B7}
03/15/2007 12:11:37.859 qfelevel = 3042
03/15/2007 12:11:37.859 sp = -1
03/15/2007 12:11:37.875
03/15/2007 12:11:37.875 Product Enumeration Results:
03/15/2007 12:11:37.890 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlxml4_x64.inf
03/15/2007 12:11:37.906 baselinebuild = 1399
03/15/2007 12:11:37.906 build = 3042
03/15/2007 12:11:37.921 description = SQLXML4
03/15/2007 12:11:37.921 details = Service Pack for Microsoft SQLXML 4.0.
03/15/2007 12:11:37.937 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:37.937 kbarticle = KB921896
03/15/2007 12:11:37.953 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:37.953 lcid = 1033
03/15/2007 12:11:37.968 legalproductname = SQLXML4 (64-bit)
03/15/2007 12:11:37.968 machinetype = x64
03/15/2007 12:11:37.984 package = HotFixSqlxml4_x64
03/15/2007 12:11:37.984 packagetype = Hotfix
03/15/2007 12:11:38.000 productname = Redist9
03/15/2007 12:11:38.000 recommendinstall = 1
03/15/2007 12:11:38.015 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:38.031 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:38.031 splevel = 2
03/15/2007 12:11:38.046 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:38.046 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
03/15/2007 12:11:38.062 version = 9
03/15/2007 12:11:38.062
03/15/2007 12:11:38.078 File Group Details: MSI
03/15/2007 12:11:38.078 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:38.093 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:38.093 File Details: sqlxml4_x64.msi
03/15/2007 12:11:38.109
03/15/2007 12:11:38.109 Product Enumeration Results:
03/15/2007 12:11:38.125 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSQLServer2005_BC.inf
03/15/2007 12:11:38.125 baselinebuild = 1399
03/15/2007 12:11:38.140 build = 2004
03/15/2007 12:11:38.156 description = Backward Compatibility
03/15/2007 12:11:38.156 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
03/15/2007 12:11:38.171 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:38.171 kbarticle = KB921896
03/15/2007 12:11:38.187 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:38.187 lcid = 1033
03/15/2007 12:11:38.203 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
03/15/2007 12:11:38.203 machinetype = x86
03/15/2007 12:11:38.218 package = HotFixSQLServer2005_BC
03/15/2007 12:11:38.218 packagetype = Hotfix
03/15/2007 12:11:38.234 productcode = {69880C00-08DD-4385-B752-9C62656F6D1E}
03/15/2007 12:11:38.234 productname = Redist9
03/15/2007 12:11:38.250 recommendinstall = 1
03/15/2007 12:11:38.265 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:38.265 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:38.281 splevel = 2
03/15/2007 12:11:38.281 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:38.296 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:38.296 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
03/15/2007 12:11:38.312 version = 9
03/15/2007 12:11:38.312
03/15/2007 12:11:38.328 File Group Details: MSI
03/15/2007 12:11:38.328 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:38.343 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:38.343 File Details: SQLServer2005_BC.msi
03/15/2007 12:11:38.359
03/15/2007 12:11:38.359 Instance Details: Backward Compatibility
03/15/2007 12:11:38.375 fullversion = 8.05.2004
03/15/2007 12:11:38.390 lcid = 1033
03/15/2007 12:11:38.390 productcode = {69880C00-08DD-4385-B752-9C62656F6D1E}
03/15/2007 12:11:38.406 qfelevel = 2004
03/15/2007 12:11:38.406 sp = -1
03/15/2007 12:11:38.421
03/15/2007 12:11:38.421 Product Enumeration Results:
03/15/2007 12:11:38.437 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSQLServer2005_BC_x64.inf
03/15/2007 12:11:38.437 baselinebuild = 1399
03/15/2007 12:11:38.453 build = 2004
03/15/2007 12:11:38.453 description = Backward Compatibility
03/15/2007 12:11:38.468 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
03/15/2007 12:11:38.468 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:38.484 kbarticle = KB921896
03/15/2007 12:11:38.500 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:38.500 lcid = 1033
03/15/2007 12:11:38.515 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
03/15/2007 12:11:38.515 machinetype = x64
03/15/2007 12:11:38.531 package = HotFixSQLServer2005_BC_x64
03/15/2007 12:11:38.531 packagetype = Hotfix
03/15/2007 12:11:38.546 productname = Redist9
03/15/2007 12:11:38.546 recommendinstall = 1
03/15/2007 12:11:38.562 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:38.562 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:38.578 splevel = 2
03/15/2007 12:11:38.578 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:38.593 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
03/15/2007 12:11:38.593 version = 9
03/15/2007 12:11:38.609
03/15/2007 12:11:38.625 File Group Details: MSI
03/15/2007 12:11:38.625 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:38.640 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:38.640 File Details: SQLServer2005_BC_x64.msi
03/15/2007 12:11:38.656
03/15/2007 12:11:38.656 Product Enumeration Results:
03/15/2007 12:11:38.671 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlWriter.inf
03/15/2007 12:11:38.671 baselinebuild = 1399
03/15/2007 12:11:38.687 build = 3042
03/15/2007 12:11:38.687 description = Microsoft SQL Server VSS Writer
03/15/2007 12:11:38.703 details = Service Pack for Microsoft SQL Server VSS Writer.
03/15/2007 12:11:38.703 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:38.718 kbarticle = KB921896
03/15/2007 12:11:38.734 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:38.734 lcid = 1033
03/15/2007 12:11:38.750 legalproductname = Microsoft SQL Server VSS Writer
03/15/2007 12:11:38.750 machinetype = x86
03/15/2007 12:11:38.765 package = HotFixSqlWriter
03/15/2007 12:11:38.765 packagetype = Hotfix
03/15/2007 12:11:38.781 productcode = {E9F44C98-B8B6-480F-AF7B-E42A0A46F4E3}
03/15/2007 12:11:38.781 productname = Redist9
03/15/2007 12:11:38.796 recommendinstall = 1
03/15/2007 12:11:38.796 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:38.812 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:38.812 splevel = 2
03/15/2007 12:11:38.828 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/15/2007 12:11:38.828 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:38.843 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
03/15/2007 12:11:38.859 version = 9
03/15/2007 12:11:38.859
03/15/2007 12:11:38.875 File Group Details: MSI
03/15/2007 12:11:38.875 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:38.890 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:38.890 File Details: SqlWriter.msi
03/15/2007 12:11:38.906
03/15/2007 12:11:38.906 Instance Details: Microsoft SQL Server VSS Writer
03/15/2007 12:11:38.921 fullversion = 9.00.3042.00
03/15/2007 12:11:38.921 lcid = 1033
03/15/2007 12:11:38.937 productcode = {E9F44C98-B8B6-480F-AF7B-E42A0A46F4E3}
03/15/2007 12:11:38.937 qfelevel = 3042
03/15/2007 12:11:38.953 sp = -1
03/15/2007 12:11:38.968
03/15/2007 12:11:38.968 Product Enumeration Results:
03/15/2007 12:11:38.984 INF File Name: d:62fd796336ff97e5e9fdd3HotFixSqlWriter_x64.inf
03/15/2007 12:11:38.984 baselinebuild = 1399
03/15/2007 12:11:39.000 build = 3042
03/15/2007 12:11:39.000 description = Microsoft SQL Server VSS Writer
03/15/2007 12:11:39.015 details = Service Pack for Microsoft SQL Server VSS Writer.
03/15/2007 12:11:39.015 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/15/2007 12:11:39.031 kbarticle = KB921896
03/15/2007 12:11:39.031 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/15/2007 12:11:39.046 lcid = 1033
03/15/2007 12:11:39.046 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
03/15/2007 12:11:39.062 machinetype = x64
03/15/2007 12:11:39.062 package = HotFixSqlWriter_x64
03/15/2007 12:11:39.078 packagetype = Hotfix
03/15/2007 12:11:39.093 productname = Redist9
03/15/2007 12:11:39.093 recommendinstall = 1
03/15/2007 12:11:39.109 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/15/2007 12:11:39.109 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/15/2007 12:11:39.125 splevel = 2
03/15/2007 12:11:39.125 supportdir = d:62fd796336ff97e5e9fdd3
03/15/2007 12:11:39.140 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
03/15/2007 12:11:39.140 version = 9
03/15/2007 12:11:39.156
03/15/2007 12:11:39.156 File Group Details: MSI
03/15/2007 12:11:39.171 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/15/2007 12:11:39.171 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/15/2007 12:11:39.187 File Details: SqlWriter_x64.msi
03/15/2007 12:11:39.203
03/15/2007 12:15:24.734 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
03/15/2007 12:15:24.750 Registry: Cannot read registry key value "PendingFileRenameOperations"
03/15/2007 12:15:24.765 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
03/15/2007 12:15:24.796 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
03/15/2007 12:15:28.875 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
03/15/2007 12:15:28.875 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
03/15/2007 12:15:28.906 Locked file: Checking for locked files
03/15/2007 12:15:30.765 Locked file: C:Program Filesmicrosoft sql server90dtsinnmsdtssrvr.exe (MsDtsServer [MsDtsSrvr.exe] - 1176)
03/15/2007 12:15:57.875 Attempting to pause the 32 bit ngen queue
03/15/2007 12:15:58.078 Installing product: DTS9
03/15/2007 12:15:58.109 Installing instance: Integration Services
03/15/2007 12:15:58.109 Installing target: DEVDB
03/15/2007 12:15:58.125 Stopping service: MsDtsServer
03/15/2007 12:16:00.156 Stopped service: MsDtsServer
03/15/2007 12:16:00.171 Installing file: sqlrun_dts.msp
03/15/2007 12:16:00.203 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log
03/15/2007 12:16:00.218 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
03/15/2007 12:16:00.218 Registry: Cannot read registry key value "Debug"
03/15/2007 12:16:50.578 MSP Error: 29528 The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.
03/15/2007 12:17:35.375 MSP returned 1603: A fatal error occurred during installation.
03/15/2007 12:17:35.453 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
03/15/2007 12:17:35.453 Registry: Cannot read registry key value "Debug"
03/15/2007 12:17:36.515 Copy Engine: Error, unable to install MSP file: d:62fd796336ff97e5e9fdd3HotFixDTSFilessqlrun_dts.msp
03/15/2007 12:17:36.531 The following exception occurred: Unable to install Windows Installer MSP file Date: 03/15/2007 12:17:36.531 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
03/15/2007 12:17:40.843 Watson: Param1 = Do_sqlPerfmon2
03/15/2007 12:17:40.859 Watson: Param2 = 0x7358
03/15/2007 12:17:40.859 Watson: Param3 = sqlLodctr2
03/15/2007 12:17:40.875 Watson: Param4 = 0x7358
03/15/2007 12:17:40.875 Watson: Param5 = utillibsqlperfmon.cpp@303
03/15/2007 12:17:40.890 Watson: Param6 = Unknown
03/15/2007 12:17:40.890 Watson: Param7 = DTS9
03/15/2007 12:17:40.906 Watson: Param8 = Hotfix@
03/15/2007 12:17:40.906 Watson: Param9 = x86
03/15/2007 12:17:40.921 Watson: Param10 = 3042
03/15/2007 12:17:40.921 Installed product: DTS9
03/15/2007 12:17:40.937 Hotfix package completed
03/15/2007 12:17:40.937 Attempting to continue the 32 bit ngen queue
View 2 Replies
View Related
Nov 15, 2006
Hi:
I am getting access denied error "cannot connect to server" while trying to connect Integration Services. I am trying to connect from my laptop to the SQLSERVER database server.
I followed the document "Connecting to a Remove Intergration Services Server" , doc id: aa337083.
But I can connect to IS if I log remotely to the server.
Any thoughts on this ?
Thanks
-Rajesh
I am getting following errors.
===================================
Cannot connect to cvsslmdd1-vm.
===================================
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Program Location:
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
Connect to SSIS Service on machine "cvsslmdd1-vm" failed:
Access is denied.
.
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)
at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.GetData()
at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
===================================
Connect to SSIS Service on machine "cvsslmdd1-vm" failed:
Access is denied.
.
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String bstrMachineName, String& serverVersion)
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)
View 7 Replies
View Related
Sep 13, 2007
Greetings,
I am using Visual Studio 2005 SP1, SQL Server Developers Edition, Both installed recently and updated completely on an XP SP2 workstation (again all updates installed, the necessary ones at least) The issue I am having is when I try to load a solution for Integration services an error message box appears with the following:
An error prevented the view from loading. (Microsoft Visual Studio)
===================================
The specified module could not be found. (Exception from HRESULT: 0x8007007E) (System.Windows.Forms)
This issue was of course occurring before the reinstall of both Visual Studio and SQL Server DE. The issue also extends to creating new projects, in which I am not able to...so the frustration is a little high at the moment, any help would be great...
View 2 Replies
View Related
