EXCEL.EXE (6040): SBIE2205 Service not implemented: NetUseAdd + Outlook locks issue

[mauriceatkinson]

When I downloaded a csv into the sandbox and start excel I receive this error message from Sandboxie v0.9.7e. The error message is "EXCEL.EXE (6040): SBIE2205 Service not implemented: NetUseAdd" and I have the option to dismiss the error in the displayed window.

Excel displays the downloaded csv file without any issues.

[DavidXanatos]

i wonder why excel wahts to create a new user on your system surely seams strange

[mauriceatkinson]

happy to provide any details you need to resolve this, just let me know

[DavidXanatos]

I'm not sure if that needs resolving sandboxie blocked a call to NetUseAdd in purpose, as you don't want sandboxed excel to create new user accounts on your system.

[diversenok]

@DavidXanatos, you are talking about NetUserAdd while the messages says NetUseAdd

[DavidXanatos]

oh right

[mauriceatkinson]

just to update you, when excel opens a sandbox file and the sandboxie error message is displayed, it is not possible to edit or access the file within excel. Everytime I attempt to move around the spreadsheet there is a windows "ding" There is not open prompts but it isnt possible to do anything other than close excel. However it is not possible to close excel normally and this has to be done via task manager.

[isaak654]

I was able to reproduce the Service not implemented: NetUseAdd dialog, it appears every time I access to a mapped network drive. This is due to the BlockNetworkFiles=y setting on your sandbox.

Since it's a default setting for any sandbox, you can turn it off with BlockNetworkFiles=n in order to not see the NetUseAdd dialog anymore.

Anyway, I think that BlockNetworkFiles setting needs to be improved internally because the block it puts caused a certain slowdown on my Windows Explorer session (while attempting to access to the mapped drive for plain curiosity).

[mauriceatkinson]

Great find. I changed BlockNetworkFiles=n and the error message no longer appears. However the excel issue does which to be honest is more criticial. Although excel opens the file as before you cannot move or click on anything within the spreadsheet. The only way to close down excel is either to terminate the excel process in the sandbox or using windows task manager. This problem still occurs in v0.9.8 attached is the trace log of the excel issue that may shed some light on it.
excel hang.txt
b

[isaak654]

You could try something like:
OpenIpcPath=*\BaseNamedObjects\MSSPHTB_*
OpenIpcPath=*\BaseNamedObjects\OfficeSharedLocks_*
OpenIpcPath=*\BaseNamedObjects\WMS Notif Engine*
OpenIpcPath=*\BaseNamedObjects\MAPI-*

If they're not enough, it would help if you could attach a shorter log with the exact time interval where you're having the issue.

[DavidXanatos]

I can't reproduce this issue, on my test VM with an up to date office excel seams to work just fine

[mauriceatkinson]

This is the version I am using and Microsoft states this is the latest version. Microsoft® Excel® for Microsoft 365 MSO (Version 2109 Build 16.0.14430.20292) 64-bit

[mauriceatkinson]

excuse my ignorance but in what config file do the openipcpath statements go?

[isaak654]

excuse my ignorance but in what config file do the openipcpath statements go?

Assuming you're on the main Sandboxie Plus window and you've closed any running program in the sandbox:

1. Go to Options menu -> Edit ini file -> confirm yes
2. Add those lines below [DefaultBox] or below your sandbox name you actually use
3. Save the ini file and close it

The main configuration file is stored by default on C:\Windows\Sandboxie.ini

[mauriceatkinson]

After making the changes into the ini file things look much better as I can now open/edit a downloaded CSV into the sandbox with Excel without any issues. Thanks very much

[DavidXanatos]

Could you please test with only some of the lines which one is making the difference, would be good to know exactly whats teh cause than it should be added to the global templates

[mauriceatkinson]

This is a weird one. I started testing and excel worked everytime, I removed all the new ini entries and it still worked. I updated to new Sandboxie version - it worked without any ini entries. I reverted back to 0.9.7b using the installed ini file and it still worked. I will keep using it and see if the problem reappears.

[DavidXanatos]

ok cool in that case i can close the issue

[isaak654]

@DavidXanatos
Two of the lines I posted above are already included in [Template_Office_Outlook] as part of an Outlook pst locks fix

Sandboxie/Sandboxie/install/Templates.ini

Lines 1070 to 1071 in 9fcfc40

	OpenIpcPath=<Office_Outlook>,*\BaseNamedObjects*\OfficeSharedLocks_*
	OpenIpcPath=<Office_Outlook>,*\BaseNamedObjects\WMS Notif Engine*

You may consider to move them in a global template, since only a few users enable manually that template.

The alternative is to add the following Scan lines to the [Template_Office_Outlook], since they allow to apply automatically and silently the Outlook template for anyone who has Outlook, in order to prevent the pst locks:

Tmpl.Scan=s
Tmpl.ScanKey=\REGISTRY\MACHINE\SOFTWARE\Clients\Mail\Microsoft Outlook

[isaak654]

@APMichael I'm looking for suggestions about #1276 (comment) and #1276 (comment), it looks like the Outlook locks issue is still happening in random Sandboxie versions (see here).

Even if this issue seems related to an Excel hang, the same author is also running Outlook: #1260

[APMichael]

Since the fix, I haven't had any problems with Office, i.e. Excel, Word and PowerPoint. Unfortunately, I have never used Outlook with Sandboxie and therefore cannot make any recommendations.

[isaak654]

I have just performed a test with v1.1.3. With this specific Sandboxie version, Outlook doesn't allow to skip the initial sign-in popups because of #2006... even worse when you apply the Office_Outlook template, because it totally prevents Outlook from being loaded for the same issue.

These particular regressions are not new:

There would be another bad news for certain Sandboxie users... in order to downgrade to a version without the issue like 1.0.22, you'll need to clean the sandbox content first, otherwise this could continue indefinitely.

In light of this, I am even more confused about my initial request to set [Template_Office_Outlook] as default when Outlook is detected... what it could be done is to tweak it a little bit in a separate PR, because it contains some unnecessary lines.

EDIT: For some unknown reason, I am no longer able to test it... suddenly Outlook presents a white screen when opening it.