When I upgraded my server from SQL-6.5 (service pack 5a) to SQL-7.0, I got an error message like this :
<<
Error:
Microsoft SQL-DMO (ODBC SQLState: 42000) returned error: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near 'where'.
The replication upgrade task was not able to completely transfer your existing replication configuration settings to 7.0 server. Following the completion of upgrade, it is recommended that you use the Microsoft Management Console in Sphinx to re-establis>>
Has any one come across this ? The existing setup is using the transaction replication with 5 other servers. In 6.5, it is functioning well.
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.
The following version and editions have been verified.
1. .NET 2.0 installed
2. Windows XP SP2
3. MSDE 8.00.2039(SP4)
4. all MSDE databases are owned by sa
5. Instance and SQLAgent running under user that is member of Administrators
What are the possible reasons this error is occurring?
We have a server instance on SQL Server 2005 SP2 build 3042. We have a 32 bit x86 server. We attempted to upgrade to SP2 build 3054 KB934458. And we got the following error as stated in the Summary.txt file.
Code Snippet ********************************************************************************** Product Installation Status Product : SQL Server Database Services 2005 (MSSQLSERVER) Product Version (Previous): 3042 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. 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. ----------------------------------------------------------------------------------
The client tools and workstation components were successfully installed. The server is still reporting build 3042.
Here is the portions of the HotFix.log file.
Code Snippet 05/12/2008 09:19:09.041 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log 05/12/2008 09:19:09.072 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller" 05/12/2008 09:19:09.103 Registry: Cannot read registry key value "Debug" 05/12/2008 09:21:29.382 MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. 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. 05/12/2008 09:22:33.678 MSP returned 1603: A fatal error occurred during installation. 05/12/2008 09:22:33.724 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
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.
I have a client whose DBA upgraded their SQL 2000 database to SQL 2005. They still have it running in 8.0 compatibility mode, for various reasons, and would like me to help them develop a migration strategy to get them to full 9.0 compatibility.
My question is: can I run the Upgrade Advisor on a SQL 2005 engine database running in 8.0 compatibility mode and get anything useful? I already know there will be some issues with existing DTS packages but it would be nice to catch any other issues in advance.
I know that the Upgrade Advisor was run before the upgrade took place but to my knowledge the report was not saved and none of the recommendations were followed.
SQL 2000 -> SQL 2005 upgrade on windows server 2003 ... We've done numerous side by side types of upgrades which have the advantages of being able to migrate things at a slower pace with limited downtime. I have a situation where it seems like it would be the least amount of work to do an in place upgrade involving 22 transactional in-house developed databases and associated in-house developed applications. There's no replication, no DTS packages, nothing I can think of that would complicate the upgrade. I was wondering if there's people out there that have done lots of these and haven't had any problems OR if there have been lots of problems. Anyway, any advice would be appreciated.
Hi, I plan to move my servers from Windows NT and SQL 7 to Win2K Advanced Server and SQL 2000. I am not going to upgrade the windows server, as I have been told this isn't a good thing. Therefore, I plan to detach my databases, install win2K, install SQL 2000, and then attach the databases. I've read that this works fine, but I am curious as to whether or not I can do this with master and msdb(as I want to keep all logins, jobs, etc). Is this possible? Also, is my plan decent? it seems to be the easiest way to me... Thanks!
I am upgrading sql 6.5 to 7.0. The 6.5 database has 3 data files. Do I need to create 3 datafiles in version 7.0 after the server has been upgraded? Before I do the upgrade on the production server, I want to do a test on another machine loaded with sql 6.5, Do I need create 3 data files on 6.5 to to load the database from the production server before I upgrade the test machine to sql 7.0?
Hi everybody, I am using SQL Server 7.0 with SP2 and I want to upgrade it to SP3. If anybody has done this please share your experiences on wha problems were faced while installing SP3 and wheather it is safe to upgrade or not.
I would like to upgrade database from SQL-Server 6.5 to SQL-Server 7.0. using upgrade wizard. but i am getting this error at the logon screen. My export server is 6.5 and import server 7.0. i am upgrading using two machines on same domain.
"Error occured on "ServerName" SQL-Server does not exist or access denied. ConnectionOpen(connect())"
Hey everyone, I need to upgrade production 6.5 databases to 7.0.. How can i do that? I read that the Upgrade wizard will stop the services in 6.5 and 7.0 while in progress.. As ours is production i dont know what to do? Any suggestions for me..
Hi , I would like to upgrade 6.5 to 7.0. But here in our server the sort order was not 52.so i need to upgrade as well as i have to change the sort order to 52. if i import data to 7.0 from 6.5 what happenes? what is the wrong with dts? Could any one pls explain me? I want to use dts because of Sort order. thanks
If you run the upgrade wizard shouldn't all your databases be upgraded from 6.5 to 7.0? The wizard created all of my databases and objects but the table doesn't have any data him them, If I switch back to 6.5 the data are in the table. Did I leave out a step?
I need to reformat SQL6.5 database tables to accept a different format for the date and currency fields. When SQL6.5 was installed the dates were set at mm/dd/yy and the currency in $ and would now like to change this to date dd/mm/yy and the currency to R (South African Rand). I was made to understand that it would be easier to reformat and convert this once we upgrade to SQL version 7(latest). Could anyone please assist as we do not have another server at hand to test with. The existing database (SQL 6.5) is not very large yet as we have only recently started using the new application but the database consists of approx. 250 tables and would be a huge job to export each table seperately into Access for conversion and back into SQL.
I just finished upgrading from SQL 6.5 to SQL 7.0 SP2. After following all the information I could find on the CDs and on Technet, I uninstalled SQL 6.5 the way the instructions said to, from within the SQL 7.0 menu.
After doing this a discovering that my SMS Database is now gone, I did some research and found a article on Technet about this. The article is: "Q236989 - BUG: Uninstalling SQL 6.5 after upgrade to 7.0 may remove 7.0 data files" This information would have been nice before I lost my data.
Any one experience this? How did you get around it?? Did you get your data back??
I am trying to upgrade a database called "FLD" running on 6.5 (version 6.5.201 which I believe is SP3) on server "SMITTY" to server "CONCEPCION" running 7.0 SP1. I get the following error when the export of data begins...
Export.exe on the remote machine was hung... Export Exit Code: 259 - export.exe -CodePage 1252 -DeviceType Pipe -AllTables yes -MasterPath C:MSSQLDATAMASTER.DAT -DatabaseName FLD -DevicePath .pipe~cnvpipe0 Import Exit Code: -1 - ~cnvpipe0 Msg 4854, Level 21, State 1, Server CONCEPCION, Procedure , Line 1 [Microsoft][ODBC SQL Server Driver][SQL Server]**** Time:12-09-1999 19:07:05.482 Error return from function CreateFile in file CnvPipe.cpp Line=140 rc=1326 Msg=Logon failure: unknown user name or bad password.
Both machines are running NT 4.0 (SP5), have the same administrator password and the same SQL SERVER 'sa' password. What would cause this? After trying to upgrade just the one database (FLD), I then tried to upgrade all databases and got the same error on a different database.
I'm not familiar with SQL at all. SQL 7 was installed during the installation of SMS 2.0 I'm not sure if the SQL db has OLAP Add-in kit and OLAP Services DTS task kit. How do I find out??? The readme.txt of upgrading SQL 7.0 sp2 said these kits must be updated if earlier verions exist. Also, can we go straight from SQL no service pack to SP2?
I have a problem about how can I upgrade from SQL Server 6.5 to SQL Server 7.0. I want to upgrade all of them that is in my database such as database objects, other database, transaction logs etc. But I don't know anything about this subject.
Please give me more detailed recommendations. Thanks a lot!! Yours sincerely
What are the main benefits of upgrading a database from 7.0 to 2000?
I have a number of databases that are SQL Server 7.0 with sp3 and they function wonderfully. I have been approached about moving them to 2K and what benefits there to do such.
I have a 24/7 SQL7 system that I must soon upgrade to SQL2000, does anyone have any advice on how I might approach this or things I need to look out for?
We have to upgrade our sql database servers from SP3 to SP4....will this upgrade wipe out all user databases information or it will just update system tables and all user databases and logins will be intact.
Hey guys - I need your help. We are using SQL Server 2000- do you think, we should upgrade to some later release of Microsoft SQL Server or Migrate to Oracle, IBM or Sybase. I am also wondering, what do you think of Open Source MySQL and PostgreSQL. Have anyone of you using these databases. Thanks guys for your help - Mark Smith
Move existing Meta Data Services packages to SQL Server storage (in the msdb database) or to structured storage files before you upgrade from SQL Server 2000 to SQL Server 2005.
