Ticket #80 (closed defect: worksforme)
Viewer fails to initialize
| Reported by: | michelpons | Owned by: | michaelhalloran |
|---|---|---|---|
| Priority: | major | Milestone: | 2.0 No dependency/Viewer/New installer |
| Component: | Viewer | Version: | Development |
| Keywords: | Cc: |
Description
I am considering a scenario that involves ProSim Plus 3.1 and a UO made in VB provided by an end-user. I have installed COLTT 1.08.05 Build May 30, 2011 in the machine and I have run the simulation where the UO is logged with COLTT. The logging works apparently fine but I can't get the Viewer to open up. I get a message box titled \"COLTTViewer.exe - Erreur d'application\" and the message is \"L'application n'a pas réussi à s'initialiser correctement (0xc0000135). Cliquez sur OK pour arrêter l'application\".
Change History
comment:2 Changed 14 years ago by michelpons
According to Dependency Walker, MSCOREE.DLL is missing (still it shows up in C:
WINDOWS
ServicePackFiles
i386. I have noticed however that there is no .Net Framework installed on the target machine. Would this matter?
comment:3 Changed 14 years ago by michelpons
Further research: I moved the MSCOREE.DLL to C:
WINDOWS. Then the Viewer still does not load. Looking at the dependencies with Dependency Walker, it shows that IESHIMS.DLL and WER.DLL are mentioned with \"Error opening file. Can't find the file\". I have researched my entire disk for both DLLs and they can't be found.
comment:4 Changed 13 years ago by michelpons
With the 1.08.05 msi file dated July 17, 2011, I get the message \"This setup requires the .NET Framework 3.5\" at the installation start. Acknowledging the message I get a screen saying \"COLTT Setup Wizard ended prematurely\" as a title and then it explains that \"COLTT Setup Wizard ended prematurely because of an error. Your system has not been modified. To instal this program at a later time, run Setup Wizard again....\" As discussed on the phone on July 18, these messages appear sufficient and won't lead to further actions that are not sanctioned by installation regulations here or there. I still need to check that installing .NET Framework 3.5 indeed resolves the matter.