Skip to main content
To homepage To homepage
Solved

Issues with TimeXtender_Ingest_Service_6823.1

  • December 12, 2024
  • 5 replies
  • 111 views
D
Contributor
Forum|alt.badge.img

I wanted to ask if others have experienced issues with the TimeXtender_Ingest_Service_6823.1.

For the second time, I’ve encountered problems with opening the ODX, where it gets stuck during the process. When attempting to restart the Ingest service, it remains in a "stopping" state and fails to restart properly.

To resolve this, I’ve had to manually force the TimeXtender_Ingest_Service_6823.1 to stop using the Command Prompt. Once the service has been forced to stop, I can restart it successfully, and afterward, the ODX opens without issue.

Has anyone else encountered similar problems? If so, are there any recommendations or fixes to prevent this from occurring again?

Looking forward to your insights.

Best answer by Christian Hauggaard

Hi ​@Benny a bug fix has now been released for this issue

 Please upgrade to this version

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

5 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1017 replies
  • December 12, 2024

Hi ​@DylanW. 

It is a known issue, we are fast at work making a fix for it to avoid doing this.

Otherwise, there is no other way to resolve it.

One suggestion is to schedule this restart in a PowerShell script and run it as a pre or post step to avoid any issues while it is running.

D
Contributor
Forum|alt.badge.img
  • DylanW.
  • Author
  • Contributor
  • 8 replies
  • December 12, 2024

Hi ​@Thomas Lind 

Could you please update this post once the issue has been resolved?

Additionally, is it possible to provide a time frame for when the fix will be implemented?

Thank you in advance!

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

HI ​@DylanW. we are unable to provide a timeline at this time. The product team are investigating this with the highest priority level, with the aim of implementing a bug fix as soon as possible. I will provide an update on this post as soon as I have more information

B
Contributor
Forum|alt.badge.img+1
  • Benny
  • Contributor
  • 25 replies
  • December 17, 2024

​@Christian Hauggaard, ​@Thomas Lind,
Considering this is a known issue, I would expect a warning in bold capital letters on the page with the release note of this version and also on the products update page. Now only users who happen to read this post are informed of the possible risk before installing this version.

 

Kind regards

D
1 person likes this
  • D
    DylanW.
Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@Benny a bug fix has now been released for this issue

 Please upgrade to this version

Reply


Most helpful members this week

Terms and ConditionsCookie settings

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