REPOST Deploying project - **** VERY URGENT HELP ****

  • Thread starter Thread starter J
  • Start date Start date
J

J

I've changed the settings on my server, and now I'm still getting the same
'screen', put the error message now says...


Server Error in '/VN' Application.
----------------------------------------------------------------------------
----

Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>



Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>



Can someone answer the following questions...

Does the ASAPI filters need to have the 1.1 framework installed, and if so,
how do I change the priority from high to low.

Does FrontPage Server extensions need to be installed, again should this be
in the asapi filters? I've been told I only need FPSE if I'm copying my
project from the NET.IDE to the server.

What about the asp account? Does this need access to the directory? If so,
which one, the virtual directory, or the physical file directory.
 
J,

I would start by doing what the error message says. Set the web.config file
so you can see the actual error. Then you'll know what's wrong.

Sincerely,

--
S. Justin Gengo, MCP
Web Developer

Free code library at:
www.aboutfortunate.com

"Out of chaos comes order."
Nietzche
 
I have now resolved the error. The user "ASPNET" did not have any
permissions to the directories.

As I'm sure you may appreciate, the answer you gave would would have been NO
HELP whatsoever.

However, my thanks for the response.
 
You ungratefull amateur !
Hope nobody gives you advice again !

Justin was just trying to help out !
Don't criticize others if you don't even know what the problem is !
 
Certinaly not ungrateful NOR am I an amateur (17 years experience with the
second biggest building company in the world proves that).

If you and Justin had read the error message, you would have noted that it
gave NO indication whatsoever regarding the problem. Justin mentioned to
see the web.config file to see what the problem was. I did, it didn't help.
The error message was specifically telling me to change the custom errors to
"Off", of which it was, and it still didn't work.

I ALSO asked a series of questions, of which the cure to the problem was
actually in one of those questions.

Justins reponse was similar to someone asking where the lightswitch is in a
darkened room! How on earth can one see the lightswitch, or be told where
it is, if the room has no sense of direction to navigate!

Finally, you're own personal attitude of "hope nobody gives you advice
again" is, ahem, amateurish. I would imagine you are the kind of person
that throws a tantrum over the slightest criticism. I did, afterall, thank
Justin for his help, I did say it was no help (honesty obviously doesn't pay
again!!!), perhaps the tone was harsh, of which I apologise. Your own tone
however, is unexcusable.

Finally, I suggest you spend your time 'helpng' others, rather than
hindering or indeed trying to cause an argument that really is just a waste
of time!
 
Back
Top