- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI have been getting a strange error with regards to WebResource.axd and ScriptResource.axd lately. The background information is as follows: I have developed a records management application with ASP.Net (Dot Net Framework Ver 2.0). The application is installed in 4 different locations (4 different customers) and each one is set up the same way. Each customer utilizes SonicWall as their firewall. I have the application errors forwarded to my blackberry and one particular customer continues to get the following error daily. It does not occur every time someone utilizes the application. It only occurs once or twice a day originating from different locations. I have checked and re-checked my settings in IIS and my application and I am stumped on this one. The error that I receive is
Error Message: Compilation Error - Check server log.
Error Path: http://192.168.2.4/EWS/EWS
Or
Error Message: Compilation Error - Check server log.
Error Path: http://192.168.2.4/EWS/EWS
The correct virtual path should be http://192.168.2.4/EWS/ but somehow every now and then an extra /EWS is added to the path with throws an error.
Additional Info:
Server OS: Windows Server 2003 SP2, IIS 6.0, ASP.Net 2.0.50727. The server also has ColdFusion 7.0 installed on it (I don't know if this is an issue).
Client (Workstation) OS: Windows XP SP2, IE 8.0, AVG Virus Scan.
Im leaning towards an IE 8 issue or AVG Virus Scan. Is anyone familiar with any problems that they may cause with ASP.Net. My other customers are all setup up with IE 7.0 and use the McAfee Virus Scan that comes with SonicWall. I do not get this error with my other customers.
Any input would be greatly appreciated.
Respectfully,
Bernard Bobinski
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: BBobinskiPosted on 2009-07-13 at 05:26:54ID: 24838994
Resolved! It was IE 8.0. All the clients were rolled back to IE 7.0 and no more error messages. Microsoft is getting ridiculous.