You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When copying a lot of mnemonics (around 450 in this particular case), it sometimes fails with a timeout error. The mnemonics were copied to a new log without any existing curves.
"Failed to copy log data." - "The request channel timed out attempting to send after 00:01:30. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."
It seems like the error is logged from this try/catch in CopyLogDataWorker.cs, which is a part of copying the log header, before copying actual data.
Note: This might be WITSML server-related, as I could not reproduce it with the same log on another WITSML server. If it is server-related we should still investigate why it happens and if it's possible to request a timeout increase from the API.
The text was updated successfully, but these errors were encountered:
When copying a lot of mnemonics (around 450 in this particular case), it sometimes fails with a timeout error. The mnemonics were copied to a new log without any existing curves.
"Failed to copy log data." - "The request channel timed out attempting to send after 00:01:30. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."
It seems like the error is logged from this try/catch in
CopyLogDataWorker.cs
, which is a part of copying the log header, before copying actual data.Note: This might be WITSML server-related, as I could not reproduce it with the same log on another WITSML server. If it is server-related we should still investigate why it happens and if it's possible to request a timeout increase from the API.
The text was updated successfully, but these errors were encountered: