Hi Scott!  Of course!  I poke fun at myself all the time.  

Yes, the application has been restarted.  It seems, that my other implementations of DNN on other servers are exhibiting the same behavior.  Whatever it is that I am doing, I am consistent.  

The last thing that I did was to make a template “with content” of one of the portals.   Perhaps there is a way to rebuild the database to mirror what is on disk? 

Consistently “bad Sal”.  J

 

Hello Scott,

I thought that it might be a file protection problem, too.  So I made sure that the network service, aspnet, and anonymous (covering all the bases) had full access to all folders in dotnetnuke.  Still no success.  

Since this is a production server, I had to restore from a prior backup of the database and dotnetnuke directories.  The version that I had to move back to is 3.1.1.  Thank God this is a fairly static implementation!  However, I did save the bogus implementation, too.  I have also restored to a test server and I am going to retrace my steps, from upgrading to 3.2.2, to posting new files to the portals, and creating a templates, etc. to see if I can reproduce the problem.    I'll continue to post to this thread with my observations.

Thanks for all your help.

Sal

 

I am experiencing the same problem as "bad Sal". I recently upgraded from 3.1.1. to 3.2.2. and I now get the same error at exactly the points Sal describes. I have sync'd, cleared cache and gone through the folder and file structure with a toothcomb...perhaps some tears may be required....