My problem is simple - I was going to edit one of my mockups and I received information about an update to install. I've mad the update and that's when problem started - Indigo Studio don't launch anymore. Window appear for a second and then disappears.I've tried to restart both the Studio and OS, I've reinstalled Adobe AIR and Indigo Studio.Nothing helped. Hours of work for nothing, so I really need to find a solution. Worst, that I can't continue my work.
Additional info:Adobe AIR 3.7Windows 7(I'm sorry to bother you both on forum and support, but I thought maybe someone here have the same problem)
Hi Anna,
Could you try downloading the installer from the website again, uninstall and reinstall?
BTW, Indigo uses Silverlight, not AIR ;), but if it worked previously, you should have the right version installed.
Thanks,
Andres
aaguiar said: Could you try downloading the installer from the website again, uninstall and reinstall?
Yes I've done it - I have reinstalled both Silverlight and Indigo Studio. Still without a result. I'm running out of ideas how to solve that...
aaguiar said: BTW, Indigo uses Silverlight, not AIR ;), but if it worked previously, you should have the right version installed.
Sorry, haven't noticed that.
Are you running Indigo with the same user as you install it? Do you get prompt to enter administrative credentials to install it?
Other things to try:
- Clear you Internet Explorer cache- Delete the contents of C:\Users\<your user>\Documents\Indigo Studio\Settings
Also, please send us the logs in C:\Users\<your user>\Documents\Indigo Studio\logs to indigo@infragistics.com
Thanks!
And, try deleting C:\Users\<your user>\Documents\Indigo Studio\Update
I'm resurrecting this thread.
I just installed the latest version (update 13) of Indigo Studio after using it for the past few months. I was excited to experience the bug fixes it was touted to contain. After installing update 13, Indigo stays open for about 30 seconds and then either crashes or just disappears.
I have followed all of the directions in the prior posts on this thread. I have cleared IE cache, deleted the contents of all Indigo Studio folders in Users/Documents, uninstalled Indigo and Silverlight and reinstalled.... Indigo just keeps crashing. I can't keep it open for more than 30 seconds. It will even crash if I just let it sit there after opening.
I'm stuck. I attached the log files for review.
Thanks for the help.
Hi Lance,
I'm sorry to hear that!
Could you try checking the content of the registry entry at HKEY_CURRENT_USER\Software\Infragistics\Indigo\Port?
What number does it have?
Can you try changing it to a number that points to a port that is not being used in your PC? Try 1234 for example.
If you manage to do all of that, please end me the logs again.
Thanks a lot!
Sure. I changed it from 58063 to 9550. Same crash. Logs attached.
Thanks for looking into this.
-- Lance
Ah, found it. Updated it. Problem solved! The usual crash has not recurred since updating 'DisplayLink Core Software' to version 7.3.49122.0 (12 Jul 2013).
Thanks for all your help troubleshooting this. Now I can get back to work.
Cheers!
I haven't any idea what 'DisplayLink Core Software' is. A quick search of my computer found nothing by that name. Can you help me to locate it?
Thanks.
A long shot:
In this version we are using "Chromium Embedded Framework" to host the HTML5 prototypes.
I found a similar issue reported in their forums:
http://www.magpcss.org/ceforum/viewtopic.php?f=6&t=10840
They say:
"The DisplayLink driver dlumd32.dll seems to be the common culprit. Both machines had 'DisplayLink Core Software. Product Version: 5.6.31854.0' installed. We've since updated the display link driver on the second machine, and removed it from the first (which wasn't actually using one of the USB Graphics adapters), and CefClient is now stable on both machines. "
Do you have by chance installed that 'DisplayLink Core Software'? If so, could you try updating it?
Thanks Lance!
The crash is in nvwgf2um.dll, which is the NVidia Driver. This is gonna be fun ;)
There were two error logs for each crash. I've included the logs in evtx and xml formats.