I have reportviewer control for manipulating with rdlc reports. Now everything works fine when i run application on localhost. Problem is when I run application from server, print button doesn't do anything. It acting like there is no any functionality for it.
Also to mention this is problem when i use IE browser(IE 9).
Does any one know why is this happening and how to solve this problem?
For any more info about problem leave a comment, please.
Ok I solved it, problem actually was with some IE add on. So if anyone else got the same problem you can try this.
Related
Whenever I try visiting an aspx file in Chrome, the browser will download the file. When I open it in IE, it will actually render that page. I'm not sure what changed with Chrome as this was working, then half way through the day decided to stop working.
I've tried following aspnet_regiis -i with no success. Other aspx pages render without issue. I've been poking around IIS trying to find something that might indicate an incorrect setting, but cannot find anything in particular.
I've done plenty of Googling without any helpful results.
I'm not sure what other information to provide at this time, so please let me know if I can provide any specific information to help.
As said here: https://www.concrete5.org/index.php?cID=750921 when I try and save any text with redactor, I get the index page's mark-up as the error message.
Someone suggested that this could be an ajax error however I really have no idea. There is no error log produced and I am at a loss as to what is actually causing this to happen.
The strange thing is I can leave the content block empty and it will save fine but when I type anything into the box and hit save it throws an error.
The site has been working for the last 3 months without issue so I'm not sure why it has suddenly stopped working.
If anyone could help, this problem is driving me and my client nuts.
Edit:
On further testing this problem is localized to the server which is running the website because it works absolutely fine on my local version of the website. It also seems to not only affect redactor but also any form.
Updating to 5.7.4.2 solved my problem.
Thanks to #pc-shooter for the suggestion!
I am working on an asp.net page that contains a fileupload server control (not async fileupload).
I recently noticed that whenever that control is on the page and any postback occurs, the page crashes and stops executing..giving me strange and broken data like in the screenshot attached!!
I also noticed that is happening in any webkit based browser (e.g safari, chrome, etc..)
Strangely, the problem is only occurring when am running this page online, but when am debugging it locally, this problem doesn't occur!!
Any ideas??
Note: The following link [ http://i.stack.imgur.com/lpe24.png ] is a screen of how the crash looks like, and i remember something now, i used to get this screen sometimes while am browsing through google.com or images.google.com !! hope this helps :S
Turns out this whole problem was caused by the compression module referenced in the web.config file.
As a permanent solution however, I changed all FileUpload controls to AsyncFileUpload, gaining both a solution and an easier way to navigate and work.
Thanks everyone ;)
I have a Dojo EnhancedGrid connected to a JsonRestStore. clearOnClose is set to true on the store. Usually I refresh it by doing
grid.store.close();
grid.setStore(window.store.tester);
Or
grid._refresh();
This works fine in every browser, but not in the newest version of FF9 (in version 4,5 it worked well).
In FF9, nothing happens at all and the store is not cleared or refreshed. Oddly, it does work after trying a few times and debugging it. But when I clear the browser history and cache and then try to refresh, it never works.
Does anyone have a clue what happens? What could be different in FF9 and is there another way to definately refresh the grid?
Are You using Firebug. If yes, then try switching it off and reloading the page. Dojo grids don't get along very well with Firebug.
Thanks for the suggestion. I found the reason now, it was some screwed hashtag logic which caused the grid to be refreshed twice at a time in Firefox. I corrected it and now it works.
I have a weird issue. I am opening a popup window in IE6 with SSL enabled on the server.
When the following executes it seems to lock the browser up. I know this is vague. This is the JScript that appears to be the problem. Gotta love your IE6!
function PopoffWindow(url) {
var features = "height=400,width=550,top=60,left=100,"
+ "toolbar=no,location=no,menubar=no,status=no,"
+ "scrollbars=yes,resizable=yes";
var win = window.open(url, "DSRocks", features);
win.focus();
return win;
}
This is not a problem in IE7 or Firefox. And the problem seems to be isolated to this server (with SSL). Anyone have any insight on this?
Thanks,
Nick
Is it possible that the window.open call does not return quickly enough to allow you to perform a .focus() on it, in the next line?
What happens if you throw an alert() between those two lines?
have you tried assign the window a name? IE6 sometimes does funny things when you open an unnamed window. just add a "windowName", before the url
With a problem like this, it is usually best to get back to basics. A few things to check:
How are you testing IE6? Are you using the Microsoft Internet Explorer Application Compatibility VPC Image or some workstation install where you've managed to get IE6 and IE7 working on the same PC? Having both IE6 and IE7 on the same PC may appear to work, but lead to issues like you are seeing. Even if you are using an existing VPC Image, you may want to download (or extract from an existing download) a fresh copy and see if it happens on that copy of IE6.
Have you cleared the Temporary Internet Files, Cookies and History of the IE6 install? I know it sounds obvious and stupid, but perhaps a resource that is being loaded in the PopUp window is corrupt in cache, causing the problem.
Have you disabled every Add-on in IE6?
I think the first thing to determine is whether the problem is with every copy of IE6, or just your copy of IE6 (covered by the first bullet point).
Grant,
Thanks. But the problem is with all IE6 instances that are viewing the hosted site. I will try to add an alert before the focus() to see if this is the issue. As for the windowname.. that is the second parameter I am passing, "DSRocks".
The problem was with a JSON webservice call. Please see this link for details:
http://codeclimber.net.nz/archive/2006/12/22/How-to-enable-an-ASP.NET-WebService-to-listen-to-HTTP.aspx