9 Replies Latest reply on Oct 26, 2009 2:08 AM by konecnym

    Insufficient Memory

      I'm currently running SafeBoot 5.1.3 on Win7, which has been working great for 2 weeks.

      This morning I saw the following, but only on one sync.

      5/21/2009 11:11:27 AM Starting synchronization
      5/21/2009 11:11:27 AM SbFs total space = 20879360 bytes (19.91 MB)
      5/21/2009 11:11:27 AM SbFs free space = 17545216 bytes (16.73 MB)
      5/21/2009 11:11:27 AM Connecting to database: "<SERVERNAME>"
      5/21/2009 11:11:27 AM Address=<IP>
      5/21/2009 11:11:27 AM Port=<Port>
      5/21/2009 11:11:27 AM Authenticate=Yes
      5/21/2009 11:11:27 AM Checking for machine configuration updates
      5/21/2009 11:11:27 AM Checking for user updates
      5/21/2009 11:11:29 AM Error [e0050043]: Unable to open client data store attribute
      5/21/2009 11:11:29 AM Checking for hashes updates
      5/21/2009 11:11:31 AM Error [e0050043]: Unable to open client data store attribute
      5/21/2009 11:11:31 AM Transferring local audit information to database
      5/21/2009 11:11:31 AM Checking for file updates
      5/21/2009 11:11:31 AM Applying configuration
      5/21/2009 11:11:33 AM Synchronization complete
      5/21/2009 11:11:33 AM Automatically synchronizing again in 60 minute(s)
      5/21/2009 11:11:33 AM Applying cryption changes

      Now every sync I get the following. But I haven't received any additional e0050043 errors.

      5/21/2009 11:28:13 AM Transferring local audit information to database
      5/21/2009 11:28:13 AM Error [e0000001]: Insufficient memory

      The device has 1.5GB of RAM, only about half is being used. Any thoughts?
        • 1. RE: Insufficient Memory
          known issue resolved in later releases I believe. you should migrate to the current release when possible.
          • 2. RE: Insufficient Memory
            Thanks, I'm starting to hear that more and more. Guess it's a hint happy
            • 3. RE: Insufficient Memory
              sorry we keep fixing things happy
              • 4. RE: Insufficient Memory
                We had that problem on that version, but it went away as soon as we deployed 5.1.7 to the clients (fixed old and stopped creating new occurrences).
                • 5. RE: Insufficient Memory
                  I had the some problem. (we have EE 5.1.9)
                  I solved ....

                  1) decrypt (from console ... move to Decrypt group...decrypt disk and remove EE)
                  2) restart
                  3) run -> reinstall by file EEPC.exe
                  4) restart
                  5) OK

                  I think that error was in the files in root SafeBoot.fs or SafeBoot.rsf

                  • 6. RE: Insufficient Memory
                    You could have also resolved by setting the client to disable, then enable (after it had finished disabling itself), or by doing an eBoot (no decryption required).
                    • 7. Disable options = decrypt
                      OK. But...

                      I created copy from my group and i set Disable in general options .
                      I synchronized PC with error ": [e0050043] Client data store attribute not open"
                      (McAfee KB dont help)

                      And then stasus was changed to decrypt ....

                      After decrypt HDD was disabled pre-boot but software EE wass still on PC.
                      I restarted PC.
                      Then I moved PC back (to my standard group with Enable)
                      I synchronized PC.
                      After this step was PC encrypt and error wasn´ t there.

                      (When i tested only disable and syncrhronize and enable and synchronize error was still)

                      • 8. RE: Disable options = decrypt
                        your two situations seem identical - what's different about them?

                        but, disable/enable is all you need to do - you need to force a SBFS rebuild.
                        • 9. RE: Disable options = decrypt
                          We have about 200 NTB with EE.
                          We used EE about 2 month.
                          We will can migrate to 2500 NTB.

                          This problem we solved twice.
                          And we have to decrypt 80-160 GB HDD and again encrypt.
                          This is too much (CPU/HDD/user) time.

                          This problem is from synchronise.
                          Some discusion says " Longer synchonize time = better save for SBFS"
                          But we have to actual password in SBFS DB.
                          We have set 120 min without sync files.

                          There is not any SBFS backup ?
                          (For example ...when i synchronize and it is in half process and i switch off NTB ...)
                          Will by SBFS demaged or copy restore from some backup ?...

                          We are interested in how error arises as to prevent ..., the solution is now clear.


                          Sorry for my ENG happy