Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
11
Erster Beitrag:
vor 4 Jahren, 11 Monaten
Letzter Beitrag:
vor 4 Jahren, 11 Monaten
Beteiligte Autoren:
Geert Debruyne, Fabrice Harari, Joris, Arie

WD18 - stops working while generating a library

Startbeitrag von Geert Debruyne am 05.09.2013 07:47

project in Windev 18
When generating a library, Windev 1! stops working, generating a GPF...
Tried this on different PC's, project in/out of SCM: always the same problem...

Very annoyed because we need to deploy a now version.
Anyone has an idea how to solve this problem?

Antworten:

Hi Geert,

Are you sure there are not any references to network paths in your project?
Maybe something has changed (share name, password etc..)?

Kind regards,

Joris.

von Joris - am 05.09.2013 09:29
I'm very sure....there are no network paths etc in the project itself...

We dit try a lot of things to get a new version, but WIndev always crashes making a new library.
This is what I already tried:
-Creating on another PC (actually 3 PC’s!!!) (FAIL)
-Removing the project from the SCM (FAIL)
-Restoring a previous version of the project from the SCM (FAIL)
-Deleting the PCsoft registry (HKEY_CURRENT_USER\Software\PC SOFT) (FAIL)
-Creating new project an import everything: NOT POSSIBLE WINDEV CRASHES WHEN IMPORTING!!! (BIG BIG FAIL!)
-Check the version of windev (Using latest release)

Just to say: i'm really stuck here....

von Geert Debruyne - am 05.09.2013 12:11
Hi Geert

I see 3 things missing in your checklist:
- deleting the .cpl directory
- deleting the .env file
- using the "repair the project" option

Let us know if it helps

von Fabrice Harari - am 05.09.2013 12:55
Hi Fabrice
Thanks for the help,
I tried that 3 you listed up, but without any succes, generating the WLS always stops at 59% and Windev crashes then....

von Geert Debruyne - am 05.09.2013 12:59
Hi again

if it's always at the same place, then there is a good chance that you have ONE object broken (one window, one report, etc)... If I remember correctly, the currently processed object is displayed during the generation. Try and identify the last one showing, and REMOVE it from the project list... Once you know which one is guilty, replace it by a backup.

Best regards

von Fabrice Harari - am 05.09.2013 13:23
Hello,
i did tried this, but the object shown is not always the same....

Any other suggestions? Because i'm out of ideas..
Also tried to remove from SCM etc, nothing helps, WIndev keeps crashing (on all of the pc's we try it)

von Geert Debruyne - am 05.09.2013 13:28
Hi again

I do have another idea, but you're not going to like it...

Create a new project (empty) verify you can work with it normally
Replace the project file by YOUR project file and try again
Loop till it crashes
Import a "block" of files from YOUR PROJECT and try again
EndLoop

When you know in which block the crashes occurs, remove all but one of the object of the block,
loop till it crashes
Generate
Add one object of the block
EndLoop
At that point, you WILL know the guilty one (check that there is a SECOND broken file of course, but generally, it's only one) and you will be able to replace it in YOUR project by a backup

Best regards

von Fabrice Harari - am 05.09.2013 14:04
Hi Fabrice,
thanks for your help... let's say i thought of this as being the last option.... because this is such a huge project (200+windows...a lot of reports etc....) it will take up a lot of work; but i suppose i will have to go through this to get the problem solved because i looked for some kind of testing program to figger out which file is corrupt....but found none.

I'll try testing this out this evening....

Geert

von Geert Debruyne - am 05.09.2013 14:35
Geert,
empty the CPL map again and maybe it gives you a hint where the process stopped during the crash?
Assuming the compilation uses some kind of understandable order of processing?
Or maybe the bad object is already created there as the last one?

von Arie - am 05.09.2013 15:04
Hi Geert,

If Windev really fails on a certain file, maybe you can detect it using the process monitor :

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

You can set a filter so that only the actions of the windev process are listed. When it crashes you can see the last action(s) that where done.

Regards,
Joris.

von Joris - am 06.09.2013 11:14
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.