Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error #1502: A script has executed for longer than the default timeout peri

I'm getting an error 1502 when opening my Xcelsius file with Adobe's Flash 9 Player debugger installed.

Adobe flash describe this error as follows:


1502 A script has executed for longer than the default timeout period of 15 seconds. A script executed after the timeout period. (The default timeout period is 15 seconds.) After this error occurs, the script can continue to execute for 15 seconds more, after which the script terminates and throws run-time error number 1503 (A script failed to exit after 30 seconds and was terminated.)

1503 A script failed to exit after 30 seconds and was terminated. The script was still executing after 30 seconds. Flash Player first throws run-time error number 1502 (A script has executed for longer than the default timeout period of 15 seconds.) if the script executed more than 15 seconds, which is the default timeout period. This error occurs 15 seconds after Error 1502 occurs.


But how do I indentify which script or component in my Xcelsius file that is causing this error? My full error message is as follows:


Error: Error #1502: A script has executed for longer than the default timeout period of 15 seconds.

at mx.managers.layoutClasses::PriorityQueue/contains()

at mx.managers.layoutClasses::PriorityQueue/removeLargestChild()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\layoutClasses\]

at mx.managers::LayoutManager/validateClient()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\]

at mx.core::UIComponent/validateNow()[E:\dev\flex_201_borneo\sdk\frameworks\mx\core\]

at xcelsius.controls::DialGaugeBase/resizeUniformly()

at xcelsius.controls::DialGaugeBase/updateDisplayList()

at xcelsius.controls::Gauge/updateDisplayList()

at mx.core::UIComponent/validateDisplayList()[E:\dev\flex_201_borneo\sdk\frameworks\mx\core\]

at mx.managers::LayoutManager/validateDisplayList()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\]

at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\]

at Function/

at mx.core::UIComponent/callLaterDispatcher2()[E:\dev\flex_201_borneo\sdk\frameworks\mx\core\]

at mx.core::UIComponent/callLaterDispatcher()[E:\dev\flex_201_borneo\sdk\frameworks\mx\core\]


Former Member

I can't say exactly what is big binding because it depends on combination of factors: how fast your machine is, how big the Excel model is, how many components you have etc. Generally if you have bindings with several thousand cells it's going to cause the timeout problem. The problem is that we use Flash player in the application, and if some operation takes longer than a minute it times out. So, if getting data from the big bindings took too long, the flash player stops the operation and you have this timeout error.

You see the timeout error only if you have debug version of Flash player installed. If you have release version installed, you don't see any erors, but you notice strange things, for example selecting component on the canvas does not cause property sheet to display. Release version of Flash is faster, so you can try to remove debug flash player and install release and there is chance that it will work.

FP1 version is going to include some optimisations to reduce this problem and allow working with larger files.


0 View this answer in context

Helpful Answer

Not what you were looking for? View more on this topic or Ask a question