Ssis Error Converting Database From Version 539 To The Current Version 611
Jan 7, 2008
I have an ssis package that downloads a SQL Server 2000 database and restores it to a SQL 2005 server. Ninety-five percent of the time it runs just fine, but every so often the job fails and I get the following set of error messages in the log file. (I have had to delete some of the proprietary information for this message to satisfy my boss like putting in [Database name] in place of the actual name of the database in the error message).
OnError, Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Converting database [Database name] from version 539 to the current version 611.
OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Converting database [Database name] from version 539 to the current version 611.
OnError,Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Database [Database name] running the upgrade step from version 539 to version 551.
OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,Database [Database name] running the upgrade step from version 539 to version 551.
OnError,Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,The transaction log for database [Database name] is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,The transaction log for database [Database name] is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
OnError,SQL5,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,RESTORE could not start database [Database name].
OnError,SQL5,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,RESTORE could not start database [Database name].
OnError,SQL5,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,-1073548784,0x,Executing the query "RESTORE DATABASE [Database name]
FROM DISK = '[Path to back up file]' WITH REPLACE,
MOVE 'ASP_Live_Data' TO [Path to MDF file],
MOVE 'ASP_Live_Log' TO [Path to LDF file]" failed with the following error: "RESTORE DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
OnError,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,-1073548784,0x,Executing the query "RESTORE DATABASE [Database name]
FROM DISK = '[Path to backup file]' WITH REPLACE,
MOVE 'ASP_Live_Data' TO [Path to MDF file]',
MOVE 'ASP_Live_Log' TO [Path to LDF file]" failed with the following error: "RESTORE DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
OnTaskFailed,Restore backup file to DB,,,1/6/2008 2:59:31 AM,1/6/2008 2:59:31 AM,0,0x,(null)
Is there any way to restore a database of higher version to lower version.
E.g. I have created a database in sql server 2012, created some tables & procedures in that.I took Full backup of that database. Can I restore it to sql 2008r2 or any lower version.
I know direct restore is not possible, I have to use either import or export option or generating script,but i want to know is there any easy step to do so.
I have tried to attatch a database ,created by SQL server Express within a C# application , in SQL server 2005 Enterprise edition, but the following error message appears:
-----------------------------
TITLE: Microsoft SQL Server Management Studio ------------------------------
Attach database failed for Server 'MEDO'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft SQL Server&ProdVer=9.00.1187.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach database+Server&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The database 'E:X.MDF' cannot be opened because it is version 611. This server supports version 607 and earlier. A downgrade path is not supported. Could not open new database 'E:X.MDF'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
------------------------------
so , how can I solve this problem , I need to reed the data resides in the tables of 'X' database , how can I do it?? please help me.
Now, I checked and verified that my backup version of SQL Server is the same as the version installed on the computer I'm restoring too.
I have SQL Server on a production machine that I backed up and want to test a full restore on a dev machine to make sure it will work when I need it to.
Now that I've run the restore command on my tape backup and go to restart the SQL server service I receive:
Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
I'm afraid I don't understand why this is happening. If the builds are the same, then shouldn't restoring the MASTER database have worked normally and I'd be able to restart the service now?
Since some analysis services features are only available in Enterprise version , I have to upgrade my SQL 2005 server from standard edition to enterpise edition.
So I uninstall originial standard version of analysis service and install a Enterprise version. However, the analysis service is still a standard version after installation.
Is it possible to keep data engine as standard version and install a enterprise version of analysis service?
I have copied a SQL Server 70 database to SQL Server 2000. Got error message during copying - 'unable to attach db' and when click on the db on SQL Server 2000, go erro - error 946 cannot open database version 525. Upgrade the database to the latest version. Anyone has any idea??:confused:
Hello,I have been searching and reading a lots of information on the microsoft website about the different version of SQL server, but still can not make my decision.In term of performance, is there a real big difference between the workgroup and the standard version? The workgroup is limited to 3 GB of RAM while the standard is unlimited, would that really change the performance if my server has 16Gb or RAM?The price difference is pretty substantial so if could only have to buy the workgroup , it would be better.One more question, regarding the type of licence, my server has 2 processors, could I avoid buying 2 licences and get the Server plus CAL instead. I am using this server to host 4 web-application running on SQL server. Each database is about 15 MB.Thanks in adavance for your advises.Arno
I am wondering if it is possible to change from SQL Server Enterprise Evaluation Version to Developer Version. The reason is because the Enterprise Evaluation version expires after 180 days. So if I create reports and cubes in Enterprise Evaluation I can import them into Developer Edition right? Should I remove the Enterprise Evaluation version after 180 days or leave it then install Developer Edition?
I have received the error message "Package migration from version 8 to version 6 failed".I have developed a SSIS package with Visual Studio 2013 which gives me PackageFormatVersion of 8. I then deploy my package to the ssisdb catalog that is running on a SQL Server 2012, this works fine but when I try to execute the package the error arises…due to SQL Server 2012 has a PackageFormatVersion of 6 and it can’t run something that has a greater version.I haven’t seen any good solution for this but one that would work for me would be to upgrade the Integration Services Server from 2012 to 2014, leaving everything else in 2012 (database, ssms, ssas, ssrs).Would this solve the package format problem? Would I then be able to execute my packages in the ssisdb catalog?
I have the trial version of SQL Server 2005 installed and have setup a couple of databases. This trial version will expire in another few weeks. I recently purchased a copy of the software and want to install it. Will I lose my databases, user info, etc? How do I go about installing without losing anything?
We have a 64bit os machine that we accidently loaded the 32 bit version of sql server on. We now want to upgrade it to 64 bit sql server, but we now have a production database on it. My understanding is that all I have to do is detach the production database, upgrade to 64bit sql server, then reattach the database. Is this really all I have to do?
I started this thread as the last attempt to sort the issue out.
I have an SSIS package that loads data from a .csv file into my database. It works fine on my developer machine. I start it programmatically or from Management Studio or from Visual Studio, and it works. Then I deploy it to the MSDB database on the computer on which it will have its final place. There again I can start it from Management Studio or from Visual Studio (using the source file), and it works. But when I start it programmatically, it just fails telling me:
Package Warnings: Package Errors: The version of component "****" (11773) is not compatible with this version of the DataFlow. Component "component "Derived Column" (13627)" could not be created and returned error code 0x80070005. Make sure that the component is registered correctly. The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Flat File Source;Microsoft Corporation;Microsoft SqlServer v9; (C) 2005 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;1". component "Agreement File" (11773) failed validation and returned error code 0xC0048021. One or more component failed validation. There were errors during task validation.
Maybe the source of the problem is that this machine is a 64-bit one, while the developer machine is 32-bit one. But why does the package run fine when I start it from Management Studio?
Can some one here give me more insight about how to upgrade a SQL Server 2005 Standard Version (32 bits) to a SQL Server 2005 Enterprise Version (32 bits) as default instance on a Windows 2003 enterprise OS (32 bits). I want to know what is the easist way and what is the safest way. May I preserve some settings I have for the STD version, or I have to start from strach again to configure the server? Is there any catches, anything I should have attention to (We are using heavily about CLR and fulltext indexing)?
Hello, I installed the SQL Server 2k EnterPrise version and developer version on the same version, and the developer version is an instance "Development". How do I expose both of them to internet? Just open both of them to port 1433? And on the client side, just say IP and IP/Development? Do I need specific set up, will they conflict? Thanks,
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.8.54'. the expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. I'm getting this whenever try to access the report server via SSMS, I have tried to upgrade via the Reporting Service Configuration Manager but get an error message similar to above except it says: The database version (C.o.8.54) does not match your Reporting Services installation. This version of the database cannot be upgraded. You must use a different database. Has anyone seen this before? I can create a new database, but don't want to loose all my reports. Any ideas. Oh, not even sure if the backups exist from before this error, I've spent 2 weeks trying to get access to the server so I could try to upgrade, only to get the above results. Thanks for your help, David
I downloaded the 101 Samples installation (i.e. 101SamplesCS.msi) from Microsoft's website, which contains SQL Server database files.
While working with the databases in the "Data Access" samples from the 101 Samples projects, I get the following error:
"Database <mdf_name> cannot be upgraded because its non-release version (600) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database..."
I assume the database files were created with a beta or CTP version of SQL Server 2005. Does anyone know where I can get an updated version of these database files or scripts to update them?
i am working on upgrading the clients and server computers from 2000 MSDE to 2005 SQL Express Adv. Plan to upgrade using the template.ini.
i can find the version of sql server running on th server by @@version but how do i find the version of client connctivity components the computer has installed in order to ugrade?
1. somehow i need to know whether to upgrade a client computer CONNECTIVITY COMPONENTS from 2000 to 2005?
2. is there a way to enable tcp/ip in installation script of SQL Express?
Can I set up sql server 7.0 standard version in cluster enviorment, what the different betwent sql server 7.0 enterprise version and standard version? any problem I may encouter when I install the SQL server 7.0 standard version in Cluster enviorment? Thank you very much. Judy
We have a Sqlserver 2005 Installed on One of our servers.I wanted to know whether the installed database is a Evaluation copy or Licensed Copy.How to Evaluate this. Do we have to check any Log files etc for knowing whether it is evaluation copy or Licensed copy. Please help me Asap. thanks in Advance
I recently upgraded to SQL Server 2005. My databases are stable and functioning perfectly. However, these databases are using the 32-bit version of SQL Server. The servers are going to be upgraded to 64-bit processors and new Server 2003 64-bit OS's.
Everything I have been able to find says that it is a simple process of backing up the databases in the 32-bit environment and restoring them in the 64-bit environment.
Could it really be that easy? I am looking for someone who has done this to provide any "heads up" commentary on what to look out for during that process. Can anyone provide some information on this process?
Does anyone know how to get SQL Server versions, Service pack versionsand the Server that instance of SQL is running on a network. I haveseen some threads on how to list SQL servers in a network but I need tofind more info about these SQL servers.Any help appreciated..!Thx...
Is it possible to use versioning at all with SSIS components?
My experience so far is that I have not figured out how version them at all, because if I change the version number, then apparently the <property name="UserComponentTypeName" ...> has to be changed in every single reference to the component, in every dataflow, in every single dtsx file that uses the component at all -- this will be a tremendous headache as some of this stuff is in source control. It seemsl clearly infeasible to check out and substitute and change all these references, and check them all back in, except very infrequently -- surely not feasible to do it for each small change.
I am in the habit of versioning dlls and assemblies, and actually changing at least a minor build number for each actual change, so I am a bit unhappy to find that apparently I cannot feasibly do this for a custom SSIS component :(
(I just find a dislike at apparently being forced to leave the version number invariant when I make code changes.)
What I would be very happy with, is if there were a way to adjust all the references in all the dtsx files, to refer to only the major and minor build numbers say, specifying that I am not picky about the revision numbers below those, so that it will find the latest component in the GAC matching the major and minor numbers.
That way I could still update the component version with each code change, which would make me happy, and not have to edit a zillion dtsx occurrences (not having to do that would also make me happy).
Anyone know if that is possible?
I'm hoping it is, and that it is only my ignorance at component references preventing me from doing so.
I have a problem, and I'm fairly sure I know what the answer is going to be, but I'll ask it anyhow.
I have a database which I switched over to SQL 2005 last year, and in the process converted all the DTS packages I had to import the data over to SSIS. We have several reports that we generate to Excel files, and I attempted to migrate these over also, but they would never run in production. Worked fine in when I developed the packages, but nothing I did would make them run in production, so I droped back and punted by modifying the DTS packages to point to the new database. Everything works fine that way, but we want to retire the old SQL box.
When I started digging into the problem by running the package from the dev platform on the production box, I got the following error info:
Error: 0xC0202009 at TSC_Outbound_Calls, Connection manager "Excel Connection Manager": An OLE DB error has occurred. Error code: 0x80040154.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC00291EC at Create Excel Table, Execute SQL Task: Failed to acquire connection "Excel Connection Manager". Connection may not be configured correctly or you may not have the right permissions on this connection.
Task failed: Create Excel Table
What I have seen about this error is that it cannot find a 64-bit Excel driver, which (I believe) does not exists. So, as the server is already built with Server 2003 64-bit and SQL 2005 64-bit, does anyone have a suggestion to help me get these exports working again, or am I as stuck as I think I am?
I have a database which was created in a beta release of SQL Server Express. It was also create when I had the .Net Framework 2.0 Beta installed.
Since then, I have installed .Net Framework 2.0 (Current Release) because that is what was required for MS SQL Server Management Studio Express.
When I try to connect to the DB now it says Cannot connect to server.
I also have the mdf/ldf files. When I try to attach them on another computer running the latest version of SQL Server Express it says:
Database 'Name' connot be upgraded because its non-release version (587) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this vertion of sqlservr.exe. You must re-create the database....
Any ideas how i can get the mdf/ldf files converted over? Or how I can attach the the ealier version of sql server express?? thanks.
we have a backup of a database from a release version with version number 9.00.1399 and we wanted to restore it to a server with version number (9.00.1116) CTP release. we were issued a version incopatibility message. is it possible to backup from a 9.00.1399 release with a backup file compatible for a CTP release, is there an available option during backup? thanks!
1.) I have developed some SSIS packages that are currently out in production. We are on to the next phase of development and enhancments to the packages are being developed as a phase 2 release. I can push these changes to a QA setup for testing. But I also need to do fixes to the existing packages out in production and run them through testing. Unfortunatly I do not have an extra server to have a QA and a QA Current Production setup for seperate testing. So is there any way to run two versions of the same package on one (the same) server? I presently store the packages in the MSDB. Can I have or specify which version of package to run?
2.) Additionally, can you run multiple configurations for a single version of a package but only call one of them? For example can I create two configurations and then specify which one to use when calling the package to run? So that I could have code pass which configuration to load which would change connection strings and such. Any examples would be awesome.
The database 'maindb' cannot be opened because it is version 611. This server supports version 603 and earlier. A downgrade path is not supported.Could not open new database 'maindb'. CREATE DATABASE is aborted.Could not attach file 'I:DataWebaspdotnet.skskuska_14edf6b4-8caa-4d92-8324-89e1108255bcwwwApp_DataDatabase.mdf' as database 'maindb'.The url is: http://skuska.aspdotnet.sk/Database.aspxIf you have some idea, how to fix it, please post it.Thanks in advance!
I am having a question about SSIS. Is it a totally new product in SQL Server 2005 or it is a upgrade version of previous version DTS? Thanks a lot for any guidance for that.
