[SOLVED] Can´t execute new 2.2.0 version

Any issues related to FORScan application
Post Reply
carlus
Posts: 80
Joined: Sun Jul 13, 2014 9:15 am
Vehicle: MAZDA CX7 MZR CD 2.2 2010
Location: Spain

[SOLVED] Can´t execute new 2.2.0 version

Post by carlus »

I install a new version but when i try to run, i can´t. A problem ocurr.

SO: Windows 7 64 bits.

The program install correctly but when i execute it, apperas this windows:

Image

More information?

Thanxs.
Last edited by carlus on Wed Jan 07, 2015 6:33 am, edited 1 time in total.
MAZDA cx7 diesel
carlus
Posts: 80
Joined: Sun Jul 13, 2014 9:15 am
Vehicle: MAZDA CX7 MZR CD 2.2 2010
Location: Spain

Re: Can´t execute new 2.2.0 version (problem)

Post by carlus »

More information.

I just installed the version 2.1.24 and it works perfectly.
MAZDA cx7 diesel
FORScan
Site Admin
Posts: 2970
Joined: Fri Jun 13, 2014 2:21 am

Re: Can´t execute new 2.2.0 version (problem)

Post by FORScan »

We will investigate this problem as soon as possible.
carlus
Posts: 80
Joined: Sun Jul 13, 2014 9:15 am
Vehicle: MAZDA CX7 MZR CD 2.2 2010
Location: Spain

Re: Can´t execute new 2.2.0 version (problem)

Post by carlus »

FORScan wrote:We will investigate this problem as soon as possible.
OK, I just found a solution to it, until the team forscan the solvent with a new version.

If we have installed a previous version of forscan program and have connected the program with our car, we must manually delete the temporary directory forscan application before installing the new version 2.2.0. In my case, this temporary directory is: c:\users\username\AppData\Roaming\FORScan

A greeting.
MAZDA cx7 diesel
Holger

Re: Can´t execute new 2.2.0 version (problem)

Post by Holger »

Hello Carlus,

I ran into the same error after installing the new version.

Thank you for your information, it solved my problem too :-)
In my case it was only necessary to delete the file settings.ini.

Greetings

Holger
FORScan
Site Admin
Posts: 2970
Joined: Fri Jun 13, 2014 2:21 am

Re: [SOLVED] Can´t execute new 2.2.0 version

Post by FORScan »

We have released version 2.2.1 that should have this problem fixed.
Post Reply