Value cannot be null. Parameter name: path2 error message
Tony T
server running w2k and IIS5
It installed ok, but even if I try and run the simplest of aspx applications
I get an error message....
Server Error in '/' Application.
----------------------------------------------------------------------------
----
Value cannot be null. Parameter name: path2
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: path2
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: Value cannot be null.
Parameter name: path2]
System.IO.Path.Combine(String path1, String path2) +419
System.Web.FilePathParse..ctor(String path, Boolean isFile, Boolean
getShortNames) +366
System.Web.FileChangesMonitor.StartMonitoringDirectoryRenamesAndBinDirectory
(String dir, FileChangeEventHandler callback) +46
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +324
[HttpException (0x80004005): ASP.NET Initialization Error]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +927
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +128
----------------------------------------------------------------------------
----
Version Information: Microsoft .NET Framework Version:1.0.3705.0; ASP.NET
Version:1.0.3705.0
Bret Bentzinger
This could be a permissions issue on the new server. To verify that,
add the ASPNET User account to the Admin group. Does it work? If so,
then we have verified it is Permissions. You could also use
regmon/filemon from http://www.sysinternals.com to look at this as well.
If it is permissions, then you need to configure the new server to allow
the access that your ASPNET Application needs.
What type of IIS Security are you using?
By default the ASPNET worker process will run as the ASPNET User. So this
user needs rights to access the files, registry keys etc...
If you want to use impersonation you can add the following to your
web.config file:
<identity impersonate="true">
Then, all calls will be made with the IIS user accessing your ASPNET web
application instead of ASPNET User. For example, if you are using
anonymous security, then the IUSR_Machine account must have access to the
resources instead of ASPNET.
Hope this helps. Let me know if you have any questions.
This Posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. (C) 2001 Microsoft Corporation.
Allrights reserved.
Bret Bentzinger MCSD
Microsoft Developer Support
Chuck Grimes
> Hi Tony,
> This could be a permissions issue on the new server. To verify that,
> add the ASPNET User account to the Admin group. Does it work?
Hi Bret,
I have the same problem on a WIN2k/IIS5 setup, and adding the ASPNET
user to the Admin group resulted in no change in behavior. It seems to
me it's looking for some something that should be part of its
configuration, but isn't?
Any advice or recommendations?
Chuck Grimes
Advances.Com
Tony T
I tried changing the permissions as suggested but it made no difference.
I did however manage to resolve the problem by turning the directory
containing the aspx files into an 'application'
I don't know why this fixes the problem.
However, if I want to use aspx files in the root folder of my web site, I am
still faced with the same problem, and I cannot apply the work around
mentioned above because the root folder is an application by default.
any ideas?
Tony T.
"Chuck Grimes" <ch...@advances.com> wrote in message
news:cb8647e6.02022...@posting.google.com...
Bret Bentzinger
web .config file?
DId that work?