Dave,
 
FYI - More info on this I should have also posted to the Declude Forum.  Their is a private MS hotfix for this - that reverses this.  Right now it appears as if it has passed internal testing but its not public.
 
Darrell
 
------------------------------------------------------------------------
Check out http://www.invariantsystems.com for utilities for Declude And Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers.
----- Original Message -----
Sent: Friday, September 15, 2006 5:47 PM
Subject: Re: [IMail Forum] Web Messaging is down this morning

Do you have Terminal Services installed on the machine? Did KB917422 get installed recently?
 
It has been reported that this hotfix prohibits reading and writing .INI files outside the Windows root (c:\windows or c:\winnt). That would be really stupid, but there seems to be a lot of traffic indicating it is going on.
 
It seems that MS knows about it and is telling users to have the vendors rewrite their software to place INI files only in the Windows root.
 
 
I count nine .INI files in c:\Imail...
 
Logistics and vendor relations aside, this could really set up a new kind of "DLL Hell" with conflicting names for INI files that now all have to be in the same directory.
 
What a mess.
 
-Dave Doherty
 Skywaves, Inc.
 201-847-0933
 [EMAIL PROTECTED]
 
 
 
----- Original Message -----
Sent: Friday, September 15, 2006 1:03 PM
Subject: RE: [IMail Forum] Web Messaging is down this morning

John,
 
I can't speak for Jeffrey, but I used CurPorts for this at http://www.nirsoft.net/utils/cports.html
 
It showed that 0.0.0.0:80 is being used by iwebmsg.exe (IMail's IWEBMSG proc).
 
There are no other port 80 listener processes.
 
CurPorts still shows 0.0.0.0:80 iwebmsg.exe if when it's dead.
 
Just to test, I changed IMail to use 8080 and CurPorts correctly displays 0.0.0.0:8080 iwebmsg.exe
 
Port 80 no longer shows up and iwebmsg.exe is the only process using 8080.
 
After I uninstalled IIS and it still wasn't working, I thought the same thing... figure out what is using port 80.  "netstat -an" only returns the one port 80 listener and CurPorts shows that it is iwebmsg.exe (as it should be).
 
I've included this information in an earlier email (including a few log file lines). I don't know if it ever made it to the forum.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John T (Lists)
Sent: Friday, September 15, 2006 11:59 AM
To: Imail_Forum@list.ipswitch.com
Subject: RE: [IMail Forum] Web Messaging is down this morning

There is a free utility on the Systernals site that will show you what is running on the ports. You should run that and see if something else is listening on port 80.

 

John T

eServices For You

 

"Seek, and ye shall find!"

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Heath
Sent:
Friday, September 15, 2006 6:48 AM
To: Imail_Forum@list.ipswitch.com
Subject: RE: [IMail Forum] Web Messaging is down this morning

 

We also lost web messaging on port 80 yesterday. Tried everything including backing out recent MS updates. No joy on port 80 but any other port will work but no joy in telling so many users to use a port number. Why would a number of systems go down on the same morning? MS updates is an easy target but does not seem to answer that question.

 

Cheers,

Jeffrey

Reply via email to