Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade 5.6.3 to 6 errorUpgrade 5.6.3 to 6 error
Previous
 
Next
New Post
7/22/2011 6:18 PM
 
Any ideas on this one?

Cannot resolve collation conflict for DISTINCT operation.
Cannot resolve collation conflict for DISTINCT operation.
Could not use view or function 'dbo.vw_PortalsDefaultLanguage' because of binding errors.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Cannot resolve collation conflict for DISTINCT operation.
Cannot resolve collation conflict for DISTINCT operation.
Could not use view or function 'dbo.vw_PortalsDefaultLanguage' because of binding errors.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): Cannot resolve collation conflict for DISTINCT operation. Cannot resolve collation conflict for DISTINCT operation. Could not use view or function 'dbo.vw_PortalsDefaultLanguage' because of binding errors.] System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) +1951450 System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection) +4849003 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2394 System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +33 System.Data.SqlClient.SqlDataReader.get_MetaData() +83 System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +297 System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +954 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32 System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +141 System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +70 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) +364 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +124 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +107 DotNetNuke.Data.SqlDataProvider.GetPortals() +71 DotNetNuke.Entities.Portals.PortalController.GetPortals() +28 DotNetNuke.Common.Initialize.CacheMappedDirectory() +37 DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +268 DotNetNuke.Common.Initialize.Init(HttpApplication app) +174 DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +184 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 
 
New Post
7/22/2011 7:00 PM
 
this can happen if a refernce to a database changes - did your web.config have the correct settings (i.e. did you let the automerge handle it) as if you manually merged and forgot the databaseowner/objectqualifier settings it might cause this

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/27/2011 4:12 AM
 
Hi 
I have worked out when I migrated from an old host to another the collation was wrong. All the upgrades have gone ok to 5.6.3, but I can't get 6.0 there must be collums or table with the old collation SQL_LATIN opposed to LATIN etc.. what would be the best way to migrate to  a new database? Or repair it?
 
New Post
8/31/2011 12:12 PM
 
im not really sure, you basically have to stick on the same collation - i've never tested to see if changing the collations on tables after the fact will resolve - the error suggests it may be possible - see http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=77212 and http://support.microsoft.com/kb/325335 for some suggestions

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade 5.6.3 to 6 errorUpgrade 5.6.3 to 6 error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out