Del,
This is the reaction of Microsoft to your comment on the bug in MS Exchange.
Can
you comment on this?
Jan
> ----------
> Sent: Wednesday, August 19, 1998 9:47 AM
> To: 'Post Jan'
> Subject: RE: ADSM Exchange backup failiure
>
> In the article NT backup is mentioned. Not the ADSM from IBM. I really
> would
> not know what is wrong here. Maybe you can ask your contact at IBM if they
> also pointed to the fix from this article.
>
> Does the NT Backup software work ?
> Did you check the file size and date of the edbcli.dll on your system ?
>
> Bye
> Bart
>
> -----Original Message-----
> From: Post Jan [mailto:Post_Jan AT delaware-computing DOT com]
> Sent: woensdag 19 augustus 1998 9:33
> To: Bart Meijer
> Subject: RE: ADSM Exchange backup failiure
>
>
> Bart,
>
> Thanks for the extremely quick reply.
> If the fix IBM mentioned is already in SP1 for 5.5, what is causing those
> mentioned problems than?
> The symptoms are the same as described in the KB-article.
>
>
> Kind regards,
>
> Jan
>
>
> On Wednesday, August 19, 1998 9:04 AM, Bart
> Meijer[SMTP:bartm AT microsoft DOT com]
> wrote:
> > Probably two different problems. The fix IBM mentioned is already in
> > Exchange 5.5 SP1.
> >
> > Below is the kb article:
> >
> > XADM: Thread Deadlock When Windows NT Backup Is Stopped [exchange]
> > ID: Q185694 CREATED: 14-MAY-1998 MODIFIED: 06-AUG-1998
> > WINDOWS:5.0,5.5
> > winnt
> > PUBLIC | XADM
> >
> > ======================================================================
> >
> --------------------------------------------------------------------------
> -
> > The information in this article applies to:
> >
> > - Microsoft Exchange Server versions 5.0, 5.5
> >
> --------------------------------------------------------------------------
> -
> >
> > SYMPTOMS
> > ========
> >
> > When you are running a backup using the Windows NT Backup program
> against
> a
> > Microsoft Exchange Server computer, if the backup is stopped before the
> > backup completes, Windows NT Backup stops responding (hangs).
> >
> > CAUSE
> > =====
> >
> > When a backup is stopped, the closing procedure blocks infinitely,
> waiting
> > on a thread's handle to close. The thread handle is never closed, so
> > Windows NT Backup stops responding.
> >
> > RESOLUTION
> > ==========
> >
> > To resolve this problem, contact Microsoft Technical Support to obtain
> the
> > following fix, or wait for the next Exchange service pack.
> >
> > This fix should have the following time stamp:
> >
> > 03/27/98 11:06a 31,504 edbbcli.dll (Intel) Exchange
> 5.5
> > 03/27/98 10:40a 44,816 edbbcli.dll (Alpha) Exchange
> 5.5
> >
> > 04/08/98 03:03p 63,760 edbbcli.dll (Intel) Exchange
> 5.0
> > 04/08/98 03:03p 75,536 edbbcli.dll (Alpha) Exchange
> 5.0
> >
> > STATUS
> > ======
> >
> > Microsoft has confirmed this to be a problem in Microsoft Exchange
> Server
> > version 5.0.
> > A supported fix is now available, but has not been fully
> regression-tested
> > and should be applied only to systems experiencing this specific
> problem.
> > Unless you are severely impacted by this specific problem, Microsoft
> > recommends that you wait for the next Service Pack that contains this
> fix.
> > Contact Microsoft Technical Support for more information.
> >
> > Microsoft has confirmed this to be a problem in Microsoft Exchange
> Server
> > version 5.5. This problem has been corrected in the latest U.S. service
> > pack for Microsoft Exchange Server version 5.5. For information on
> > obtaining the service pack, query on the following word in the Microsoft
> > Knowledge Base (without the spaces):
> >
> > S E R V P A C K
> >
> > -----Original Message-----
> > From: Post Jan [mailto:Post_Jan AT delaware-computing DOT com]
> > Sent: woensdag 19 augustus 1998 8:53
> > To: Bart Meijer
> > Subject: FW: ADSM Exchange backup failiure
> >
> >
> > Dear Bart,
> >
> > At the moment I'm testing the ADSM for MS Exchange agent from IBM to
> back-up
> > our Exchange databases. I do, however, get to often the problem reported
> > below. Please read the reaction of IBM.
> > I would hereby report this probelm on our Exchange 5.5 server (build
> > 2232.18: SP1), and would also like to test any bug/hot fix.
> >
> > Kind regards,
> >
> > Jan Post
> > Delaware Infrastructure Managment
> >
> >
> > > ----------
> > > From: Del Hoobler[SMTP:hoobler AT US.IBM DOT COM]
> > > Reply To: ADSM: Dist Stor Manager
> > > Sent: Tuesday, August 18, 1998 1:58 PM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: ADSM Exchange backup failiure
> > >
> > > Jan,
> > >
> > > Here's what is happening...
> > > The Exchange Agent has asked for some data from the
> > > Exchange Server and the Exchange server is not returning.
> > >
> > > This is most likely the following known problem
> > > opened with Microsoft:
> > >
> > > Bug x5:66198 is for Exchange 5.5
> > > Bug x5:66942 is for Exchange 5.0
> > > Bug x5:66943 is for Exchange 4.0
> > >
> > > There are fixes for these available from Microsoft.
> > >
> > > This has been seen mostly on single CPU machines.
> > > The fact that you get "Backup is already active. ,"
> > > when retrying the backup is also because of another
> > > Exchange bug (which can only be fixed by closing
> > > the Exchange Agent GUI, waiting 4-6 minutes, then retrying
> > > the backup). We are working with Microsoft on this too.
> > >
> > > Both of these problem are not particular to the
> > > ADSMConnect Exchange Agent and will happen with other
> > > backup products using the defined backup/restore API's.
> > >
> > > If you are seeing this "hang" quite often, call Microsoft,
> > > mention the bug number above and obtain/apply the hotfix.
> > > If you don't want to do that, you could also try the
> > > possible workaround of the "/BUFFERS:1" (only available
> > > with the FIXTEST 1.1.0.0 "A" version).
> > >
> > > Thanks.
> > >
> > > Del Hoobler
> > > ADSM Agent Development
> > >
> > > >> Dear All,
> > > >>
> > > >> A couple of days ago I encountered back-up problems with the ADSM
> agent
> > > for
> > > >> MS Exchange.
> > > >> What is happening:
> > > >>
> > > >> The back-up starts as planed, but hangs after some time. Here is a
> > > >> extraction of the log-file:
> > > >>
> > > >>
> > > >> ADSTAR Distributed Storage Manager
> > > >> ADSMConnect Agent for Microsoft Exchange Server
> > > >> Command Line Interface - Version 1, Release 1, Level 0.0
> > > >> (C) Copyright IBM Corporation 1998. All rights reserved.
> > > >>
> > > >> ***FIXTEST - Version 1.1.0.0 "A"
> > > >>
> > > >> ADSM API Version 3, Release 1, Level 3
> > > >> ADSM Nodename: DCZEXCHG
> > > >>
> > > >> This is a "Try and Buy" license which has 43 days until expiration.
> > > >>
> > > >> Starting a backup to the ADSM server...
> > > >>
> > > >> Exchange Server : DCZ01S20
> > > >> Database : Directory
> > > >> Backup Type : Incremental
> > > >>
> > > >> Logging on to the ADSM server...
> > > >>
> > > >>
> > > >> ...(text removed)...
> > > >>
> > > >> When I than stop the scheduled ADSM service an dstop the MS
> Exchange
> > > >> Directory service, I get of course:
> > > >>
> > > >> Backup error encountered.
> > > >> Exchange Error: The interface is unknown.
> > > >>
> > > >> When I manually try to make a back-up of the IS or DS without
> stopping
> > > the
> > > >> ADSM & Exchange service first I get "Backup is already active. ,"
> > > >> At the ADSM host, the back-up session has timedou, because of no
> > > response
> > > >> from client (i.e. MS Exchange).
> > > >>
> > > >> Does any one has a clue why my incremental back-ups fail?
> > > >>
> > > >> (There has been made a successfull full and incremental back-ups
> > > before
> > > >> these failiures)
> > > >>
> > > >>
> > > >> Jan
> > > >>
> > > >> > Delaware Computing Group
> > > >> > Delaware Infrastructure Management
> > > >> > Blokkestraat 29A
> > > >> > B-8550 Zwevegem
> > > >> > Phone +32-56-76.76.00
> > > >> > Direct +32-56-76.76.52
> > > >> > Fax +32-56-76.77.93
> > > >> > E-mail post_jan AT delaware-computing DOT com
> > > >> > URL http://www.delaware-computing.com
> > >
>
|
