Cannot log on to MAPI with specified credentials

Is it Exchange 2007  Server?

Is Exchange on same Server as Backup Sever?

On windows 2008 server , update the hosts file with IPV4 entries as given in below technote

An attempt to run a Granular Recovery Technology (GRT) backup of the Information Store to tape for Exchange 2007 running on a Windows 2008 server fails with an "Access Denied" error.

 http://support.veritas.com/docs/305539

Restart the remote agent on Exchange server , or all BE services if it is on same server.

Make sure that exchange is the first resource in selection list order OR only select exchange in the bakcup job.

Check the credentials with the help of below technote

How to configure Microsoft Exchange Server 2007 backups in Backup Exec 11d and above 

http://support.veritas.com/docs/306281

Hi, I will investigate your links above.

SBS2008 is Small Business Server 2008 (which contains Exchange 2007), and yes, the backup server and exchange server are the same.

/ Lars

I've gone through all the points in the checklist, and the problem still appears. I ran a diagnostics check from within Backup Exec, and what I see is that the administator user is not said to be a Domain Admin:

Local Group Memberships for Backup Exec service account MYDOMAIN\administrator on \\MYSERVER

Offer Remote Assistance Helpers
Denied RODC Password Replication Group
Administrators
Users

MYDOMAIN\administrator is a member of the following groups:
     MYDOMAIN\Domain Users
     Everyone
     BUILTIN\Administrators
     BUILTIN\Users
     BUILTIN\Pre-Windows 2000 Compatible Access
     BUILTIN\Certificate Service DCOM Access
     NT AUTHORITY\SERVICE
     NT AUTHORITY\Authenticated Users
     NT AUTHORITY\This Organization
     LOCAL

MYDOMAIN\administrator has the following privileges:
     Create a token object
     Adjust memory quotas for a process
     Add workstations to domain
     Act as part of the operating system
     Manage auditing and security log
     Take ownership of files or other objects
     Load and unload device drivers
     Profile system performance
     Change the system time
     Profile single process
     Increase scheduling priority
     Create a pagefile
     Back up files and directories
     Restore files and directories
     Shut down the system
     Debug programs
     Modify firmware environment values
     Bypass traverse checking
     Force shutdown from a remote system
     Remove computer from docking station
     Enable computer and user accounts to be trusted for delegation
     Perform volume maintenance tasks
     Impersonate a client after authentication
     Create global objects
     Increase a process working set
     Change the time zone
     Create symbolic links

Could this be anything? I'm shooting in the dark, here...:mansad:

Did  you create hosts file entries on windows 2008 server as given in technote?

I would recommend using another account which is unique instead of Administrator like symantec or veritas.

It should be part of Domain Admins

Give Exchange FUll Administrator role using system Manager.

It should have active mailbox which is not hidden from GAL.

Mailbox should be able to receive and send messages.

Should be part of  local Administrator  on exchange server.

OK, now I have something to work with. I added a new user, gave it all the correct rights, and now this happens (from the Event Log):

An error occurred while attempting to log in to the following server: "MYSERVER".
 SQL error number: "4814".
 SQL error message: "Login failed for user 'mrbackup'. The user is not associated with a trusted SQL Server connection.
". 

I added 'mrbackup' to the SQL Server using the SQL Server Express Management Console. Obviously didn't make any difference. Are there any particular db-rights I should assign this user? It is configured to use Windows Authentication.

The failed backup job responds with the same error as before (MAPI...).

what are you doing SQL management studio?

You are backing up exchange , right?

is it windows 2008 (backup or exchange)?

This error is logged from Backup Exec. Backup Exec uses SQL Server Express as its backend db, doesn't it?

It is Small Business Server 2008, which is Windows Server 2008 and Exchange Server 2007 bundled.

Can you follow this technote step by step.. I think you are going away from the basic things

How to configure Microsoft Exchange Server 2007 backups in Backup Exec 11d and above 

http://support.veritas.com/docs/306281

I have foun this suggestion.

Mine is sorted now (after a fashion).  There is definitely a bug with BE12.5 and Ex2007.  I have tried putting the exchange backup FIRST in the selection order in the backup.  It works 100% that way, but if it comes after any NTFS backup it fails.  I hope this works for you.

I've actually had this error and a host of other errors such as Exchange 2007 GRT backups working to tape but crashing the server when I attempted to run them to local disks or a SAN. I've also had the VSS writer failed errors. All of these things started happening about a month ago after 2 updates (can't recall the exact numbers). Then about a week ago this hotfix was released 319699. I read the release notes which listed things that closely matched but not directly matched the many odd errors I was receiving. I applied the patch, updated the agent on the Exchange server now everything is working without error. I can write backups to local disk, SAN, tape and it doesn't matter the resource order or if I include other things in the backup job.

It was quite frustrating for me for a long time trying to diagnose each problem only to have a different one appear the next time I rebooted or tried the backup job. Then when the original problems came back I felt like throwing the server out of the window. I tried reinstalling MS CDO, the VSS update patch for Server 2003 sp2, everything. Nothing seemed to help. If anyone is experiencing some/all of these problems, install the hotfix, reboot if the GUI says to and update the agent on the exchange server using the agent update tool (forgot the name of that) and reboot the exchange 2007 server if the tool instructs you to. In my case I didn't have to, my agent on the Exchange server was up to date except for the latest hotfix. Hope this helps someone