I suppose you're not using a client acceptor service that somehow slipped past 
you?  (Grasping at straws)  - Margaret

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bill Boyer
Sent: Tuesday, January 15, 2013 1:12 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

The TSM Scheduler service is running under the domain userid in the 
"organization Management" group. If I logon as that userid I can run the 
backups. But running them as a scheduled task fails. That's what's 
strange....same userid... works logged on...fails as service.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Rick Adamson
Sent: Tuesday, January 15, 2013 11:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

Also, remember that the account used for the scheduler has to be a member of 
the Exchange Security Group "Organization Management", which in our case is a 
security group in our root domain.
~Rick

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Clark, Margaret
Sent: Tuesday, January 15, 2013 11:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

We saw RC=1819 when the scheduler was started using the local system account, 
and the local system account did not have access to the Exchange system.
- Margaret

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Bill Boyer
Sent: Tuesday, January 15, 2013 5:10 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

Windows 2008 R2 server running Exchange 2010. Installed the agent and my 
Exchange admin gave me a userid with the permissions. Running the backup while 
logged in as the user works fine, but when I run it as a scheduled backup I get 
RC=1819. The TSM Scheduler service is configured to run as the same domain 
userid I used to successfully backup while logged on.



Never seen this one before. Scheduler fails with the same userid that works if 
I logon locally. My Windows guy is stumped, too.



Any ideas?



Bill Boyer
DSS, Inc.
(610) 927-4407
"Enjoy life. It has an expiration date." - ??