Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

Upgrading dmx 3.4.9 to 4.3.2 or 5.3.7
Last Post 03/21/2011 3:55 PM by Peter Donker. 7 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
philb
New Member
New Member
Posts:13


--
03/16/2011 2:57 PM
I'm trying to upgrade DMX from 3.4.9 to 5.3.x. Having upgraded DNN to 5.1.1, I tried to install DMX 4.3.2. During the installation I got the following error:

SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Cannot drop the trigger 'dbo.DMX_Init', because it does not exist or you do not have permission. 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) DROP TRIGGER dbo.[DMX_Init] System.Data.SqlClient.SqlException: Cannot drop the trigger 'dbo.DMX_FollowUp', because it does not exist or you do not have permission. 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) DROP TRIGGER dbo.[DMX_FollowUp] System.Data.SqlClient.SqlException: Cannot drop the procedure 'dbo.DMX_FindAttributesByName', because it does not exist or you do not have permission. 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) DROP PROCEDURE dbo.[DMX_FindAttributesByName]


Althought the rest of the installation was reported as successful, and the module seems to be mostly working, it obviously was't totally clean:

- When slecting 'Mail me' I get an error:

An error 'The INSERT statement conflicted with the FOREIGN KEY constraint "FK_DMX_Log_DMX_Entries". The conflict occurred in database "mydb", table "dbo.DMX_Entries", column 'EntryId'. The statement has been terminated.' occurred. Trace:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at ......(have truncated this)

- When logging out of DNN I get this error:

An error has occurred.
Error loading Bring2mind/DMX/ViewCollection.ascx

- There are also errors in the Event log which I can supply if useful.

- I get the same errors if trying to install DMX 5.3.7.

If I then try and upgrade DNN from 5.1.1 to 5.2.2, the upgrade immediately fails with :

[NullReferenceException: Object reference not set to an instance of an object.]
Bring2mind.DNN.Modules.DMX.WebDAV.AuthenticationModule.ᜀ(Object A_0, EventArgs A_1) +30
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75


How can I get around this?

Thanks in advance

Phil


Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
03/17/2011 12:48 AM
Hi Phil,

The SQL errors you mention first are harmless luckily even though they surprise me somewhat as this is not normal.

Then there are a bunch of errors that I think have probably been resolved in the meantime. DMX 4.3.2 is pretty old and there have been incompatiblity issues with several DNN platforms in the past that needed to be resolved. I'll have to assume this is not due to a bad installation but due to the constellation of DNN 5.1.1 with this DMX version and 5.3.7. Note that DNN 5.0 and 5.1 have not been very "happy" releases of the platform. There were many issues and not just with DMX. Since 5.2.3 things have been calmer.

Then you mention "trying to install DMX 5.3.7". Are you now on 5.3.7?

Finally: The AuthenticationModule error. What you'll need to do is to (temporarily) remove this module from the modules section of the web.config.

Peter
philb
New Member
New Member
Posts:13


--
03/17/2011 3:19 PM Accepted Answer
Hi Peter,

Thanks for the reply. I've now upgraded the DNN install to v5.6.1 and attempted to upgrade DMX. My experience is:

DMX 4.3.2 :
- Same SQL error on install as above
- Same error when trying to access the 'Mail me' function
- Same error as above on logout (Error loading Bring2mind/DMX/ViewCollection.ascx)

but with on 5.6.1, I cannot Access the Admin/Main Option function as I get an 'Object reference...' error:

AssemblyVersion: 5.6.1
PortalID: 0
PortalName: MyPortal
UserID: 1
UserName: host
ActiveTabID: 79
ActiveTabName: Resources
RawURL: /AboutUs/Resources/tabid/79/language/en-GB/Default.aspx?ctl=MainOptions&mid=432
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; Avant Browser; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 0f80c770-d85e-4792-b6b2-a8aa269d144e
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: Bring2mind.DNN.Modules.DMX.Security.Controls.SimplePermissionsGrid.SaveViewState
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Bring2mind.DNN.Modules.DMX.Security.Controls.SimplePermissionsGrid.SaveViewState() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Control.SaveViewStateRecursive() at System.Web.UI.Page.SaveAllState() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---


With 4.3.2 installed on 5.1.1, I was able to access the Main Options menu.


I also have to comment out the folling in the web.config to avoid an error:

<!-- -->



DMX 5.3.7:
The installaltion reports and SQL error the same as that in the original post but the installation fails and I have to rollback the site and start again.

Also we are past the 'Service Until' date - I'm not sure how that affects the upgrade?

As regards the DNN installation, I have upgraded this incrementally from v4.3.7 to v5.6.1. To achieve this I've had to modify the collations of the following columns in order to avoid collation conflicts:

Tabs.iconfilelarge nvarchar(100) collate SQL_Latin1_General_CP1_CI_AS
PortalSettings.settingvalue nvarchar(2000) collate SQL_Latin1_General_CP1_CI_AS
PortalLocalization.CultureCode nvarchar(10) COLLATE SQL_Latin1_General_CP1_CI_AS

I thought I should mention this just inc case it impacts upon the problem above.

I can provide a login for the test site if that would help diagnose/resolve the issue.

Hope you can help with this.

Cheers

Phil
philb
New Member
New Member
Posts:13


--
03/17/2011 3:22 PM
Web.config mod filtered out from above post is:

      <!--  -->
       
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
03/17/2011 5:43 PM
Hi Phil,

Your best bet is the latest DNN (or at the very least 5.2.3) and the latest version of DMX. Not too long ago we took out incompatibilities with recent DNN versions. Module development is an ongoing task in that respect.

From your posts I gather you're working in isolation (i.e. a test upgrade and not the production site) which is great. What we need to solve is the upgrade path. IMO the best way is to first upgrade DNN to the version you'd like to go to and then upgrade DMX to the latest version. You'll need to renew the license so you're still in the service period to install the latest version by the way.

If the only stumbling block is the FK_DMX_Log_DMX_Entries error in SQL then remove that constraint manually in the DB. It is on the DMX_Log table.

Peter
philb
New Member
New Member
Posts:13


--
03/17/2011 7:15 PM
Hi Peter, thanks again for the reply.

THe DNN install is currently at 5.6.1. As noted above, installing DMX 5.3.7 fails (and also gives the same SQL error as in the first post). I'll arrange to renew the licence so that we're in the service period. Will being outside the service period account for the installation failing?

Thanks

Phil
philb
New Member
New Member
Posts:13


--
03/18/2011 12:52 PM
Hi Peter,

A little further clarification required please...we will of course renew the licence for the module but if, as noted above, installing DMX 5.3.7 on DNN 561 actually fails how will that help? Does the module check a remote licence server on installation ?...or is the PA that's supplied on purchase different to that available from the downloads page on this site?

Thanks

Phil

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
03/21/2011 3:55 PM
Hi Phil,

I've never seen it fail upon installation due to something *in* the module. The DNN installer does not run any DMX code. So this is somewhat puzzling.

But if the problem boils down to the FK that was mentioned in your first post than the best way forward is to remove it by hand. Have you tried that? Then upgrade.

Peter
You are not authorized to post a reply.