Want to upgrade 2008 R2 to 2012. Upgrade advisor giving errors relating to Database Compatability Level and Server Collation

I want to upgrade a SQL Server from 2008 R2 to 2012. When I run upgrade advisor, I get the following error messages:
Rule "Valid Database compatibility level and successful connection" failed.
The report server database is not a supported compatibility level or a connection cannot be established. Use Reporting Services Configuration Manager to verify the report server configuration and SQL Server management tools to verify the compatibility
level.
Rule "Valid Database server collation and successful connection" failed.
The SQL Server Database Engine is not configured with a valid server collation and cannot be used as the Reporting Services SharePoint Shared Service catalog database.
The database called ReportServer has Collation = Latin1_General_Cl_AS_KS_WS and Compatibility level = 100

Hi Andrew,
Regarding to the first error message, please check the Reporting Service Configuration Manager, make sure that you connect to ReportServer database from the correct server
and use servername\instancename format connection string. For more details, please review this similar
thread.
Regarding to the second error, it is caused by that the current SQL Server Database Engine server is using an incompatible server collation.
SQL Server 2012 Reporting Services SharePoint mode utilizes the SharePoint shared services architecture. SharePoint does not support SQL Server Database Engine configured for case sensitive or server collations or binary server collations.
And since the SQL Server Database Engine server collation property cannot be changed, you will not be able to complete an upgrade of Reporting Services. You will need to migrate your Reporting Services installation to a new server which is using a compatible
server collation. For more details, please review the following article:
Incompatible Database Engine Server Collation:
https://msdn.microsoft.com/en-us/library/hh759335%28v=sql.110%29.aspx?f=255&MSPPError=-2147217396
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Similar Messages

SQL Server Upgrade Advisor 2014 - Database Compatibility Level checking

I have the following scenario... I have a database server running SQL Server 2008 R2 (10.50.4260). On that server I restored a database from SQL Server 2005. Looking at the compatibility level through the properties of the database (using SSMS) and
by querying against sys.databases, I can see the database has the compatibility level of 90, which is what I expected.
In looking to bring this database over to a SQL Server 2014 database server, I have run the SQL Server Upgrade Advisor 2014 tool as well as the SQL Server Upgrade Advisor 2012 tool. With the 2014 tool, my expectation would be that it would warn me
that the compatibility level will be upgraded to 10 (or something), however, I received no such warning. I ran the 2012 version of the tool as well, expecting that I might get a deprecation warning (or something), no such luck. I have run the 2014
tool from my computer and from another one, same results.
Does the upgrade advisor not check for the compatibility level? Or does my configuration maybe have something to do with it (having it on a 2008 R2 server)? From looking at screenshots of when other people have ran the tool, I was under the impression
it checked this. See the link below for an example...
http://blogs.msdn.com/b/mspfe/archive/2012/12/06/sql-server-upgrade-advisor-considerations-when-upgrading-from-sql-2000-to-sql-2012.aspx
Thoughts anyone?

Lydia,
I agree with regards to the 2012 version. However, in SQL Server 2014, upgrading a database with a compatibility level of 90 sets
the database to compatibility level 100. See link below...
https://technet.microsoft.com/en-us/library/bb510680.aspx
Shouldn't the 2014 version of the advisor tool issue the same warning seen in the screenshot of the msdn blog post we both mentioned? As in... "After upgrade, compatibility levels <list of levels>, will be set to 100".
Hi JJordheim,
According to my test, SQL Server 2014 Upgrade Advisor also only raise warning when database compatibility level is less than 90 in the “SQL Server Parameters” page.
From your description, when database compatibility level is set to 90, SQL Server 2014 Upgrade Advisor should also raise warning, right? If so , this is a design issue of SQL Server 2014 Upgrade Advisor, personally, I recommend you
submit a feedback to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback . Your feedback enables Microsoft to offer the best software and deliver superior services.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

HT201210 When I am trying to upgrade my iOS version I am getting an error message saying " the iPad software update server could not be contacted", I also get an error message prior to that which says the certification of the server is invalid

When I am trying to upgrade my iOS version I am getting an error message saying " the iPad software update server could not be contacted", I also get an error message prior to that which says the certification of the server is invalid?

Temporarily disable any security software on the computer and try again.

Pls have been having issues upgrading to the os 10.9. downloads encounter error when it gets to 955mb and starts over again-.suggestions pls?

pls have been having issues upgrading to the os 10.9. downloads encounter error when it gets to 955mb and starts over again….suggestions pls?

http://www.apple.com/support/mac/app-store/contact/

Inplace Upgrade - 2008 R2 to 2012 R2 (with DataProtection Manager installed)

Hello all,
I have a simple question.
I have a main file server, that is running on Server 2012 R2 operating system with Deduplication feature switched On, on the main share disk.
This file server is supposed to be backed up by Data Protection Manager we have up and running, but there is a problem described here:
https://social.technet.microsoft.com/Forums/en-US/2e50b0ef-fa1c-4654-9186-fef4b6b2d61d/dpm-2012-sp1-windows-server-2012-and-deduplication?forum=dpmfilebackup
My question is: Can I execute an in-place upgrade or do I have to reinstall the server?
The IT guys from LukOIL

Hi,
In-place upgrade of the operating system on a server running DPM isn’t supported. You could backup the DPM database, then perform the Windows 2012 R2 upgrade or new installation on the same machine. After that, restore the DPM database on the Windows 2012 R2.
For more detailed information, please refer to the links below:
Supported and unsupported scenarios in DPM
http://technet.microsoft.com/en-us/library/dn554221.aspx
In place upgrade of DPM 2012 SP1 server from Windows 2008 R2 to Windows 2012 R2?
https://social.technet.microsoft.com/Forums/en-US/8c42efc2-7f3e-45ba-8ecd-a3eedbffe2ad/in-place-upgrade-of-dpm-2012-sp1-server-from-windows-2008-r2-to-windows-2012-r2?forum=dpmsetup
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Thanks Mandy
The IT guys from LukOIL

Help to resolve error in sending database email from SQL Server 2012.

Please help to resolve error in sending email from SQL Server 2012.
SQL Instance Version:
Microsoft SQL Server 2012 (SP1) - 11.0.3449.0 (X64)
Jun 29 2014 23:15:18
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
Error Message: Error MeThe mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2015-01-15T19:48:25). Exception Message:
Cannot send mails to mail server. (The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Client was not authenticated).)

The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1
Client was not authenticated).
I think the error message is pretty clear, you have to setup authentication for the SMTP connection in Database Mail, see
Database Mail Configuration Objects
Olaf Helper
[ Blog] [ Xing] [ MVP]

Migrate Active Directory 2008 to 2012 but need to keep the same ip address and server name

Hi,
Current setup is 2 DCs in one site running 2008 R2 AD.
We are planning to migrate from 2008 R2 to 2012 R2 but need to keep the same ip address and server name. I have came up two plans to do this and hope someone can tell me which one would be the best approach. What is the pros
and cons in Plan A and B or may be plan C if there is a better one?
First, I was planning to do plan A but just had a second thought of Plan B. My concern in Plan A is about changing the server name when the new 2012 R2 already running as DC. Plan B would be changing all the old server
name and ip before they become member sever and DC.
Any information and suggestion would be very appreciated.
Plan A
Run adprep /forestprep on 2008 R2 DC
Build a new 2012 R2 server and promote it as 3rd DCs in current Domain
Transfer FSMO from 2008 R2 to 2012 R2
Run Repadmin /syncall to force replication
Rename the demoted 2008 R2 DC to something else
Change the demoted 2008 R2 ip address to something else
Restart the demoted 2008 R2 server to take effect
Now, run Netdom computername command to change the new 2012 R2 server name to the old 2008 R2 DC server name
Change the new 2012 R2 DC's ip to old 2008 R2 DC's ip
Run ipconfig /flushdns
Run ipconfig /registerdns
DCDIAG to see any error
Plan B
Build 2 new 2012 R2 standalone servers
In 2008 R2 ServerA transfer FSMO to 2008 R2 ServerB
Demote 2008 R2 ServerA to become member server
Rename 2008 R2 ServerA to something else and change the ip address to something else and shut it down
Now, rename one of the new 2012 R2 standalone server to the old demoted 2008 R2 ServerA name
Change the new 2012 R2 standalone server ip to the old demoted 2008 R2 ServerA's ip address
Add the new 2012 R2 standalone server (now with the old 2008 R2 ServerA name and ip) to become member server
Run adprep /forestprep on the 2008 R2 ServerB
Promote the new 2012 R2 (now with the old 2008 R2 ServerA name and ip) as DC
Transfer 2008 R2 ServerB FSMO to the new 2012 R2 DC (now with the old 2008 R2 ServerA name and ip)
Demote 2008 R2 ServerB as member server
Rename 2008 R2 ServerB to something else and change the ip address to something else and shut it down
Now, rename the 2nd new 2012 R2 standalone server to the old demoted 2008 R2 ServerB name
Change the new 2012 R2 standalone server ip to the old demoted 2008 R2 SeverB 's ip address
Add the 2nd new 2012 R2 standalone server to become member server
Promote it as DC
Run DCDIAG to check error
Thanks.

Hi,
Renaming a Domain Controller is a risky operation which may lead to issues, therefore, I would suggest you go with the Plan B, rename the server before it becomes DC.
Here is a blog below which could be helpful to you:
Remove an Old DC and Introduce a New DC with the Same Name and IP Address
http://blogs.msmvps.com/acefekay/2010/10/09/remove-an-old-dc-and-introduce-a-new-dc-with-the-same-name-and-ip-address/
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Upgrading hyper-v 2008 r2 to 2012?

is it possible/will it be possible to just upgrade hyper-v server from 2008 r2 to 2012 or will I have to reinstall the whole os and vms?

"Hyper-V Server (Server Core) cannot be upgraded to Hyper-V Server 2012. You can choose to install
a new copy of Hyper-V Server 2012 instead, but this is different from an upgrade, and does not keep your files, settings, and programs."
Any know how to work around this problem?
Yes - export your VM's and re-install your host OS! It really doesn't add that much time.
And here's a tip for quicker exports - if you have a VM that has several really large VHD's you can temporarily remove the VHD's from the guest VM config and then export. I had an SBS 2011 VM with the Guest OS, Exchange, Swap and User data all on separate
VHD's.
I shut down the VM normally and then detached the large user data VHD's. The export/import of the VM went much faster. Once the Host OS was re-installed and the VM was re-imported, I just re-attched the user data VHD's before restarting the VM
and the server in the VM was none the wiser. I went through the trouble of keeping the VHDs in same location in the virtual SCSI controller in the guest VM configuration settings, but I don't know if that's strictly required or not. It worked like
a champ and didn't add that much time to the overall process of rebuilding the HyperV host OS. If I ever get comfortable enough to switch to Server 2012 HyperV, I'll do the exact same process. For something as simple as a hypervisor OS install,
upgrading it doesn't make much sense to me! As others have pointed out you are MUCH better off doing a clean install. Especially if it won't upgrade it for you :o)

Using upgrade advisor on a database with compatibility level 80 on SQL Server 2008

Hi All,
My DB compatibility level is 80 which is on SqL server 2008, however I want to upgrade the database server to sql 2014.
Now in my case the upgrade advisor of SQL 2014 is not detecting the DB which is in 80 compatibility level and hence I cannot proceed with the upgrade (as I do not want to rollback).
So what exactly can I do in this situation? any help would be appreciated
aa

What Olaf said Or if possible change compatibility level of database to 100 and try. I guess since you want to upgrade there wont be any issue in changing. Well if anything happens you can safely change it back to 80
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

"Software Usage Metrics initialize failed" error when open Report Manager, after moving ReportServer from SSRS 2008 to SSRS 2012 (Native Mode)

I've asked this question in SQL Server Upgrade forume, I'm asking here as well:
Your help is highly appreciated!
After migrating ReportServer db from 2008 to 2012, when access Report Manager throughhttp://myserver:80/Reports, I got the error below:
ui!ReportManager_0-3!11d8!02/04/2013-15:19:12:: e ERROR: Software Usage Metrics initialize failed
The process is below:
•I successfully installed SQL Server 2012 (64-bit) Enterprise as a Native Mode on a server who runs Windows 7 Enterprise SP1 (64-bit).
•I restored "ReportServer2008To2012" and "ReportServer2008To2012TempDB" in SSRS 2012 from the db files backed up in SQL 2008. In SSRS 2008, I have SSRS Model, ad-hoc reports based on model, and I also have canned reports built through BIDS
report server project.
•I reconfigured both databases' Compatibility level to SQL Server 2012(110) from SQL Server 2008(100).
•I configured SSRS through Reporting Services Configuration Manager as below:
> I chosen "Use built-in account:" as Service Account
> In "Database" tab, I selected "Choose an existing report server database" and choose "ReportServer2008To2012" db, I used "Windows Authentication" (my login has the System Administrator priviledge). I got all 4 parts
success: Verifying database sku = Success; Generating rights scripts = Success; Applying connection rights = Success; Setting DSN = Success.
> I went to "Scale-out Deployment" to check if the initializing succeed, I found nothing there.
Here are what I did from different approaches:
A •I went to "Encryption Keys" and restored the key I backed up from SSRS 2008, after retoring, I got two initialized instances: One is on my current server (SSRS 2012), the other one is from the old server (SSRS 2008).
   I deleted the old one(SSRS 2008) through "Remove Server" action and kept the one on my current server(SSRS 2012).
   After I restart SSRS service, and tried to connect Report Manager, I got "An internal error occurred on the report server. See the error log for more details."
   I checked the log file, the error is actually "ERROR: Software Usage Metrics initialize failed"
B •I also tried to "Delete Encrypted Content" and did see the SSRS was initialized through checking it on "Scale-out Deployment", however when I tried to open Report Manager, I got the same error.
Anyone had the same issue? Any solution? Thanks in advance!

Your help is highly appreciated!
After migrating ReportServer db from 2008 to 2012, when access Report Manager through
http://myserver:80/Reports, I got the error below:
ui!ReportManager_0-3!11d8!02/04/2013-15:19:12:: e ERROR: Software Usage Metrics initialize failed
The process is below:
•I successfully installed SQL Server 2012 (64-bit) Enterprise as a Native Mode on a server who runs Windows 7 Enterprise SP1 (64-bit).
•I restored "ReportServer2008To2012" and "ReportServer2008To2012TempDB" in SSRS 2012 from the db files backed up in SQL 2008. In SSRS 2008, I have SSRS Model, ad-hoc reports based on model, and I also have canned reports built through BIDS
report server project.
•I reconfigured both databases' Compatibility level to SQL Server 2012(110) from SQL Server 2008(100).
•I configured SSRS through Reporting Services Configuration Manager as below:
> I chosen "Use built-in account:" as Service Account
> In "Database" tab, I selected "Choose an existing report server database" and choose "ReportServer2008To2012" db, I used "Windows Authentication" (my login has the System Administrator priviledge). I got all
4 parts success: Verifying database sku = Success; Generating rights scripts = Success; Applying connection rights = Success; Setting DSN = Success.
> I went to "Scale-out Deployment" to check if the initializing succeed, I found nothing there.
Here are what I did from different approaches:
A •I went to "Encryption Keys" and restored the key I backed up from SSRS 2008, after retoring, I got two initialized instances: One is on my current server (SSRS 2012), the other one is from the old server (SSRS 2008).
   I deleted the old one(SSRS 2008) through "Remove Server" action and kept the one on my current server(SSRS 2012).
   After I restart SSRS service, and tried to connect Report Manager, I got "An internal error occurred on the report server. See the error log for more details."
   I checked the log file, the error is actually "ERROR: Software Usage Metrics initialize failed"
B •I also tried to "Delete Encrypted Content" and did see the SSRS was initialized through checking it on "Scale-out Deployment", however when I tried to open Report Manager, I got the same error.
Anyone had the same issue? Any solution? Thanks in advance!

Upgrade SQL 2000 to SQL 2005 --- schema conversion error

Hi, I execute an upgrade from MSSQL 2000 to MSSQL 2005 and everything executed succesfully. Then i download the "SAP Tools for MSSQL Server"
to execute the schema conversion of the database. But i get an error when a step tries to create the stored procedures in the db. Specifically i get the error in the sap_blocked_procccess store procedure with the following error:
ERROR 2006-12-07 10:19:57
FCO-00011 The step ExeProcs with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
ERROR 2006-12-07 10:19:57
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
INFO 2006-12-07 10:30:00
An error occured and the user decided to retry the current step: "|SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs".
ERROR 2006-12-07 10:30:29
FCO-00011 The step ExeProcs with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
I didn't find any note or something else.
Do you have any idea about this problem?
Best Regards,
Thanasis

Hello,
please ensure that the Database compatibility level for all databases is 90 by
running
exec sp_dbcmptlevel 'master',90
exec sp_dbcmptlevel 'model',90
exec sp_dbcmptlevel 'msdb',90
exec sp_dbcmptlevel 'tempdb',90
exec sp_dbcmptlevel 'EA5',90
Then rerun the STM tools.
Regards
Clas

Windows 2012 root certification authority in a 2003 Domain/ Forest level

Hello,
We are currently on Windows 2003 Domain & Forest Functional Level. Our Root CA is also currently on Windows 2003 DC.
If we have to setup a new Root/Issuing CA ( not exporting the current 2003 CA cert) on Windows 2012 R2 servers, is it then mandatory to first upgrade Domain & Forest levels to 2012 R2 ? Can we have a PKI infrastructure with
Enterprise CA's on a Windows 2012 Platform but the Domain/Forest levels still on 2003 level ? i understand it will be good to have everything on 2012 R2 , but can a mix of 2003 domain level and 2012 CA work ?

Hi,
Look at below tread it might help:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/fa8cac92-0f71-426c-ac95-e89e90e1c8d1/certificate-authority-and-forestdomain-functional-level?forum=winserversecurity
Basically the answer is yes you can have CA on 2012 R2 and DFL/FFL still on 2003.
Regards,
Calin

¿Is it possible to upgrade from SCCM 2012 a domain controller in Windows Server 2008 R2 TO 2012 R2?

Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.

Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.
Anything is possible if you can script it. You could create a task sequence to do the following (with scripts):
1. Demote 2008R2 DC to member server
2. Remove 2008R2 member server from domain
3. Build new 2012R2 member server and join to domain
4. Promote 2012R2 member server to DC
You can do this. However, why would you? Just because you can doesn't mean you should. In my opinion it's more trouble and testing than it's worth. How many times would you need to do this?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

I want to reinstall OS on my 2012 MacBook Pro. It shipped iwth 10.8, but now runs 10.9. Can I reinstall to 10.9, I do I have to reinstall 10.8 and upgrade again to 10.9?

I want to reinstall OS on my 2012 MacBook Pro. It shipped with 10.8, but now runs 10.9. Can I reinstall straight to 10.9, or do I have to reinstall 10.8 and upgrade again to 10.9?

Best to install 10.9 straight up. If you still have your OS 10.9 downloaded file you can use that, or you can go to the app store and download it again. It will be in your previous purchase history. Or you could even upgrade to 10.10. If you want to start from scratch you will need to boot from USB or DVD and initialise (erase) your internal HD. To do create a bootable USB thumb drive with OS 10.9 or 10.10 follow this guide
Create a bootable installer for OS X Mavericks or Yosemite - Apple Support
And heres a how to on installing a fresh copy of Yosemite (OS X 10.10)
http://osxdaily.com/2014/10/18/clean-install-os-x-yosemite/

Error upgrading Hyper-V Server 2008 R2 to 2012: 0x80070490

Hi everyone!
As it is release day for Hyper-V Server 2012, I decided to go ahead and upgrade from Hyper-V Server 2008 R2. However, I keep getting this error:
"Windows Setup cannot find a location to store temporary installation files. To install Windows, make sure that a partition on your boot disk has at least 1198 megabytes (MB) of free space.
Error code 0x80070490"
I have over 20 gigs free on the boot volume, and tons more on my VHD volume, so I don't know why it's doing this. I have shut down all VMs, there are no snapshots, nothing cluttering up my C: drive, and yes I've rebooted it several times. I have
also tried copying the installation DVD to a local volume and installing that way, but I keep getting the same error. I know the quick solution would be to just format, reinstall clean, and pray that my VMs import into 2012 (which are already safely
on another volume), but there has to be a reason this is happening.
Any ideas? :) Thanks!

Hello Vincent,
I get the same error trying to upgrade my 2008R2 server to 2012. Here's my diskpart output for the partition (it's a mirrored partition):
DISKPART> detail volume
Disk ### Status Size Free Dyn Gpt
Disk 2 Online 298 GB 1024 KB *
Disk 1 Online 298 GB 1024 KB *
Read-only : No
Hidden : No
No Default Drive Letter: No
Shadow Copy : No
Offline : No
BitLocker Encrypted : No
Installable : Yes
Volume Capacity : 297 GB
Volume Free Space : 268 GB
Any suggestions?

Want to upgrade 2008 R2 to 2012. Upgrade advisor giving errors relating to Database Compatability Level and Server Collation

Similar Messages

Maybe you are looking for