Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Collection cannot be null. Parameter name: c error while moving DotNetNuke site from one server to aCollection cannot be null. Parameter name: c error while moving DotNetNuke site from one server to a
Previous
 
Next
New Post
2/1/2013 5:35 AM
 

I was trying to migrate a DNN website from one server to another by following this blog post.

After creating the new alias for the site, like theabc.co.uk, I have copy paste the source files from server A to server B under httpdocs and used Import and export tool to move my database to destination.

But while running the page, I get the following error. It seems to me that its related to portal but the alias in the portalalias table is already defined for '0' portal id.

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. [ArgumentNullException: Collection cannot be null. Parameter name: c] System.Collections.ArrayList..ctor(ICollection c) +9364083 DotNetNuke.Entities.Portals.PortalController.GetPortals() +183 DotNetNuke.Common.Initialize.CacheMappedDirectory() +39 DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +375 DotNetNuke.Common.Initialize.Init(HttpApplication app) +155 DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +231 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
 
New Post
2/19/2013 5:42 AM
 
Same thing happened to me yesterday. The solution was: the user who runs the app pool was in the public role for the SQL Server database, and not in the db_owner role (I was pretty sure, I added the db_owner role, but this was obviously not the case!). After assigning db_owner, everything worked fine.

Best wishes
Michael

Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Collection cannot be null. Parameter name: c error while moving DotNetNuke site from one server to aCollection cannot be null. Parameter name: c error while moving DotNetNuke site from one server to a


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out