ContextCapture Engines stop working with “boost error: could not convert calendar time to local time”

Felix James — Fri, 16 Oct 2020 15:48:26 GMT

Current Revision posted to ContextCapture | Descartes | Pointools | Orbit Wiki by Felix James on 10/16/2020 3:48:26 PM

	Product(s):	ContextCapture
	Version(s):	N\A
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

Problem

Some users have reported error messages received intermittently when running the ContextCapture Engine

Error: Failed to set job status to "Completed"

Fatal error: could not convert calendar time to local time

Solution

This occurs (more likely when using grid computing) when there is a connectivity issue between the ContextCapture Engine and a network drive.

· The engine loses the connectivity to the network drive used for the job queues.

· In such cases, the Engine meets the issue and crashes in an unfortunate chain of events.

We recognize this issue and in the first instance would recommend that a thorough investigation is done on the problem network to resolve all network connectivity issues.

We will implement fix in which we will ensure the engine does not crash. However, some manual action will be required by users to clean up the Job Queue and restart the job on another engine.

Original Author:

Felix James

Tags: ContextCapture, en, SELECTsupport

ContextCapture Engines stop working with “boost error: could not convert calendar time to local time”

Felix James — Fri, 16 Oct 2020 10:51:34 GMT

Revision 3 posted to ContextCapture | Descartes | Pointools | Orbit Wiki by Felix James on 10/16/2020 10:51:34 AM

	Product(s):	ContextCapture
	Version(s):	N\A
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

Problem

Some users have reported error messages received intermittently when running the ContextCapture Engine

Error: Failed to set job status to "Completed"

Fatal error: could not convert calendar time to local time

Solution

This occurs (more likely when using grid computing) when there is a connectivity issue between the ContextCapture Engine and a network drive.

· The engine loses the connectivity to the network drive used for the job queues.

· In such cases, the Engine meets the issue and crashes in an unfortunate chain of events.

We recognize this issue and in the first instance would recommend that a thorough investigation is done on the problem network to resolve all network connectivity issues.

We will implement fix in which we will ensure the engine does not crash. However, some manual action will be required by users to clean up the Job Queue and restart the job on another engine.

Original Author:

Felix James

Tags: ContextCapture, en, SELECTsupport

ContextCapture Engines stop working with “boost error: could not convert calendar time to local time”

Felix James — Tue, 16 Aug 2016 13:39:55 GMT

Revision 2 posted to ContextCapture | Descartes | Pointools | Orbit Wiki by Felix James on 8/16/2016 1:39:55 PM

	Product(s):	ContextCapture
	Version(s):	N\A
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

Problem

Some users have reported error messages received intermittently when running the ContextCapture Engine

Error: Failed to set job status to "Completed"

Fatal error: could not convert calendar time to local time

Solution

This occurs (more likely when using grid computing) when there is a connectivity issue between the ContextCapture Engine and a network drive.

· The engine loses the connectivity to the network drive used for the job queues.

· In such cases, the Engine meets the issue and crashes in an unfortunate chain of events.

We recognize this issue and in the first instance would recommend that a thorough investigation is done on the problem network to resolve all network connectivity issues.

We will implement fix in which we will ensure the engine does not crash. However, some manual action will be required by users to clean up the Job Queue and restart the job on another engine.

Original Author:

Felix James

Tags: ContextCapture, en, SELECTsupport

ContextCapture Engines stop working with “boost error: could not convert calendar time to local time”

Felix James — Tue, 16 Aug 2016 13:37:24 GMT

Revision 1 posted to ContextCapture | Descartes | Pointools | Orbit Wiki by Felix James on 8/16/2016 1:37:24 PM

	Product(s):	ContextCapture
	Version(s):	N\A
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

Problem

XXXXXXX

Some users have reported error messages received intermittently when running the ContextCapture Engine

Error: Failed to set job status to "Completed"

Fatal error: could not convert calendar time to local time

XXXXXXX

Solution

This occurs (more likely when using grid computing) when there is a connectivity issue between the ContextCapture Engine and a network drive.

· The engine loses the connectivity to the network drive used for the job queues.

· In such cases, the Engine meets the issue and crashes in an unfortunate chain of events.

We recognize this issue and in the first instance would recommend that a thorough investigation is done on the problem network to resolve all network connectivity issues.

We will implement fix in which we will ensure the engine does not crash. However, some manual action will be required by users to clean up the Job Queue and restart the job on another engine.

Original Author:

Felix James

Tags: ContextCapture, en, SELECTsupport