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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Collection cannot be null. Parameter name: c  (after failed upgrade)Collection cannot be null. Parameter name: c (after failed upgrade)
Previous
 
Next
New Post
6/16/2014 11:42 AM
 

I moved to a new server and all went well.  Then did an upgrade that had numerous errors because I didn't know you had to unzip all of the folders within folders.  So I tried to undo the upgrade with my backup copies and that failed, then ended up just deleting all files and website and starting over. But I keep getting this error message even though all of the files are from weeks before I tried the move to a new server and the separate sql database was restored to a copy from weeks ago. Any help is greatly appreciated.  I run IIS7.5 with .net 4.5 and a separate sql server database.

 

Collection cannot be null.
Parameter name: c

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.ArgumentNullException: Collection cannot be null.
Parameter name: c

Source Error:

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.

Stack Trace:

[ArgumentNullException: Collection cannot be null.
Parameter name: c]
   System.Collections.ArrayList..ctor(ICollection c) +10647211
   DotNetNuke.Entities.Portals.PortalController.GetPortals() +180
   DotNetNuke.Common.Initialize.CacheMappedDirectory() +36
   DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app, Boolean& initialized) +324
   DotNetNuke.Common.Initialize.Init(HttpApplication app) +191
   DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +229
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +136
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69
 
New Post
6/16/2014 2:44 PM
 
it is hard to guess from the error message.
I would delete all files and database, and restore both from the move.
You will need to adjust both connection strings in web.config file - and
portal alias in the database, if the domain names is changing.
Which version are you upgrading from and to?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/16/2014 2:46 PM
 

Last Friday, I moved the file folder to the new server.  Setup the new site in IIS, added the apppool process to the folder and ran the site in chrome.  It worked perfectly.  So then I did the upgrade to 7.03 and received numerous errors that I discovered later were because I didn’t unzip all of the zipped folders before I ran the upgrade process.  So I restored the whole folder from back up after deleting the website and the folder, then rebuilt the website and ran it and got the error message below. So, that’s when I started asking for help from you.

Our DB Admin restored the database to a copy from the week before and I deleted everything off the new serve, rebooted and started over with clean copies of the files and the database this morning.  And I still get this error message.  There is no reason why I am still getting this message with all clean files and database. 

I am running server 2008, IIS 7.5, DotNet 4.5 is installed but the apppool processes are running under version 4.0.  And SQL stand alone, not sure what version.

 
New Post
6/16/2014 3:35 PM
 

Sebastian,

 

The domain name did not change we moved those as well using host headers and a different ip address than it had.  But host headers should be fine. What do I need to change in the web.config file?  Upgrading from 7.00.06  to 7.03

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Collection cannot be null. Parameter name: c  (after failed upgrade)Collection cannot be null. Parameter name: c (after failed upgrade)


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