I have tried to install the package on the SQL server as explained in http://msdn2.microsoft.com/en-us/library/ms365344.aspx .
I did not see any error message or anything when I installed. But there were not any package installed when I opened SQL Server Management Studio and connected to Integration Service under stored package. What did I do wrong? Why I was not able to save my package on the SQL server?
I get an error when trying to install the SQL Native Client. It
says it cannot find the installation package and to use a valid copy of
'sqlncli.msi'. I've downloaded the Express setup twice and get
the same error from both of them.
I'm attempting this in a VMWare session setup for Windows 2K, Advanced
Server. I am trying to test my installation and setup
procedures. This is not a production setup, just install testing
and documentation. I have allocated only 272MB to the VMWare
session, which is why the system doesn't meet the recommended settings.
Any help would be greatly appreciated.
Below is the Summary.txt output file.
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows 2000 Advanced Server Service Pack 4 (Build 2195)
Time : Wed May 03 09:54:23 2006
CPCWIN2KVM1 : The current system does not meet recommended hardware
requirements for this SQL Server release. For detailed hardware
requirements, see the readme file or SQL Server Books Online.
Machine : CPCWIN2KVM1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : CPCWIN2KVM1
Product : SQL Native Client
Error : An
installation package for the product Microsoft SQL Server Native Client
cannot be found. Try the installation again using a valid copy of the
installation package 'sqlncli.msi'.
--------------------------------------------------------------------------------
Machine : CPCWIN2KVM1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Failed
Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_SQLNCLI_1.log
Last Action : InstallFinalize
Error String : An installation package for the
product Microsoft SQL Server Native Client cannot be found. Try the
installation again using a valid copy of the installation package
'sqlncli.msi'.
Error Number : 1706
--------------------------------------------------------------------------------
Machine : CPCWIN2KVM1
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : CPCWIN2KVM1
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_MSXML6_1.log
--------------------------------------------------------------------------------
Hey, I've a few jobs which call SSIS packages. If I run the SSIS package, it runs fine but if I try to run the job which calls this package, it fails. Can someone help me troubleshoot this issue? None of my jobs that call an SSIS package work. All of them fail.
Thank you
Tej
Hi,
In our project we have two SSIS package.
And there is a task (Execute SSIS package) in First package that calls the execution of second package.
I m continuously receiving an error "Failed to decrypt protected XML node "PackagePassword" 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."
As we are running first package by job, job runs successfully logging above error
The protection level of second package is set to "EncryptSensitiveWithUserKey"
Can anybody please suggest how to handle it?
I have a SSIS job, one of the last steps it performs is to execute a SQL 2000 DTS package. This has to be done as a SQL 2000 DTS package as it is performing rebuilds of SQL 2000 Analysis Services dimensions and cubes. We've found that when the DTS fails the SSIS job is happily completing showing as a success, we would prefer to know it went wrong.
As far as I'm aware SSIS merely starts the DTS off and doesn't care about it's result. I've taken a look in to turning on the logging for the execute DTS package and thought that the ExecuteDTS80PackageTaskTaskResult would give me the answer I need...but is merely written to the log not available as an event-handler. It also looks like it is not safe to put a SQL task in as the next item to go look at the SQL 2000 system tables to look at the log for the DTS package as the SSIS documentation warns that the DTS package can continue to run after the execute DTS package task has ended.
Ideally I want any error raised within the DTS package to cascade up to be an error in the SSIS job, I can then handle it appropriately. I cannot find a way to do this. Is there a way?
If not, can anyone suggest how in the remainder of the SSIS tasks I can be sure that the DTS has completed before I start any other tasks that will check for the SQL 2000 log of its execution?
Hi,
I have developed an SSIS package for ETL purpose. I am invoking the SSIS package through .Net console application by referencing the ManagedDTS Assembly. I am able to execute the package in Sql Server 2005 Developer Edition and it runs fine till completion.
But when i try to execute the packahe in Sql Server 2005 Standard edition, by invoking the package through .Net console application the status of the package is failure.
Can any one help me how to over come this problem.
Hi All,
I am in the process of moving from a 32-bit SQL Server 2005 Enterprise (9.0.3054) to a 64-bit SQL Server 2005 Enterprise (9.0.3054 with 4 CPUs and 8GB of memory on Win 2003 SP2) and the process has been very frustrating to say the least. I am having a problem with packages that I created on my 64-bit SQL Server. I am importing a few tables from the 32-SQL Server into the 64-bit SQL Server using the Task --> Import to create the package.
Sometimes when I am creating a package I get the following error in a message box:
SQL Server Import and Export Wizard
The SSIS Runtime object could not be created. Verify that DTS.dll is available and registered. The wizard cannot continue and it will terminate.
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Windows.Forms)
Other times when I run a package that has run successfully before I get the following error:
Faulting application dtexecui.exe, version 9.0.3042.0, stamp 45cd726d, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x025d23f0.
Other times I get this error message:
.NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (79FFEE24) (80131506)
And still other times
The package appears to hang when running. By this I mean that the Package Execution Progress shows progress up to a point then it just stops. (The package takes about 17 seconds to run normally) CPU usage is at 1% and the package cannot be stopped.
I have deleted and re-created the package several times and I have also re-installed the service pack on the SQL Server (9.0.3054) but that did not help.
Does anyone have any other suggestions to try?
Thanks.
I would like to standardize SSIS development so that developers all start with the same basic template. I have set it up so it is an available template ( http://support.microsoft.com/kb/908018 ) but I would like it to be the default when a new project or package is created. Is this an option?
View 4 Replies View RelatedI would like to fetch the data flow component name while package is executing. Since system variable named [System::SourceName] only fetches name of the control flow tasks? Is there a way to capture them?
View 5 Replies View RelatedHi there
We have a SSIS run which runs as follows
The master package has a configuration file, specifying the connect strings
The master package passes these connect-strings to the child packages in a variable
Both master package and child packages have connection managers, setup to use localhost. This is done deliberately to be able to test the packages on individual development pc€™s.
We do not want to change anything inside the packages when deploying to test, and from test to production. All differences will be in the config files (which are pretty fixed, they very seldom change). That way we can be sure that we can deploy to production without any changes at all.
The package is run from the file system, through a job-schedule.
We experience the following when running on a not default sql-server instance (called dkms5253uedw)
Case 1:
The master package starts by executing three sql-scripts (drop foreign key€™s, truncate tables, create foreign key€™s). This works fine.
The master package then executes the first child package. We then in the sysdtslog get:
Error - €ścannot connect to database xxx€?
Info - €śpackage is preparing to get connection string from parent €¦€?
The child package then executes OK, does all it€™s work, and finish. Because there has been an error, the master package then stops with an error.
Case 2:
When we run exactly the same, but with the connection strings in the config file pointing to the default instance (dkms5253), the everything works fine.
Case 3:
When we run exactly the same, again against the dkms5253uedw instance, but now with the exact same databases defined in the default instance, it also works perfect.
Case 4:
When we then stop the sql-server on the default instance, the package faults again, this time with
Error - €śtimeout when connect to database xxx€?
Info - €śpackage is preparing to get connection string from parent €¦€?
And the continues as in the first case
From all this we conclude, that the child package tries to connect to the database before it knows the connection string it gets passed in the variable from the master package. It therefore tries to connect to the default instance, and this only works if the default instance is running and has the same databases defined. As far as we can see, the child package does no work against the default instance (no logging etc.).
We have tried delayed validation in the packages and in the connection managers, but with the same results (error).
So we are desperately hoping that someone can help us solve this problem.
Thanx,
/Nils M - Copenhagen
hi,
I am interested in Passing value from a child Package variable to the Parent package that calls it in ssis.
I am able to call the Child package using the execute package task and use Configurations to pass values from the parent variable to the child, but I am not able to pass the value from the child to the parent.
I have a variable called datasetId in both the parent and child. it gets computed in the child and needs to be passed to the parent...
Any suggestions?
Thanks for any help in advance..
smathew
Deployed Report having SSIS package as source do not work when Indirect Package configuration is used in ETL package. It seems ETL package when called/executed from Report manager does not recognize environment variable to pick up the dtsconfig file.
The Report works when Direct package configuration is used to same dtsconfig file.
What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod very difficult.
Dear All,
I now have two SSIS package, "TESTING" and "LOADING". The "TESTING" package have an execute package task that call the "LOADING" package. When I want to execute the TESTING package, how can I setup the connection string so that I can edit the password of the database connected by the "LOADING" package?
Regards,
Strike
Hi,
I am using the SQL Package Installation Wizard to deploy my SSIS packages on to a 64-bit SQL Server and I am getting this error, Library not registered. I am also getting the same error when I tried to import a SSIS package from a 32-bit SQL Server. I was able to save my SSIS packages to the 64-bit SQL Server one by one from Visual Studio. My server is run Windows 2003 Enterprise x64 with SP1, and SQL 2005 Enterprise x64 with SP1 and hotfixes. 64-bit .Net Framework is also registered on the machine.
This is the error from the installation log file:
Exception details: Microsoft.SqlServer.Dts.Runtime.DtsTaskException: Library not registered.
---> System.Runtime.InteropServices.COMException (0x8002801D): Library not registered.
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
Thanks in Advance.
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll.
-----------------------
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--------------------------
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
I have two SSIS packages in a project, one calling the other. The parent package works fine in my local mechine. After they are deployed to the production, I schedeul jobs to run the packages in the SqlServer. The child package works fine if I run it alone, but the parent package could not find its child package if I run the parent package . As I checked, all xml config files and the connection string pointing to the child package were set correctly. It seems the parent package did not use the xml config file. Can someone help me? Thanks in advance.
View 9 Replies View Related
I have successfully created a SSIS package which execute a DTS 2000 package and with no problem to execute the task. But I failed to schedule this package. I was not success in setting the logging. When running the package in command line:
dtexec file "C:Documents and SettingslyangMy DocumentsVisual Studio 2005ProjectsTraingDTSTraingDTSDTSTraining.dtsx"
Error: 2008-03-24 08:03:24.36
Code: 0xC0012024
Source: Execute DTS 2000 Package Task
Description: The task "Execute DTS 2000 Package Task" cannot run on this edit
ion of Integration Services. It requires a higher level edition.
End Error
Warning: 2008-03-24 08:03:24.38
Code: 0x80019002
Source: DTSTraining
Description: The Execution method succeeded, but the number of errors raised
(2) reached the maximum allowed (1); resulting in failure. This occurs when the
number of errors reaches the number specified in MaximumErrorCount. Change the M
aximumErrorCount or fix the errors.
End Warning
DTExec: The package execution returned DTSER_FAILURE (1).
Any help will be greatly appreciated.
(32 bit machine, standartd edition of SQL 2005)
Hi,
I am making use of the DtUtil tool to deploy my package to SQL Server.
Following is my configuration:
32-bit machine and 32-bit named instance of Yukon.
I have some package variables which need to be set in the code.
Previously I did it as follows:
Set the package variables in the code. For example:
pkgFile.Variables["User::DestinationServerName"].Value = <myvalue>
Deploy the package as follows:
applnObj.SaveToSqlServer(pkgFile, null,
destinationServer, null, null);
Here the package was successfully deployed and when i open those packages using BIDS, I am able to see that the variables are set to the values as doen in teh code.
Because of oen problem I am not using SaveToSQLServer method. So I switched to DTUtil tool.
Now I am doing it this way:
Set the package variables as before.
Deploy the package to SQL Server using DTUtil tool.
Now is the problem:
The package is successfully deployed. But the variables are not set to the value that I have specified in the code.
I also tried DTexec utility to set the package variable. Even that does n't work.
Can anyone help me out? Is there any alternate method to set package variables?
Thanks,
Sandhya
Hi
We are planning to use SQL Server Integration Services in our company. I have some doubts about SSIS installation. Can some one help me...
1. What is CPU requirmenet for SSIS?
2. What is the memory requirement for SSIS?
3. Should SSIS installed on a separate staging server or can it be installed in the same box of SQL Server 2005.
Thanks & Regards
Shri.DBA
Hi
I downloaded the SQL server 2005 trival version (180 days trival
peroid) from the MS website. But i got a error saying that I have
don't have enough space to extract the package on my C: drive when I
do the installation. Actually I have 13g space on my c drive, so I
may be miss something? I looked up the internet and found a solution
using SET TEMP=C:TEMP and SET TMP=C:TEMP, but it doesn't work for me.
Does anyone have a better idear? I had a SQL 2005 express edition
installed on my laptop before, but I have remove it, maybe I did not
remove it completely and cause this problem?
Thanks in advance
Li
when i run the job using network service account credentials job is failing. But when i run the package individually, it is tasting success. when it runs as job, this is the error message i am getting
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
I have changed to 32-Bit run time and ran the excel package, even then it is failing...i tried to use my credentials (i am admin on the box), even then it is failing...please suggest
We installed SQL 2005 Developer edition and it appears that Integration Services is installed and running (if I go to SQL Server Configuration Manager I can see it) but if I go to the BIDS and try to open a new project the only project type listed is Reporting Services. Also, if I go to SQL Server Management Studio, in the Connect to Server, it is not listed.
Any thoughts on why this would be the case?
The logon is set up as Network Services. Could that cause the problem?
Thanks.
Hi everybody,
I've a windows 2003 server machine, and try to install sql server 2005 with reporting services, analysis services and integration services. After the installation finishes, i'm trying to connect to the integration service with Management studio but i can't. When I select the server type as "Integration Services" the "server name list" comes empty. I remember tehere should at least exist the local machine name. Anyway, when i click <browse more> link, i can see my machine's name in the server list; but when i select it, an error popup appears saying that:
"Failed to retrieve data for this request
Connect to SSIS server on machine <machine name> failed.
The specified service does not exist as an installed service."
I really can't see the SSIS under windows services. When i try to reinstall the SSIS, i get an error saying that SSIS has already been installed on my machine. I tried uninstalling an reinstalling all SQL components for several times, but the result is the same.
Any help would be appreciated. Thanks..
isaya
Part of our product will be using several SSIS packages. One of our installers wants to be able to create a .cmd file that will run DTEXEC against one of the packages, with the correct config file specified. It had been assuming that SQL Server was installed in the Program Files special directory, but that's not always the case.
What is the correct way to locate the installation of SSIS? In fact:
What is the correct way to determine whether SSIS is installed?
What is the correct way to determine the version and SP that is installed (I want to require SP2)
I had been using the values under HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server90DTSSetup until I found an SP2 machine with SSIS installed which did not have these keys. Where's the right place to look?
running ssis package with ssis run time compoenents and sql server 2000...
Is it possible to run ssis packages that point to servers on sql server 2000
without installing sql server 2005 ?
Can we just install runtime for ssis and run the packages ?
Please explian with links if possible
thanks a lot
I want to achieve the following in (SSIS/SSDT for SQL 2012) -Â
I have a generic SSIS package which simply sends out email notifications using SMTP email task (this package is within its own project, and has project level input parameters).
I need to be able to call this package in the Event handler section of every package (numbering in about less than 60) that we have. These packages are within their own respective projects.
I thought I could use the "execute package task", but it turns out , using this, I cannot call a package that is part of some other project. I also cannot call a package that is stored in the CATALOG. Is there any way I can do this ?
When I call the child package , I should be able to send in parameters like - error information and package name of the Parent package.
I have an SSIS package (TransAgentMaster) that I recently modified to include a call to a child package via the file system. The child package creates a text file. When I run the package in dev studio then the child package/text file is produced.
I then imported the TransAgentMaster as a stored packagesfilesystem package into SQL SSIS and executed the package. The child package produced the text file.
I then ran the SQL Server Agent to see if the child package would work and it did not generate the text file. Thus after updating a SSIS package importing the package into SSIS the job that calls the package will not call the child package. Please not that the TransAgentMaster package calls 7 children packages €¦ just not my new one.
Any thoughts why the agent will not run the child newly crated childe package?
Hi,
While I am trying to install SQL server 2005 I get the following message - "Machine does not have a product that matches the installation package". The installation does not occur.
I am using Windows 2000 Professional SP4 and using 32 bit installer - SQLServer2005SP2-KB921896-x86-ENU.exe
Help would be appreciated... thanks.
Regards,
Ravindranath Kini
Hi There
I installed Sql Server 2005 and SSIS to the C: drive of a server.
However i am going to install 3 more instances on this server and i want to install SSIS on the RAID drive.
So i uninstalled SSIS, then i installed another Sql Server instance on the D drive.
Now when i try to install SSIS, when i go to advanced and browse for installation path it is greyed out and it says that the path has already been bound to the 90DTS folder of the first instance i installed on the C: drive, so basically i dont know how i can install SSIS to another drive ???
Please help.
Thanx
How to Install SQL Server SSIS Designer? Is it part of SQL Server Buisness Intelligence?
View 5 Replies View RelatedI bought a new HP server with Windows 2003 SBS Premium.
I also was told buy the company how installed the server, that they installed all the components of SQL.
When another company came to install a new business software for us, they told me that the Integration services is not installed.
We tried together to install the SSIS with no luck.
When we run the Setup(or used Add/Remove software) we couldn't find the Integration services check box in the list of the setup.
I also asked assistans from the company that i bought the server fromk, and they also couldn't understand where is it.
We have an HP Proliant server, Windows server 2003 small business preminum SP1, SQL server 2005.
I was told that without the SSIS we can't start working with our new software, so this is very urgent for us.
Hi,
I have tried to install SSIS going steps msdn2 using "mssql setup" but my "ssis" option is not available for installation.
Pls, help!
Hi everyone,
I've a problem which I think a lot of SQL Server 2005 users had already ...however I didn't found any answers so far. Maybe anyone of you might know.
I have installed SP1 for SQL Server 2005 on 2 systems, one is an Enterprise Edition (english) on a Win. 2003 SP1 system and one is a Developer Edition (also english) on a Win. XP Prof. system.
On both systems the installation process of the SP1 worked fine except that it gave me the message "Reboot required" on the step installation of SQL Server Native Client.
After my reboot I reexecuted the installation of SP1 with the result of no error nor reboot message. Everything seemed fine....
However when I checked the status of the services I recognized that the SSIS has switched from LOG ON AS ...my specific login.... to NT AUTHORITYNetworkService and the automatic startup failed.
I tried to change the login to my previous login which also failed. It tried to change it to any other possible login but the startup with all logins failed with the error message:
The service did not respond to the start or control request in a timely fashion.
The event log of the system does tell me the same error message. The summary log of the SP1 installation doesn't show any error or warning message except "Failed to read registry key: Debug". Enclosed is the log file:
05/02/2006 22:11:09.609 ================================================================================
05/02/2006 22:11:09.625 Hotfix package launched
05/02/2006 22:17:22.296 Attempting to install instance: SQL Server Native Client
05/02/2006 22:17:22.312 Attempting to install target: MHPA0F7C
05/02/2006 22:17:22.312 Attempting to install file: sqlncli.msi
05/02/2006 22:17:22.328 Attempting to install file: e:de43f41a74855a4cfc41014b760758HotFixSqlncliFilessqlncli.msi
05/02/2006 22:17:22.328 Creating MSI install log file at: D:WINNTHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log
05/02/2006 22:17:22.343 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
05/02/2006 22:17:22.343 Failed to read registry key: Debug
05/02/2006 22:17:38.437 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/02/2006 22:17:38.515 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
05/02/2006 22:17:38.515 Failed to read registry key: Debug
05/02/2006 22:17:38.515 Pending reboot, successfully installed file: e:de43f41a74855a4cfc41014b760758HotFixSqlncliFilessqlncli.msi
05/02/2006 22:17:38.515 Successfully installed target: MHPA0F7C
05/02/2006 22:17:38.515 Successfully installed instance: SQL Server Native Client
05/02/2006 22:17:38.515
05/02/2006 22:17:38.515 Product Status Summary:
05/02/2006 22:17:38.515 Product: SQL Server Native Client
05/02/2006 22:17:38.515 SQL Server Native Client (RTM ) - Reboot Required
05/02/2006 22:17:38.515
05/02/2006 22:17:38.515 Product: Setup Support Files
05/02/2006 22:17:38.515 Setup Support Files (RTM ) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Database Services
05/02/2006 22:17:38.531 Database Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531 Analysis Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531 Reporting Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Notification Services
05/02/2006 22:17:38.531 Notification Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Integration Services
05/02/2006 22:17:38.531 Integration Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Client Components
05/02/2006 22:17:38.531 Client Components (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: MSXML 6.0 Parser
05/02/2006 22:17:38.531 MSXML 6.0 Parser (RTM ) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.562 Product: SQLXML4
05/02/2006 22:17:38.593 SQLXML4 (RTM ) - Not Applied
05/02/2006 22:17:38.687
05/02/2006 22:17:38.687 Product: Backward Compatibility
05/02/2006 22:17:38.687 Backward Compatibility (RTM ) - Not Applied
05/02/2006 22:17:38.687
05/02/2006 22:17:38.687 Product: Microsoft SQL Server VSS Writer
05/02/2006 22:17:38.687 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/02/2006 22:17:38.687
I know there are a lot more LOG files in the directory ..HotFix.. which might tell more about the problem. However I don't know in which file I have to look.
Can anyone help me?
Regards,
Stefan