Upgrading SQL Server 7.0 to SQL Server 2000

Hello,
We want to upgrade Microsoft SQL Server 7.0 to SQL Server 2000 to implement Mobile scenario in CRM .If anyone has any utility implementation guide or good information regarding it ,kindly please forward it to my mail id [email protected]
Thanks and Regards,
Saumya Maheshwari

Hello Saumya,
I have sent you a Upgrade note. Hope that will be of help. However, I like to tell you that there is no migration procedure, per se. But you could follow the steps in the document and it should be a straight forward approach to 2000.
In case,the authentification of the SQL Server 7.0 is set to "Windows NT only";While upgrading, the user chooses "The SQL Server system administrator login information (SQL Server authentication)" in the "Connect to Server" step and enters the password for the system administrator (sa).
In the next step, the upgrade program checks if the user can log on to SQL Server. First, the Windows authentification of the logged on user is checked, which is successful. The 'sa' user and the relevant password are not verified. However, later in the upgrade process, the program tries to execute the scripts with the 'sa' user; this fails due to the "Windows NT only" authentification for SQL Server. The error ("Error running script: upgrade.sql(1)") message is written to the log file (upgrade.out) of the script (upgrade.sql):
Login failed for user 'sa'. Reason: Not associated with a trusted SQL
Solution - The upgrade program of SQL Server 2000 saves the settings of the upgrade in the registry. You can change the authentification mode there. Start the registry editor and go to the following entry in the left panel:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup\Resume\
Locate the "DO-NT" value in the right panel. Change this value from "0" (SQL Server authentification) to "1" (NT authentification). You can then restart the upgrade; the program now logs on to SQL Server via the Windows authenification and also executes the scripts under this authentification.
Please award points in case you find the solution of help to you.
Thanks
Sumit

Similar Messages

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Upgrade from sql Server 9.0 to sql Server 12.0

I am currently running SQLEXPRESS (SQL Server 9.0) It appears that there is a limit to the size of the database which I have exceeded. I want to restore a backup of my customers DB and am not allowed to do so. Appears to be a size issue,
the customer DB is over 5 GB.
Will I eliminate this size restriction using sql Server 12.0?
I don't see any references to upgrading sql Server 9.0 to sql Server 12.0, only references to a new installation. Can it be upgraded and how do I do that?

Hello,
Please read the following article.
http://www.mssqltips.com/sqlservertip/2941/upgrading-to-sql-server-2012-express
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

MOSS 2007 SP1 & SQL Server 2008 upgrade plan into MOSS 2010 and SQL Server 2008 R2 ?

Hi All,
I've got the following setup in one single server:
Windows Server 2008 Standard
SQL Server 2008 Standard
SharePoint Server 2007 Enterprise SP1
that I'd like to upgrade into the following:
Windows Server 2008 R2 Standard
SQL Server 2008 R2 SP1 ?
SharePoint Server 2010 Enterprise
can i just perform CA farm level backup then import it on the new SharePoint server ? is there any caveat that i should pay attention to ? (eg. non working site list or web parts ? )
thanks.
/* Infrastructure Support Engineer */

Backup/import will not work for upgrade. As mentioned on the other thread, you need to perform a database attach upgrade to move to a separate 2010 from from a 2007 farm. For information about upgrading to SharePoint Server 2010, see the upgrade guide:
http://technet.microsoft.com/en-us/library/cc303420.aspx

Install SQL Server 2008 R2 in Windows Server 2012 using SQL4SAP Script

Hi guys,
Since we are performing a SAP System Migration from older releases of Windows/SQL Server, as detailed on SAP Note
1780433 - System copy of SAP systems on Windows 2012 : SQL Server
We need to install SQL Server 2008 R2 before upgrading the system
When running SQL4SAP Script it states the following
17/03/2014 08:13:44 p.m.
Message Box "Windows version error"
OS Family "WindowsNT6.3" is not supported by this script.
Result: vbOK
On Windows 2012 should i run the SETUP instead the script?
Thanks!

Hi Sunny
Im following SAP Note 1780433 - System copy of SAP systems on Windows 2012 : SQL Server
in order to migrate a SAP 640 system from Windows 2003/SQL Server 2005 to Windows 2012/ SQL Server 2012
Reason and Prerequisites
This note describes how to migrate the mentioned SAP products to Windows 2012/SQL Server 2008 R2,
in order to prepare an upgrade to SAP releases based on NW 7.0 and higher.
Note, that only SAP upgrade paths are supported, that are supported by the SUM tool. For more
information about the upgrade paths supported by SUM, read the Central SUM Note referred to at
http://www.service.sap.com/SLToolset.
Immediately after the SAP upgrade, your database has to be upgraded to SQL Server 2012. SAP does in general not support SQL Server releases prior to SQL Server 2012 on Windows 2012.
I understand this is not supported from Productive system, we are performing this on a Development system for test purposes.
Nevertheless on the note says Install First SQL Server 2008 R2 and after SAP upgrade, perform upgrade of SQL Server Upgrade, so there is misleasing information.
Im not sure if a 640 System would be able to copied and upgraded in Windows 2012/SQL Server 2012
It doesnt mention that 640_EX2 Kernel Support SQL Server 2012 to install the system.
How would yo recommend a system copy restoring database on these conditions?
640 System (SQL Server 2005,Win 2003) --> 640 System (SQL Server 2012, Win 2012)
(and then Upgrading to 740)
Thanks

Migrating from SQL Server Express 2012 to SQL Server 2012

Hello,
I am running SQL Server Express 2012 on a Virtual Machine for my learning box.
My work load has brought me to the place where I need to be using the full blown SQL.
I have backed up my databases (in the Express instance) and am looking for an 'upgrade' path.
Can I install another instance of (full deal of SQL) on the same machine?
Andy

Hello,
Yes, you can perform a side-by-side upgrade by installing another instance of SQL Server (a full licensed/paid edition)
and them move the databases to the newly installed instance by using backup/restore or detach/attach.
https://msdn.microsoft.com/en-us/library/ms189625.aspx
Make sure the new instance has applied the same updates/service packs of the Express instance.
You can have up to 50 instances/installations of SQL Server (standalone) on the same computer.
Alternatively you can perform an edition upgrade from Express to any licensed/paid edition.
https://msdn.microsoft.com/en-us/library/cc707783(v=sql.110).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrate SQL 2005 from windows 2005 server to Windows 2008 R2 server

Hi all,
I need to move our SQL 2005 on a windows 2003 server to a new server with Windows 2008 R2 installed. Could someone show me what are the necessary steps I need to do?
Thank you.

Hey TR,
As per Microsoft recommendation, Before Installing new server try to run Upgrade Advisor and follow these steps
1. Take Full backups of all System and Application databases on your 2005 machine.
2. Script all logins --
3. Script all jobs
4. List out all Maintenance plans and their schedules -- You cant migrate so you have to create them manually
5. List out all Linked server(s) currently being used.
6. Check the service pack
7. Check the Edition
8. document the existing server settings so that it should match the same (collation,version,...)
Migration process
1. Migrate logins
2. Restore all App databases
3. Fix the orphan users
4. create the jobs
5. create maintenance plans
6. create Linked Servers
7. perform checkdb on all databases
8. rebuild indexes
9. update the statistics
10.move all the DTS / SSIS packages
11. Point the application to new server
12. Testing .... Change all the application connection string to new server and then start the testing then finally if everything looks good then you can down the sql 2000 server and start using new server.
LIKE THIS POST, PLEASE VOTE & MARK AS A ANSWER TO HELP OTHERS
DBA

Migrate SQL 2005 to 2008r2 to diferent server running 2008r2

I need to migrate sql server 2005 to a diferent server running windows server 2008r2 and install SQL 2008r2 can some one help with that step by step please
UPDATE:: i just realize its sql 2014 not 2008, does it make it easier or more difficult or same or there is any tool that make it easier?
thanks for all your response and help.

This is what I follow.
First Run upgrade advisor 2008 r2 against sql 2005 to confim there are no issues,.
Check depreceated features , discontinued functionality, breaking changes etc in sql 2008 r2.
http://msdn.microsoft.com/en-us/library/ms143729(v=sql.105).aspx
http://msdn.microsoft.com/en-us/library/ms144262(v=sql.105).aspx
http://msdn.microsoft.com/en-us/library/ms143179(v=sql.105).aspx
Once this is done, depending upon the criticality of databases I do a performance test on the new server. If doing performance tests then I do all these below steps before hand and do a database refresh during cutover.
So basically take backup of all databases and move it to the new server.
Now need to move the logins using this KB article - <cite class="_Rm">support.microsoft.com/kb/918992 </cite>
Move all jobs/linked servers etc
Setup all the configuration in sp_configure.
Update stats of all the databases + Reindexing of all indexes.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

MS14-044 for SQL Server 2008 Standard on Windows Server 2003?

MS14-044 was recently released and states that it applied to MS SQL Server 2008 SP3, yet the patches available for this security bulletin do not list Windows Server 2003 in the supported operating systems. Does MS14-044 not apply to SQL Server running
on Windows Server 2003? If it does apply, why isn't there an update available to run on Windows Server 2003?

Hi Chasg76,
According to your description, the patches available for MS14-044 do not list Windows Server 2003 in the supported operating systems and you want to know whether MS14-044 applies to SQL Server running on Windows Server
2003.
Based on my test, KB2977321 applies to SQL Server 2008 Service Pack 3 product and it does apply to SQL Server 2008 SP3 running on Windows Server 2003.
I installed SQL Server 2008 Service Pack 3 in Windows Server 2003 SP2 x86. After the service pack 3 installation completed, KB2977321 was offered in the Automatic Update.
Besides, you can manually install the update by downloading the update form the Download Center web site as well.
I also tried the manually installation and I downloaded the Security Update for SQL Server 2008 Service Pack 3 (KB2977321) from this web: Security Update for SQL Server 2008 Service Pack 3 (KB2977321) (https://technet.microsoft.com/library/security/MS14-044),
it was installed successfully.
After installed security upgrade, I checked the file attributes and compared to this article: MS14-044: Description of the security update for SQL Server 2008 SP3 (GDR): August 12, 2014(http://support.microsoft.com/kb/2977321/en-us).
The result is the same.
According to my test, MS14-044 applies to SQL Server running on Windows Server 2003 even though Windows Server 2003 is not listed in the supported operating systems.
Best regards,
Qiuyun Yu

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

Attempted to perform an unauthorized operation error while installing SQL Server 2008 R2 Enterprise edition on Windows Server 2012 R2 standard VM server

I've been trying fresh installation of SQL Server 2008 R2 enterprise on Windows Server 2012 R2 standard VM server several times for two weeks, but always get the error "Attempted to perform an unauthorized operation". At first, I attempted
to install all features, but failed several times. So I decided to try install just Database Engine service, and still fail at the SqlBrowserConfigAction_Install_ConfigNonRC_Cpu32, with the error "Attempted to perform an unauthorized operation".
I remote login to server with my admin domain account. This account is in server local Administrators group. I
1. Right-click on setup.exe file | properties | Compatibility tab | select compatibility to Windows 8.Then click OK.
2. Right-click on setup.exe file | Run as Administrator, to start the Installation Center.
I have the document of my installation steps and zip file of the installation logs, if you need to take a look.
Appreciate for any help!
ntth

Hi ntth,
"Attempted to perform an unauthorized operation"
The above error is always related to the Windows account SID mapping. I recommend you login into Windows using another Windows account which has administrative privileges and run SQL Server setup using that Windows account.
Besides, please note that we need to apply SQL Server 2008 R2 Service Pack 2 or a later update when installing SQL Server Windows Server 2012 R2. For more information, please review this
KB article.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

Hi all,
I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
System specification:
Windows server 2012 64 bit
SQL SERVER 2012 64 bit
REMOTE SERVER SQL 2000 32 bit
I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
Create a linked server with the query below in SQL 2012:
EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
GO
but when i browse the linked server i receved error 7303.

You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
SQLNCLI11 - does not support connections to SQL 2000.
SQLNCLI10 - failed with some obscure message that I don't recall.
SQLNCLI - Don't recall that the problem was here.
SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
I don't think I got through all version of the ODBC drivers, though.
Erland Sommarskog, SQL Server MVP, [email protected]

How to restore SQL Server 2008 database to SQL Server Express 2012

How to restore SQL Server 2008 database to SQL Server Express 2012.
I BACKED UP a SQL Server 2008 database from work, which runs the enterprise version of 2008, and I tried to RESTORE it to my new 64-Bit home PC which is running the new SQL Server Express 2012 64-Bit (Advanced Edition).
But if fails. I get the following message text.
Can anyone help me please. I thought restoring a 2008 database to the later version 2012 would be possible.
Here is the error message. Thanks.
TITLE: Microsoft SQL Server Management Studio
Restore of database failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the backup, or use a
backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)

ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the
backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
Are you sure your database is SQL server 2008 from error message it seems your SQL server version is 2000.I guess you have multiple versions of SQL server.
AFAIK you cannot restore backup of SQL server 2000 to 2012 directly .Restore it first to SQL 2008/2008R2 or 2005 then take backup again of new database created and then you would be able to restore it on 2012.Its kind of intermediate way
Also make sure your DB size is less than 10 G as max DB size supported by Express edition is 10 G and if your DB size is more than 10 G restore will fail.
You are also trying to restore enterprise DB backup on express edition so you will loose enterprise features on express edition
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

How to change backend databases sql server 2008 R2 to Sql server 2012 datacenter

Hi
i have current sharepoint 2010 form has backend database is sql server 2008 R2 on windows server 2008 R2 Enterprise
and this form has
1 application server
1 Search server (index server)
1 wfe server ( all web applications are running)
1 databse server
here how i change this form back end to new windows server 2012 and sql server 2012 datacenter
adil

Information on SQL Aliases (using cliconfg.exe):
http://sqlandme.com/2011/05/05/create-sql-server-alias-cliconfg-exe/
You need to migrate content back into the database prior to migration:
http://technet.microsoft.com/en-us/library/ff628255(v=office.14).aspx
http://technet.microsoft.com/en-us/library/ff628257(v=office.14).aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Upgrading SQL Server 7.0 to SQL Server 2000

Similar Messages

Maybe you are looking for