Thinking of upgrading? :) Unless you know how to configure 3.2.2 to work with .Net 2.0 then you pretty much HAVE to upgrade. I think upgrading to 4.0 would be less painless than trying to make 3.2.2 play nice with .net 2.0...

SO I've made some progress tonight. I believe I had an error somewhere somehow in the connection string for the database. I made some changes, made a pig's ear of the web.config file so I deleted it and uploaded a fresh one (with the keys already pasted into it) and input the server name, dbname, uid and pwd etc.

I went to /portal/install/install.aspx?mode=install and it said nothing to install, databse version 04.00.03. after that I went to the default.aspx and some of the stuff was there (text) but no graphics. Logging in as Admin gave more detailed error messages, and basically it said that it was a file not found. I flipped over to FTP and looked at the portals folder and there was no 0/ folder. I must have overwrote it when I uploaded the 4.0.3 files.

Fortunately, I keep my feathers numbered, for just such an emergency. I uploaded the /portals/o/ folder from the 3.2.2 backup and then the site seemed to work. pictures worked again, and after re-configuring the logo from the admin>site settings everything seemed to be OK

And then I tried to upload the skin via the host>skins menu and it all fell apart. In Firefox 1.0.7 I got the "FileUpload is not currently available" message. I switched to IE (fresh, no session cookies) and it seemed to work, until I clicked upload file, then I got this error:

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

And that was all she wrote. The site seems to work OK as a static website, but that's not exactly why I'm using DNN in the first place. :) File I/O seems to be the major thing that's not working now... Im not a developer and I don't know .Net much more than being able to look at the web.config and sort of understand what some of it is. I believe I've reached the limit of what I can do by myself now, so hopefully someone here can help out.
-M

in both the connection string and the appsetting sections I rem'd out the sql 2005 express strings and un-commented out the sql 2000/2005 strings. both the connectionStrings and the one that's remarked "for backwards compatibility" in the appSettings section.

I'll triple-check it tomorrow, I just flew in after a long day and boy are my arms tired.. joke half intended :)