Discussion:
clr 2.0 missing in iis log (& broken app)
(too old to reply)
frank
2006-08-01 21:17:47 UTC
Permalink
We created an asp.net 2.0 app, which sends smtp email using System.Web.mail.
The app is in an IIS 6 application pool isolated to 2.0 apps on a 2003
server.

The app worked fine for a few days; recently however it began failing when
sending to external addresses (it works fine if the recipient is inside our
internal domain).

Comparing the logfiles, I notice when it was working both versions of the
CLR appear in log entries, for example:

(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)

Log entries from when it fails only contain CLR 1.1, for example:

(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)

The app is configured to use ASP.NET 2.0. What would be causing that
version to disappear from the log entries (and presumably the app) like
this?
Greg Young
2006-08-01 21:27:37 UTC
Permalink
That is the header from the client (i.e. the client only had version 1.x). I
think you are barking up the wrong tree.

Cheers,

Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
Post by frank
We created an asp.net 2.0 app, which sends smtp email using
System.Web.mail. The app is in an IIS 6 application pool isolated to 2.0
apps on a 2003 server.
The app worked fine for a few days; recently however it began failing when
sending to external addresses (it works fine if the recipient is inside
our internal domain).
Comparing the logfiles, I notice when it was working both versions of the
(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
The app is configured to use ASP.NET 2.0. What would be causing that
version to disappear from the log entries (and presumably the app) like
this?
frank
2006-08-01 22:17:03 UTC
Permalink
OK thanks; back to the debugging board... -fgb
Post by Greg Young
That is the header from the client (i.e. the client only had version 1.x).
I think you are barking up the wrong tree.
Cheers,
Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
Post by frank
We created an asp.net 2.0 app, which sends smtp email using
System.Web.mail. The app is in an IIS 6 application pool isolated to 2.0
apps on a 2003 server.
The app worked fine for a few days; recently however it began failing
when sending to external addresses (it works fine if the recipient is
inside our internal domain).
Comparing the logfiles, I notice when it was working both versions of the
(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
Bob Barrows [MVP]
2006-08-01 21:38:21 UTC
Permalink
Post by frank
We created an asp.net 2.0 app, which sends smtp email using
Please cut down your crossposts in the future .. you hit several
irrelevant newsgroups, such as the .inetserver.asp.general group which
is focussed on classic ASP. The groups containing "dotnet" as part of
their names are the only relevant groups for your question
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Trevor Benedict R
2006-08-01 23:34:27 UTC
Permalink
The SMTP service has its own Log. If it not turned on then enable logging
and see what is happening. Do you see any entries in the badmail folder. You
should also check with your Exchange Administator (if you have one) to see
if they are blocking any emails. You can also configure your SMTP service to
send underlivered emails to an alternate email. You may get more information
from that.

Regards,

Trevor Benedict
MCSD
Post by frank
We created an asp.net 2.0 app, which sends smtp email using
System.Web.mail. The app is in an IIS 6 application pool isolated to 2.0
apps on a 2003 server.
The app worked fine for a few days; recently however it began failing when
sending to external addresses (it works fine if the recipient is inside
our internal domain).
Comparing the logfiles, I notice when it was working both versions of the
(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
The app is configured to use ASP.NET 2.0. What would be causing that
version to disappear from the log entries (and presumably the app) like
this?
Loading...