You need and account with some specific permissions as mentioned in the admin guide for the mailbox level backups. These are like Send-As, Receive-As etc. Please check from the module admin guide for the exact permissions.

Create this account and start Networker Remote Execution Services on the Exchange server with this account. It should be able to get you the list of mailboxes.

thanks much,
but the account i logged on with is an exchange admin and the exchange administrator told me that this account inherited by default the required permissions listed in the module admin guide (list, send as,recieve as,....)

but there are things i need to check with you that they are not the reason for that problem:
-the networker cliuent was installed on the exchange server using a domain account that is a member of agroup that is a local admin on the machine

-the networker module was installed on the exchange server using the windows administrator of the exchange server

actually i can take manual backup to IS (information stores) but i still can't list the private mailboxes and the error message is as follows:

Could not open EMS Store for Exchange Server EXCH1, status 0x8004011d.

I would prefer to install both using Windows administrator account and then start service using the account that has all the priviledges.

Did you try backing up mailboxes through nsrxchsv OR Server initiated?

I have seen sometimes that it does not list mailboxes on the module but backups happen properly. You can use save sets and include/exclude files to list out which mailboxes to backup.

Also, any specific reasons for not using NME 5.1 build 278?

thanks,
i will try to backup from server side or the CLI

actually i didn't install the NME 5.1 cause the exchange server is win2k3 sp1 32 bits

Actually i tried to backup the mailboxes using the nsexchsv command but it gave me the same errors as following:


[6120] 09/14/08 11:57:12 nsrxchsv_ese.exe Version: 4.1.0.440 Supporting Exc
hange 2000 and Exchange 2003
[6120] 09/14/08 11:57:12 System Version: 5.2 Build 3790 Service Pack 2
[6120] 09/14/08 11:57:12 ESEBCLI2.DLL Version: 6.5.7638.1 Service Pack 2
[6120] 09/14/08 11:57:12 Performing an Exchange save operation; save level
is Full (Legato Backup Level: full).
[6120] 09/14/08 11:57:12 Parsing parameters from the command line...
[6120] 09/14/08 11:57:12 Opening connection to NetWorker Server...
[6120] 09/14/08 11:57:12 Opening connection to Exchange Server...
[6120] 09/14/08 11:57:12 mapi(1076): OpenMsgStore() = 0x8004011d: The attempt to log on to the Microsoft Exchange Server computer has failed. (Microsoft Exchange Server Information Store)
[6120] 09/14/08 11:57:13 mapi(1076): OpenMsgStore() = 0x8004011d: You do not have permission to log on. (Microsoft Exchange Server Information Store)
[6120] 09/14/08 11:57:13 Backup operation finished with errors. No savetim
e was sent.

Even this error suggests there is some problem with the account you are using. I would still like to remove everything from Exchange server. Log in as Windows administrator...install NEtworker client...followed by NME...Start Networker Remote Execution Service using the service account created with required permissions for the backups.

This is definitely a problem with permissions.

Sometimes you assign Send As and Receive As permissions to one account, but this account belongs to other groups that have these permissions denied. For example, if the exchuser has these permissions assigned, but this user belongs to Administrators and Exchange administrators, and these have these permissions denied, you¿ll have the same problem. Other things you have to take in mind is to make sure the ¿deny¿ is not ¿grayed out¿ (which means the permissions is being propagated from the parent directory), so even if you have ¿allow¿, you¿ll see the same error message.

And the last thing to check if to check not only the mailbox store permissions for this user, but also the permissions for this user on each one of the parent¿s directories up to the server name.

This should resolve your problem.

Also, make sure you upgrade to the latest NetWorker module for Exchange 5.1, as there are many important fixes and improvements that you should have in order to avoid issues in the future.