Diese Seite mit anderen teilen ...

Informationen zum Thema:
WinDev Forum
Beiträge im Thema:
Erster Beitrag:
vor 1 Jahr, 11 Monaten
Letzter Beitrag:
vor 1 Jahr, 10 Monaten
Beteiligte Autoren:
StanleyBarnett, GuenterP, Al

Why, Not enough storage error in analysis generation?

Startbeitrag von StanleyBarnett am 29.06.2016 06:12


When closing WinDev it asks to sync and I say Yes. The I get a dialog named "Analysis Generation" with these details...

Unable to load wdmod210.dll DLL
System Error Details:

Not enough storage is available to process this command.

So how much does it need? My C:\ has 45.7gb free and my d:\ has 95.9gb free...

Take a look...

[attachment 2065 Picture0001.png]

Thanks, Stanley


Hi, wdmod210.dll is the dll which does the work of wdmodfic.exe (restructuring the data files). It has not enough RAM memory for loading and execution. How much RAM has your computer? Have a look into Task Manager.Are you using the 32-bit or the 64-bit version of WD? It's recommended to use the 32-bit version.

von GuenterP - am 29.06.2016 06:51
Hi Guenter,

I'm using the 32bit version of Windev 21 on Windows 10pro64 with 8gb ram. 8GB should be more than enough. If not, then how much is needed?

Are there any recommendations or worksheet to determine the correct amount?

Thanks, Stanley

von StanleyBarnett - am 01.07.2016 03:39
Hi Stanley, this is strange indeed. If you have only 100 or 200 files in your analysis, this should be considered lightweight. Did you try to repair the analysis already? In the Analysis Tab of the IDE there's an item Maintenance and in its menue you can fin "Reapir the Analysis". If the problem stays in spite of repairing it then please contact PC Soft Tech Support!

von GuenterP - am 01.07.2016 04:57
Hello Stanley

The other thing to try is to just open the analysis on its own rather than via it's associated project.
You can open do this either by double click on the .wda file in the analysis folder or from Windev using the File >Open menu. if either of these methods work, then just something in a file and regenerate.


von Al - am 01.07.2016 05:06
Hi Guenter,

If you have only 100 or 200 files in your analysis

Good to hear, I have 40 tables in the analysis...

Did you try to repair the analysis already?


Importing MSSQL tables into my analysis has been nothing but problematic and unreliable for me. I have yet to see a successful import from a MSSQL database to a HFSQL database vis WinDev's import functions. Errors, crashes and crashes.

The import did add some data and then crashed saying it cannot get to the source data. Attached is a screenshot showing the error dialog, then the CRASH dialog, and finally Windows explorer's list showing that it did get some of the data imported.

Is there anything in a MSSQL table that would cause WinDev to crash as shown?

[attachment 2074 Picture0002.png]


von StanleyBarnett - am 03.07.2016 06:01
Hi, I'm sorry, I do not have a lot of experience with external databases. However ..

... did you first import the MS SQL data structure into the analysis?
... what is the type of connection to the MS SQL database? Native Access, ODBC, OLE DB?

von GuenterP - am 03.07.2016 08:23
did you first import the MS SQL data structure into the analysis?

Yes with 2gb and type (classic and c/s) issues... see new message thread addressing them...

... what is the type of connection to the MS SQL database? Native Access, ODBC, OLE DB?

I've tried Native Access and it appears that it is broken as it errors with erroneous errors. I'm having better results with OLE DB, but don't know how to get past the 2gb limit as all import functions is only creating 2gb max classic files, (which is also the subject of the newly started thread)

Thanks, Stanley

von StanleyBarnett - am 03.07.2016 08:59
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.