Pack&Go problem

[emef]

Hello everyone,
this day, problems with "Pack & Go" at the end of IMatch: whether it is to save my base on the internal disk (SSD) or on an external disk (USB3), P & G informs me that it is impossible for him to access the base (see screenshot). But, when I open it, IMatch works well    
An idea maybe?

[Mario]

Please look at the protocol file for additional warnings or errors.
Make sure your anti-virus is not acting up and that there is enough disk space (at least 3 times the database size) available and that the database has no errors.
The protocol file will tell us more.

[emef]

Thank you Mario.
Attached is one of the files created during the problem, I hope this is the one you expect.

[Mario]

This is the diagnosis log file. Please attach the protocol file.

Tip: The name of the protocol file is displayed right at the top in your screen shot (... IMatchPackAndGo.txt). You can open it by clicking on that link in the Pack & Go dialog.

[emef]

  Oups !

[Mario]

Since the diagnosis log file is OK and the protocol file only reports "optimization failed", I guess there is not enough disk space and the database system aborts the optimization because of that. Did you check the disk space as I explained in my post above?

[emef]

Yes of course. My base is on the disk "H", a 700 gigabyte SSD with nearly 514 gigas of free.   

[Mario]

The database compact is an atomic database operation, it either succeeds or fails.
Since this usually does not fail, Pack & Go don't report any additional error.

Can you run a Compact & Optimize for that database from within IMatch (Database menu > Tools > Compact & Optimize)?

[emef]

Yes, I have done this many times since this problem started and everything is going on normally, without a warning message.

[Mario]

Try to place the Pack & Go package on another drive, e.g. H: instead of I:

[emef]

 Alas, same punishment. Pack & Go forfeits.   

[Mario]

No idea, sorry.
Is your TEMP folder on drive c:? If so, how much disk space is available on C: ?

If the compact works in IMatch, just disable it for Pack & Go. Keep the diagnosis enabled, though.

[emef]

My "temp" folder for downloading or decompressing some files is on the "G" disk, with about fifty gigabytes of free. Nevertheless, the "log" messages of IMatch are under "c: \ Users \ emef \ AppData \ Local \ Temp \" and there I have more than a gigas and a half of free. I do not know exactly where IMatch is compressing and optimizing its base: on "c" or "G"?
Anyway, I ordered a bigger SSD to replace the "C" ... but it had never been a problem before.   

[Mario]

The database system may utilize the TEMP folder on your system, which is most likely on your C: drive.

You can open the TEMP folder by typing

%TEMP%

into the Windows Explorer address bar.

1.5 GB is very little disk space. This is not good for Windows, and most likely not enough for the database system to compact the database.
Maybe you can free up space by running the Windows disk cleanup from the START menu for your C: drive. This built-in Windows utility deletes old files from the temp folder and other hidden folders on the system drive.

[emef]

I made room with disc cleaning, but I could only win one and a half gig. Others test on Pack & Go tomorrow. Thanks for the help.

[Mario]

You can use a tool like the free TreeSize (https://www.jam-software.de/treesize_free/) to find out which files take up the most space on your disk.

[lbo]

You can use a tool like the free TreeSize (https://www.jam-software.de/treesize_free/) to find out which files take up the most space on your disk.

Or 1/10 the size, open source: https://windirstat.net/

[Jingo]

You can use a tool like the free TreeSize (https://www.jam-software.de/treesize_free/) to find out which files take up the most space on your disk.

+1... one of the first programs I install on a new system... there is even a portable version out there which I use on a USB stick to review space concerns on client devices... very useful software!

[emef]

Hello everyone,
sorry for the delay. Rectification of my previous post: concerning the Windows cleaning tool to regain space on my disk "C", I thought I had only won about 1 gig, but the next day, when I started the Windows computer told me that he took care of the updates and worked for about 20 minutes before handing me his hand ... and there, I realized that he had made +/- 11 gigas of free (by erasing the updates made, the temporary files and other things) ... In short, my SSD of 128 gigas (C) now includes a free space of +/- 10%, and I do not seem to have any problems with Pack & Go anymore   .
Thanks again to you and ... see you next time ;-)

[Mario]

So it was indeed "extremely low disk space on the drive hosting TEMP". You should never let the disk space get that low. This is not good for the SSD and not for Windows. A major Window update (like in your case) can easily occupy 10 or 15 GB (so you can roll-back to the previous version when you run into trouble). And on a tiny 128 GB SSD this is a lot.

Thankfully SSD storage has become very cheap and with the tools provided by the disk vendors you can easily migrate a "live" Windows installation from a small SSD to a 256 or (better) 512 GB in an hour and for less than 100US$ 

[emef]

Exactly, I'm waiting for the arrival of a Samsung 860 512 gigas SSD that I ordered to replace my "C". He should be here tomorrow   

[Carlo Didier]

So it was indeed "extremely low disk space on the drive hosting TEMP". You should never let the disk space get that low. This is not good for the SSD and not for Windows. A major Window update (like in your case) can easily occupy 10 or 15 GB (so you can roll-back to the previous version when you run into trouble). And on a tiny 128 GB SSD this is a lot.

Actually, for one of the next major updates of Windows 10 (probably the version 1909), Microsoft will introduce a feature to reserve at least (!) 7GB on the system drive for updates. Outside of updates, this space can be used for temporary files, but before installing updates it will be cleaned.

[emef]

The new disc has arrived; Cloned the old with "Data Migration" from Samsung ... and everything rolls.
So, I have 321 gigas of free on the "C".