I get this "object not set to instance of an object error". It occurs when I click on the pencil (edit) of a module on the host/modules page. The action is not performed. The stacktrace shows it is pointing to a deleted skin. I look at the page source code and there is no reference to this deleted skin. I'm guessing it's something dynamically linked perhaps from the database associated with the edit page that fails. Perhaps if I look at the edit page I would find the deleted skin? 

Are there any tools linking pages/modules/skins that can be displayed to find out where this is referencing?  Is this a database entry? What tables and table relationships would be involved? Is the only solution to manually fix bad associations in the database? Any utilities to find/fix/replace this sort of thing?

Thanks I appreciate your care and effort.

I did a "select distinct skinsrc from tabs" and it came back with null as the only entry. Did the update anyway. Didn't have any effect but I appreciate the idea.  I'm trusting it clears the use of any skin overrides at the page level and forces the page back to using the default? Does it also do that at the module level? Is there a flush at the module level along these lines?

The dashboard says that there are 3 skins in use. There should be 1 and perhaps the MinimalExtropy. Is shows 2 skins as not in use that have been deleted so I wonder why they still show up as even existing? One of the two deleted skins that the Dashboard shows as not in use is the skin that the hosts/modules page chokes on. Again, I can get around it but what I'm trying to do is get the skin creator (artiseer) to figure out why they are referencing an old skin and not the one actually in use.

If you know of a way to force every module back to the default please let me know. Or for that matter any other ideas. I know I can clear the problem for this page but what I'm concerned about is having it effect a page I don't knowabout particularly what happens if I update the their skin.

I'm not sure that this is totally an issue with artiseer, it may be tied to dnn 5.?? not dropping information out of the database completely when I skin/module is removed. In my quest to fix this I was advised to drop all purchased modules and that would likely fix it. I did that but ran into several cases of database errors during the dropping of modules. It may be bugs in the module writers code. I don't know. I would expect better integrity checking and correction options. Seems like a good business opportunity. They again, I'm guessing the DNN people have their eye on selling you that in the Professional edition? I would hope to find third party analysis tools. If you know of any please advise.

Again, thanks for caring. -Paul