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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...05.01.00.SQLProvider Error05.01.00.SQLProvider Error
Previous
 
Next
New Post
6/26/2009 3:20 PM
 

We were testing the upgrade from 5.0.1 to 5.1.0 and came across this error.   It was triggered because the primary key index is PK_EventLog not PK_EventLogMaster in our installation.  The following is from the 05.01.00.log:

System.Data.SqlClient.SqlException: Table 'EventLog' already has a primary key defined on it.
Could not create constraint. See previous errors.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)

/* Change primary key of EventLog Table */
/****************************************/

IF NOT EXISTS (SELECT 1 FROM INformATION_SCHEMA.COLUMNS WHERE TABLE_NAME = 'dbo.EventLog' AND COLUMN_NAME = 'LogEventID')
 BEGIN
  --Note this name does NOT have an object qualifier in 4.x upgrades
  IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'PK_EventLogMaster'))
   ALTER TABLE dbo.EventLog
    DROP CONSTRAINT PK_EventLogMaster

  --Note this name does have an object qualifier in 5.x installs
  IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'PK_EventLogMaster'))
   ALTER TABLE dbo.EventLog
    DROP CONSTRAINT PK_EventLogMaster

  ALTER TABLE dbo.EventLog
   ADD LogEventID bigint NOT NULL IDENTITY (1, 1)
   
  ALTER TABLE dbo.EventLog
   ADD CONSTRAINT PK_EventLogMaster PRIMARY KEY CLUSTERED ( LogEventID )  
 END

We have already edited the script and will restore the test site from our backup and retry the upgrade.   However, we felt this issue needed to be shared with others.

Mike

 
New Post
6/26/2009 4:43 PM
 

This error has already been reported (half a dozen times) and will be fixed in next version. it shall not affect function of your DNN installation.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/26/2009 6:51 PM
 

You are the expert but I'm not sure I agree with you.  The outcome of the upgrade on our test sites, which are a copies of the production sites, was something I would not put into production.  There is an error on the Home page that we have not been able to figure out yet, the dates at the bottom of the page in module 'Settings' are 01/01/0001, the bottom of the Control Panel is obscured for some reason and there seems to be other issues that, at this moment, I can't describe exactly.  Of course, I don't know if all of these issues relate to this error.  We have 3 different websites in production with 5.0.1 using skins from two different publishers and of two different ages but so far the problems appear to be identical on all three test sites.  As I said, your the expert but we believe we've fixed the ObjectQualifier and the Provider so we'll see what happens with the retest.

Thanks for your attention.

Mike

 
New Post
6/26/2009 7:01 PM
 


Alex Shirley


 
New Post
6/26/2009 8:09 PM
 

Thanks a bunch!  That was helpful.  We'll give that a try before we run the retest and see what happens.

Thanks again,

Mike

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...05.01.00.SQLProvider Error05.01.00.SQLProvider 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