SQL2005 collation error

Hi gurus
i am running sapinst installing sap 47 on sql 2005 server and iam getting this error :
Wrong server collation :J2ee installatin requires SQL_LATIN_GENERAL_CP850_BIN collation.
I have checkek there is a note but it seems its applying to SQL2000 not 2005 unless it will work for both.
any ideas welcome

Hello,
you installed the SQL Server with the wrong collation. When you instal lthe SQL Server manually you have to choose the collation:
Binary Order based on code point comparison, for use with 850 (Multilingual)
This is the BIN2 collation.
If you are using the SQL4SAP.vbs script on the SQL Server DVD the SQL Server will be installed correctly.
Regards
Clas

Similar Messages

Collation error when data mining

I'm trying to process a data mining model but keep getting this error: "Errors in the OLAP storage
engine: The sort order specified for distinct count records is incorrect. Errors in the OLAP storage engine: An error occurred while processing the..."
I changed my sql server collation to to Latin1_General_CS_AI with a compatibility level of 100, and in SSAS, I set it to Latin1_General_100 and "Case Sensitive" checked...but I still get the same error...am I not setting the collation correctly?

I changed my sql server collation to to Latin1_General_CS_AI ...
The SQL Server setting is just a default value for new databases, when you don't explicit define the collation in the CREATE DATABASE command; same for the database setting, also just a default value. The effective collation is defined on column level.
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL2005 cluster error MDB-05053 Errors when executing sql command: p nr="

Hi all,
We are migrating from 32 bit to x64 bit machines. SQL 2005 database on windows 2003.
I am trying to install E 4.7-200 SR1 on the clustered nodes. The installation manuals for 4.7 are very old and there is nothing for SQL2005 installation.
Now that some how we were able to have SQL up and running in clustered environment (It only took 10 days), After installing CI, I am not able to deploy the database and database creation phase is failing with the following error:
MDB-05053 Errors when executing sql command: <p nr="0"/>.
I am heavily relying on our server managment team on clustering and hoping they have done a good job, However I need some guidelines which can help me in verifying what they have done is correct and meets SAP and SQL requirments and issues we are facing is actually install problems not cluster.
SAP install manuals are not detailed in this regards. Also manuals are out dataed and they only show the sql 2000 clustering pre-requisit for 4.7 installls.
Can any one with clustering experience please help.
Calling out NPC, As his sql installation and upgrade manual has helped me with stand alone installs, Hoping he has some thing for clustering as well.
Regards,
KG

Hi,
What installation CD/DVD are you using?
Try look at SAP note [924288|https://service.sap.com/sap/support/notes/924288],
and note [969699|https://service.sap.com/sap/support/notes/969699],
and note [967124|https://service.sap.com/sap/support/notes/967124],
and note [106275|https://service.sap.com/sap/support/notes/106275].
In special the last note say at the end:
"3. You must use the 51031444 CD to install Enterprise 4.7 on an x64 platform with SQL Server 2005. This CD installs the central instances and database instances. To convert the A and B nodes in MSCS, use the SAP NetWeaver 04 SR1 installation master CD or DVD."
Hope this helps
Regards
Rolf

COLLATE Error on Table Comparison

Hi,
We have just upgraded to from version 11.7.3 to version 12.2.2 and we are getting this error when running the table comparison transform with sorted input:
"Expression type int is invalid for COLLATE clause. "
I asked our DBA to see what BODS was passing through at it is sending this:
WHERE ( "TCRdr_1"."VEHICLE_ID_NK" >= @P1 COLLATE Latin1_General_BIN)
Why is it using COLLATE, and more importantly is there anyway to control this?
The database is SQL Server 2005.
Thanks

this issue is fixed in 12.2.3, there were some issues prior to 12.2.3 related to Access Violation in case of SQL Server 2008 as target table, for DATETIME and DATETIME2 datatypes in target table
as you mentioned you are using SQL Server 2005, do you get the Access Violation in a particular case, is the issue consistently reproducible ? please file a support case for the Access Violation issue or give me a reproducible scenario so that I can file a bug for that
if you don't want to apply the 12.2.3 then you will see this issue for all table compare with sorted input and key columns with datatype other than CHAR, VARCHAR or NCHAR or NVARCHAR

SQL2005 collation setting

Hi,
I reinstall SQL 2005 and restore company database. I login SAP B1 and do drag and relate, hit error message: No matching records found (ODBC -2028) [Message 131-183]
I browse thru the forum and get know this might due to SQL collation setting issue. The correct collation is Latin1_General_CI_AS. I checked my collation in SQL server by master and company databases, the result is Latin1_General_BIN.
How to change the collation from Latin1_General_BIN to Latin1_General_CI_AS? Thanks.
Regards
Cheh Lu

Hi Cheh,
I suggest to do these following steps:
1. Open server properties in the SQL server and check the collation setting. Right Click in server...(9.00.1399-...)\Administrator
--> server collation. make sure the collation is Latin1_General_CI_AS. If yes, it will be as same as master db
2. Open database properties and check the collation settings. Is it SQL_Latin1_General_CP850_CI_AS or Latin1_General_CI_AS ?
3. Make sure the database collation and the server collation are match one another i.e. Latin1_General_CI_AS.
if the server collation is not Latin1_General_CI_AS, you may change it by reinstalling SQL server and choose that collation.
For the db, you can alter the collation using this simple query:
alter database [database name] collate SQL_Latin1_General_CI_AS
In the thread provided by Gordon, the collation is SQL_Latin1_General_CP1_CI_AS. It is correct but I see it in the SQL 2008 but not in SQL 2005.
JimM

Collation Error during SAP ABAP Engine Unicode Central Instance

I am trying to follow instructions on installing XI Prerequisite components.
I am getting conflicts on collations. My back-end database is SQL Server 2000 (SP3,hot-fix and unicodecp850bin2 fix). SAP expecting SQL_Latin1_General_CP850_BIN2 collation and SQLServer showing only SQL_Latin1_General_CP850_BIN. My OS is
Windows 2003 (SP1) Server.
Immediate response is greatly expected

hello Naresh,
Please try to run the script SQL4SAP.VBS which might be present in the MS SQL server CD.
Rgdz
Yogi

Procedure performing a "Retry Secondary Site" Operation in SCCM 2012 R2 Secondary Server

Dear Brother,
My SCCM 2012 R2 Secondary Site Server, unfortunately crashed and required to be restored, doing this I end up performing a "Retry Secondary Site Operation.
One by one I am clearing out the errors but there are few remaining errors on the prerequisite checks:
1.[Failed]:The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
Actions Done: SQL Related Services use Logon As Domain Account "Microsoft-Domain\BillAdmin" , but still the above message still appears in the logs.
Actions Done: None
2.[Failed]:The collation of the site database does not match the collation of the parent site's database. All sites in a hierarchy must use the same database collation.
3.[Failed]:The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have
manually verified these permissions. For more information about your options to configure required permissions, see
http://go.microsoft.com/fwlink/p/?LinkId=233190.
Actions Done: None, as this machine is previously a working Secondary site for 1 Year already. So I do not suspect anything from the current related configuration.
4.[Failed]: Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions.
Setup cannot continue.
Action Taken: Domain Account "Microsoft-Domain\BillAdmin" has a
Sysadmin roles and actually all the check boxes are chosen to acquire all SQL account roles"
5. [Failed]:Prerequisite checks complete with failure - check ConfigMgrPrereq.log
in the root of the primary site server system drive.
6[Failed]:Unable to complete secondary site server installation - check ConfigMgrSetup.log in the root of the secondary site server system drive.
ConfigMgrPrereq.log-Start
?<12-27-2014 23:39:35> ********************************************
?<12-27-2014 23:39:35> ******* Start Prerequisite checking. *******
?<12-27-2014 23:39:35> ********************************************
?<12-27-2014 23:39:35> Commandline :
"E:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe"
?<12-27-2014 23:39:35> Check Type: Secondary site
Site Server: SecondarySite2.microsoft.com,
SQL Server: SecondarySite2.microsoft.com,
SQL Named Instance: MSSQLSERVER,
Install Folder: E:\Program Files\Microsoft Configuration Manager\,
Setup Source Folder: E:\Source\SCCM2012-R2
?<12-27-2014 23:39:35> INFO: Executing prerequisite functions...
?<12-27-2014 23:39:35> ===== INFO: Prerequisite Type & Server: SITE_SEC:SecondarySite2.microsoft.com =====
?<12-27-2014 23:39:35> <<<RuleCategory: Access Permissions>>>
?<12-27-2014 23:39:35> <<<CategoryDesc: Checking access permissions...>>>
?<12-27-2014 23:39:35> INFO: CheckLocalSys is Admin of <SecondarySite2.microsoft.com>.
?<12-27-2014 23:39:43> SecondarySite2.microsoft.com;    Site server computer account administrative rights;    Passed
?<12-27-2014 23:39:43> <<<RuleCategory: System Requirements>>>
?<12-27-2014 23:39:43> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
?<12-27-2014 23:39:43> INFO: Check Lanman service: <SecondarySite2.microsoft.com>.
?<12-27-2014 23:39:44> SecondarySite2.microsoft.com;    Check Server Service is running;    Passed
?<12-27-2014 23:39:45> INFO: OS version:601, ServicePack:1.
?<12-27-2014 23:39:46> INFO: Target computer is a Windows server.
?<12-27-2014 23:39:46> SecondarySite2.microsoft.com;    Unsupported site server operating system version for Setup;    Passed
?<12-27-2014 23:39:46> SecondarySite2.microsoft.com;    Domain membership;    Passed
?<12-27-2014 23:39:47> INFO: Free disk space on target
\\SecondarySite2.microsoft.com\E$\. = 83157 MB
?<12-27-2014 23:39:47> SecondarySite2.microsoft.com;    Free disk space on site server;    Passed
?<12-27-2014 23:39:47> SecondarySite2.microsoft.com;    Pending system restart;    Passed
?<12-27-2014 23:39:48> INFO: The server SecondarySite2.microsoft.com is not read-only domain controller.
?<12-27-2014 23:39:48> SecondarySite2.microsoft.com;    Read-Only Domain Controller;    Passed
?<12-27-2014 23:39:48> INFO: Check FQDN Length for site server: <SecondarySite2.microsoft.com>.
?<12-27-2014 23:39:48> SecondarySite2.microsoft.com;    Site Server FQDN Length;    Passed
?<12-27-2014 23:39:48> <<<RuleCategory: Dependent Components>>>
?<12-27-2014 23:39:48> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
?<12-27-2014 23:39:48> SecondarySite2.microsoft.com;    Microsoft XML Core Services 6.0 (MSXML60);    Passed
?<12-27-2014 23:39:49> SecondarySite2.microsoft.com;    Microsoft Remote Differential Compression (RDC) library registered;    Passed
?<12-27-2014 23:39:49> INFO: Checking Windows Installer version on SecondarySite2.microsoft.com.
?<12-27-2014 23:39:50> INFO: Path of Windows Installer is <\\SecondarySite2.microsoft.com\C$\Windows\system32\msi.dll>.
?<12-27-2014 23:39:51> INFO: Msi.dll version is: <5.0.7601.17807> .
?<12-27-2014 23:39:51> SecondarySite2.microsoft.com;    Microsoft Windows Installer;    Passed
?<12-27-2014 23:39:51> INFO: Start Checking InstallSQLExpress on site server: SecondarySite2.microsoft.com, SQL Server instance MSSQLSERVER
?<12-27-2014 23:39:51> INFO: SQL Server Express installation was not selected.
?<12-27-2014 23:39:51> SecondarySite2.microsoft.com;    SQL Server Express on Secondary Site;    Passed
?<12-27-2014 23:39:52> SecondarySite2.microsoft.com;    Existing Configuration Manager server components on site server;    Passed
?<12-27-2014 23:39:52> SecondarySite2.microsoft.com;    Firewall exception for SQL Server (stand-alone primary site);    Passed
?<12-27-2014 23:39:52> INFO: SQL Server computer <SecondarySite2.microsoft.com>
?<12-27-2014 23:39:52> INFO: SQL Server named instance <MSSQLSERVER>
?<12-27-2014 23:39:53> SecondarySite2.microsoft.com;    SQL Server service running account;    Error;    The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service
name> or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
?<12-27-2014 23:39:53> INFO: SQL Server computer <SecondarySite2.microsoft.com>
?<12-27-2014 23:39:53> INFO: SQL Server named instance <MSSQLSERVER>
?<12-27-2014 23:39:53> INFO: Cannot connect to registry key.
?<12-27-2014 23:39:53> SecondarySite2.microsoft.com;    Dedicated SQL Server instance;    Passed
?<12-27-2014 23:39:53> INFO: CheckSQLCollationSecondary
?<12-27-2014 23:39:53> INFO: Collation on <PrimarySite2DB.microsoft.com> <SQL_Latin1_General_CP1_CI_AS>
?<12-27-2014 23:41:27> ERROR: failed to get collation from secondary site
?<12-27-2014 23:41:27> SecondarySite2.microsoft.com;    Parent/child database collation;    Error;    The collation of the site database does not match the collation of the parent site's database. All
sites in a hierarchy must use the same database collation.
?<12-27-2014 23:41:27> INFO: Checking .NET framework versions 3.5...
?<12-27-2014 23:41:28> INFO: .NET is installed
?<12-27-2014 23:41:28> SecondarySite2.microsoft.com;    Minimum .NET Framework version for Configuration Manager site server;    Passed
?<12-27-2014 23:41:28> INFO: Skipping check for .NET version, user did not select to install SQL Server Express for Secondary Site.
?<12-27-2014 23:41:28> SecondarySite2.microsoft.com;    Minimum .NET Framework version for SQL Server Express edition installation for Configuration Manager Secondary Site;    Passed
?<12-27-2014 23:41:28> INFO: CheckInstallSourceVersion <E:\Source\SCCM2012-R2>
?<12-27-2014 23:41:29> SecondarySite2.microsoft.com;    Setup Source Version;    Passed
?<12-27-2014 23:41:29> INFO:CheckInstallSourcePath <SecondarySite2.microsoft.com>
?<12-27-2014 23:42:14> SecondarySite2.microsoft.com;    Setup Source Folder;    Passed
?<12-27-2014 23:42:14> INFO: Enter CheckSecSiteSqlOnSameMachine.
?<12-27-2014 23:42:14> INFO: Target secondary site Machine <SecondarySite2.microsoft.com>
?<12-27-2014 23:42:14> INFO: SQL Server computer <SecondarySite2.microsoft.com>
?<12-27-2014 23:42:14> SecondarySite2.microsoft.com;    SQL Server on the Secondary Site Computer;    Passed
?<12-27-2014 23:42:14> INFO:CheckSupportedFQDNFormat <SecondarySite2.microsoft.com>
?<12-27-2014 23:42:15> INFO: NetBIOS <SECONDARYSITE2>
?<12-27-2014 23:42:15> SecondarySite2.microsoft.com;    Primary FQDN;    Passed
?<12-27-2014 23:42:15> INFO:CheckMachineAccountHasADAccess <SecondarySite2.microsoft.com>
?<12-27-2014 23:42:40> ERROR: Site server does not have create child permission on AD 'System Management'
?<12-27-2014 23:42:40> WARN: Site server does not have delete child permission on AD 'System Management'
?<12-27-2014 23:42:40> SecondarySite2.microsoft.com;    Verify site server permissions to publish to Active Directory.;    Warning;    The site server might be unable to publish to Active Directory. The computer
account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure
required permissions, see
http://go.microsoft.com/fwlink/p/?LinkId=233190.
?<12-27-2014 23:42:40> INFO:CheckRemoteWMIConnection <SecondarySite2.microsoft.com>
?<12-27-2014 23:42:48> SecondarySite2.microsoft.com;    Remote Connection to WMI on Secondary Site;    Passed
?<12-27-2014 23:42:48> INFO: Check required collation of Sql Server.
?<12-27-2014 23:42:48> INFO: LangID <409>
?<12-27-2014 23:42:48> INFO: NOT primary site or CAS install, skipping check for reqired collation of SQL Server.
?<12-27-2014 23:42:48> SecondarySite2.microsoft.com;    Required SQL Server Collation;    Passed
?<12-27-2014 23:42:48> ===== INFO: Prerequisite Type & Server: SQL:SecondarySite2.microsoft.com =====
?<12-27-2014 23:42:48> <<<RuleCategory: Access Permissions>>>
?<12-27-2014 23:42:48> <<<CategoryDesc: Checking access permissions...>>>
?<12-27-2014 23:42:48> INFO:RemoteCheckAdminOnSQL <SecondarySite2.microsoft.com>, SQL Server <SecondarySite2.microsoft.com>
?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;    SQL Server sysadmin rights;    Error;    Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions
on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.
?<12-27-2014 23:44:33> ===== INFO: Prerequisite Type & Server: MP:SecondarySite2.microsoft.com =====
?<12-27-2014 23:44:33> <<<RuleCategory: Access Permissions>>>
?<12-27-2014 23:44:33> <<<CategoryDesc: Checking access permissions...>>>
?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;    Administrative share (Site system);    Passed
?<12-27-2014 23:44:33> INFO:CheckSiteSystemtoSQLConnectivity <SecondarySite2.microsoft.com>
?<12-27-2014 23:44:33> INFO: Installing secondary site, skipping SQL Server connectivity check.
?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;    Site System to SQL Server Communication;    Passed
?<12-27-2014 23:44:33> <<<RuleCategory: System Requirements>>>
?<12-27-2014 23:44:33> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
?<12-27-2014 23:44:33> INFO: The rule 'Check Server Service is running' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:44:34> INFO: OS version:601, ServicePack:1.
?<12-27-2014 23:44:35> INFO: Target computer is a Windows server.
?<12-27-2014 23:44:35> SecondarySite2.microsoft.com;    Unsupported management point operating system version for Setup;    Passed
?<12-27-2014 23:44:35> INFO: The rule 'Domain membership' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:44:36> INFO: Windows Cluster not found on SecondarySite2.microsoft.com.
?<12-27-2014 23:44:36> SecondarySite2.microsoft.com;    Windows Failover Cluster;    Passed
?<12-27-2014 23:44:36> INFO: The rule 'Pending system restart' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:44:36> <<<RuleCategory: Dependent Components>>>
?<12-27-2014 23:44:36> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
?<12-27-2014 23:44:36> INFO: The rule 'Microsoft XML Core Services 6.0 (MSXML60)' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:44:36> SecondarySite2.microsoft.com;    IIS service running;    Passed
?<12-27-2014 23:45:35> INFO: CheckWebSvcExtnRemote, result:<7>.
?<12-27-2014 23:45:35> SecondarySite2.microsoft.com;    BITS installed;    Passed
?<12-27-2014 23:47:00> INFO: CheckWebSvcExtnRemote, result:<7>.
?<12-27-2014 23:47:01> WARN: BITS Service is not running on SecondarySite2.microsoft.com.
?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    BITS enabled;    Passed
?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    IIS HTTPS Configuration for management point;    Passed
?<12-27-2014 23:47:01> INFO: Stand-alone primary site or secondary site. Skip checking firewall settings for SQL Server
?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    Firewall exception for SQL Server for management point;    Passed
?<12-27-2014 23:47:01> SecondarySite2.microsoft.com;    Administrative rights on management point;    Passed
?<12-27-2014 23:47:01> INFO:CheckV4ClientNotInstalled <SecondarySite2.microsoft.com>
?<12-27-2014 23:47:45> SecondarySite2.microsoft.com;    Client Version on Management Point Computer;    Passed
?<12-27-2014 23:47:45> ===== INFO: Prerequisite Type & Server: DP:SecondarySite2.microsoft.com =====
?<12-27-2014 23:47:45> <<<RuleCategory: Access Permissions>>>
?<12-27-2014 23:47:45> <<<CategoryDesc: Checking access permissions...>>>
?<12-27-2014 23:47:45> <<<RuleCategory: System Requirements>>>
?<12-27-2014 23:47:45> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    Unsupported distribution point operating system version for Setup;    Passed
?<12-27-2014 23:47:47> INFO: The rule 'Domain membership' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:47:47> INFO: The rule 'Windows Failover Cluster' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:47:47> INFO: The rule 'Pending system restart' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:47:47> <<<RuleCategory: Dependent Components>>>
?<12-27-2014 23:47:47> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    Microsoft XML Core Services 6.0 (MSXML60) for distribution point;    Passed
?<12-27-2014 23:47:47> INFO: The rule 'IIS service running' has been run on server 'SecondarySite2.microsoft.com', skipped.
?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    IIS HTTPS Configuration for distribution point;    Passed
?<12-27-2014 23:47:47> SecondarySite2.microsoft.com;    Administrative rights on distribution point;    Passed
?<12-27-2014 23:47:48> ***************************************************
?<12-27-2014 23:47:48> ******* Prerequisite checking is completed. *******
?<12-27-2014 23:47:48> ***************************************************
?<12-27-2014 23:47:48> INFO: Updating Prerequisite checking result into the registry
?<12-27-2014 23:47:48> INFO: Connecting to SecondarySite2.microsoft.com registry
?<12-27-2014 23:47:50> INFO: Setting registry values
ConfigMgrPrereq.log-End
Well my question is what would be the best solutions as it bugs me for days now.
Regards,

Hello,
?<12-27-2014 23:44:33> SecondarySite2.microsoft.com;
SQL Server sysadmin rights;    Error;
Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions.
Setup cannot continue.
Did you install SQL server with a local account?
?<12-27-2014 23:41:27> SecondarySite2.microsoft.com;
Parent/child database collation;    Error;
The collation of the site database does not match the collation of the parent site's database.
All sites in a hierarchy must use the same database collation.
Try this blog:
http://jthys.wordpress.com/2012/04/02/sccm-2012-required-sql-server-collation/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

New SSRS 2012 Service Application Fails to Upgrade ReportServer Database

Hi -
I am in the middle of an SSRS upgrade from 2008R2 to 2012, SP 2010 integrated, without upgrading the database engine. This is on my DEV environment. I am running into problems when I add the new SQL Server Reporting Services Service Application through Central
Administration. I am keying in the previous db names, so they will be upgraded, "ReportServer". After clicking OK, a screen pops up notifying me that "ReportServer" and "ReportServerTempDB" will be upgraded. So far so good
right? Well as it is processing, it returns with the error found at the bottom:
The correlationID is nowhere to be found in the ULS Logs. I turned on Verbose logging and still no luck. I have restored the ReportServer database from a backup from 3 days ago and tried again. Same error, different correlation ID, not found
in ULS logs. NOTE: I first encountered a specific permissions error for the service account I was using. That was nice and descriptive :). Changed the permissions to db_owner and sys_admin (for overkill) and now this non-descriptive error appears. I
have a few questions:
1. I have gone through the same process of adding a new service application and let a new set of the 3 SSRS db's be created with a different name. But that means I lose all previous subscriptions, data source connections
to the rdls, etc. Is there a way to port/migrate over the previous ReportServer db contents to the newly created db's? I tried a simple SSIS transfer of each table, and as expected I immediately received FK contraint errors, ID Inserts and so forth.
2. Why wouldn't the correlation ID be showing up with verbose tracking?
3. Does anyone know common reasons why the previous RS databases would not be successfully upgraded???
Thank you for any and all help. I am in the position of being able to roll back to snapshots created Thursday morning of the entire SP farm, but we are now at the point of having consultant work being lost so I am really trying hard to get this upgrade to
be successful and done in our DEV environment.

I restored to a backup of the databases REportServer and ReportServerTempDB that I took last night before I tried to manually update them with writing out the SQL File via Powershell. I tried to have the Service Application upgrade the database
again, knowing it would fail, which it did, and am now reviewing the logs in the location you mentioned above. For the 2 minutes that the failure could have happened during, all I see is OWSTIMER.EXE (0x07CC) errors, which I'm fairly positive
are unrelated, mainly cause they keep occurring round the clock and a caching error? Again, I am trying to simply find out why the Service Application upgrade the db's and have reverted back to a previous state. I felt the collation errors i was troubleshooting
above were too far down the rabbit hole.
Batch Read on counter \servername\SharePoint Foundation\*\Process ID get 3 instances
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.91 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
84yj Medium
Performance Counter OS (pdh) call failed with error code PDH_CSTATUS_BAD_COUNTERNAME.
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.91 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
ff69 Medium
PDH failure on counter \servername\SharePoint Publishing Cache\\Publishing cache hit ratio with error Unknown error (0xc0000bc0)
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
563a Medium
Unable to create system performance counter servername\SharePoint Publishing Cache\Publishing cache hit ratio\. The following exception was thrown: System.ComponentModel.Win32Exception: Unknown error (0xc0000bc0) at Microsoft.SharePoint.Win32.SPPdh.CheckReturnValue(PDH_STATUS
status, Boolean throwOnError) at Microsoft.SharePoint.Utilities.SPPerformanceCounter.Initialize() at Microsoft.SharePoint.Utilities.SPPerformanceCounter.NextValue(Int32 retry, Int32 retryInterval) at Microsoft.SharePoint.Utilities.SPPerformanceCounterMonitorInternal.UpdateValue()
at Microsoft.SharePoint.Utilities.SPPerformanceCounterMonitorInternal.Create(String computer, String category, String counter, String instance)
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)
0x1204
SharePoint Foundation General
84yj Medium
Performance Counter OS (pdh) call failed with error code PDH_CSTATUS_BAD_COUNTERNAME.
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)

Installing CE with SQL Server

Hi,
I have SQL server Developer edition (version 8.00) , OS : Vista
I am trying to install CE and I am getting the follwoing error during the installation wizard
ERROR      2009-12-19 13:08:59.602 [sixxcstepexecute.cpp:984]
FCO-00011 The step dAskForConnection with step key |CE_DevSystem_App|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|3|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|NW_getDBInfo|ind|ind|ind|ind|3|0|NW_MSS_DBINFO|ind|ind|ind|ind|3|0|MssLoginInfo|ind|ind|ind|ind|0|0|dAskForConnection was executed with status ERROR .
WARNING    2009-12-19 13:08:59.649 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2009-12-19 13:08:59.649 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
ERROR      2009-12-19 13:08:59.587
           lib=iamodmssql module=CIaNtMssDmo
MDB-05053 Errors when executing sql command: [Microsoft][ODBC SQL Server Driver][SQL Server]Insert Error: Column name or number of supplied values does not match table definition.
[Microsoft][ODBC Driver Manager] Function sequence error
<p> SOLUTION: If this message is displayed as a warning, you can ignore it. If this is an error, contact SAP support.</p>
Regards, Anil

Hi
Have a look on this resolved thread. [HELP |SQL2005 Upgrade Error in Post-Processing - HELP PLEASE;
Best Regards
Satish Kumar

Error in creation of database (planning 9.3.1) base- SQL2005

This error appears when you create database (planning 9.3.1) base- SQL2005.
com.hyperion.planning.olap.EssbaseException (1019060)
I would be grateful, if you give me advices how to solve it.
Thank you

Another thread on this very topic => Re: com.hyperion.planning.olap.EssbaseException (1019060)
todd rebner
http://www.advancedepm.com/

Error collation conflict

I keep getting the following error with this statement
Msg 468, Level 16, State 9, Line 6
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
Statement :
SELECT Clients.biz_name,Clients.ID,Employers.Name,Employers.RefId
FROM ClientBook.dbo.Clients
JOIN za_FinCloud.dbo.Employers
ON Clients.biz_name=Employers.Name
How do I correct this ?

E.g.
SELECT Clients.biz_name ,
Clients.ID ,
Employers.Name ,
Employers.RefId
FROM ClientBook.dbo.Clients
JOIN za_FinCloud.dbo.Employers ON Clients.biz_name = Employers.Name COLLATE SQL_Latin1_General_CP1_CI_AS;
But the question is: Why do you use different collations?

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

Error when connection to SQL2005 from MX7

I am trying to connect to a Microsoft SQL2005 database from
cfadmin on MX7. Seems pretty straightforward as it looks set up
like the cf5. However, I keep getting the following error:
"Connection verification failed for data source: ProfDev
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver]Could not establish a connection using integrated security:
No LoginModules configured for JDBC_DRIVER_01
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver]Could not establish a connection
using integrated security: No LoginModules configured for
JDBC_DRIVER_01"
I have followed all thed directions from the documents
section- (
http://livedocs.macromedia.com/coldfusion/7/htmldocs/wwhelp/wwhimpl/common/html/wwhelp.htm ?context=ColdFusion_Documentation&file=part_adm.htm)
I have sql set to integrated,etc and still no luck. Any ideas? Any
help would be appreciated.
Thanks,J

Sabrina,
Its all dependent on the application and whether its 32-bit or 64-bit. For example, SSRS reporting services 2008 R2 is a 64-bit application, so load the 64-bit oracle client there for report execution. Report builder is a 32-bit client application,
assuming its running on a different machine, so load the 32-bit oracle client on any user computers using RB 3.0 and working with Oracle. If the computers are one in the same, then do as the post above says, load both...

Collation conflict error OVGT table

Hi Guys,
I get a collation conflict error as above. Server instance and company databases are now set to same collation "latin1_general_CP1_CI_AS" but still error appears.
Before that company database was on "CP850" setting.
Any ideas to resolve this?
Is there a query I can run to identify tables that have a different collation to database?
Regards

Use
select * from INFORMATION_SCHEMA.tables
select * from INFORMATION_SCHEMA.columns
Petr

Collating sequence error???

hi guys... i am trying to execute an SQL query on a database created from another system. I open a connection to the dsn of the database and use db tools execute query vi. i get the following error right after this vi.
Possible reason(s):
Exception occured in Microsoft OLE DB Provider for ODBC Drivers, [Microsoft][ODBC Microsoft Access Driver] Selected collating sequence not supported by the operating system.. in Conn Execute.vi->CM2 front panel.vi
help please =) thanks

Hi Scotty,
Please take a look at the responses posted to your question at the location below:
collating sequence error???
Sincerely,
Feroz

SQL2005 collation error

Similar Messages

Maybe you are looking for