Hi,



Thanks everybody for your different ideas!!!!



I had the same problem on an other machine which was on Windows 10.



But finally I found a solution ant it's now OK. It's possible for me to execute my sources migrated from PB10.5 into APPEON2017 from APPEON2017 on my machine which is on Windows10.



The solution I found is :



I saved the application pbl in a specific folder. Then I constructed a new (workspace + target + application + application pbl ) from scratch. I added the old application pbl which has been saved into a specific folder in the library list of pbl defined into the target

and then I copied everyelements from the application corrupted pbl

to the new application pbl constructed from scratch. To finish I copied the script from the corrupted application object to the new application object just init with the constuction of the new (workspace + target + application + application pbl ).



And it's OK....



Kind regards,





Bertrand

Excellent news! :-)

Hi Tom,



As I explained to Chris, almost of my applications have migrated properly. I have only one with the problem that it's impossible to execute the sources from Appeon on Windows 10. On Windows 7, everything is OK.

I tried to install appeon on an other Computer with Windows 10 installed on and tried again to migrate from PB 10.5 sources to Appeon 2017 sources and I obtained the same problem.

Here is what I can see in the windows events :

Nom du journal :Application

Source : Application Error

Date : 02/08/18 09:45:10

ID de l’événement :1000

Catégorie de la tâche :(100)

Niveau : Erreur

Mots clés : Classique

Utilisateur : N/A

Ordinateur : LAPTOP-2VAM6D0C

Description :

Nom de l’application défaillante PB170.EXE, version : 17.0.0.1769, horodatage : 0x5aab7d21

Nom du module défaillant : MSVCR100.dll, version : 10.0.40219.1, horodatage : 0x4d5f0c22

Code d’exception : 0xc0000005

Décalage d’erreur : 0x00001ed7

ID du processus défaillant : 0x1b4

Heure de début de l’application défaillante : 0x01d42a34a2ac615d

Chemin d’accès de l’application défaillante : C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE

Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\MSVCR100.dll

ID de rapport : 87d8d210-c5dc-48c6-867d-c1eee8c2ef19

Nom complet du package défaillant :

ID de l’application relative au package défaillant :

XML de l’événement :







1000

2

100

0x80000000000000



2763

Application

LAPTOP-2VAM6D0C







PB170.EXE

17.0.0.1769

5aab7d21

MSVCR100.dll

10.0.40219.1

4d5f0c22

c0000005

00001ed7

1b4

01d42a34a2ac615d

C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE

C:\WINDOWS\SYSTEM32\MSVCR100.dll

87d8d210-c5dc-48c6-867d-c1eee8c2ef19















Thanks in advance if you have an idea. I can propose you to give the sourcesof the application (It's an application I get in maintenance in 2016 and that have somme years behind) to have a look.



Regards,



Bertrand

Thanks in advance.

If you copy the project that you successfully migrated to 2017 R3 using Windows 7 to your Windows 10 machine and open it there, do you get the same issue?

Just to clarify, do you mean that 2017 R3 crashes when you attempt to run the application?

I don't see where you said you did a FULL REBUILD after the migration. You should always do that after migration.

Hi Chris,

I had also no difficulties with other applications but this one... I don't undestand what's the problem.

I installed R3 with an upgrade. Il also had the same problem with R2. If I try with a Windows7 PC, it's OK but with Windows 10 I have the problem.

I you've got an idea to trace... (impoossible with classic debug tools) I accept it ;-)

If you want I can give you my sources...

Regards,

Bertrand

That would be great!



I would suggest though that you do that via opening a Support Ticket ... https://www.appeon.com/standardsupport