Scheduler crashes

This year (for the first time) I've had unexpected scheduler shut downs.

Always at different times during the show, and always different songs.

Here is the latest from the log file.

Aurora Error Encountered at 9/20/2010 8:12:33 PM
Debugging Information:
339: Component '' or one of its dependencies not correctly registered: a file is missing or invalid
Refresh Grid  
AuroraSequencer



Aurora Error Encountered at 9/20/2010 8:12:36 PM
Debugging Information:
339: Component '' or one of its dependencies not correctly registered: a file is missing or invalid
frmMain Loaded  
AuroraSequencer

System is WinXP - version is 69.. (or the scheduler shows 68)

D-lights hardware (ac16 & fireflies)

Still running 1.17 and 2.0 firmware.  (Hard to think it's a firmware issue though.)

Any ideas where I should start looking?  Is another piece of software running in the background starting up and interfering?

Many Thanks!
Bob P.

I just double checked, and yes, all are .wav files.

Last night the crash occurred towards the end of the third loop of the show.  Aren't all conversions done and cached before the scheduler starts?

If it happens again, I'll try to get the error message that displays on the screen.  (I haven't caught it before because I'm having to do the ctl-alt-del method to close the program as well.)

Thanks for the advice!
Bob

Yes. 

I did see another post today that mentions double clicking the window.  I'll try that tonight.

Well, the double click does minimize the video screen, giving access to the scheduler screen, allowing a 'proper' shutdown.

And....  The show ran perfectly tonight.  (of course it has for several nights in a row in the past week as well.)

I did make one 'shift' in the system tonight, and we'll see what happens in the following nights.

And I'll say again, thank you all for your help!

Cheers!
Bob P

Error 339 is almost always a bad installation.  Those experiencing error 339 about component registration should do a complete reinstall of Aurora.  Follow this procedure exactly:

0) Backup all sequences

1) From the Control Panel Add/Remove Programs (not from the Aurora uninstaller), remove every copy of Aurora that shows up there.

2) Reboot

3) Install the latest version of Aurora

4) Reboot again

The two reboot steps are necessary to prevent the Windows MSI installer cache from "protecting" old files that it incorrectly thinks should still be present.  Failure to follow these steps results in Aurora functioning with a crazy mix of components from its various versions.  Even when it works the behavior can be unpredictable.  Error 339 can happen when Aurora needs something that a newer version of the component provides, but the installer pulled a "protection" switch and forced the old version to persist. 

The only other condition of error 339 is when another software product has switched out an Aurora third party dependency with an older version (such as videoedit.ocx, etc.).

The good news is that error 339 will be a thing of the past once we roll out the next version.  The MSI installer is going away in favor of a registration free installation (completely portable, can even run from a USB drive without installation).  Before public release we will be fixing the errors surrounding file format conversions that have been the big issue this season.

As for the midnight show start bug, even if you roll back to a pre-69 version that used to not do this, you will find that it does now.  This bug began when a Windows Update altered a Windows API in a way that broke Aurora.  I highly do not recommend running older versions of Aurora as not only do they not contain this bug fix, they also are not stable with modern firmware releases and do not contain fixes for bugs which led to data corruption.

Michael


Edited by LightsOnLogan - 20 Dec 2011 at 7:48am