[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference chefs::ms-exchange

Title:Microsoft Exchange Server
Notice:
Moderator:FLASK2::SYSTEM
Created:Fri Feb 17 1995
Last Modified:Thu Jun 05 1997
Last Successful Update:Thu Jun 05 1997
Number of topics:1099
Total number of notes:5174

305.0. "problem with exchange clients." by QCAV01::CHENTHIL () Mon May 20 1996 11:19

T.RTitleUserPersonal
Name
DateLines
305.1Exchange hangs on IntranetSAYER::ELMORESteve [email protected] 412-364-5893Fri Feb 07 1997 04:0739
    Was this ever fixed?  I am having a similar problem.

    For the third time since January my exchange client on W95 hangs.  I
    can neither send mail nor receive it.  When I exit, the exit box never
    goes away.  I have to ctrl-alt-del and start deleting tasks to get rid
    of it.

    When I click again to start exchange all over, the first couple of mail
    messages in the outbox get mailed, then they stop.  No new mail can
    get sent.  I continue to receive no new mail.

    When not attached to the network, exchange works and exits properly. 
    The problem on happens when connected to the net (I am a Telecommuter
    using a ppp dial-up).

    The problem has repeated itself three times since January, but then it
    sort of fixed itself after about three days.  No one seems to know what
    is going on.  

    This has been extremely frustrating.  I have switched over to exchange
    and now depend on it.  Not receiving mail is impacting my very job.

    Can *anyone* help?  CCS has been unable.  If I had some kind of
    tool, perhaps I could trace this myself.  It's definitely network
    related.  When I exit the PLEASE WAIT WHILE MICROSOFT EXCHANGE EXITS,
    never goes away, and when I ctrl-alt-del, the following tasks are
    active:

    	Microsoft Exchange
    	MAPISP32 (not responding)
    	Explorer
    	Keasys
    	Awfxex32
    	Lights
    	Systray
    	Microsoft Office Shortcut Bar


                 
305.2BBRDGE::LOVELL� l'eau; c'est l'heureFri Feb 07 1997 08:0816
    This sort of behaviour has started to happen to me and I am not
    connected via RAS - I have a very high spec PC on a reliable Ethernet
    LAN. I've made no changes to my PC or Exchange setup - the problem has
    just recently started to become worse and worse.
    
    I suspect some sort of server or network loading interaction causing a
    timeout.  From pure network terms, the timeout should be recoverable
    but the Exchange application is very sensitive and hangs.  On .0's
    advice, I've disabled Browse Master to see if that has any beneficial
    effect for me - I'll let you know.
    
    If you have to kill off Exchange with the Task Manager, be sure that
    you kill off MSAPI32 as well.  At least that should avoid the need for 
    a complete reboot.
    
    /Chris/