Page 1 of 1

Chromera software not opening!

Posted: Wed Jun 14, 2017 6:54 pm
by vanene1313
Hello Everyone,

My university has a Perkin Elmer Flexar LC coupled to a Perkin Elmer AxIon2 TOF MS instrument and we run them on Chromera software and TOF MS Driver software. Everything was working fine last week, but now I cannot even get the software to open! My university does not have a maintenance program for this instrument, so basically I have to try to troubleshoot to fix it myself. I am wondering if anyone has any ideas I could try? I have already tried the following:

-Restarted computer several times; program still does not open (task manager does not even list it as "not running"...task manager is blank).

-The space available on the computer was near full so I moved 50 gigs worth of files onto an external hard drive to make room. Program still doesn't open or show up in task manager.

-I checked CPU usage and it seems to be around 5-15%, so I do not think it has to do with that

-I am not super computer savvy and that about exhausts my knowledge of trouble shooting on the computer. I have emailed Perkin Elmer, and I am waiting to hear back from them. Plus, I do not know if they will even get back to me or help me without a fee. I am a recent Undergrad graduate who just officially started a grad program. My experience/ trouble shooting skills on this instrument are basic at best.

Thanks in advance for any suggestions!

-Vanessa

Re: Chromera software not opening!

Posted: Thu May 03, 2018 7:44 pm
by ranasaad08
Let me know if you are still facing the issue

Re: Chromera software not opening!

Posted: Sat May 05, 2018 5:26 pm
by antonk
Got a very similar issue with Chromeleon after installing! another! program.

At some point I relaized (from system log) that it cannot find MS VC++ 2011 runtime (which were installed) but after this the VC++ 2012 runtime installed too.
I have to find 2011 MSVC redistributable and reinstall it again.

In 21st century modern Windows should have 2005 to 2016 (in a year step) VC++ runtimes installed and carefully managed.
Of course C# application have their own .NET 3.5 ... 4.x installed (do not mix 3.5 and 3.51).

Welcome to the "DLL bundle hell" instead of "DLL hell" the MS wanted to manage.