Skip to main content
To homepage To homepage
Solved

Scheduled execution fails but works when run manually.

M
Explorer

Hello,

I have a data export object/task. I have created an execution package that runs this export. When I start this execution via a schedule it fails with this error (table does not exist):

1Execute ReaturnPortefeu:Info:Initialized
2  -Execute ReaturnPortefeu
3Execute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_Export:Info:Initialized
4    -Execute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_Export
5Fill Data Export Table 'vw_ReaturnPortefeuille_Export':Error:Failed
6      -Fill Data Export Table 'vw_ReaturnPortefeuille_Export' 'Failed'
7      	The table vw_ReaturnPortefeuille_Export does not exist!

When I start the execution manually (right click and execute) it works without issue.

Execution log

The source table for the export is a view:

Source table

Why does it fail when scheduled and not when run manually?

Best answer by daniel

Dear @Mvest ,

Could it be a scoping / rights issue where you as a user (running it manual) has more rights / permissions / grants on accessing this source / executing the script as the service account does not?

 

View original
Did this topic help you find an answer to your question?

3 replies

daniel
TimeXtender Xpert
Forum|alt.badge.img+8
  • daniel
  • TimeXtender Xpert
  • 192 replies
  • Answer
  • April 29, 2024

Dear @Mvest ,

Could it be a scoping / rights issue where you as a user (running it manual) has more rights / permissions / grants on accessing this source / executing the script as the service account does not?

 

Christian Hauggaard
Bernarddb
2 people like this
  • Christian Hauggaard
    Christian Hauggaard
  • Bernarddb
    Bernarddb
Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Mvest did you manage to resolve the issue by adjusting user permissions? 

M
Explorer
  • Mvest
  • Author
  • Explorer
  • 9 replies
  • May 6, 2024

Yes, it turned out to be a user permissions issue. Thank you for pointing me in the right direction.

The service account did not have access to the drive to which I was exporting the data. The confusing part was that I (with my personal account while developing) would click on Check Connection / Open the destination folder and there would be no issue. The error message that the service account got (“table does not exist”) did not really imply an authorisation issue. 

Most helpful members this week

Terms and ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings