We recently upgraded our client's website (using DMX 6.1.6) from DNN 6.2.5 to DNN 7.2.0. Now, when we add a folder to the tree (as we have always done in the past), it doesn't appear in the UI. There's no error message. And there's no exception in the Event Viewer.

The entry for the folder can be found in the DMX_Entries table. It differs from a visible entry in that:
1. Its Path is NULL instead of something like "0;1;3021;3212;", and
2. Its PermissionsOnlyByAdmin is "0" when visible ones are "1".

Any idea what could be going wrong?

Also, there have been some reports that the folders show up "eventually" - perhaps hours or days later. I'm not sure if this is spontaneous or due to some other random change that we make that triggers some update.

Any help would be appreciated because this feature is actively used and not functioning currently.

Thanks!

Larry

One other difference about the problem folder entries: they all have LastModified = NULL.

I have tried calling:

EXEC DMX_UpdatePaths 0, 3712

in the hope of updating the Path for one entry. It appears to have updated paths for all the entries. The path for entry 3712 appears correct. But the folder still does not appear in the UI (even after doing a Tools > Clear Cache).

Also, setting PermissionsOnlyByAdmin to True does not help. Setting LastModified to Created date for this entry also does not help.

Also, after uploading a file to a visible folder, the upload triggers a notification email, but the file is not visible in the UI.

Is there some sort of DMX stored procedure that we could run that would clean things up or delete some cache to solve this even on a temporary basis? Performance is not an issue since it is not working at all for us right now.

Manually running the Host > Schedule "DMX Maintenance task" seems to clean up whatever the problem is. By default this only runs every 12 hours. Since it takes less than a second to run, I'm going to set it up to run more frequently for now.

But the question remains, "What is DMX Maintenance fixing?" The Schedule history doesn't give much clue. It just has a large block that looks like this:

DMX Maintenance Task Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents Cleaning Temp Directory for portal EOS CCA Deleted 0 documents Cleaning Temp Directory for portal EOS NCN Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Cape Cod Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Falmouth Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Jordan Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Memorial Hospital Deleted 0 documents Cleaning Temp Directory for portal iPatientSurvey for Test Hospital Deleted 0 documents

Is there some more refined task we can run to find out / see exactly what is wrong that is being cleaned up and fixed in our case? That would be a big clue as to where the root problem is.

With Peter's help, we were able to quickly find the cause and solution to the problem.

The problem was caused by missing Triggers in the DMX_Entries SQL table. There are supposed to be three triggers there and there were none. If I had to guess how this problem came about, I'm thinking it was the Papayas DnnAutoUpgrade module (v6.2.9) rollback feature that caused the problem. During the DNN 7.2 upgrade, it had to roll back to the 6.2.9 install due to a DLL overwrite permissions error. I'm guessing that this rollback is what lost the triggers somehow.

The solution was to restore these triggers. Since Peter said a "repair install" of the DMX module would not restore these triggers, he restored them via a SQL query instead.

I cannot thank Peter enough for his excellent service when we needed him most. That speaks volumes about both him personally and the Document Exchange module!