Developer forum

Forum » Integration » Error in live-integration

Error in live-integration

Jonas Krarup Dam
Reply

Hi, 

I have a customer who had problems with their live-integration in the weekend after black friday. 

The live-integration simply stopped transfering orders. For the duration of the outage,  the only thing that was written to the live-integration was the lines I've included below. 

It seems like the "connectionError" response was cached and it only reset when the app-pool recycled. 

The customer is on DW 9.17.3, and we are using the standard live-integration dll. 

This is a fairly rare error, but I have seen it on at least two other solutions. 

When I look at the source code for the live-integration dll that I have available (which is probably not the exact same version), I can see that the IsConnectionAllive response is being cached for the request through the Dynamicweb-wrapper for HttpContext - it looks like something went wrong with this caching. 

Would it be possible to look into this, and maybe at least add a time-limit for the cache, so that if it somehow becomes cached for all requests, at least it doesn't continue to cause problems until the application pool recycles?

Thanks, Jonas

11-28-2025 02:21:33.396 : DebugInfo: Reload prices. products #2

11-28-2025 02:24:19.900 : ConnectionError: Error checking Web Service connection: 'Object reference not set to an instance of an object.'. Request: '<GetEcomData></GetEcomData>'.
11-28-2025 02:24:19.900 : ConnectionError: Error checking Web Service connection: 'An item with the same key has already been added.'. Request: '<GetEcomData></GetEcomData>'.
11-28-2025 02:24:19.900 : ConnectionError: Error checking Web Service connection: 'An item with the same key has already been added.'. Request: '<GetEcomData></GetEcomData>'.
11-28-2025 02:24:19.900 : ConnectionError: Error checking Web Service connection: 'Object reference not set to an instance of an object.'. Request: '<GetEcomData></GetEcomData>'.
11-28-2025 02:24:19.900 : ConnectionError: Error checking Web Service connection: 'An item with the same key has already been added.'. Request: '<GetEcomData></GetEcomData>'.
11-28-2025 08:36:27.573 : DebugInfo: Updating order with ID: ORDER-59639. Complete: True. Order submitted from the backend: True
11-28-2025 08:36:27.651 : Error: Order with ID 'ORDER-59639' was not created in the ERP system.
11-28-2025 08:43:48.409 : DebugInfo: Updating order with ID: ORDER-59639. Complete: True. Order submitted from the backend: True
11-28-2025 08:43:48.409 : Error: Order with ID 'ORDER-59639' was not created in the ERP system.
11-29-2025 10:31:58.223 : DebugInfo: Updating order with ID: ORDER-59639. Complete: True. Order submitted from the backend: True
11-29-2025 10:32:43.030 : DebugInfo: Updating order with ID: ORDER-59639. Complete: True. Order submitted from the backend: True
11-29-2025 10:33:01.243 : DebugInfo: Updating order with ID: ORDER-59640. Complete: True. Order submitted from the backend: True
11-29-2025 10:33:01.243 : Error: Order with ID 'ORDER-59640' was not created in the ERP system.
11-29-2025 11:09:22.738 : DebugInfo: Updating order with ID: ORDER-59566. Complete: True. Order submitted from the backend: True
11-29-2025 11:09:22.738 : Error: Order with ID 'ORDER-59566' was not created in the ERP system.
11-29-2025 07:24:17.976 : ConnectionError: Error checking Web Service connection: 'Object reference not set to an instance of an object.'. Request: '<GetEcomData></GetEcomData>'.
11-29-2025 07:24:17.976 : ConnectionError: Error checking Web Service connection: 'Object reference not set to an instance of an object.'. Request: '<GetEcomData></GetEcomData>'.
11-30-2025 04:59:50.057 : DebugInfo: Updating order with ID: ORDER-59636. Complete: True. Order submitted from the backend: True
11-30-2025 04:59:50.135 : Error: Order with ID 'ORDER-59636' was not created in the ERP system.
11-30-2025 04:59:54.638 : DebugInfo: Updating order with ID: ORDER-59636. Complete: True. Order submitted from the backend: True
11-30-2025 04:59:54.638 : Error: Order with ID 'ORDER-59636' was not created in the ERP system.
11-30-2025 05:14:38.396 : DebugInfo: Updating order with ID: ORDER-59733. Complete: True. Order submitted from the backend: True
11-30-2025 05:14:38.410 : Error: Order with ID 'ORDER-59733' was not created in the ERP system.
11-30-2025 05:14:44.315 : DebugInfo: Updating order with ID: ORDER-59733. Complete: True. Order submitted from the backend: True
11-30-2025 05:14:44.330 : Error: Order with ID 'ORDER-59733' was not created in the ERP system.
11-30-2025 07:08:19.577 : DebugInfo: Updating order with ID: ORDER-59756. Complete: True. Order submitted from the backend: True
11-30-2025 07:08:19.577 : Error: Order with ID 'ORDER-59756' was not created in the ERP system.
11-30-2025 07:08:24.475 : DebugInfo: Updating order with ID: ORDER-59756. Complete: True. Order submitted from the backend: True
11-30-2025 07:08:24.475 : Error: Order with ID 'ORDER-59756' was not created in the ERP system.
12-01-2025 12:24:32.427 : ConnectionError: Error checking Web Service connection: 'Object reference not set to an instance of an object.'. Request: '<GetEcomData></GetEcomData>'.
12-01-2025 12:24:32.443 : ConnectionError: Error checking Web Service connection: 'Object reference not set to an instance of an object.'. Request: '<GetEcomData></GetEcomData>'.

Replies

 
Dmitriy Benyuk Dynamicweb Employee
Dmitriy Benyuk
Reply

Hi Jonas,
we will look into this. Do you know what Live integration version was used there?
Once the connection is lost the Live integration tries to check if it is restored back (using background empty request pings with some interval), so there is no smth which is cached forever, maybe it failed somewhere at checking the connection was restored (when it was actually restored).
BR, Dmitrij

 
Jonas Krarup Dam
Reply

Hi Dmitriy,

Thank you for looking into this :-)

This is from the solution that had the problem - is that enough information?

/Jonas

 
Dmitriy Benyuk Dynamicweb Employee
Dmitriy Benyuk
Reply

Hi Jonas,
we had a similar problem some time ago and it was fixed in #23104 and was released in the DW9 Live integration 7.4.13.
Could you update the solution to the latest Live integration 7.4.20?
BR, Dmitrij

 

You must be logged in to post in the forum