Del,

We are in the midst of a migration from Exchange 5.0 -> 5.5 and therefore
have run the optimizer after each conversion. However our Exchange team have
converted over 20 servers with the same procedure and are confused as to why
only 2 servers have exhibited this backup problem.

Is it necessary to reboot the server or can you just stop and restart the
Exchange Services after running optimizer?

I checked the UNC shares and the permissions. Both appear to be fine.

Thanks,

Nathan

        -----Original Message-----
        From:   Del Hoobler [SMTP:hoobler AT US.IBM DOT COM]
        Sent:   Thursday, September 30, 1999 7:26 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: ADSM Connect Agent for MS Exchange

        Nathan,

        The message indicates that access to one of
        necessary files for backing up Exchange is not
        accessible by the user running the backup.

        I have seen this in a few situations:

        1. When Optimizer is run on the Exchange Server
           and the machine was not rebooted.
           (The Exchange Server services have not been
           refreshed with the new location of the Exchange
           databases and/or log files.)

        2. The UNC shares for the location of the database
           and/or logs was removed (some security products
           do this.)  For example, the \\EXCHSRVR1\D$ is not
           listed as a valid share.  The Exchange API accesses
           all of its data via the UNC shares (even for local
           machine backups).

        3. Permissions on the directory or file involved
           in the backup are not such that the user can back them up.


        Thanks,

        Del

        ----------------------------------------------------

        Del Hoobler
        IBM Corporation
        hoobler AT us.ibm DOT com

        > ADSM Server AIX 3.1.2.20
        > ADSM Connect Agent for MS Exchange 1.1.0.0B
        > Windows NT 4.0 SP4
        > Exchange 5.5
        >
        > While backing up the Information Store incrementally, the error
"Exchange
        > Error: Unable to find the file" is obtained.
        >
        > Does anyone know what the source of this error is and how it can
be
        > corrected?
        >
        > Thanks,
        >
        > Nathan