I am working on asp.net. I have developed one website and it is working fine. But there is one client's PC where the website is not working properly.
The main problem is with some of the AJAX controls. The two controls which are not working are Accordion Pane and Model Popup.
I saw the developer option of the browser and its states the following error/warning while I am visiting that page.
**InterYield Click Bind version 1.0-SNAPSHOT.4,685 20131123-0125 clickbinder.do?ver=1.0-SNAPSHOT.4%2C685:1
Uncaught SyntaxError: Unexpected token ILLEGAL xdm.html:8
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. init2.js:1
InterYield click bind handler had no ad coverage. nocoverage.do?callback=InterYieldNS.NoCoverage&product=iy&title=&matchedKeyword=&affiliate=adpeak2&…:6
Resource interpreted as Script but transferred with MIME type text/html: "http://telemetry.scorpionsaver.com/te.aspx?callback=jQuery18308800485304091…22%3A%22about+to+call+server%22%2C%22sampleRate%22%3A10%7D&_=1386416017076".
jquery.min.js:2
Uncaught SyntaxError: Unexpected token <**
The website is deployed on .net 2 framework. The client is using windows 8 operating system.
I have checked three browsers on clients pc. IE, Chrome and Firfox. but the problem exists on all 3 browsers.
I work with a couple of different websites that have users with a similar issue, where nothing loads past a certain point. The only thing similar with all the users is the InterYield Click Bind in their Console logging.
I had them run a Malware scanner (Malwarebytes Anti-Malware works best), and after it cleans the system, they are able to access the sites.
Hope this helps!
Related
I have an old application built with .NET Framework 2.0 hosted on a server with IIS 10. While using it, some (random) pages are not displayed properly (some scripts aren't executed), and when I check the console there is an error about some undefined function or variable inside a script tag. Apparently, a function call, a variable name, or sometimes a random 2-3 characters in the script are deleted. For example, below is the part where the name of the function gets changed in only one incident while using Chrome:
new searchandler ('sig_policy_EDITOR_sig_policy_323_EDITOR_Fransh'
whereas everywhere else it's alright:
new search_handler ('sig_policy_EDITOR_sig_policy_323_EDITOR_Fransh'
(notice the missing _h in search_handler).
There's another example, this time it happens on Firefox, but nowhere else:
fields : [{name:'Title',nocomplete: ue,readonly:true,searchmode:0}]
fields : [{name:'Title',nocomplete:true,readonly:true,searchmode:0}]
(notice the missing tr in nocomplete:true).
This doesn't happen on IE or when the app is started on different Servers. This only happens on the production server in Chrome and in Firefox. I've also checked what is served before going through IIS, there's no such problems, everything is fine until the pages are opened on a browser. Emptying the cache or sometimes reloading the page fixes the problem, but it gets really annoying when it happens frequently.
According to your description, I have seen similar problems to yours on stackoverflow, you can refer to the following threads：
Response body missing characters
Response from httpHandler is randomly missing characters on client
It is recommended that you can further diagnose based on network captures performed on the server browser and client browser.
I've been hired into a company that uses ASP.NET for all of their external and internal sites. I'm not too familiar with ASP.NET.
I'm currently working on a external site that runs perfectly in Internet Explorer.
When using the site on chrome, I have certain pages that give me the 404 - File or directory not found.
What can I do to help prevent this error code from showing up when using this site the chrome?
From your description, I understand that your site is a legacy site that is compatible with the IE browser but it is not working properly with modern browsers.
The 404 error information generally informs us that something is not found but if the site works fine in the IE browser then it could be possible that the issue is something else. In that case, this is too little information to predict the cause of the issue.
You may need to provide detailed information about which exact piece of code has the issue. Which version of the Asp.Net project and which kind of project(Web application, web API, etc.) it is. You may need to modify your code or project to make it work with modern browsers including Google Chrome.
At present, if you don't want to make any changes in your code then you could try to use the IE mode in the MS Edge browser to load your legacy site.
You could configure the IE mode manually or using the group policy.
To quickly check it, Launch the Edge browser. Paste edge://settings/defaultBrowser in the address bar and press the Enter key. Add your page to the Internet Explorer mode pages. Visit your site, it should load properly in the IE mode in the Edge browser.
Summary
Environment: Windows Server 2016, IIS 10, ASP.NET webforms site, Wildcard SSL/TLS Certificate, IIS URL Rewrite 2.1 (MS supported download)
Goal: a) Determine and resolve the root cause(s) of the issue, b) [preferred] Get the two failing features working without users having to change settings on their browser, c) get the two failing features working, period, without first-time-processing issues on ubiquitous browsers (Chrome, FF, Edge, IE, Safari, Opera).
Issue Summary: Two of the site features i.e. downloading files and displaying SSRS reports fail with a first-time-processing error or fail entirely, depending upon the browser, with the SSL certificate bound to the site. Subsequent attempts to execute these features within the same browser window succeed in most cases. Various browsers fail in different ways and some don't fail at all depending upon the browser in question. Please bear with me as I try to provide details below.
NOTE: Both features work fine without the SSL certificate in the mix.
I have scoured the Internet for a solution to no avail and would be very grateful for any assistance on this.
Details
I have a client with an ASP.NET Webforms site containing file download and SSRS report display features. Users must be logged in to access these features. Sadly, the original developers implemented a rudimentary, homegrown approach for authenticating users i.e. it's not a "formal" authentication framework but, rather just a simple comparison of the provided username/password pair to the values stored in the database ... no formal authentication tokens are set to my knowledge ... could this be part of the issue?
Both of the aforementioned features have been working flawlessly for years using all current, major browsers. My client recently purchased a wildcard SSL/TLS certificate which I installed on the production IIS instance and configured the appropriate site bindings. In case this matters, the site is also using URL Rewrite with a basic rule in the web.config to modify all HTTP protocol requests to the HTTPS protocol.
All aspects of the site work fine with the SSL certificate in place except file downloading and SSRS report displaying. Current versions of Chrome and Firefox [Windows], and Mac browsers (I don't have first-hand access to a Mac environment) are exhibiting errant behavior. IE 11 (go figure) appears to be the only browser with no issues whatsoever. I have not tested Edge as I don't have access to that browser version.
File Downloading
The site has a feature that allows logged in users to download files from the site.
Chrome
Chrome displays a first-time-processing error "Failed - Network error" shown in the download status bar at the bottom of the browser. Clicking the chevron in the error message and choosing the "Resume" option from the context menu completes the download but, any attempt to open (double-click) the zip archive from its actual folder location results in the following error message: "Windows cannot open the folder. The Compressed (zipped) Folder '{path}' is invalid." Analyzing the zip file in a hex editor reveals that it contains the web page source code and not the intended file download. Repeating the file download operation in the same browser window works fine (culminating in a successfully downloaded, valid zip archive of files) and all subsequent file download attempts also succeed with no further issues for the remainder of the life of that browser instance. If the user closes their browser (all Chrome instances must be closed) and then re-opens Chrome navigating to the site, the browser, again exhibits the first-time-processing error and then works fine from then on for the remainder of the life of that browser window.
NOTE: All instances of the Chrome browser must be closed to reproduce the issue a second time. If the user leaves even one Chrome instance open on their computer and then navigates to the site using a new browser window and retries the file download, there are no issues. Perhaps Chrome is caching some kind of an authentication token? I am intentionally shying away from using the term "session" as the behavior does not appear to be session related. Opening a new tab within Chrome (after experiencing the aforementioned first-time-processing behavior) and navigating to the site (which culminates in a new session) does not exhibit the issue.
Firefox
Firefox displays a "Secure Connection Failed" error message when trying to download files from the site. All subsequent attempts continue to fail. This differs from Chrome's first-time-processing only behavior. Modifying the Firefox advanced preference "network.http.spdy.enabled.http2" from true (the default) to false permanently resolves the issue.
IE 11
IE 11 does not fail at all. No browser settings were altered from the default installation of IE 11.
Mac Browsers
Mac users report that file download attempts appear to succeed but attempts to open the zip archive culminate in the Mac environment thinking that the zip archive is password protected. NOTE: There is no explicit assigning of a password to the zip archive in the code that processes the download request. No users in Windows environments report this behavior.
SSRS Report Display
The site has a feature that allows logged in users to display a PDF document created at runtime from SSRS. The PDF displays directly in the browser window (as opposed to immediately initiating a download operation).
Chrome
Chrome displays a similar first-time-processing error when the user attempts to display an SSRS report. The browser displays the following error message: "Error Failed to load PDF document." The error message has a "Reload" button which culminates in the report displaying successfully. All subsequent attempts to display reports in the same browser window succeed with no further issues. The first-time-processing behavior is, again, experienced when the user closes and re-opens Chrome to the site, and retries the report display.
NOTE: It is interesting that in Chrome with either feature (file downloading or SSRS report display), once the user has experienced the first-time-processing issue with either feature, then the other feature works fine with no issues for the life of that browser instance. Example: User opens new Chrome instance, navigates to site, and attempts to download files. The file download will fail the first time. Immediately attempting to display a report succeeds ... and vice versa.
Firefox
Firefox displays the same "Secure Connection Failed" error message as was the case with the file downloading feature. Modifying the same Firefox advanced preference "network.http.spdy.enabled.http2" from true (the default) to false permanently resolves the issue.
IE 11
IE 11 does not fail at all. No browser settings were altered from the default installation of IE 11.
I am working on a custom action for our company's shopping cart website. It is a software that is installed and setup, and we are able to add to it by creating custom actions. I created an ASP.NET (web forms) page that uses SignalR to add to it, but whenever it tries to grab an instance of the hub within javascript, it is always undefined.
In Chrome, I can see signalr/hubs, and there are no 404 not found errors on the page either. It works perfectly fine when running it in debug from VS 2012, but not from within the web site on the server.
I am certain I have deployed all the necessary components, and have tried many approaches to changing the way it finds the hub, but nothing seems to work.
I can provide code samples if needed.
I found the issue. It was related to the name of the hub being misspelled in javascript. Once that got fixed, then the function name needed to be changed in javascript so the first character is lowercase. It is working as intended now.
I'm trying to get BlogEngine working with ExpressCheckout. I've tested the API credntials with the same user controls as I'm using with BlogEngine and they work. In BlogEngine, however, I get "Sorry, an error occurred after you clicked the last link". I'm using the same .ascx user control and the same API settings and credentials.
In BlogEngine, if I use Firefox I can get to the PayPal login screen without problems, but with IE or Chrome (IE7 and IE8) on low privacy and security settings, I get the error.
I've tried sandbox and live credentials but I really don't know what else to try. I'm using the MarkExpressCheckout method on PayPal's NVP C# samples and have never had problems before. Could some part of BlogEngine be interfering somehow? I'm running ASP.NET 4.
If it helps, my site/checkout is at http://chickenping.com (http://chickenping.com/category.aspx to add prroducts to the cart).
This was caused by passing the country as United Kingdom rather than GB (which works)