Hi Sebastian and
all, I have been experiencing what appears to be the same TimeOut problem and
attempted to follow your suggestion above of deleting empty user folders.
Almost all of our user folders (a few thousand) are empty. I made a local
backup copy of the Users directory, then used WinDirStat to determine which top
level folders (from among "Users/000" to "Users/255")
contained only empty folders, then I deleted the first 30 or so of these empty
top level directories and did a recursive file sync on the Users directory
using Admin > File Management.
This did resolve the
problem of the timeouts, however it caused a nasty side effect: for some or all
of the users whose folders I deleted, DNN now shows a “(1)” at the end of the
display name at top right of the page (e.g., an account with display name “Example
User” now shows as “Example User (1)”).
In the hopes of
restoring the prior status, I copied back to the server all the folders I had
deleted (using the local backup copy mentioned above). However, the display
name problem continues to be present. Additionally, I then received the
following error when trying to do a recursive file sync on the Users directory
using Admin > File Management:
"An error occurred while loading the folder content Cannot insert duplicate key row in object
'dbo.FolderPermission' with unique index 'IX_FolderPermission_Folders'. The
duplicate key value is (9589, 6, 0, ). The statement has been terminated."
I cleared the cache and restarted the application, and can now do the recursive
sync without error, but there is no change to the displayname problem.
The dbo.Users table
lists the display names correctly, and when logged in as an affected user,
under edit profile the display name displays correctly. However it continues to
show with the " (1)" appended at top right of the page.
We are using DNN
7.02.02 (303).
I would be very
grateful for any guidance about how to remedy this situation.