Skip to main content

Message: "Initialization Error. Code -7" (Windows)

Author cognitone

This content is for an older version of Synfire. The current version is more streamlined and advanced, but most of the functionality shown here still exist.

If you encounter the error message "Initialization Error. Code -7" on Windows, this may indicate a conflict with some security or  defense utility. Reportedly, this was the case with the product "Emsisoft Online Armor", but it may also occur with other products (Panda, Comodo, etc).

Disabling the utility during Installation, or, if possible, excluding (white listing) Synfire in its settings will solve the problem. 

If you are running Synfire, please also make sure you have the latest PACE iLok drivers installed. The people at PACE are very responsive and issues that arise from conflicts third party products usually get fixed quickly:

(http://www.ilok.com)

Comments

Thu, 2013-07-25 - 14:39 Permalink

I do experience this issue after having bought a license which is very unfortunate for this rather expensive software.
I spent a whole day uninstalling and reinstalling without any progress, and I'm getting tired.

 

I used msconfig > selective startup
tab services: select 'hide all Microsoft services' and disable all except for the PACE license service 

tab startup: disable all

rebooted, and (re)installed (first ilok license manager, on next reboot synfire, with ilok connected), to no avail....
still a pop-up 'initialization error: error -7' after all those reboots, even without any startup-service or program enabled (except for the microsoft services).

 

any ideas about how to troubleshoot this further ? How did the other users with this problem got it solved ?

I guess it's simple once you know which is the conflicting program, but in this case I even have the error without any programs started up during the bootsequence.

 

Is there any way to force 'verbose logging' while starting up to generate some more logging ?

 

Wim  :-/

 

 

Thu, 2013-07-25 - 16:25 Permalink

 

finally.... it was comodo firewall.... disabling the drivers was NOT enough. I had to uninstall it completely, and then... synfire started.  :-)

Now I only have to find a new free firewall.