Installation failed - SQL Server Collation

2008년 5월 3일 토요일 오전 8:28Lasse Hansen

0
로그인하여 투표
I´v set up a lab running on WinSrv 2008 X64 with 4 VM on Hyper-V (all WinSrv2008 X64 Ent ED).
FCS is not yet supported on Win2008, but still I tried for a couple of days before I gave up.
Now I´m trying to get Stirling working on mye lab...

Installation ends with the error: Failed to execute the SQL string, error detail: Unable to resolve collation conflict between SQL_Latin1_general and Danish_Norwegian etc etc etc...

Is there any way to make this work without changing collaton?

I´m starting to hate beta products and unsupported applications from MS now ;-(
And I´m so frustrated now that I just must say I loath all the pre-requisites needed to install FCS...
If FCS needs SQL 2005 SP1, SCOM, Visual C+, .NET framwork, Powershel etc, then make the wizard install everything on the fly!
It takes forever to install antivirus on MS Platform - Symantec Endpoint Protection runs on its own, and is installed and configured in less than an hour...

Wintel
- 응답
- 인용

모든 응답

2008년 5월 6일 화요일 오후 2:22Kass

0
로그인하여 투표
Hi,

i am getting a similar type of error.

mine says:

ExecuteSqlStrings: Error 0x80040e14: failed to execute SQL string, error: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation., SQL key: InstallDACDB SQL string: CREATE VIEW dbo.vwES_UMM_CompromisedMachines

i found that the OPS manager db install with the SQL_Latin1_General_CP1_CI_AS collation & the server uses Latin1_General_CI_AS.

i am trying to install on a W2K3 box.

i followed the install instructions off the technet site. it does not mention anything about specifying collations.

any ideas before i rebuild.

Thanks

Kass
- 응답
- 인용
2008년 5월 7일 수요일 오전 2:08Chris Sfanos - MSFTMSFT

0
로그인하여 투표
Hi folks
I can't say if we've done any testing with various collation settings, especially for non-English installs. At this time, for Beta 1, we only support English language installs

From the Deployment Guide (http://technet.microsoft.com/en-us/library/cc441281.aspx)

"For this beta release, the operating system, the software prerequisites (including SQL Server), and the installation of Stirling on the servers must all be in English. In addition, you must install into an English-only locale."
Chris Sfanos / Forefront PM
- 응답
- 인용
2008년 5월 7일 수요일 오전 8:36Kass

0
로그인하여 투표
Hi Chris,

i am using English locale settings & still get the error.

Kass
- 응답
- 인용
2008년 5월 9일 금요일 오후 10:11Chris Sfanos - MSFTMSFT

0
로그인하여 투표
Hi Kass
I'm worried that this is a SQL collation issue in general - when you installed SQL, which collation did you select?

Thanks
Chris
Stirling PM
Chris Sfanos / Forefront PM
- 응답
- 인용
2008년 5월 13일 화요일 오전 4:33Lasse Hansen

0
로그인하여 투표
The installation defaulted to Danish/Norwegian (since my regional settings was Norwegian)...

Wintel
- 편집됨Lasse Hansen 2008년 5월 13일 화요일 오전 4:41More precise comment
- 응답
- 인용
2008년 5월 20일 화요일 오후 7:00Kass

0
로그인하여 투표
Hi Chris,

apologies for delay in replying. i used the default collation settings(latin i think) when installing sql. there is no mention in the documention to change it.

Kass
- 응답
- 인용
2008년 6월 11일 수요일 오전 11:19Heiti2

0
로그인하여 투표
Hi,
are there any updates regarding this problem?

Denis
- 응답
- 인용
2008년 6월 17일 화요일 오후 11:15Senthil Murugesan

0
로그인하여 투표
Yes it is the collation settings
I have replied in another thread, at this point we donot know how to change collation settings for sql at run time so i proposed reinstall with en-us as a work around

Senthil Murugesan
PM, Forefront "Stirling"
- 응답
- 인용
2009년 5월 26일 화요일 오후 7:15Susana Guedes.

0
로그인하여 투표
For Stirling FCS v2 Beta 2 you must use SQL_Latin1_General_CP1_CI_AS collation for all Stirling databases, regardless of the default collation. Do not use binary collation. http://technet.microsoft.com/en-us/library/cc441285.aspx

In detail I resumed the following:

For the Beta 2 version of Stirling the SQL 2005 Std with SP3:
- - SQL Cluster not supported.
  - Database Services + Analysis Services + SQL Server agent + SQL Server engine + Integration Services + Reporting Services + and Workstation components.
  - SQL Server Action Account = Local System (mandatory!)
  - Reporting Services User = Stirling Admin (mandatory! Must choose the account created to be the Stirling admin)
  - Must Enable SQL Server Replication
  - Must use SQL_Latin1_General_CP1_CI_AS collation for all Stirling databases (regardless of the default collation! Don’t use binary) http://technet.microsoft.com/en-us/library/cc441285.aspx
  - Start all services automatically
- Enable file handler mapping reports
  1. IIS \ Connections \ Sites \ Default Web Site \ Reports-> Handler Mapping -> Open Feature
  2. StaticFile -> Edit Feature Permissions = Read, Script and Execute
- Set the managed pipeline mode for reporting server and report manager
  1. IIS \ Connections \ Application Pools \ Reporting Server Pool -> Basic Settings
  2. Managed Pipeline Mode = Classic
- Configure Reporting Database for Remote Connectivity
  1. Surface Area Configuration for Services And Connections \ Remote Connections -> Using both TCP/IP and named pipes
  2. Start all services automatically
- Ensure you can access both reporting server and report manager sites and add them to the local intranet.
- In order to avoid a situation where the SQL Server uses up all available memory on the computer, under heavy loads, you should allocate a specific amount of memory to the server that is less than the maximum memory installed on the computer.
Was this Helpful?
by Susana Guedes
- 답변으로 제안됨Susana Guedes. 2009년 5월 26일 화요일 오후 7:15
- 응답
- 인용