Solved

Logging around setting "when transfer fails".

  • 12 March 2020
  • 6 replies
  • 40 views

We started to use the configuration continue without data in case a transfer fails. The feature works fine, and we also see the message that one or more datasources fail. My question is, how can we easily see which datasources failed, and with what error message?

 

icon

Best answer by Thomas Lind 12 March 2020, 10:30

View original

6 replies

Userlevel 5
Badge +5

Hi Eric

We have some feature suggestions regarding this.

 

 

So it seems like you can't actually see which table is failed. You can see that parts of an execution is failed in the execution message in the area that is marked in yellow.

 

Thanks Thomas, I will put my votes on them!

Are you aware of any workaround at this moment? If it is somewhere in the log / repository, we should be able to create a report on it ourselves.

Userlevel 5
Badge +5

I don't think it is stored anywhere, I could not find any mentions regarding this.

Userlevel 3
Badge +5

Hi Eric, you can see very very detailed execution information using this script:

https://legacysupport.timextender.com/hc/en-us/articles/360041434372-Execution-Details-SQL-Query

However I don't think the failure messages are stored anywhere unless the entire package fails. sorry. 

Thanks Thomas, Joseph.

What about this logging, any idea what is being captured?

 

Userlevel 5
Badge +5

Hi Eric

Depending on what CData provider you are using and what verbosity level you have added it will log all info of the authentication, synchronization and transfer.

Reply