HCHTech
Well-Known Member
- Reaction score
- 4,203
- Location
- Pittsburgh, PA - USA
Ok, I have a web-design guy in my BNI group that I'm trying to help out here, but I'm striking out. He's developing a site for a customer that utilizes a Woocommerce plugin for it's shopping cart. On the site owner's Win7 computer, the site freezes (the screen greys over and freezes but you can still kill the page) at the point where you are supposed to be directed to authorize.net to enter your credit card information - If he uses IE11. If he uses either Chrome or Firefox, it works fine. It also works fine on my developer friend's iMac and Windows 7 install in Parallels.
The site owner is in Manhattan, so I offered to do a remote session to see what's up. I can NOT reproduce the error on my own computers here, I've successfully gone through the process with IE11-32 & 64 on both Windows 7 and Windows 8 computers, Safari on an iMac and Firefox on a Linux box.
So, I remote in and do the standard stuff. Scan (and look manually) for malware (removed a handful of minor things), scanned for viruses, reset IE to defaults, uninstalled old java & installed the latest java & flash, flushed the java cache, added the site to the trusted sites list (no change so removed), added the site in the java console to the exception list (no change so removed). Deleted temporary files, remove all non-MS addins from IE, checked the host file for problems, and flushed the DNS cache.
If I run the page with the java console open, about every third time the page freezes, I get the following error:
SCRIPT7002: XMLHttpRequest: Network Error 0x2ef3, Could not complete the operation due to error 00002ef3.
File: checkout
...which I've googled, which points to various workarounds and a potential incompatibiltiy between Woocommerce & IE10, but that doesn't explain why it works on my machine.
At the end of all of this, the site owner reports that it doesn't work on his other two computers (Windows) in the house either. I didn't have time or inclination this evening to remote into either of them to check them out, but it that's true, then it has to be something environmental. Just for kicks, I tried changing the DNS on the computer I was working on to GoogleDNS, but it didn't affect the problem. I also reset Winsock & the TCP/IP stack as a hail mary, but that didn't change anything either. I might try downgrading to IE10 to see what happens there - then re-upgrade to IE11.
I'm giving up for tonight, but I figured someone would have a suggestion or two that my foggy brain can't think of now.
The site owner is in Manhattan, so I offered to do a remote session to see what's up. I can NOT reproduce the error on my own computers here, I've successfully gone through the process with IE11-32 & 64 on both Windows 7 and Windows 8 computers, Safari on an iMac and Firefox on a Linux box.
So, I remote in and do the standard stuff. Scan (and look manually) for malware (removed a handful of minor things), scanned for viruses, reset IE to defaults, uninstalled old java & installed the latest java & flash, flushed the java cache, added the site to the trusted sites list (no change so removed), added the site in the java console to the exception list (no change so removed). Deleted temporary files, remove all non-MS addins from IE, checked the host file for problems, and flushed the DNS cache.
If I run the page with the java console open, about every third time the page freezes, I get the following error:
SCRIPT7002: XMLHttpRequest: Network Error 0x2ef3, Could not complete the operation due to error 00002ef3.
File: checkout
...which I've googled, which points to various workarounds and a potential incompatibiltiy between Woocommerce & IE10, but that doesn't explain why it works on my machine.
At the end of all of this, the site owner reports that it doesn't work on his other two computers (Windows) in the house either. I didn't have time or inclination this evening to remote into either of them to check them out, but it that's true, then it has to be something environmental. Just for kicks, I tried changing the DNS on the computer I was working on to GoogleDNS, but it didn't affect the problem. I also reset Winsock & the TCP/IP stack as a hail mary, but that didn't change anything either. I might try downgrading to IE10 to see what happens there - then re-upgrade to IE11.
I'm giving up for tonight, but I figured someone would have a suggestion or two that my foggy brain can't think of now.