DMXControl 2.12 crashing on start up

We proudly present: The release of DMXControl 3.3.3!


On September 29, 2026, we held our release show for DMXControl 3.3.3. During our usual “hour-long” session, we showed you all the new features in this version and what it now has to offer.
Read all about it in the corresponding news article: We proudly present: The release of DMXControl 3.3.3!

    I have DMXControl 2.12 working fine for about a week. Then I installed Q Light (another lighting control software) and now when DMXControl starts, it crashes with a message

    "Error during activiation of plugin 'Enttec DMX Pro Driver': Error 2147417848: Method '~' of object '~' failed. Try again?"

    Quote

    The Windows 'problem details' says


    I am using Windows Vista, DMXControl 2.12.2 with Enttec USBDMX Pro.
    I have uninstalled Q Light, uninstalled DMXControl, rebooted, re-installed DMXControl - same problem. I have reinstalled the FTDI driver, rebooted, reinstalled DMXControl. Done all that twice. :argh:

    Any ideas on how to get this working? I have a show to rig and plot next Tues.
    Thanks
    Paul

    Edited once, last by paulthom (January 14, 2016 at 11:26 AM).

    Hi,
    there is a error log file in the DMXControl folder (DMXControl.EPT). Can you zip it or change the file extention to .txt and add it here.
    Regards
    JP

    im Falle eines Falles klebt Gaffa einfach alles, denn Gaffa ist dein Freund und Helfer :thumbup:

    I can see any file called DMXControl.EPT in folder C:\Program Files (x86)\DMXControl or anywhere else on C: when I searched.
    could it be something else?

    Is there some command line switch I need to use to get it dump the error log?

    thanks
    Paul

    Edited once, last by paulthom (January 14, 2016 at 11:49 AM).

    Update: Ran the Plugin Administrator (comes with DMXControl) and this ran,
    selecting DMXUSB Pro and clicking Configure Plugin button did nothing.
    so I unchecked the Enttec DMXUSB Pro (#9) and exited the program.

    Now DMXControl will start but when I go to Settings menu and select Output Plugins the entire list says "Plug in not supported"

    I can't find the place where the configuration of plugs is stored (file? registry?)

    The error file should be generated automaticaly. When not, DMXControl can not write to its Directory (the Windows UAC prevents this). In this case the error file should be in C:\Users\[your Username]\AppData\Local\VirtualStore\Program Files (x86)\DMXControl

    Plugins: DMXControl needs adminrights to initialize the plugins. But this would lead to the effect that one have to start DMXControl with admin rights on every start. To solve this problem, there is the plugin administrator. This program initializes all plugins with the required admin rights and you do not need to start DMXControl with admin rights. Thats the reason, why there is a plugin administrator. But to work properly (DMXC can see the plugins and suport them), all interfaces should be checked in this program.

    im Falle eines Falles klebt Gaffa einfach alles, denn Gaffa ist dein Freund und Helfer :thumbup:

    Ah yes, here is the error file, from C:\Users\user\AppData\Local\VirtualStore\Program Files (x86)\DMXControl
    also attached with cfg file from same folder as zip file.

    When I have all the output plugins check in the Plugin Administrator, DMXController crashes on start up (even if Run As Administrator). When they are unchecked in Plugin Administrator the program will start the the Output Plugin menu says <Plugin not supported> to everything.

    I tried reinstalling again in different directory but the problem is the same. Here is the error file:

    Thanks

    ----------------------------------------------------------------------
    F E H L E R P R O T O K O L L
    ----------------------------------------------------------------------
    DMXControl V2.12.2 - Fehlermeldung
    ----------------------------------------------------------------------
    FEHLERBESCHREIBUNG
    Fehler-Nr: 340 (Control array element '1' doesn't exist)
    Modul: frmFormParser
    Prozedur: cmdCtl_Click
    Zeilen-Nr.: 50080
    Datum/Uhrzeit: 01-09-2016 / 12:14:33
    ----------------------------------------------------------------------
    CALLSTACK
    ----------------------------------------------------------------------
    SYSTEMINFO:
    Plattform: Windows NT
    Version: 6.0
    Build: 6002 Service Pack 2
    ----------------------------------------------------------------------


    ----------------------------------------------------------------------
    F E H L E R P R O T O K O L L
    ----------------------------------------------------------------------
    DMXControl V2.12.2 - Fehlermeldung
    ----------------------------------------------------------------------
    FEHLERBESCHREIBUNG
    Fehler-Nr: 340 (Control array element '1' doesn't exist)
    Modul: frmFormParser
    Prozedur: cmdCtl_Click
    Zeilen-Nr.: 50080
    Datum/Uhrzeit: 01-09-2016 / 12:26:19
    ----------------------------------------------------------------------
    CALLSTACK
    ----------------------------------------------------------------------
    SYSTEMINFO:
    Plattform: Windows NT
    Version: 6.0
    Build: 6002 Service Pack 2
    ----------------------------------------------------------------------


    ----------------------------------------------------------------------
    F E H L E R P R O T O K O L L
    ----------------------------------------------------------------------
    DMXControl V2.12.2 - Fehlermeldung
    ----------------------------------------------------------------------
    FEHLERBESCHREIBUNG
    Fehler-Nr: 340 (Control array element '1' doesn't exist)
    Modul: frmFormParser
    Prozedur: cmdCtl_Click
    Zeilen-Nr.: 50080
    Datum/Uhrzeit: 01-09-2016 / 12:26:24
    ----------------------------------------------------------------------
    CALLSTACK
    ----------------------------------------------------------------------
    SYSTEMINFO:
    Plattform: Windows NT
    Version: 6.0
    Build: 6002 Service Pack 2
    ----------------------------------------------------------------------


    ----------------------------------------------------------------------
    F E H L E R P R O T O K O L L
    ----------------------------------------------------------------------
    DMXControl V2.12.2 - Fehlermeldung
    ----------------------------------------------------------------------
    FEHLERBESCHREIBUNG
    Fehler-Nr: 340 (Control array element '1' doesn't exist)
    Modul: frmFormParser
    Prozedur: cmdCtl_Click
    Zeilen-Nr.: 50090
    Datum/Uhrzeit: 01-09-2016 / 12:26:26
    ----------------------------------------------------------------------
    CALLSTACK
    ----------------------------------------------------------------------
    SYSTEMINFO:
    Plattform: Windows NT
    Version: 6.0
    Build: 6002 Service Pack 2
    ----------------------------------------------------------------------

    Hi JPK
    Is there any update on this?
    I imagine as it was working and then stopped after I installed another VB program, it might be a clash of DLLs, related to the permission enhancement needed for control of the plugins.
    I really like DMXControl, it does things in a reasonable sensible manner, so I would like to get this fixed.
    Thanks.

    Hi,
    sorry, I was busy the last days and couldn't try to find some solutions for you. There is an exam on Wednesday and some other stuff to do this week. But I try to find some time (maybe on weekend).
    Regards
    JP

    im Falle eines Falles klebt Gaffa einfach alles, denn Gaffa ist dein Freund und Helfer :thumbup:

    The settings of the plugin probably will be in the registry in the "HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DMXControl\Plugins" hive.
    That DMXC shows "unsupported plugins" when they are disabled in the plugin administrator and DMXC is run without admin priviledges is perfectly normal - that is what the plugin administrator is for.

    Stefan

  • Newly created posts will remain inaccessible for others until approved by a moderator. The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.
    • :argh:
    • :shit:
    • :)
    • :(
    • ;)
    • :P
    • ^^
    • :D
    • ;(
    • X(
    • :*
    • :|
    • 8o
    • =O
    • <X
    • ||
    • :/
    • :S
    • X/
    • 8)
    • ?(
    • :huh:
    • :rolleyes:
    • :love:
    • 8|
    • :cursing:
    • :thumbdown:
    • :thumbup:
    • :sleeping:
    • :whistling:
    • :evil:
    • :saint:
    • <3
    • :!:
    • :?:
    • :glaskugel: