I did not say a permissions problem on the DSM.OPT file.
I was referring to the login permission for TDPEXCC to
access the correct AD objects required for backup.
Good idea to get the trace... especially since your other machines
are working with the exact same setup.
If you still have issues, you should place a call with IBM Service.
Thanks,
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/14/2009
10:35:39 AM:
> [image removed]
>
> Re: Scheduled Exc backup failing on -1073741819
>
> Matthew Large
>
> to:
>
> ADSM-L
>
> 07/14/2009 10:38 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Hi Del,
>
> Scheduler is configued to use the system account, and that has never
changed
> either.
>
> The only thing that has changed is the TCPserveraddress in the
> \tdpexcc\dsm.opt file, and that was changed by the Oracle DBA, under my
> instruction. But how can a user altering+saving the options file change
the
> file permissions such that the Scheduled run cannot read it?
>
> And if it were the opt file causing the problem, wouldn't the error be
more
> like 'Unable to read options file dsm.opt'?
>
> I'm going to configure the trace on the scheduled job tonight.
>
> Much appreciated,
> Matthew
>
> On Tue, Jul 14, 2009 at 3:16 PM, Del Hoobler <hoobler AT us.ibm DOT com>
> wrote:
>
> > C0000005 looks suspiciously like RC=5... which many times means
> > permissions issue.
> >
> > Make sure you set the login account for the scheduler service
> > to be an id that has proper domain permissions for managing Exchange.
> >
> >
> > Thanks,
> >
> > Del
> >
> > ----------------------------------------------------
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/14/2009
> > 10:00:36 AM:
> >
> > > [image removed]
> > >
> > > Re: Scheduled Exc backup failing on -1073741819
> > >
> > > Matthew Large
> > >
> > > to:
> > >
> > > ADSM-L
> > >
> > > 07/14/2009 10:01 AM
> > >
> > > Sent by:
> > >
> > > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > >
> > > Please respond to "ADSM: Dist Stor Manager"
> > >
> > > Nothing in the event.log except the same ANS1512E dsmsched.log
entry,
> > > nothing in dsierror.log, no crash files. Exchange reports nothing
> > related at
> > > the time of the failure.
> > >
> > > 5.3.3 TDP for Exchange
> > > 5.5.0.4 TSM client
> > > on W2K3sp2
> > > The problem is that the backup runs absolutely fine from a manual
> > trigger.
> > >
> > > Just got Del's post - how did I miss that!? (late night's, early
> > mornings)
> > >
> > > Much appreciated,
> > > Matthew
> > >
> > >
> > > On Tue, Jul 14, 2009 at 1:19 PM, Richard Sims <rbs AT bu DOT edu> wrote:
> > >
> > > > The -1073741819 reported by the ANS1512E message could have been
> > > > better programmed for such high negative values, to more
appropriately
> > > > and helpfully report it as C0000005, which is more readily
findable as
> > > > a memory access problem. Your posting doesn't cite your software
> > > > levels: this might be APAR IC49467. Look for event log,
dsierror.log,
> > > > and dsmcrash.log problem indications, and take a look at the
Exchange
> > > > side log if necessary.
> > > >
> > > > You might also see if the backup can be invoked manually: If the
same
> > > > problem occurs, you can trace it thereby.
> > > >
> > > > Richard Sims
> > > >
> >
|
