Can you try deleting the current view?  If you click on the arrow for the view and then select a DIFFERENT view option that should enable the Delete button so try to get the view back to the standard default view and see if that helps…
 

HI Reid, I cant get that far. The module does not open. When I try the drop arrow for the view options, this is what I get

I suspect this one might require a cleanup script at the database level, so I would suggest that you log a support ticket for it at this time…
Thanks,
Reid

There is a table cp_application_view which if you have DB access where you can find all the views for that user and it also has which modules, etc.

Perhaps you can find the views for that user and module and delete those row(s) from a DB level?

Deleting a view with the method described by Reid normally would just delete the row but if you can’t get that far….

Thanks guys. I will issue a ticket. I would like to determine the root cause if possible. 

Hi Sean,

I know you logged the case in our portal but I am unclear whether the solution we proposed resolved the issue or not as you flagged the question as answered.

It should be an issue with data in the database as you reported this occurs regardless what client the user operates thus is not a caching issue.

What Reid proposed is not an option as I the module does not even open to a point where I can delete a view.

What you proposed, I have no access to. So no, the issue is not Resolved. I clicked “like” believing it would simply end this string with no further action. I issues temporary alternate credentials to the user as a work around and issued the ticket.

Thanks again for the quick responses. 

We have one user that is experiencing this error when trying to access the Customer center module. It occurs on any machine we try to use her credentials on. It is not something we have ever encountered. Any suggestions before I issue a support ticket?

 

 

Deleting the view is one way of solving the issue, but I found that sometimes an invalid character (Form Feed) gets saved into the XML.  The view can be fixed with this query (replacing {person_id} with the user’s ID)
 

update cp_application_views set view_data = replace(view_data, '', '') where created_by = '{person_id}' and view_data like '%%';