Excuse us for the belated response here, but we've already answered your support ticket a couple of days ago. So for the sake of the forum readers, here's the relevant part of our answer to your ticket:
We've dealt with a number of OpenAccess globalization issues caused by Turkish being the culture of the current thread, some of which where addressed by hotfixes, but never investigated the scenario of having Turkish as server collation.
We've installed an SQL Server instance with Turkish_CI_AS server collation and we've successfully added Turkish as a second language in Sitefinity's backend. We didn't experience any exceptions in the code (with a debugger attached), only a strange issue logging the user out, which disappeared after some time.
We've also contacted the OpenAccess team to confirm that they don't know of any issues caused by a Turkish server collation, and they've told us they even have tests running successfully on it.
Could you guide us by answering a couple of questions:
- Are you getting this error only after adding Turkish as a second language?
- When adding Turkish as a second language, did you set is as default?
- Does removing Turkish resolve the issue?
- Is your Windows, IIS, or website default culture set to Turkish?
- Also are you using the 4.2 SP1 version?
- What is your upgrade history?
And could you also you send us all your error and upgrade logs - the contents of the App_Data\Sitefinity\Logs
directory? Also if feasible it would be a great help if you can send us your project (with any custom development included) and a backup of your database, which we'll restore on our SQL server instance with Turkish server collation.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items