cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot Schedule Discovery Accellerator

wilsond3010
Level 6
Partner

I'm not sure if anyone else has had this one.

But I went to create a scheduled query to run for a specific period of time. 

Anyway when you submit the request it fails to create and even after making the relevant changes as per the install docs for permission still does the same thing.

So the solution is to ignore the microsoft best practices for SQL in which you rename your SA account to something else.


1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Ok then!  I think this is the technote http://seer.entsupport.symantec.com/docs/323355.htm.

I guess all the installs I have done the customer has just used SA.

regards,

View solution in original post

6 REPLIES 6

Liam_Finn1
Level 6
Employee Accredited Certified
I have had no such issues.

What account are you using to submit the scheduled reports and what rights does the user have

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi Wilson,
Just to second Scanner001, I haven't had issues with that either.

What version of DA and SQL are you running?

Regards,

wilsond3010
Level 6
Partner

it was DA for EV8 Sp3

Didn't matter is I tried doing them as myself or EVService it wouldn't schedule them

We ended up on a support call and it seems there is a stored proc which calls SA or something couldn't get the complete story but the fix was to rename the SA account back to SA

Try renaming your SA account to something else and then create a scheule and it fails

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Ok then!  I think this is the technote http://seer.entsupport.symantec.com/docs/323355.htm.

I guess all the installs I have done the customer has just used SA.

regards,

Liam_Finn1
Level 6
Employee Accredited Certified
We don't use the SA account we do everything as the service account SA is never used for anything

wilsond3010
Level 6
Partner

Must use the SA account as that was the fix from symantec for it