Trying to move my existing DNN site to a new hosting provider with little luck.  The new host supports v 3.1.1 only so luckly my site was currently at a version below this.  I sucessfully upgraded the site to 3.1.1 to agree with the new host.  I than back a BK of the database and moved all the files to the new host (ISQ Solutions).  Apparently the process as stated by the host was to: create a new DB with Enterprise Mgr. run the 3.1.1 install to create a new DNN site and to populate the DB.  Then use Export & "copy tables and views from source database" from existing site's DB to the newly created DB at the new host.  Finally I was to upload all the files from my old host to the new host, (overwriting all the DNN files at the new host).  OK I know this is a little confusing but I think you get the drift.  The problems seem to be with the DB copy as doing so produced several Foreign Key and Key constrainsts errors.  I suspect the issues might have something to do with the fact the DB was originaly upgraded to 3.1.1 and the DB at the new host started out @ 3.1.1.  If there is anyone out there that can help me that would be great as I have a second DNN site which also needs to be moved as soon as I get things sorted out with this one.  BTW, the host does not support a database restore for DNN sites so I'm limited with my transfers options.

Cheers,

Brownie

OK so I have the site files and DB uploaded and the site does seem to work, sometimes!  I'm getting a lot of errors on simple things like loading the site sometimes gives me "System.Data.SqlClient.SqlException: General network error. Check your network documentation".  If I try to sync the file system with the DB I get the same error. Going to Admin-Pages gives me this error "Failed to start monitoring changes to '\\nas-001\winspace003\10-sitename.com\www\Admin\Tabs\App_LocalResources".  I get this error from time to time "The timeout period elapsed prior to completion of the operation or the server is not responding.
General network error."  As well I'm not able to add modules only edit the ones that already exist, when I do I get this error "DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot insert the value NULL into column 'ModulePermissionID". 

My question is, can I do anything to check and fix all errors in the DB that could be causing this?  Would forcing an install (host only supports 3.1.1) do any sort of fix? It seems like I would be a lifetime finding and fixing all the errors in both my sites, and I would hate to start from scratch on both sites or worse, switch to another CMS.

BTW in order for me to get to where I am now with the sites I, scripted the database opbjects, views, SP, permissions, and when transfering data many tables gave me the same errors as before with key issues and constraints but I was able in most cases to do one table at a time or drop and recreate the object to get past the transfer errors.

Brownie

I agree this would be a very daunting task.  Unfortuanatly the steps you outlined are those I've already done.  Before I was able to upload any files or DB to my new host I was forced into upgrading the sites to 3.1.1.  This process seemed to go rather well and without error at my old host. Once this was complete I downloaded the entire site to my local development environment and did a simple DB restore, pointed a local IIS web to the files (created a local entry in the PortalAlias table) and was off to the races.  In fact the sites work fine from the dev. server but I believe this is simply due to the fact that I was able to do the restore rather than Copy tables and views function.  I did get lots of errors in the transfer but was able to successfully get everything over to the tables at the new host but still having issues.  Everything at the new host was copied from my local dev. site including the DB.

I'm certainly running out of ideas here and starting to wonder if perhaps there might be some restrictions at the host perventing this from happening.  They do not allow db_owner to the SQL accounts but I don't think DNN needs this since all other access is permitted.

Is it possible to have two seperate copies of DNN running on the same site.  If I was to do an install (with the hosts DNN 3.1.1 files) and run it from a VDir (called dnn2) would this allow me to run both copies?  Each copy would need its own web.config file but would DNN look to the current folder for this or the web root?  I know this sounds crazy but it might give me some options for getting one good site out of the pair then delete the files from the nonworking site later.

B