I have a simple ASP net web form that consists of two textboxes one single line and one multiline in addition to a fileupload control and a button.
the page works perfect and the button triggers the post back as usual. But when I copy and paste text from "Web pages" in particular and paste them in the multiline textbox the post back is never triggered, sometimes I get time out error, sometimes I get bad request!!!
This behavior is generated only in IIS, it is not observed in IIS express.
The text is not that long, it is about 30 lines or less, but I noticed that when deleting some lines of text the issue is resolved and no errors is generated, but I can't find anything special in those lines that are deleted, no control characters or any other special characters.
Any idea? has someone encounter this same situation?
That is strange problem, never had experienced it but i think it can be a problem related to browser cache or browser compatibility issue. Make sure you have declared right version of browser in your HTML code. Also, try to debug the problem by placing the breakpoint and see it runs every time or not.
Related
I have the problem that I cannot use the ScriptManager in my ASP.NET Web Forms (4.5) anymore. It always throws the following critical JavaScript error messages (SCRIPT1002 is telling a syntax error) in Internet Explorer 11:
I tried to solve the problem with https://pavanarya.wordpress.com/2011/page/11/ and found out that WebForms.js shall cause the problem regarding to the decrypted WebResource.axd URL of the first error message (see above).
Furthermore, I found out that the error vanishes if I remove the line
from my Layout.Master file. All error messages vanish, but AJAX elements like TreeView (I also use UpdatePanel and Calendar) do not work anymore then, too.
I also tried the Script Resource Viewer from http://www.dotneti18n.com/Downloads.aspx via
http://www.guysmithferrier.com/post/2007/07/Script-Resource-Viewer.aspx. But the funny thing is that even the Script Resource Viewer implements the line
which exactly causes the same error as before, and so it is not a real help for me.
It must be some global problem in the whole project since it does not accepts any ScriptManager (no matter in which ASPX file) anymore. Does someone know that problem?
Many thanks in advance!!!
Remark: The Firefox Browser does not throw an error message, but it does not show the TreeView correctly, too. All images (ImageSet) of the TreeView are missing and the Web Browser displays text instead of the images. I also use a Chart (System.Web.DataVisualization) in the Web project, it was the last item which was added there. I use C#.
I am unable to put this as comment. So I will put it as Answer:
Use ToolScriptManager instead of ScriptManager.
I am working on a ASP page having search option. After getting search result, wherever i click on any link which calls javascript function, I am getting an error as 'object expected'. (All search result is displayed on single page only and this happens only on large result). When i enabled javascript debugging, it allows me to debug this error scenario in Visual studio. Here What i found is, the ASP page gets loaded is incomplete(clipped inbetween). So the javascript function which gets called is not in this perticular frame as it is written after body tag.
So my question is, Is there any page size limitation for processing ASP or HTML.
(I am using IE browser). Please let me know any more infor needed.
Thanks.
Not sure page size has anything to do with your problem. However if you are using a grid control set EnableViewState="false" this will reduce your page size considerably and speed up any postbacks you may be doing.
I having an issue with the ASP.NET Treeview control. I create the treeview just fine but the nodes will not expand or collapse. I see there is a javascript error but it is for line 1 character 0 of the webpage, there is nothing at line 1 character 0.
I am using the ASP:Treeview control in conjunction with the Telerik controls, but I'm not sure if that is an issue.
I saw there was a similar question here but the answer is not pertinent to my site. Has anyone run into this issue before? I've tried searching Google and tried a number of proposed solutions but so far none have worked.
Thank you,
Normally with problems like this it is best to isolate the code which is causing the problem. For example, create a minimal page with no other controls or external JavaScript and see if the problem persists.
It's also useful to use a decent debugger. The latest IE8 actually has a very good Visual Studio-style JavaScript debugger built in - go to your page, hit F12 and the go to the Script tab and click 'Start Debugging' and see where that leads you.
I've seen unhelpful javascript errors when a page does an AJAX postback, an exception occurs on the server, and the client javascript is unable to handle what the server returns. You could ascertain if this is happening by debugging the site, putting a breakpoint on the Page_Load method (or something similar), and see if it gets hit when trying to collapse or expand the TreeView.
We have an ASP.NET application that we recently migrated onto a new server with IIS7 and .NET 3.5.
In this new environment, some users that are on IE (6, 7, or 8) are experiencing bizarre intermittent problems with postback not working on ASP.NET buttons. (you click the button and nothing happens)
The issue happens sporadically. Sometimes it works, sometimes it doesn't. For some users the button postback almost never works (but sometimes yes!). To complicate matters there are some pages with asp.net button postbacks that DO always work.
Other pages contain a mix of 'asp buttons' and 'asp link buttons', in which the asp button postbacks often don't work, but the link button postbacks always work.
Javascript is enabled and works. The source DOES contain valid tags.
I actually managed to take View Source snapshots of the same page when it was working and when it was not working and the source was EXACTLY the same!!!
At first I thought it was a problem with IE6, but it's now been reproduced on IE7 on one user's machine.
How would I even BEGIN to tackle this problem?
Any help, ideas, or guidance would be vastly appreciated. I am at the end of my mental rope here.
I know this topic is pretty old, but I found the same problem in my code.
I am using the ComponentArt component library.
In certain circumstances after a postback, buttons with codebehind will no longer execute in IE. I also noticed that buttons with onClientSide clicks would execute their postback when the JS function completes and returns true.
I was able to get all the buttons on the page to submit by adding the following code to my buttons:
OnClientClick="javascript:return true"
Any buttons that are already running a JS function and returning true, should work without issue.
See if this post helps? IE 6 treats buttons a little differently, especially if you have some name conflicts. I could see this being a problem for events if that is the case.
Found the culprit.
It was ComponentArt's 2007 Web.UI components that were being dropped on the page.
Apparently the menu control mixed with the 3.5 framework causes wierd issues with postback not working.
I have an asp.net page with a gridview and a couple of input text boxes and a search button.
Once I put something on both text boxes and press search, I get a result list (gridview) from a MS SQLExpress 2008 database.
Everything runs great BUT for some unknown reason the search stops working every now and then.
I type values on the two text boxes and press Search.
Instead of getting a result like always, the text on the text boxes dissapear, on the bottom says status "Done" but in fact is not displaying anything.
it gives no errors at all...it just runs...but doesn't display any data.
I have tried used several other Pc's as clients, same problem.
I have closed and restarted IE/Firefox but does't fix it.
Turning off-on the web server's pc fixes it sometimes, but of course I don't want to be doing that every 30 minutes
Any comments/ideas are appreciated
Sounds like it's giving you a redirect to GET. My guess is you're set to use Forms Authentication, and it's timing out. Try increasing the timeout, or removing authentication.
You could use Fiddler to verify that it's redirecting you.