We have a site up and working and this module was working two days ago and is still working on our development server, but in production we are now getting an error if we are logged in (otherwise this module just doesn’t display).  This is the error we are getting:

Data Binding Failed. This issue might be caused by an unsupported cast of a data type.
Error Description: A column named 'Created by_UDT_Original' already belongs to this DataTable.

We have tried re-importing the data that we had exported from our development site to load the production site that worked.  We have also delete this module from the page and re added it and still get this error.  It will allow us to do the “form and list configurations” and displays all the fields defined.  We can click on the edit for the “Created by” field, without an error but if we try the other required fields “Created at”, “Changed by”, or “Changed at”, we get this error.

An error has occurred.
Error: is currently unavailable.

We are at a loss as to where to look next, or what to do to correct this error.  This is only happening with this one module all the rest of the pages/modules are working fine.

Also if we add this module to a new page we are getting the same thing and have notice in the events that we are getting this error logged:  InnerException: An entry with the same key already exists.

Anyone have any ideas?

Thanks for your help!

--Jim Lowary

Stefan,

If we set this up on a new page we get the same error, even before we put any data into the.  We could add new fields but nothing would show and it didn't hit me but when we added a new module to a new page it would only show the “Created by” field not the other three required fields mentioned before.

As for the import/export we used the function in form/list module (which created an xml file I think).

The form/list module that we are using is 5.0.2 and DNN is at 5.1.2

Every night at about 2am the server this is on is re-booted (on purpose) and this morning everything is back working again, so there must have been some kind of caching error or internal code error that caused the problem, that is the only thing we can think of.  We had just thought the DB for this module had gotten corrupted or had a duplicate record based on some other posts, but we couldn't find any.

Thanks,

-- Jim