To homepage To homepage
Solved

TX not responding when opening ODX task log (v20.10.45)

  • 18 April 2024
  • 6 replies
  • 43 views
rogier.helmus
Rank
Badge +1

Hi all,

I have v20.10.45 running in Azure with ODX server running for a client. We have about 15 ODX datasources. The synch/loads run daily and the server has been up for about 9 months, so no extraordinary amount of logging I think. 

The issue that I’m having is that it’s not possible anymore to check the execution logs of  some ODX task runs. The popup doesn’t appear and TX goes into a “Not Responding” state. Any click in the client will crash the application. This happens when I have no TX project opened, only the Manage tab for ODX server (see screenshot).

I’ve upscaled the VM from DS2v2 (2 core, 8GB) to D4S_v3 (4 core, 16GB), but this doesn’t change it. Restarting ODX server also doesn’t help.

The issue is not with all tasks. Tasks for which all recent executions are successful will show the logging. Checking the event logging at ODX server level will crash and tasks with a lot of recent failures also crash. 

Edit 1: A connection that has this logging issue is a connection using the CData Sharepoint connector. I recreated this connection to ensure that there’s no logging at all. The synch task runs but with warnings. When trying to view the log, TX crashes again.  

What can I do to view these logs?

ODX server in 20.10.45 has no retention period option as is available in the new release:

 

Screenshot:

 

icon

Best answer by Christian Hauggaard 18 April 2024, 13:14

View original

6 replies

daniel
Rank
Userlevel 4
Badge +5

Dear @rogier.helmus ,

Because you are running 20.10.45 you still have access to you own repo.

When this query is getting slow, you can archive the logging table in a new table (you need to do this by hand) and then delete all the logging from the repo table. 

I usually have a SQL query to check the logging over longers periods of time.

 

Hope this helps

= Daniel

rogier.helmus
Rank
Badge +1

@daniel  Are you perhaps talking about the Execution Package logging? My issue is with the ODX server task logging which is store in the TX cloud and stored locally in a sqllite database file.

 

daniel
Rank
Userlevel 4
Badge +5

@rogier.helmus ,

I see. It looks a little bit more like an issue to me.
A sqlite db of 55 mb should not give you these kind of waiting times or crashings issues.

In a bit support will come across this thread and hoplefully will be able to help you

= Daniel

rogier.helmus
Rank
Badge +1

Edit 1: A connection that has this logging issue is a connection using the CData Sharepoint connector. I recreated this connection to ensure that there’s no logging at all. The synch task runs but with warnings. When trying to view the log, TX crashes again. So, maybe the issue is with the CData Sharepoint connector, but not sure. 

rory.smith
Rank
Userlevel 5
Badge +7

Hi @rogier.helmus,

 

you can query the sqlite backlog directly (see: https://legacysupport.timextender.com/hc/en-us/articles/360054444552-How-to-Query-ODX-local-Backlog-SQLite-database) that may also give some hints. I would also have a look at the Windows Event Viewer, perhaps something is logged there. 

Christian Hauggaard
Rank
Userlevel 6
Badge +5

Hi @rogier.helmus I have created a support ticket for this

Reply


Terms and ConditionsCookie settings