Not a solution, just an observation: I don't think that the error is the result of a collaction conflict between the two databases, it's a conflict between the call and the database. I have seen something similar once when I was running a query on one database that was created on a database with a different collation. I would try to figure out what query the failing method call results in.
Thanks for your reply.
The stored procedure called creates some temporary tables.
I foud this article that seems to explain the problem: http://foxtricks.blogspot.com/2008/07/how-to-properly-create-temp-tables-in.html
The collaction of the server im using is SQL_Latin1_General_CP1_CI_AS.
I really don't want to change any Community sql and the only other solution I can think of is to make sure both databases, their tables & the server has the same collation.
That seems to ba a hassle (especially since i have a copy of the EPiServer database in production already), does anyone have any other ideas?
Hello,
Fix problem with collation when deploy data of community.
Here is work around that I tried and succeed :)
- On your source server, generate script of community database with following option (select database, Task -> Generate Scripts):
o Generate script for dependent objects: true o Script Collation: True (Important)
o Script Data: True (used to generate data)
o Script full-text indexes: true if you want o Script Triggers: true
- On your destination server, create new database with any name, open the script file on previous step
- Make sure you use the newly created database, execute the script
- Stop your community site (via IIS)
- Rename your old community database
- Rename your new database to your original database name
Hope this helps
/Dung Le
Hi,
Did you manage to solve this problem? I'm having the same problem here. I've tried to alter the collation on both cms and community databases to match the collation on the sql server, with no luck so far. I also tried to create a new database as described above.
Vibeke
My solution was to move the community database to another SQL server instance which have the same collation as the database. The problem originally occured after I restored the database onto a new SQL Server instance.
Vibeke
We had the same problem;
The problem was that the spEPiServerCommunityCalendarGetEvents made use of the DB server local temp table (which had another collation). What we did was the following inside of the sp:
Remove the "#" (which means create as temptable) in the beginning of these tablenames:
#tmptblEPiServerCommunityEvents
#recurrentEvents
The difference is that we write the tables to the current DB (the community DB) which has the right collation. This was a tweak for our dev env. the tables get dropped in the end of the SP.
Hi, I have an existing EPiServer 6.0.530.0 site and I tried to add EPiServer Community 4.0.517.255 by using "Install Community on existing site" in the deployment center.
Most of the stuff seems to be working, but some db calls fail with the message "Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict".
For example.
The collation of both the episerver and the episerver community databases are Latin1_General_CI_AI
Any ideas?
Thanks.
Martin