I have mostly gotten Dot Net Nuke v3.2.2 installed and running in a hosted environment on ASP.NET v2.0.  I have found several posts in this forum indicating the the release.config / web.config file that came with v3.2.2 was for ASP.NET v1.1.  I  have modified my <compilation debug="false" /> and <pages validateRequest="false" enableViewStateMac="true" /> as per other threads herein.

For browsers of my site, everything is fine.

When I run in the "Administrator" or "Super User" roles to update my site, I get occasional "Object not found" Javascript errors.  Whenever this happens I know that whatever it was I was trying to do is not going to work.  The "File Manager", in particular, seems really messed up.  I have not gotten it to work at all.

Does anyone have any ideas on how to fix this, or other changes I may need to make to successfully run v3.2.2 on ASP.NET v2.0?  Does anyone have  any ideas on how to troubleshoot and fix Javascript and/or "File Manager" problems?

Could I / should I try to go back to ASP.NET v1.1?  Is this possible without completely losing all of the passwords due to some new kind of encryption? Machine Encryption? functionality?  I've tried to rebuild this site numerous times, and have often ended up with installs that I could no longer get into.  I have seen other messages to that effect on this forum.

Anyway, thanks in advance for any help.

Hi there,

No fix, I'm afraid, but I'm seeing similar errors.

Installed 3.2.2 on a development machine with ASP.Net 2.0 Beta 2. Getting a bunch of javascript errors. From memory: - dnntree.js had an "Object Required" error any time I tried to change the layout to one with a vertical menu, resulting in no Site Navigation menu. Also getting "; required" errors on the File Manager and Administrator Profile pages.

Maybe something to do with Beta 2?

Some further info, may help someone somewhere.

Installed on an old 1.1 dev machine and installed and ran fine. I then connected to that machine from my 2.0 beta 2 machine and was getting some more javascript errors similar to above. Seems to be pointing towards the ASP.Net client script files?