I'm getting the following errors in DMX after the subject upgrade.

I have these errors in the SyncFolders task:

Checking 'Partner File Share' on portal 1Finished checking 'Partner File Share' on portal 1 from 2013-03-20 14:53:28Z to 2013-03-20 14:53:28Z
Filestream opened '\\rpcws2k8h\Medical-File-Shares\CDC\Medical_Exam_Form201303191600.zip'
Filename :Medical_Exam_Form201303191600.zip
Could not copy '\\rpcws2k8h\Medical-File-Shares\CDC\Medical_Exam_Form201303191600.zip' to DMX folder 4657 at Bring2mind.DNN.Modules.DMX.Entities.Entries.EntriesController.SimplifiedUpload(Int32 PortalId, Int32 CollectionId, Stream File, String OriginalFilename, String Title, UserInfo User, Boolean BypassSecurity)
at Bring2mind.DNN.Modules.DMX.Services.SyncFolders.SyncFolderSynchronizer.ᜁ(String A_0, Int32 A_1)
Filestream opened '\\rpcws2k8h\Medical-File-Shares\CDC\Medical_Exam_Form201303201200.zip'
Filename :Medical_Exam_Form201303201200.zip

And if I login as the host, the module displays:

A critical error has occurred. Object reference not set to an instance of an object.

And the Event Viewer shows:

AssemblyVersion: 7.0.4

PortalID: 1

PortalName: Refugee Processing Center

UserID: 3071

UserName: myhost

ActiveTabID: 238

ActiveTabName: NVC Datafiles

RawURL: /FileTransfers/NVCDatafiles/tabid/238/Default.aspx

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: https://www.wrapsnet.org/Host/Schedule/tabid/25/portalid/1/Default.aspx

UserAgent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0)

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID: 62f22d23-86f6-454e-92fe-f52c61bc612c

InnerException: Object reference not set to an instance of an object.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: DotNetNuke.Security.Roles.RoleController.GetRolesByUser

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 DotNetNuke.Security.Roles.RoleController.GetRolesByUser(Int32 UserId, Int32 PortalId) at Bring2mind.DNN.Modules.DMX.UI.ModuleBase.get_UserXml() at Bring2mind.DNN.Modules.DMX.UI.ModuleBase.get_RequestFixedXml() at Bring2mind.DNN.Modules.DMX.Views.AjaxTwoPanel.ᜁ(Object A_0, EventArgs A_1) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Source:

Server Name: RPCWS2K8H

So two errors. The first: "Could not copy '\\...etc'" signifies that the sync folder task could not access (i.e. read) that file. Either because it didn't have permission or locked or something else. From within DMX it is impossible to determine *why* it can't access a file, only that it can't.

The second error: "Object reference not set to an instance of an object. at DotNetNuke.Security.Roles.RoleController.GetRolesByUser" looks a lot like an old bug. I'll see what I can do to replicate that.

Peter

I looked into this but I can't reproduce the second error. I also did some analysis of the framework, but the mentioned method has not changed recently. There must be something up with the users and or roles on your installation which prompts this error. But I'm left guessing as to what it can be. The method should never return this error as far as I can tell.

Peter

O ... one more observation just after I clicked submit ... if the user's ID doesn't return a user for the current portal it could throw this error. Now that would normally not be possible. DMX retrieves the UserID from the context and then calls this method to get the user's roles which looks up the user in the current portal.

Did the user that encountered this error jump portal? How is his/her portal registration handled?

Peter

Peter, the reason this error occurred is because the user was deleted. The user was deleted a while ago, but as you know DNN just soft deletes the user. Then recently I clicked the "Removed Deleted Users" in the Manage Users area, and it must hard delete the user. That's when I started seeing the error. I restored the user from a backup of the DB, and all is well again.

However, you may see this error again with another customer, just to be wary.

R,

TPM