Hi,
This issue is under investigation for a fix in a ProFile update. This occurs for those using classic database, and the work around is to uncheck file protection as mentioned in this thread.
I apologize for the inconvenience bit hope this helps
