customErrors issues

  • Thread starter Thread starter Pete Davis
  • Start date Start date
P

Pete Davis

I posted a question about this earlier, but I thought I'd take a different
tack. Has anyone compiled a list of all the things that can cause setting
the customErrors mode to "Off" in the web.config file to fail to work?

I know that there's a bug that will cause it to happen if the application
directory is more than 8 characters.

It can also happen if there's a problem with the web.config file itself.

What are some of the other possibilities? If nobody has made a list, I'll be
happy to put one up on my site, because I've seen a lot of people struggle
with this issue through the history of this newsgroup.

Thanks.

Pete
 
No, I haven't.

I've been working with the hosting provider. I'm convinced it's something on
their side. I created a simple app. It has one webform with a button, and it
won't even come up without giving me the customErrors error, so I'm pretty
sure there's something on their side that's not kosher.

I'd love any ideas for what might be causing it, though.

Pete

--
http://www.petedavis.net
Alvin Bruney said:
Your post went unanswered. Have you resolved this issue?

--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
Pete Davis said:
I posted a question about this earlier, but I thought I'd take a different
tack. Has anyone compiled a list of all the things that can cause setting
the customErrors mode to "Off" in the web.config file to fail to work?

I know that there's a bug that will cause it to happen if the application
directory is more than 8 characters.

It can also happen if there's a problem with the web.config file itself.

What are some of the other possibilities? If nobody has made a list,
Click to expand...
I'll
Click to expand...
 
so to clarify, you have the webconfig file in your application directory,
and you know for a fact that it isn't being overridden by administrative
policy on the machine thru an administrative config file
and you know for a fact that it isn't being overridden in the machine.config
file right?

if you aren't sure of these answers please verify
--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
Pete Davis said:
No, I haven't.

I've been working with the hosting provider. I'm convinced it's something on
their side. I created a simple app. It has one webform with a button, and it
won't even come up without giving me the customErrors error, so I'm pretty
sure there's something on their side that's not kosher.

I'd love any ideas for what might be causing it, though.

Pete

--
http://www.petedavis.net
Alvin Bruney said:
Your post went unanswered. Have you resolved this issue?

--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
Pete Davis said:
I posted a question about this earlier, but I thought I'd take a different
tack. Has anyone compiled a list of all the things that can cause setting
the customErrors mode to "Off" in the web.config file to fail to work?

I know that there's a bug that will cause it to happen if the application
directory is more than 8 characters.

It can also happen if there's a problem with the web.config file itself.

What are some of the other possibilities? If nobody has made a list,
Click to expand...
I'll
be
happy to put one up on my site, because I've seen a lot of people struggle
with this issue through the history of this newsgroup.

Thanks.

Pete
Click to expand...
Click to expand...
Click to expand...
 
No,

I'm not sure of what's in the machine.config, to be honest.

Here's my situation. I've done the app for a small client here in Mexico.
The server is hosted by a guy who, frankly, I don't think really knows much
about ASP.NET. Unfortunately, I've got access to the machine only through a
control panel that's pretty weak on the control side.

My previous experience in deploying apps has been with larger hosting
services, so these issues have not come up.

What would be really helpful is to have a list of possible causes of this
problem that I can send to him so that we can find a solution and get my app
up and running.

Pete

--
http://www.petedavis.net
Alvin Bruney said:
so to clarify, you have the webconfig file in your application directory,
and you know for a fact that it isn't being overridden by administrative
policy on the machine thru an administrative config file
and you know for a fact that it isn't being overridden in the machine.config
file right?

if you aren't sure of these answers please verify
--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
Pete Davis said:
No, I haven't.

I've been working with the hosting provider. I'm convinced it's
Click to expand...
something
on
their side. I created a simple app. It has one webform with a button,
Click to expand...
and
it
won't even come up without giving me the customErrors error, so I'm pretty
sure there's something on their side that's not kosher.

I'd love any ideas for what might be causing it, though.

Pete

--
http://www.petedavis.net
Alvin Bruney said:
Your post went unanswered. Have you resolved this issue?

--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
I posted a question about this earlier, but I thought I'd take a different
tack. Has anyone compiled a list of all the things that can cause setting
the customErrors mode to "Off" in the web.config file to fail to work?

I know that there's a bug that will cause it to happen if the application
directory is more than 8 characters.

It can also happen if there's a problem with the web.config file itself.

What are some of the other possibilities? If nobody has made a list, I'll
be
happy to put one up on my site, because I've seen a lot of people struggle
with this issue through the history of this newsgroup.

Thanks.

Pete
Click to expand...
Click to expand...
Click to expand...
 
Problem solved. We switched providers. The original provider was simply
incompetent and didn't know how to configure an ASP.NET server. The guy is
definitely a unix guy.

Anyway, we switched to CrystalTech who I've used in the past and like a lot.
Their support has always been excellent for me and it took me about 2
minutes to get my app uploaded and running on their server :-)

Pete

--
http://www.petedavis.net
Alvin Bruney said:
so to clarify, you have the webconfig file in your application directory,
and you know for a fact that it isn't being overridden by administrative
policy on the machine thru an administrative config file
and you know for a fact that it isn't being overridden in the machine.config
file right?

if you aren't sure of these answers please verify
--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
Pete Davis said:
No, I haven't.

I've been working with the hosting provider. I'm convinced it's
Click to expand...
something
on
their side. I created a simple app. It has one webform with a button,
Click to expand...
and
it
won't even come up without giving me the customErrors error, so I'm pretty
sure there's something on their side that's not kosher.

I'd love any ideas for what might be causing it, though.

Pete

--
http://www.petedavis.net
Alvin Bruney said:
Your post went unanswered. Have you resolved this issue?

--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
I posted a question about this earlier, but I thought I'd take a different
tack. Has anyone compiled a list of all the things that can cause setting
the customErrors mode to "Off" in the web.config file to fail to work?

I know that there's a bug that will cause it to happen if the application
directory is more than 8 characters.

It can also happen if there's a problem with the web.config file itself.

What are some of the other possibilities? If nobody has made a list, I'll
be
happy to put one up on my site, because I've seen a lot of people struggle
with this issue through the history of this newsgroup.

Thanks.

Pete
Click to expand...
Click to expand...
Click to expand...
 
Back
Top