Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2k backup fails on autostart only

Status
Not open for further replies.

jcoaps

Technical User
Jul 23, 2001
12
US
We have been doing a full backup of our exchange server on a nightly basis for the last 6 months, and up until 2 weeks ago, everything was peachy. We now get an error that looks like this in the nsrxchs.log and the daemon.log:

nsrxchs.log- [3184] mapi.c(145): MAPILogonEx() = 0x80004005: unknown error -2147467259 (0x80004005)

daemon.log- mapi.c(75): MAPIInitialize() = 0x80040108: unknown error -2147221240 (0x80040108)

However, this only happens when the backup auto-starts itself. When I stat the process manually using the administrative console, the backup finishes without any problems. I am starting it manually by starting the default group, which is Exchange on our system.

We are running Network 6.1 build 186 and the Exchange Plugin 3.0

Has anybody else experienced this problem?
 
We are also receiving this error but are still none the wiser to why it is happening. At the moment we are testing the backup with our anti-virus solutions deactivated incase there is a mapi conflict.

If you have any success with the problem then can you pls let me know.

Cheers
 
Look at how the Exchange service is set up under service. Is it using the system account or a proper account?

Also, you are using the exchange BSM command to backup the saveset in the client entry aren't you?
 
Upgrade to 6.2--6.1 has some bugs.
If you have Exchage modulues, check to see if they need upgrading.
Check parallism, or resource conflict.
check host file, resolve cleint names by long and sourt verison.
Fazil.Saiyed@anixter.com
 
Ive finally figured it out! First of all on the Client Resource make sure the remote tab has the account and password of the Account used to install Exchange. This ensures it has the right Exchange permissions.
Secondly check the Messages file on the Networker Server. In here you may notice that it lists some disabled AD accounts where the errors normally appear and it can be these causing the mapi errors. Either remove or enable to prevent the mapi errors.
 
I see this error in Exchange 2000 sp2 using OWA

I moved the site to a unspecified port and when logging into the domain User; Pass; Domain > Enter

OWA comes Up and gives error then goes away...

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top