Hello all,
I get the following error when trying to install this into DNN 6.0.2:

Server Error in '/' Application.

---

Value cannot be null.
Parameter name: file
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: Value cannot be null.
Parameter name: file

Source Error:




The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:







Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.


Stack Trace:





[ArgumentNullException: Value cannot be null.
Parameter name: file]
DotNetNuke.Common.Requires.NotNull(String argName, Object argValue) +70
DotNetNuke.Services.FileSystem.FileManager.GetUrl(IFileInfo file) +62
DotNetNuke.Services.Exceptions.ErrorPage.OnLoad(EventArgs e) +179
System.Web.UI.Control.LoadRecursive() +66
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428

---

Version Information: Microsoft .NET Framework Version:2.0.50727.5456; ASP.NET Version:2.0.50727.5456.
If this is an issue of running on the wrong framework version, can I just move it to 4.0 and then it will install fine? It's a bit confusing because .net framework 3.0/3.5 still shows up as version 2.0, and the latest Form and List module installs just fine in this configuration. I'm running on Windows Server 2008 R2 with all .NET Framework versions installed side-by-side from version 2.0 onward. Any help with this would be great. Thanks so much.

---

To run the latest DNN and YAF modules will require .NET 4.0 -- For sure on the YAF module. I don't know for sure if tha_watcha's DNN module requires .NET 4, but since YAF does, either way to run it you'll have to set your Application Pool to be 4.0 --

---

Yeah; it's certainly not a .net framework issue; I moved it to .net 4 and then tried again to install; I get the same error either way.

---

Yeah; it's certainly not a .net framework issue; I moved it to .net 4 and then tried again to install; I get the same error either way.

When did the error occured, during the installation of yaf, or after you added the module to a page?

This error looks more like an issue with your dnn installation, 6.02 is an old Version 6.2.0 is already out and upgrade maybe fix the problem if possible.

That's very odd; I just installed the latest DNN Version offered on the downloads page, which was 6.2. It was the first one down the list of them. Maybe I clicked the wrong one? But if you think that running the upgrade installer over it will help, then I'll try that. The error occurred when I went to install the module from the install extension wizard.

---

I installed the upgrade files over the existing ones, and the upgrade didn't even trigger which tells me that I'm already at the latest version. There is though, a link on the homepage which I can click to get the latest, but it hangs in Internet Explorer right when the new tab opens. But if this may help solve the issue with YAF being installed, other modules are installing fine, both those from DNN Corp as well as one from Oliver Hine's web site, and then your own skin object. So since the upgrade didn't work out if I'm at the latest version, do you have anything I should try next to try and stop this notNull exception from occurring? Thank you very much for all of your help so far.

---

That's very odd; I just installed the latest DNN Version offered on the downloads page, which was 6.2.

Ok you are using the latest version. There could be only 2 possible reasons why the installation fails.

1. there is something wrong with the dnn installation.
2. The YAF Module Installer fails on updating the web.config. Did you manually modified the web.config?

I just installed dnn 6.2 an yaf without a problem, with the standard web.config included with the dnn download package (Only the database connection string was modified).

Thank you again for staying on this. I'll tell you that the only modification I did that is manual to web.config is that I changed the customError value to off instead of remote only so that I could see the error from a remote machine. Everything else, like the database connection was inserted by the installer when I inserted it into the corresponding fields on the installation page. That's about all I did for web.config changes since if I don't have to touch it, I usually don't.

---

Ok i looked at the source code of the error page. The error occurs while the page is trying to load the portal logo, it looks like there is a problem with your portal logo. Please make sure that your portal logo is correctly setup.

If it still doesnt work try comment out the code from the file, by opening up the ErrorPage.aspx.cs in the dnn root folder

and change ...


to

Okay thanks. Now, before I go commenting out any source code, what should I check on the portal logo file to ensure that it is set up correctly? And what does that bit of source code do anyway that you told me to comment out? And if I comment it out, how then will DNN behave

---

Okay thanks. Now, before I go commenting out any source code, what should I check on the portal logo file to ensure that it is set up correctly? And what does that bit of source code do anyway that you told me to comment out? And if I comment it out, how then will DNN behave

Please take a look at the Portal Settings if the logo is setup correctly. The source code, on the error page should display the logo on the error page which currently doesn't work an throws the error message. If you comment out the code there will be no logo displayed at the error Page.

You can directly open the error page to see the error... yourwebsite.com/ErrorPage.aspx

Nice! It worked when I commented out that line in ErrorPage.aspx.CS. No wonder you point out that I had a problem with my portal logo; I don't think I have one. I looked in the path for portal 0, and all I see are three folders; cache, templates, and users, two of which, are empty. Very odd; but what can I say, I'm as new as they come to DNN and to coding; just learning C#. I had to change the max request length attribute in web.config to 10192 and the max disk threshold to 108192 respectively, but after a bit, the installer worked just fine and now things are working as expected. We'll see what happens as time goes on and I actually get a forum configured.

---

I also experienced this error with DNN 6.0 and a skin from Artisteer 4. In my case, the error was caused by a background image that was too large. I reduced the size of the background image (using a much higher jpg compression) and this solved the problem.