I admit to being unfamiliar with ASP, but I desperately need a product like this. I put it on my website, and get a runtime error message that suggests that I turn customErrors mode to "off" to see more info. Well, it IT oss, and I still get that error, with no clue as to what might be wrong. Can someone help me? BTW, the URL where I put it is http://www.chandler-enterprises.net/test/SQL/default.asp
thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-19
Our site is hosted by Cosmotek.net, and their info page says that we have .Net.
I just verified that web.config file in the test/SQL directory says CustomErrors is off. I did it just like the error page suggests, inside configuration and system.web tags.
Still lost,
Carol
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In order to get the project to work in the directory structure that you have, you are going to have to move the "web.config" file and the "bin" directory from the test/SQL directory to the root directory of the website.
There are some issues with version 0.1.3 with connections not being closed on the SQL Server (The Data Class is a bust) that I have resolved in the code that I am going to release soon. The new code can be downloaded at http://new.aspenterprisemanager.com/SourceCode.zip
To run that code, the "bin" directory, "web.config" file and the "global.asax" file will have to be in the root directory of your website.
When I set up the project in the /test/SQL directory I had several errors too. If this doesn't work we'll try something else.....let me know
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-19
I'm one step further now. The default page loaded, but when I clicked "click here to launch application", I got the same error page that says to tuen custom error off.
I moved those two files and the bin directory to the root of our site, and verified that.
I really appreciate your help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The next thing I would try is to make sure that there is not a "web.config" file in either the test directory or the SQL Directory. If you only have the "web.config" file in the root directory, and it still does not work. THere may be some issues with the server configuration and a bare-bones configuration might help.
Erase everything in the "web.config" file and try replacing the current text with the following:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-19
Aha, we're getting somewhere! Getting rid of the other web.config file did the trick. Now I'm getting an informative error about permissions. I added read-write-browse-execute to all those directories and verified that Default.aspx is there, and am still getting the error. Here's the trace:
Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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.Web.HttpException: Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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.
DId you try the second part and make the "web.config" file with the text from the previous post. I can't access any of the .Net files in the project from your site, so I would imagine that it has something to do with the debugging option in "web.config".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-19
Yes, I did that too. Sorry I didn't say so. I really appreciate you helping me so much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-19
Okay, tried that, I don't think it helped. Here's the whole error message again:
Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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.Web.HttpException: Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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.
Well, that didn't give more detailed error than before. I have never seen this problem before. I would have to think that it is something with the configuration of the .Net Framework on the server. The error is caused by System.Web.Caching.CacheDependency and System.Web.FileChangesMonitor which are not used explicitely in the project.
I would email tech support for your host and see if they have encountered this in any other situation, and make sure that they do not have special directories set-up for .Net.
I have a friend in Georgia that is going to take a look at it and see if he has any idea what the problem might be.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-19
I'll email tech support. thank you very much for all of your time and help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Let me know if you find out what this is so that I will know if I ever encounter it again.
I would greatly appreciate it!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-22
Tech support said, "Your web.config file was not properly configured. I replaced it with a generic web.config file, and your site now works. I renamed the old
config file web.config.old2 (since there was already one called
web.config.old). I''m not too experienced with the web.config file, but
it appears as though the add application line was causing the
problem.
It really does work now. Thank so very much for all your time and help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I admit to being unfamiliar with ASP, but I desperately need a product like this. I put it on my website, and get a runtime error message that suggests that I turn customErrors mode to "off" to see more info. Well, it IT oss, and I still get that error, with no clue as to what might be wrong. Can someone help me? BTW, the URL where I put it is http://www.chandler-enterprises.net/test/SQL/default.asp
thanks!
Make sure that you modify the web.config file in the test/SQL directory to set the CustomErrors to "Off"; the latest code that I am working on is set to "RemoteOnly". Also, this is ASP.NET, so you will need the .Net Framework installed ( http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true ).
Our site is hosted by Cosmotek.net, and their info page says that we have .Net.
I just verified that web.config file in the test/SQL directory says CustomErrors is off. I did it just like the error page suggests, inside configuration and system.web tags.
Still lost,
Carol
In order to get the project to work in the directory structure that you have, you are going to have to move the "web.config" file and the "bin" directory from the test/SQL directory to the root directory of the website.
There are some issues with version 0.1.3 with connections not being closed on the SQL Server (The Data Class is a bust) that I have resolved in the code that I am going to release soon. The new code can be downloaded at http://new.aspenterprisemanager.com/SourceCode.zip
To run that code, the "bin" directory, "web.config" file and the "global.asax" file will have to be in the root directory of your website.
When I set up the project in the /test/SQL directory I had several errors too. If this doesn't work we'll try something else.....let me know
I'm one step further now. The default page loaded, but when I clicked "click here to launch application", I got the same error page that says to tuen custom error off.
I moved those two files and the bin directory to the root of our site, and verified that.
I really appreciate your help!
The next thing I would try is to make sure that there is not a "web.config" file in either the test directory or the SQL Directory. If you only have the "web.config" file in the root directory, and it still does not work. THere may be some issues with the server configuration and a bare-bones configuration might help.
Erase everything in the "web.config" file and try replacing the current text with the following:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<compilation defaultLanguage="vb" debug="false">
<assemblies>
<add assembly="*"/>
</assemblies>
</compilation>
<customErrors mode="Off" />
</system.web>
</configuration>
Aha, we're getting somewhere! Getting rid of the other web.config file did the trick. Now I'm getting an informative error about permissions. I added read-write-browse-execute to all those directories and verified that Default.aspx is there, and am still getting the error. Here's the trace:
Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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.Web.HttpException: Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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:
[HttpException (0x80004005): Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.]
System.Web.FileChangesMonitor.StartMonitoringFile(String fileName, FileChangeEventHandler callback) +184
System.Web.Caching.CacheDependency.Init(String[] filenames, String[] cachekeys, CacheDependency dependency, DateTime start) +1478
System.Web.Caching.CacheDependency..ctor(String filename, DateTime start) +75
System.Web.Caching.CacheDependency..ctor(String filename) +50
System.Web.Security.FileAuthorizationModule.OnEnter(Object source, EventArgs eventArgs) +413
System.Web.SyncEventExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87
Thanks some more!
--------------------------------------------------------------------------------
DId you try the second part and make the "web.config" file with the text from the previous post. I can't access any of the .Net files in the project from your site, so I would imagine that it has something to do with the debugging option in "web.config".
Yes, I did that too. Sorry I didn't say so. I really appreciate you helping me so much.
In the "web.config" file, try changing the line
<compilation defaultLanguage="vb" debug="false">
to:
<compilation defaultLanguage="vb" debugmode="true">
and let's see if you get more detailed error messages.
That should be "debug" instead of "debugmode"
Okay, tried that, I don't think it helped. Here's the whole error message again:
Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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.Web.HttpException: Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.
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:
[HttpException (0x80004005): Access denied to 'D:\Inetpub\virtual_servers\chandler-enterprises.net\web\test\SQL\app\Default.aspx'. Failed to start monitoring file changes.]
System.Web.FileChangesMonitor.StartMonitoringFile(String fileName, FileChangeEventHandler callback) +184
System.Web.Caching.CacheDependency.Init(String[] filenames, String[] cachekeys, CacheDependency dependency, DateTime start) +1478
System.Web.Caching.CacheDependency..ctor(String filename, DateTime start) +75
System.Web.Caching.CacheDependency..ctor(String filename) +50
System.Web.Security.FileAuthorizationModule.OnEnter(Object source, EventArgs eventArgs) +413
System.Web.SyncEventExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87
Well, that didn't give more detailed error than before. I have never seen this problem before. I would have to think that it is something with the configuration of the .Net Framework on the server. The error is caused by System.Web.Caching.CacheDependency and System.Web.FileChangesMonitor which are not used explicitely in the project.
I would email tech support for your host and see if they have encountered this in any other situation, and make sure that they do not have special directories set-up for .Net.
I have a friend in Georgia that is going to take a look at it and see if he has any idea what the problem might be.
I'll email tech support. thank you very much for all of your time and help!
Let me know if you find out what this is so that I will know if I ever encounter it again.
I would greatly appreciate it!
Tech support said, "Your web.config file was not properly configured. I replaced it with a generic web.config file, and your site now works. I renamed the old
config file web.config.old2 (since there was already one called
web.config.old). I''m not too experienced with the web.config file, but
it appears as though the add application line was causing the
problem.
It really does work now. Thank so very much for all your time and help!
Will you post the text for the web.config file so that I can see what was causing the problem incase I run into this with anyone else.
Glad you got it to work, and thanks for your help.
Problem file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<compilation defaultLanguage="vb" debug="true">
<assemblies>
<add assembly="*"/>
</assemblies>
</compilation>
<customErrors mode="Off" />
</system.web>
</configuration>
Good file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<identity impersonate="false" />
<compilation defaultLanguage="vb" debug="true" />
<customErrors mode="RemoteOnly" />
<authorization>
<allow users="*" /> <!-- Allow all users -->
</authorization>
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" />
<globalization requestEncoding="utf-8" responseEncoding="utf-8" />
</system.web>
</configuration>