I am having a similar problem.
All I did was backup and restore a DNN Instance, checking my process many times to make sure that it was done correctly, and DNN would not run giving me this error:
Exception Details: System.IO.FileNotFoundException: Could not find file 'c:\DotNetNuke.config'.
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:
[FileNotFoundException: Could not find file 'c:\DotNetNuke.config'.]
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +328
System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) +1038
System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) +114
DotNetNuke.HttpModules.Compression.RequestFilter.RequestFilterSettings.GetSettings() +265
DotNetNuke.HttpModules.Compression.RequestFilter.HttpModule.FilterRequest(Object sender, EventArgs e) +279
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +157
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +65
|
Out of despiration, I added DotNetNuke.config to the c:\ directory, now I get the error you posted above.
Some sites have led to the possibility that the .NET Framework 2.0 SP1 is the cause:
http://blogs.msdn.com/jpsanders/archive/2007/12/18/system-argumentexception-absolute-path-information-is-required.aspx
Some other clues might be here:
http://weblogs.asp.net/lancea/archive/2004/05/28/143645.aspx
The curious thing is that the original site runs just fine - i duplicated it (but using a different IP address and a copy of the database) so that I could test an upgrade from DNN 4.5.5 to DNN 4.8.2 - it's DNN 4.5.5 that broke even without the upgrade. I attempted to overwrite DNN files with the 4.8.2 upgrade with no resolution.
It is worth mentioning that this installation of DotNetNuke has been upgraded numerous times, it's origional version would have been whatever the latest was in Dec 2006. I have two dozen other DotNetNuke websites and have never encountered this problem before.
I found a thread with my original error, that led me to no solution. That thread is here: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/postid/223816/scope/posts/Default.aspx
I have tried to check Gemini, but it seems that Support.DotNetNuke.com is currently down...
Please post back if you have resolved your issue or if you have any ideas!
-Matt