Changing Components After A SQL Server 2005 SP2 Upgrade
Mar 22, 2008
I have SQL Server 2005 installed on a machine that was recently upgraded to SP2 (build 3042). The server never had the replication feature installed on it. I attempt to add replication to it and I get an error because (I think) I am installing from the initial version media (CD-ROM, build 1399) and the setup appears to want an MSI file for SP2. Any help is appreciated.
I followed the exact procedures in online help How to: Change Components in an Existing Instance of SQL Server 2005 (Setup), but after I get the Ready to Update page, I get the error box:
An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package €˜SqlRun_SQL.msi€™.
Here is a partial output of the SQLSetupxxxx_ComputerName_Core.log file:
Action 17:44:25: ResolveSource.
Action start 17:44:25: ResolveSource.
MSI (c) (E4!D4) [17:44:25:200]: Resolving source.
MSI (c) (E4!D4) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (E4!D4) [17:44:25:200]: User policy value 'DisableMedia' is 0
MSI (c) (E4!D4) [17:44:25:200]: Machine policy value 'AllowLockdownMedia' is 0
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Looking for sourcelist for product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Adding {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}; to potential sourcelist list (pcode;disk;relpath).
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing net source list.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing media source list.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Trying media source H:ServersSetup.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 2203 2: H:ServersSetupSqlRun_SQL.msi 3: -2147287037
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing URL source list.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Prompting user for a valid source.
MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'DisableBrowse' is 0
MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Browsing is enabled.
MSI (c) (E4:7C) [17:44:25:200]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing net source list.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing media source list.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Trying media source SQLSTDSEL;.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing URL source list.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:44:388]: SOURCEMGMT: Trying source H:SetupSqlRun_SQL.msi.
MSI (c) (E4:7C) [17:44:44:388]: Cloaking enabled.
MSI (c) (E4:7C) [17:44:44:388]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (E4:7C) [17:44:44:403]: SOURCEMGMT: Resolved source to: 'H:Setup'
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4!D4) [17:44:44:403]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Failed to resolve source
MSI (c) (E4!D4) [17:44:44:419]: Transforming table Error.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
MSI (c) (E4!D4) [17:45:02:731]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Product: Microsoft SQL Server 2005 -- Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
I am having a problem when trying to add the Client Components to an existing installation of SQL 2005 Standard Edition SP1 running on Windows 2003 Standard. The server was originally built with SQL 2005 Standard Edition and had SP1 installed at a later date. I am using the CD that SQL was originally installed with which is not a service packed copy of SQL. The reason given when clicking the details button is as follows:
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.
I thought I had applied sp2 successfully but I discovered when I tried to apply the hotfix ( sqlserver2005-kb933097-x86-enu.exe), that the SQL Server Tools and Workstation Components wasn't at the 3042 level.
The recommendation in the log file is to:
"Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch."
Does anyone know where I find the prerequisite patch?
Any help would be appreciated.
Regards Noel
Time: 03/13/2007 18:05:39.045 KB Number: KB933097 Machine: NOEL_EVO OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3152 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition SQL Server Database Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER SQL Server Analysis Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER SQL Server Reporting Services 2005 (SQL2005) ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Notification Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Integration Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER SQL Server Tools and Workstation Components 2005 ENU SP1 9.1.2153 x86 DEVELOPER
********************************************************************************** Products Disqualified & Reason Product Reason SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 3042 installed. Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.
Upgrade Advisor could not detect SQL Server components on the server.
===================================
The network path was not found. (mscorlib)
------------------------------ Program Location:
at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName) at Microsoft.SqlServer.UpgradeAdvisor.SqlDetection.GetClusterInfo() at Microsoft.SqlServer.UpgradeAdvisor.SqlDetection.DetectComponents() at Microsoft.SqlServer.UpgradeAdvisor.FormDetectComponents.Detect()
When running the GUI client, I chose to install the SQL Server 2005 'Client Components' on F:Program FilesMicrosoft SQL Server, the installation put over 700MB of files on my C: drive, but there were less than 400MB of files in the location I specified. Only about 1/2 of the files I expected were put in the location I specified. Why? How can I redirect all of the 'shared' files and other misc. development pieces to install somewhere other than my boot drive? There is no way to specify this when using the GUI, can it be done with a command line install?
Whenever I make a breaking change to a custom SSIS component/tasks and update the Assembly Version, it seems to break my packages beyond repair, telling me it can't load the task:
Error loading Package1.dtsx: Error loading a task. The contact information for the task is "". This happens when loading a task fails.
All of the properties of said task now show:
Could not get value for property 'c-155-designer-name'. Specified cast is not valid.
Typically, a "breaking" change when it comes to code just means that you need to update your components to adhere to the new contract of the updated signatures. But with SSIS, it seems the only solution to this is to completely remove the component, and re-add the new version, and re-enter all of the property values/expressions. If I have a package containing 10 instances of a task that only had one property removed, for example, this results in a very time-consuming process of fixing my package.
So my questions:
1) Am I doing something wrong in my versioning/deployment that is causing my packages to unnecessarily break?
2) If this is just "by design" and the way it's meant to behave, what is the best practice for making breaking changes to custom tasks/components used by many packages? Should I just never change the assembly version, even when it is a breaking change (this seems to be less disastrous)?
3) As a last resort, if I'm stuck with having to fix the broken tasks, is there a better way to fix them rather than having to completely remove them, re-add them, and re-set all of their properties/expressions?
I've got SQL Server 2014 Developer installed, and working.  After rebooting, the event log looks like it's working fine.  However, ever since I uninstalled Visual Studio 2013 Premier and installed Visual Studio 2015 Professional, both with SQL Server Data Tools, whenever I try to start SQL Server 2014 Management Studio, I get "Cannot find one or more components. Please reinstall the application."Is there any way I can avoid uninstalling SQL Server?
I managed to solve this, based on a recommendation (at URL...).  I ran SQL Server's setup.exe, and chose Repair, and now it appears that all is well.
When attempting to install SQL Server 2005 SP1, I receive the error, "a recently applied update, KB913090, failed to install." The Installation complete dialog shows the Client Components product Status as "Failure" with the description detail, "Unable to install Windows Installer MSP file". My Operating System is Windows Server 2003 SP1.
Hi, I learned this from one of SSIS book-Migrating from Data Transformation Services to Integration Services in SQL.
For the design time components, Microsoft has created a special distribution called the Microsoft SQL Server 2005 DTS Designer Components. The Designer Components distribution replaces the components that get uninstalled when you upgrade your last instance of SQL Server 2000. If you want to upgrade all your SQL Server 2000 instances, this is the best and only option for recovering the DTS designer.
Is anybody heard of this 2005 DTS Designer component? Where to download? How it works? Any experience to will be appreciated.
Please can someone give me a url or even their own list of support / unsupported components in SQL server 2005 Standard edition.
I know fuzzy lookup is not supported. Is a slowly changing dimension supported?
Its a bit difficult to tell when I get bizzare "Product level is insufficient" error for even a basic derived column transformation when executing a package using SSIS unless it is executed using a scheduled job....
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh =========== Setup
1) Microsoft Cluster of two nodes. 2) Hardare - HP Blade servers 3) OS - Windows 2003 EE with SP2 4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729 MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603 MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object. MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
This is a fresh install of SQL Server 2005 (64bit) on a Windows 2003 R2 SP2 64bit OS. The Cluster has been built and SQL 2005 has been installed (Database Engine(clustered), Analysis Server(clustered), Notification Server, Integration Server, Reporting Services). SQL 2005 SP2 has been installed.
Now, I want to install Notification Server, Integration Server and Reporting Services on the second node for high availability.
When I select 'Install New Components' from Add/Remove Programs, the System Configuation Checker tells me theres a version difference and to:
To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
I'm using the same binaries as the original install. Could this be a result of installing SQL 2005 SP2?
Can someone help me out with this. I'd prefer using the setup interface instead of a command line script.
I have downloaded Microsoft SQL Server 2005 Enterprise Evaluation Edition ISO from the following site and burned it onto a DVD. http://www.microsoft.com/downloads/details.aspx?FamilyId=6931FA7F-C094-49A2-A050-2D07993566EC&displaylang=en
Prior to this I have installed Visual Studio 2005 Professional Edtion. During setup I have selected all the native client components i.e. Management Studio, Business Intelligense Studio. But after the install I am not able to see them under All Programs-> Microsoft SQL Server 2005. On further searching I have come across this link
First of all, there is no sqlrun_tools.msi under setup folder of the dvd. And also when I tried to change component from Add/Remove programs and following the instructions as specified on clicking Change Installed components all that I see are: Connectivity Components and Software Development kit.
Could someone tell me how can I install Management Studio/ Business Intelligence Studio seperately? I don't want to go through the process of re-installation.
Hi all, Yesterday, I just downloaded the SQL Server 2005 Express (SQLEXPR.EXE) and tried to install it in my Windows XP Pro PC that is on Microsoft NT 4 LAN System. I got the following error: Microsoft SQL Server 2005 CTP setup The Microfost .NET Framework 2.0 is not installed. Please install before running setup. This morning, I downloaded the NET Framework Version 2.0 Redistributable Package Beta 2 (x86) from the Microsoft Download Center and installed it in my Windows XP Pro PC. Then I tried to install the SQL Server 2005 Express (SQLEXPR.EXE) again. This time I got a new error: SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use ADD or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. I am confused and lost in this installation problem. Was the .NET Framework Version 2.0 Redistributable Package Beta 2 (x86) a wrong Microsoft .NET Framework 2.0 I downloaded and installed in my PC? Where is the right Microsoft .NET Framework 2.0 for the SQL Server 2005 Express? Please help and advise. Thanks in advance, Scott Chang
I have a SQL Server 2005 evaluation that has already been installed and setup on a server. I believe it originally had a 180 day eval. There have been numerous databases and users added as well as maintenance plan created...
The eval was put on the machine as an interim solution while waiting for paper work and order processiing things to happen. All the paperwork and ordering... have been completed and I now have the real SQL Server 2005 Standard Edition license key ....
I am very new to SQL Server and need to determine ...
1. Can I update the eval copy to become permanently licensed?
2. Would I want to upgrade the eval to permanent? Will I lose any capabilities by keeping the current eval setup?
If it is reasonable to keep the eval setup
3. How do I go about entering the license key to make it permanent?
If it is necessary to install the new Standard Edition...
4. How do I install it while maintaining the already defined databases, data, users, maintenance plan...
I am trying to upgrade SQL Server Express 2005 Report Server to SQL 2005 Standard and it fails with the following error:
SQL Server Setup did not have the administrator permissions required to copy a file: C:Program FilesMicrosoft SQL ServerMSSQL.8Reporting ServicesReportServer ssrvpolicy.config. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
After I click OK on the message, this whole path where the upgrade is bieng installed dissapears C:Program FilesMicrosoft SQL ServerMSSQL.8Reporting Services. The error is a bit missleading because the file that it is trying to copy rssrvpolicy.config does appear in that upgrade folder so I am not sure why it would try to copy a file that has already been copied.
I was able to upgrade the Database Engine instance fine but can't upgrade Reporting Services due to that error. I have verified that the account that ran the setup had the administrator permissions. Your prompt reply to my question would be greatly appreciatted.
I installed a default SQL Server 2012 instance on Windows Server 2012.I enabled the SQL Browser and changed the TCP port of the instance to 1435. I changed port 1433 to 1435 I was able to connect to the instance using SSMS on another server. Now I have to enter Servername,1435 to make a connection.Why does the SQL Browser not resolve the servername to the right IP address and port 1435? Why am I not able to make a connection when I enter the servername or <servername>MSSQLSERVER? Is a SQL Browser only resolving named instances?This works fine for a named instance. Is there something special about default instances or the SQL Browser?
How do I upgrade Sql Server 2005 Express to SP2 if I also have SQL Server 2005 Enterprise SP2 already on the same box? I installed Sql Server 2005 Enterprise first, then applied SP2, then installed Visual Studio 2008 (which installed SQL Server 2005 Express).
When I try to upgrade Sql Server 2005 Express to SP2 using the special Express edition of SP2, I get an error message that says "None of the selected features can be installed". I end up having to cancel the install of SP2.
I'm left with SQL Server 2005 at level 9.0.3054 and SQL Server 2005 Express at 9.0.3042. How can I bring SQL Server Express 2005 to the same level as SQL Server 2005 Entperprise?
I am trying to upgrade SQL Server 2005 Express to SQL Server 2005 Enterprise Edition. (As a Preparation to install SQLServer2005 Service Pack 2 (CTP))
I tried to upgrade a particular Instance (OFFICESERVERS, which was based on SQL Server 2005 Express ).
During the upgrade I get a message saying that ...
.....Your upgrade is blocked because of edition upgrade rules.....
All other components I selected for Installation are propertly installed (Analysis, Reporting)
The setup log contains the following detail information:
---- Context ----------------------------------------------- Setting status of unmanaged components and removing unmanaged resources
Error Code: 29543 MSI (s) (DC!C8) [13:57:26:265]: Product: Microsoft SQL Server 2005 -- Error 29543. Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. Edition check: Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Error 29543. Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. Edition check: Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='0'> Doing Action: ValidateUpgrade PerfTime Start: ValidateUpgrade : Fri Dec 29 13:57:26 2006 <Func Name='ValidateUpgrade'> <Func Name='updateFeatureSellection'> Error Code: 0x80077367 (29543) Windows Error Text: Source File Name: sqlcaupgradeproduct.cpp Compiler Timestamp: Mon Sep 19 01:07:45 2005 Function Name: sqls::UpgradeProduct::CanUpgrade Source Line Number: 142
The result is the same, i.e.... Your upgrade is blocked because of edition upgrade rules...
Does anybody know about this problem? Some more information about the system: W2K3 R2 Enterprise Edition WSS3.0 MOSS2007 previously installed SQL Server 2005 Express Edition (Version 9.00.2047.00)
Everything I've read says that custom data flow components are built by inheriting from the Microsoft.SqlServer.Dts.Pipeline.PipelineComponent class.
But the stock components such as the Derived Column data flow transformation must each be implemented by their own class. So how do I base my custom components on those classes? The documentation for the PipelineComponent class doesn't list any such subclasses.
In another thread Jamie Thomson very informatively said "The components in SSIS are deliberately atomic (i.e. they do something very specific) so that its easy to put them together to build something greater than the sum of the parts". Which does make a lot of sense. However, I've been finding that I end up having to create exactly the same "pattern" of combined transform components again and again in order to solve the same problem but in different dataflows (or even within the same dataflow). Cut-and-paste-tastic! In order to obtain real re-use, it seems to me like SSIS is crying out for an easy way to create new components by using composition - i.e. the ability to take commonly-used combinations of existing components and create new "super" components (without having to write Custom Transform Components in C#/VB.Net and handle everything in code).
Does anyone know if this sort of functionality is likely to make it into SSIS in the forseeable future?
I have a DB which has its collation set to SQL_Latin1_General_CP1_CI_AS and i need to change it to Latin1_General_CI_AS,
does anyone have any idea how to do this?
i have tried right clicking on the DB and changing its collation in the options tab, but this only changes what the default is, so all the old columns still have the old collatin,
When I change the tcp/ip port to anything other than 1433 my SSIS nor DTS packages run successfully. Does the tcp/ip port have to be on 1433 for the SSIS or DTS packages to run successfully?
We are performing a SQL 2005 SP1 upgrade from SQL 2000 on our Windows 2003 SP1 Standard Edition.
When we run the upgrade, we got a error "Upgrade Advisor Return -1" as a pop-up window.
When we run the Upgrade Advisor separately, we get this error :
===================================
Common Language Runtime detected an invalid program.
===================================
Common Language Runtime detected an invalid program. (System.Xml)
------------------------------ Program Location:
at System.Xml.Schema.SchemaInfo..ctor() at System.Xml.Schema.XmlSchemaSet..ctor(XmlNameTable nameTable) at System.Xml.XmlReaderSettings.get_Schemas() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReportController.LoadAndValidateDataFile() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReport.ValidateDataFile() at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAIssueReport.Refresh() at Microsoft.SqlServer.UpgradeAdvisor.ReportPanel.OpenReport(String reportFile)
We are in a lost for solutions. We do hope to hear from anyone asap...
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log: Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. Database Mirroring Transport is disabled in the endpoint configuration. Starting up database 'master'. Converting database 'master' from version 589 to the current version 611. Database 'master' running the upgrade step from version 589 to version 590. Error: 946, Severity: 14, State: 1. Cannot open database 'master' version 589. Upgrade the database to the latest version. System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1 Error: 928, Severity: 20, State: 1. During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause. Error: 15151, Severity: 16, State: 1. Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
