Saturday, March 31, 2012
strange 404 error
Thanks in advance,
Sean Nolan
----------------
Message:
C:\Inetpub\wwwroot\ExpenseWatchApp\TE\ExpenseWatch _files\TEPrintFrame.aspx
Source:
System.Web
Stack Trace:
at System.Web.UI.TemplateParser.GetParserCacheItem()
at System.Web.UI.TemplateControlParser.CompileAndGetP arserCacheItem(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.TemplateControlParser.GetCompiledIns tance(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.PageParser.GetCompiledPageInstanceIn ternal(String virtualPath, String inputFile, HttpContext context)
at System.Web.UI.PageHandlerFactory.GetHandler(HttpCo ntext context, String requestType, String url, String path)
at System.Web.HttpApplication.MapHttpHandler(HttpCont ext context, String requestType, String path, String pathTranslated, Boolean useAppConfig)Probably a hacker, probing for a specific vulnerability in some commercial
product called "ExpenseWatch".
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Sean Nolan" <snolan@.harriton.com> wrote in message
news:#bm2B0##DHA.2520@.TK2MSFTNGP11.phx.gbl...
I'm wondering if anyone has encountered something similar to the error I've
pasted below. We get similar errors when someone hits a bad link etc., but
the part I can't figure out here is where the string "ExpenseWatch_files"
come from. The page TEPrintFrame.aspx resides in the TE folder. There is no
intermediate directory and the string "ExpenseWatch_files" does not exist
anywhere in our code. Also, I'm pretty sure that the user never knows that
an error occurred even though it is trapped and reported.
Thanks in advance,
Sean Nolan
----------------
Message:
C:\Inetpub\wwwroot\ExpenseWatchApp\TE\ExpenseWatch _files\TEPrintFrame.aspx
Source:
System.Web
Stack Trace:
at System.Web.UI.TemplateParser.GetParserCacheItem()
at System.Web.UI.TemplateControlParser.CompileAndGetP arserCacheItem(String
virtualPath, String inputFile, HttpContext context)
at System.Web.UI.TemplateControlParser.GetCompiledIns tance(String
virtualPath, String inputFile, HttpContext context)
at System.Web.UI.PageParser.GetCompiledPageInstanceIn ternal(String
virtualPath, String inputFile, HttpContext context)
at System.Web.UI.PageHandlerFactory.GetHandler(HttpCo ntext context, String
requestType, String url, String path)
at System.Web.HttpApplication.MapHttpHandler(HttpCont ext context, String
requestType, String path, String pathTranslated, Boolean useAppConfig)
Tuesday, March 13, 2012
Strange problem submit button not working
I have encountered a strange problem with an asp.net application. I have the
same code deployed on staging and production. On clicking the submit button
the app is supposed to send an email.
This works fine on staging environment for both Netscape and IE.
But on production (it has multiple servers) for some reason it fails in IE
but works in Netscape. So if I now click on submit nothing happens on
production.
Both the environments have the same code. Has anyone ever encountered this.
Not sure if this is the correct place for such a problem, if any one knows a
more suitable group please let me know.
Really puzzled here..any help will be really appreciated.
Thanks!Are using Validation? Are you familiar with the bug in Service Pack 1
for .NET v1.1 ? There's an issue with a WebUIValidation.js file. Could
the production server have intalled this SP1? An interesting page
pertaining to this is here and mention of a fix.
http://weblogs.asp.net/pwilson/arch.../16/230591.aspx
On Tue, 12 Oct 2004 11:33:06 -0700, "jbhan"
<jbhan@.discussions.microsoft.com> wrote:
>Hi,
>I have encountered a strange problem with an asp.net application. I have th
e
>same code deployed on staging and production. On clicking the submit button
>the app is supposed to send an email.
>This works fine on staging environment for both Netscape and IE.
>But on production (it has multiple servers) for some reason it fails in IE
>but works in Netscape. So if I now click on submit nothing happens on
>production.
>Both the environments have the same code. Has anyone ever encountered this.
>Not sure if this is the correct place for such a problem, if any one knows
a
>more suitable group please let me know.
>Really puzzled here..any help will be really appreciated.
>Thanks!
Thanks for the reply. I did come across this but when I inquired about the O
S
and service pack on the production server, they said it was Windows 2000
Service Pack 4 and thats for both the staging and production. They also
mentioned that they have not applied any other update or service pack.
I am thinking maybe the best option is not to use the validators at all?
They just cause problems all the time!
Any ideas?
Thanks,
jbhan
"JuLiE Dxer" wrote:
> Are using Validation? Are you familiar with the bug in Service Pack 1
> for .NET v1.1 ? There's an issue with a WebUIValidation.js file. Could
> the production server have intalled this SP1? An interesting page
> pertaining to this is here and mention of a fix.
>
> http://weblogs.asp.net/pwilson/arch.../16/230591.aspx
>
> On Tue, 12 Oct 2004 11:33:06 -0700, "jbhan"
> <jbhan@.discussions.microsoft.com> wrote:
>
>
Strange problem submit button not working
I have encountered a strange problem with an asp.net application. I have the
same code deployed on staging and production. On clicking the submit button
the app is supposed to send an email.
This works fine on staging environment for both netscape and IE.
But on production (it has multiple servers) for some reason it fails in IE
but works in Netscape. So if I now click on submit nothing happens on
production.
Both the environments have the same code. Has anyone ever encountered this.
Not sure if this is the correct place for such a problem, if any one knows a
more suitable group please let me know.
Really puzzled here..any help will be really appreciated.
Thanks!Are using Validation? Are you familiar with the bug in Service Pack 1
for .NET v1.1 ? There's an issue with a WebUIValidation.js file. Could
the production server have intalled this SP1? An interesting page
pertaining to this is here and mention of a fix.
http://weblogs.asp.net/pwilson/arch.../16/230591.aspx
On Tue, 12 Oct 2004 11:33:06 -0700, "jbhan"
<jbhan@.discussions.microsoft.com> wrote:
>Hi,
>I have encountered a strange problem with an asp.net application. I have the
>same code deployed on staging and production. On clicking the submit button
>the app is supposed to send an email.
>This works fine on staging environment for both netscape and IE.
>But on production (it has multiple servers) for some reason it fails in IE
>but works in Netscape. So if I now click on submit nothing happens on
>production.
>Both the environments have the same code. Has anyone ever encountered this.
>Not sure if this is the correct place for such a problem, if any one knows a
>more suitable group please let me know.
>Really puzzled here..any help will be really appreciated.
>Thanks!
Thanks for the reply. I did come across this but when I inquired about the OS
and service pack on the production server, they said it was Windows 2000
Service Pack 4 and thats for both the staging and production. They also
mentioned that they have not applied any other update or service pack.
I am thinking maybe the best option is not to use the validators at all?
They just cause problems all the time!
Any ideas?
Thanks,
jbhan
"JuLiE Dxer" wrote:
> Are using Validation? Are you familiar with the bug in Service Pack 1
> for .NET v1.1 ? There's an issue with a WebUIValidation.js file. Could
> the production server have intalled this SP1? An interesting page
> pertaining to this is here and mention of a fix.
>
> http://weblogs.asp.net/pwilson/arch.../16/230591.aspx
>
> On Tue, 12 Oct 2004 11:33:06 -0700, "jbhan"
> <jbhan@.discussions.microsoft.com> wrote:
> >Hi,
> >I have encountered a strange problem with an asp.net application. I have the
> >same code deployed on staging and production. On clicking the submit button
> >the app is supposed to send an email.
> >This works fine on staging environment for both netscape and IE.
> >But on production (it has multiple servers) for some reason it fails in IE
> >but works in Netscape. So if I now click on submit nothing happens on
> >production.
> >Both the environments have the same code. Has anyone ever encountered this.
> >Not sure if this is the correct place for such a problem, if any one knows a
> >more suitable group please let me know.
> >Really puzzled here..any help will be really appreciated.
> >Thanks!
>