EListError in ppDevice, 1788

rbuser

Hi,

some customers get an EListerror on line ppDevice, 1788.
Any ideas what is goign wrong? Threading issue?

Stacktrace is:
(EVI_Main, ppDevice, 1788) - (EVI_Main, ppDevice, 1787) - (EVI_Main,
ppDevice, 1042)
(EVI_Main, ppDevice, 1032) - (EVI_Main, ppDevice, 1287) - (EVI_Main,
ppDevice, 1281)
(EVI_Main, ppReport, 2258) - (EVI_Main, ppClass, 11175) - (EVI_Main,
ppClass, 11174)
(EVI_Main, ppEngine, 1845) - (EVI_Main, ppEngine, 1812) - (EVI_Main,
ppEngine, 1457)
(EVI_Main, ppEngine, 1411) - (EVI_Main, ppEngine, 1354) - (EVI_Main,
ppEngine, 1346)
(EVI_Main, ppEngine, 806) - (EVI_Main, ppEngine, 784) - (EVI_Main,
ppEngine, 575)
(EVI_Main, ppEngine, 550) - (EVI_Main, ppEngine, 523) - (EVI_Main,
ppReport, 2180)
(EVI_Main, ppDevice, 1363) - (EVI_Main, ppDevice, 1353) - (EVI_Main,
ppDevice, 1170)
(EVI_Main, ppDevice, 1154) - (EVI_Main, ppProd, 1671) - (EVI_Main,
ppProd, 1740)
(EVI_Main, ppProd, 1726) - (EVI_Main, ppReport, 2140) - (EVI_Main,
ppProd, 2076)
(EVI_Main, ppProd, 1890) - (EVI_Main, ppProd, 1613) - (EVI_Main,
ppProd, 1597)
(EVI_Main, ppReport, 1204) .............

--


Hint: We altered the sources!Hint: We altered the sources!

nicocizik

Hi Carsten,

This is not a known issue. Is there something specific about these
customers' setup or reports that could be causing this? Are you able to
recreate this behavior on your machine?

If so, please create a simple example we can run here so we can research
a solution for you.

--

rbuser

Just send an email to support with a detailed analysis of the code

Nico Cizik (Digital Metaphors) stellte die Frage :

--


Hint: We altered the sources!Hint: We altered the sources!