«

We deployed an asp.net 2.0 web app to our production web server and when we
run the site from that box we got an Done, with errors javascript message.
Now we don't get that message on any other web server so what could be
causing it on that particular web server?

Hello Mike,

From your description, when you deploy your ASP.NET 2.0 web application on
a particular server machine, the application will report a script error at
client browser when start running it, correct?

As for the script error, it may be specific to a certain built-in component
that rely on some dynamically registered scripts. Would you provide some
details of the page which report the error, or more specifically, you can
try locating the exact component or code fragment that result to the script
error.

Please feel free to let me know if you have any new finding.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Mike,

Thanks for your reply.

I think the https connection maybe a potential cause. You can check the IIS
log of the server to see whether there is any error entry indicate that
some requests failes under non-https protocol. I suspect that there is some
script requests which is requesting under http(rather than https) and
failed.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Mike,

Any further progress on this issue? If you do feel the issue hard to
troubleshooting and may involve some other complex configuration or
setting, you can consider contact product support team to open a support
incident on this:

http://support.microsoft.com/

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.