RE: Backup Exec v10 can't access mailboxes

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I've seen that problem, and the easiest way to fix it is to change the
resource credentials in the job setup to DOMAIN/Administrator; as others
note, the BE service account has problems accessing mailboxes for some
reason...

I've tried changing the NTFS permissions, but it did no good...nor does it
help when the BE service account has 'logon as a service' rights...

never had this issue w/ Sharepoint, but I suspect the same fix will do the
trick...

BA

"Nick Hill" wrote:

> Hi
>
> SBS2003 Premium, Backup Exec v10
>
> I've been getting some backup errors which seem to be due to the system
> account not having rights to read the Exchange mailboxes or Sharepoint. Has
> anyone else had this issue?
>
> Regards
> Nick
>
>
>
.



Relevant Pages

  • Re: full-text population problem
    ... can you look in the application log for event messages from MSSearch or ... changing MSSearch's service account to a local or domain account instead ... to fix 2 click Start, point to settings, click control panel, double click ... Looking for a book on SQL Server replication? ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Error 80070522 attempting to start ASP.NET
    ... I checked every folder listed and the rights are correct. ... and that didn't fix it. ... Do I have to restart ... for instructions on how to create a service account for ASP.NET ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Windows firewall doesnt work when I add vista machines to the doma
    ... the Domain controllers to fix this. ... The error says a privilege that the ... service requires to function properly does not exist in the service account ...
    (microsoft.public.windows.vista.security)
  • Access to the path "C:DOCUME~1<account>Local SettingsTemppidh
    ... We are using impersontation with a "service account" (not the default ASPNET account). ... This works on my local machine so I don't know what to tell our server admins on how to fix this. ...
    (microsoft.public.dotnet.framework.aspnet)