Any Ideas what else I can do?

I experienced this issue this week when I upgraded my Godaddy hosting account from shared server to grid server.  Encouraged by others who had the same issue, it made me realize that it is caused by something in the repository module rather than my database.  I dove into the problem further by first adding a new repository module to a test page and verifying that it worked, which it did - I was able to add an item and view it, etc. 

I then dove into the database tables behind the repository modules.  The table named grmRepositoryObjects contains the ModuleID associated with the module on any given page.  In my case I had only 2 repositories - the original one that was causing me problems (ModuleID=420), and the new one I had just added (ModuleID=518).    Tracking down those ModuleID values in the ModuleSettings table I found that the settings for the original ModuleID (420) had full path directory pointers that were not consistent with the new ModuleID (518). 

Specifically, in the ModuleSettings table, I filtered the records down to only those for my 2 repository modules, and I could see that the SettingValue for the SettingName records for "anonymouslocation", "folderlocation", and "pendinglocation" use full paths.  When Godaddy upgraded my shared hosted site to grid hosting, they physically moved everything to a new server, so the full path names changed.  Everything worked after I updated these ModuleSettings records to point to the physical path on the new instance of my remote server, but not until I restarted the application (from the Host Settings menu, at the bottom).  The restart is needed since the repository caches the module settings and they don't automatically get refreshed unless DNN is starting up or restarting.

2 important things about this:
(1)  when I first added the new repository module in my test, it didn't add all the settings to the ModuleSettings table - it only added one.  It wasn't until I modified the settings for the module and saved them that it added the entries that needed to be updated in my original module. 
(2) the restart after making the record changes was key to getting the original module to display the repository entries - don't forget to do it!

Note that I have version 3.1.15 of the Repository module installed, and I am running DNN version 05.05.01 (22)

Hope this helps others who might be experiencing this problem.

---

Gene W