sbie 2102 error Chrome browser when I clicked file>open

Discussion in 'sandboxing & virtualization' started by The Count, Apr 17, 2020.

  1. The Count

    The Count Registered Member

    Joined:
    Jun 13, 2016
    Posts:
    171
    Location:
    France
    I got sbie 2102 error using Chrome browser when I clicked file>open, however Chrome did not crash, only the file>open box crashed and the error said:

    SBIE 2102 object name not found;
    error open Process (C0000022) access = 001FFFFF initialized = 1

    Thank you in advance.

    Chrome browser v 90.0.3987.163 (official build) 64 bit
     
  2. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    13,808
    Location:
    UK
  3. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    3,221
  4. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    5,649
    Location:
    Nicaragua
    Usually you get SBIE message 2102 when a file is larger in size than whats allowed by default to be copied into the sandbox.

    Your message 2102 doesn't look like a normal SBIE 2102 message. It looks more like an error than an information message (which is what 2102 really is). The message usually has the name of the file that Sandboxie wants to copy at the end of the first line in the message.

    You have three solutions.

    Ignore it. When I get that message, I usually ignore it. I can reproduce it in two activities I do regularly. And always ignore it, and can continue doing what I am doing.

    Increase the size. You do this in Sandbox settings>File migration

    Allow direct file access to the file. I think doing this is OK will files like in your email client that might require it, or programs like Firefox, but that's about it.

    Bo
     
    Last edited: Apr 17, 2020
  5. The Count

    The Count Registered Member

    Joined:
    Jun 13, 2016
    Posts:
    171
    Location:
    France
  6. The Count

    The Count Registered Member

    Joined:
    Jun 13, 2016
    Posts:
    171
    Location:
    France
    I never got a chance to pick a file large or small, never got to that step because in Chrome I went File>Open, a list of files popped up and and then the list just as quickly disappeared in a flash then almost simultaneously SBIE 2102 error popped up. I saw the list of files for a brief moment that's about it.

    Actually I have the same issue with Firefox.

    Never got a chance to pick a file name after File>Open (see above).


    So you are able to select a file and open within your SBIE Chrome browser without a glitch or error from SBIE like mine?

    I tried 721MB, clicked apply, but same problem persists.

    How would I go about this?
     
  7. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    5,649
    Location:
    Nicaragua
    Hi The Count. I am going to give you an example that hopefully will help you make sense of SBIE message's 2102. In this example I am running a Firefox.exe to upgrade my Firefox installation in a sandbox. As the upgrade runs, I get a message 2102. See the picture below. In the picture you see the name of the file (xul.dll) that's larger in size than what SBIE allows to be copied into the sandbox before they can be modified by sandboxed programs. By default files larger than 48 MB are not copied, but become read only (no changes will done to the file within the sandbox).

    xuldll.jpg

    In the screen below, you can see the File migration Window in Sandboxie that states that files larger than 48 MB will not be copied into the sandbox.

    48mb.jpg

    So, what to do? First, you need to realize that this message has nothing to with downloading a GB or 2 GB file or playing large videos or anything like that.

    The message has more to do with files like for example the DBase file for an email client that has become very large over the years. And if the SBIE user runs their email client sandboxed, to save new mails that are received or sent, then SBIE has to copy this DB file into the sandbox before the email client thats running sandboxed can make changes to the DB in the sandbox, and save the changes outside the sandbox.

    You might also get this type of message in situations like in my example. As I upgrade Firefox in the sandbox, Sandboxie encounters a file that Firefox wants to make changes to, but since the file is larger than 48 MB, the file is not copied into the sandbox, and SBIE issues message 2102.

    So, after knowing the name of the file that Sandboxie won't copy into the sandbox because is larger than what is allowed to be copied by default, and if you are not going to ignore the message (that was your first solution), your next step is to find the file so you know what it is and where it is located.

    In my example, since I am running a Firefox upgrade, that's the tell tale sign that tells me where to look, I looked for xul.dll in the Firefox installation folder, and there is the file. See below, at the bottom.

    2.jpg

    For solutions 2 and 3.

    Solution 2. If you want to increase size, you go the Sandboxie File migration Settings window, and increase the size there.

    Solution 3. To allow Direct file access to xul.dll (remember this is the file in my example). You go to the Direct File access window in Sandbox Settings, and click Add program, to add Firefox, then you click Add, for navigating to xul.dll to select it. After doing this, you are setting up Firefox to have direct file access to xul.dll, and won't get the message again, as all changes go straight out of the sandbox to the xul file outside the sandbox.


    direct.jpg

    Bo
     
  8. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    3,221
    i dont have any issue with firefox in the box. for chrome i cannot test right now - anyhow i dont use any browser regularly in the box so my experience is limited because there is no need here. afair chrome ever was special in sandboxie.

    PS .138 is the third or fourth update of v81 and now > 2 weeks ago ;) (still running chromium dev v84 here)

    tested with chromium portable v84 in the box - no problem to add 721meg for mediafire here. windows 8. user account with admin rights, sandbox with no limitations, no antivirus enabled. either chrome related or the environment in total.

    file migration limit is 512000kb here (500meg), testing 421 meg now, chosing with file > open dialog.
     
    Last edited: May 11, 2020
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.