Skip to main content
Solved

communication object in faulted state when running execution package

  • September 16, 2024
  • 2 replies
  • 97 views

when running a execution package message The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

version 20.10.46.64
    
how to solve?

Best answer by Bernarddb

We have been investigating this problem. And our C Disk was full, since our odx is running on the same machine as our TX client, it couldn't store/update the sqllite database anymore, and there was no space on the disk to transfer the Parquet files to the DB. after cleaning up it seems to be working again execpt for a few tables. We are currently investigating if we can fix this.

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

2 replies

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

 @Pieter-Jan I have created a support ticket for this


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • TimeXtender Xpert
  • 53 replies
  • Answer
  • September 16, 2024

We have been investigating this problem. And our C Disk was full, since our odx is running on the same machine as our TX client, it couldn't store/update the sqllite database anymore, and there was no space on the disk to transfer the Parquet files to the DB. after cleaning up it seems to be working again execpt for a few tables. We are currently investigating if we can fix this.


Reply


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