We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Musicstate
3 years agoExplorer | Level 4
Couldn't Start Dropbox
This is usually because of a permissions error. etc
I moved the sync directory to my 😧 drive for info
I suspect the dropbox_path might be the problem
Text File
bn.BUILD_KEY: Dropbox
bn.VERSION: 141.4.3299
bn.constants.WINDOWS_SHELL_EXT_VERSION: 52
bn.is_frozen: True
machine_id: 0f7a47a3-475d-470e-a9fe-b9154018bcc4
pid: 8348
cwd: 'C:\\Program Files (x86)\\Dropbox\\Client'
real_path='C:\\Program Files (x86)\\Dropbox\\Client'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
HOME: None
appdata: 'C:\\Users\\music\\AppData\\Local\\Dropbox\\instance1'
real_path='C:\\Users\\music\\AppData\\Local\\Dropbox\\instance1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
dropbox_path: None
not found
parent not found
sys_executable: 'C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
mode=0o100777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
trace.__file__: 'C:\\Program Files (x86)\\Dropbox\\Client\\141.4.3299\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\141.4.3299\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
not found
parent not found
TMP: C:\Users\music\AppData\Local\Temp
TEMP: C:\Users\music\AppData\Local\Temp
tempdir: 'C:\\Users\\music\\AppData\\Local\\Temp'
real_path='C:\\Users\\music\\AppData\\Local\\Temp'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
Traceback (most recent call last):
File "dropbox\client\authentication\register_host_helper.pyc", line 483, in _try_register_host
File "dropbox\client\authentication\register_host_helper.pyc", line 949, in handle_changed_host_secret
File "dropbox\sync_root\helpers.pyc", line 367, in destroy_root_from_config
AssertionError
Hi Musicstate,
The issue you are experiencing isn't related to any access or permission troubles. It's just a standard error message for everything (with or without real permission issues). The issue is definitely related to the path you selected for your Dropbox folder. It may be due to change/move in this path, for example, or some other similar change. Don't try to change Dropbox folder name or the path pointed to there after you have selected it!
To solve it, you have to unlink the application from your account and link it anew. Remove your troublesome application/device out from your device list. Scroll down to the desired device if need. Click on trash bin next to the desired list entry. This will make sure your device isn't in link to the Dropbox server, but the application itself can still be unaware of that. Forcibly unlink it using following command in terminal:
rm -rf ~/.dropbox
The above guarantees that no any trace from previous link lefts, able to prevent further application work. Now you can link your Dropbox application to your Dropbox account anew by signing in again. 😉
Hope this helps.
Edit: Oh.. you are on Windows. One of the rule above is related to Mac/Linux only. 🤷 My fault. Instead of the command above remove Dropbox folder residing in "C:\Users\music\AppData\Local" (not the one that keeps your data).
- ЗдравкоLegendary | Level 20
Hi Musicstate,
The issue you are experiencing isn't related to any access or permission troubles. It's just a standard error message for everything (with or without real permission issues). The issue is definitely related to the path you selected for your Dropbox folder. It may be due to change/move in this path, for example, or some other similar change. Don't try to change Dropbox folder name or the path pointed to there after you have selected it!
To solve it, you have to unlink the application from your account and link it anew. Remove your troublesome application/device out from your device list. Scroll down to the desired device if need. Click on trash bin next to the desired list entry. This will make sure your device isn't in link to the Dropbox server, but the application itself can still be unaware of that. Forcibly unlink it using following command in terminal:
rm -rf ~/.dropbox
The above guarantees that no any trace from previous link lefts, able to prevent further application work. Now you can link your Dropbox application to your Dropbox account anew by signing in again. 😉
Hope this helps.
Edit: Oh.. you are on Windows. One of the rule above is related to Mac/Linux only. 🤷 My fault. Instead of the command above remove Dropbox folder residing in "C:\Users\music\AppData\Local" (not the one that keeps your data).
- Primo_SustoExplorer | Level 4
-"This is the way"-
Thank you very much, for me (in mac) after hours of searching, uninstalling and installing several times, I finally found your answer in the forum.
It was as easy as just:- *with dorpbox installed but closed
- open terminal
- copy paste:rm -rf ~/.dropbox
- press enter
- open Dropbox
- working like nothing wrong ever happened - MusicstateExplorer | Level 4
Thanks very much Здравко!, this did the trick.
One thing to add to all of this is during the installation you need to select Advanced to choose another installation directory from the default location
Musicstate
- jen1147Explorer | Level 4
I am experiencing this same issue in Windows 10 but removing Dropbox from C:\Users\username\AppData\Local did not solve the problem. Dropbox still won't start. I posted my similar issue here: https://www.dropboxforum.com/t5/Apps-and-Installations/Couldn-t-start-Dropbox-permissions-error/m-p/616430#M43261
Any advice is welcome, thank you!
Here is my error message:bn.BUILD_KEY: Dropbox
bn.VERSION: 154.4.5363
bn.constants.WINDOWS_SHELL_EXT_VERSION: 52
bn.is_frozen: True
machine_id: 18a51a83-5e05-4fd4-b71e-a8f354494112
pid: 19872
cwd: 'C:\\Program Files (x86)\\Dropbox\\Update\\1.3.583.1'
real_path='C:\\Program Files (x86)\\Dropbox\\Update\\1.3.583.1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
HOME: None
appdata: 'C:\\Users\\Jen\\AppData\\Local\\Dropbox\\instance1'
real_path='C:\\Users\\Jen\\AppData\\Local\\Dropbox\\instance1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
dropbox_path: 'C:\\Users\\Jen\\Dropbox'
real_path='C:\\Users\\Jen\\Dropbox'
mode=0o40555 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
sys_executable: 'C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
mode=0o100777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
trace.__file__: 'C:\\Program Files (x86)\\Dropbox\\Client\\154.4.5363\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\154.4.5363\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
not found
parent not found
TMP: C:\Users\Jen\AppData\Local\Temp
TEMP: C:\Users\Jen\AppData\Local\Temp
tempdir: 'C:\\Users\\Jen\\AppData\\Local\\Temp'
real_path='C:\\Users\\Jen\\AppData\\Local\\Temp'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
Traceback (most recent call last):
File "dropbox\client\main.pyc", line 828, in wrapper
File "dropbox\client\main.pyc", line 6623, in finish_dropbox_boot
File "dropbox\client\message_queue.pyc", line 311, in _wrapped
File "dropbox\client\main.pyc", line 6147, in _init_components_for_account
File "dropbox\client\main.pyc", line 6071, in create_sync_engine
File "dropbox\sync_engine_boundary\factory.pyc", line 225, in make_sync_engine
File "dropbox\sync_engine\nucleus\classic_client\sync_engine.pyc", line 251, in __init__
File "dropbox\sync_engine\nucleus\classic_client\modern_client\modern_client.pyc", line 261, in __init__
File "dropbox\sync_engine\nucleus\classic_client\modern_client\base.pyc", line 189, in __init__
File "dropbox\fs_api\lifecycle.pyc", line 192, in __init__
File "dropbox\fs_api\lifecycle.pyc", line 206, in _create_thin_client
File "dropbox\fs_api\fs_api_adapter.pyc", line 50, in __init__
File "desktop\extensions\fs_api\fs_api_python.pyx", line 63, in fs_api_python.FsApiServer.__cinit__
fs_api_python.FsApiError: "Initializing fs api |>> Initializing application filesystem |>> Attempting to initialize dbx cache directory |>> NtSetBasicInformation syscall: new handle |>> ACCESS_DENIED |>> Permission denied"- WalterDropbox Staff
Hey jen1147, sorry to hear about this.
Could you perform a clean, advanced reinstall and let us know how it goes?
If you happen to be on the Basic plan, make sure to have less than 3 devices connected to your account.
- jen1147Explorer | Level 4
My Dropbox suddenly stopped syncing two days ago, and as of last night it will not start at all. I am receiving the following error message when I click on the Dropbox icon on my Windows 10 Desktop: "Couldn't start Dropbox. This is usually because of a permissions error. Storing your home folder on a network share can also cause an error."
I am using Windows 10 and I have no pending system software updates.
I have tried all of the solutions on the permissions error support page, none of which resolved my issue. https://help.dropbox.com/installs-integrations/sync-uploads/files-not-syncingI tried uninstalling and reinstalling the application multiple times. I tried Advanced Uninstall. Every time I reinstall, I have this same error message. I tried unlinking my account from the desktop app. When I tried to contact Dropbox, the Chatbot pointed me to the community forum. I have a free account, not a paid account.
I tried the solution proposed here, but removing Dropbox from C:\Users\username\AppData\Local did not solve the problem. https://www.dropboxforum.com/t5/Create-upload-and-share/Couldn-t-Start-Dropbox/m-p/577691#M50944
Thank you for any suggestions! The error message says to contact Dropbox Support with the following:
bn.BUILD_KEY: Dropbox
bn.VERSION: 154.4.5363
bn.constants.WINDOWS_SHELL_EXT_VERSION: 52
bn.is_frozen: True
machine_id: 18a51a83-5e05-4fd4-b71e-a8f354494112
pid: 19872
cwd: 'C:\\Program Files (x86)\\Dropbox\\Update\\1.3.583.1'
real_path='C:\\Program Files (x86)\\Dropbox\\Update\\1.3.583.1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
HOME: None
appdata: 'C:\\Users\\Jen\\AppData\\Local\\Dropbox\\instance1'
real_path='C:\\Users\\Jen\\AppData\\Local\\Dropbox\\instance1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
dropbox_path: 'C:\\Users\\Jen\\Dropbox'
real_path='C:\\Users\\Jen\\Dropbox'
mode=0o40555 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
sys_executable: 'C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
mode=0o100777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
trace.__file__: 'C:\\Program Files (x86)\\Dropbox\\Client\\154.4.5363\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\154.4.5363\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
not found
parent not found
TMP: C:\Users\Jen\AppData\Local\Temp
TEMP: C:\Users\Jen\AppData\Local\Temp
tempdir: 'C:\\Users\\Jen\\AppData\\Local\\Temp'
real_path='C:\\Users\\Jen\\AppData\\Local\\Temp'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
Traceback (most recent call last):
File "dropbox\client\main.pyc", line 828, in wrapper
File "dropbox\client\main.pyc", line 6623, in finish_dropbox_boot
File "dropbox\client\message_queue.pyc", line 311, in _wrapped
File "dropbox\client\main.pyc", line 6147, in _init_components_for_account
File "dropbox\client\main.pyc", line 6071, in create_sync_engine
File "dropbox\sync_engine_boundary\factory.pyc", line 225, in make_sync_engine
File "dropbox\sync_engine\nucleus\classic_client\sync_engine.pyc", line 251, in __init__
File "dropbox\sync_engine\nucleus\classic_client\modern_client\modern_client.pyc", line 261, in __init__
File "dropbox\sync_engine\nucleus\classic_client\modern_client\base.pyc", line 189, in __init__
File "dropbox\fs_api\lifecycle.pyc", line 192, in __init__
File "dropbox\fs_api\lifecycle.pyc", line 206, in _create_thin_client
File "dropbox\fs_api\fs_api_adapter.pyc", line 50, in __init__
File "desktop\extensions\fs_api\fs_api_python.pyx", line 63, in fs_api_python.FsApiServer.__cinit__
fs_api_python.FsApiError: "Initializing fs api |>> Initializing application filesystem |>> Attempting to initialize dbx cache directory |>> NtSetBasicInformation syscall: new handle |>> ACCESS_DENIED |>> Permission denied" - dlee10New member | Level 2
Every time I try to open dropbox on my MacBook Air, I receive this message and the app won't open. I've had dropbox on this computer before, I deleted the desktop version last week on accident. How do I problem solve this so I can use the desktop app instead of the web app?
Thanks for the help!
- leeharrisHelpful | Level 5
I have a similar problem.
My Dropbox is and has always been a separate hard drive.
Here is the code report:
bn.BUILD_KEY: Dropboxbn.VERSION: 184.4.6543bn.constants.WINDOWS_SHELL_EXT_VERSION: 66bn.is_frozen: Truemachine_id: 8029901e-d72d-582c-a868-794256170e0apid: 16217ppid: 1uid: 501user_info: pwd.struct_passwd(pw_name='lee', pw_passwd='********', pw_uid=501, pw_gid=20, pw_gecos='Lee Harris', pw_dir='/Users/lee', pw_shell='/bin/bash')effective_user_info: pwd.struct_passwd(pw_name='lee', pw_passwd='********', pw_uid=501, pw_gid=20, pw_gecos='Lee Harris', pw_dir='/Users/lee', pw_shell='/bin/bash')euid: 501gid: 20egid: 20group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root'])effective_group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root'])DYLD_LIBRARY_PATH: Nonecwd: '/'real_path='/'mode=0o40755 uid=0 gid=0parent mode=0o40755 uid=0 gid=0HOME: '/Users/lee'appdata: '/Users/lee/.dropbox/instance3'real_path='/Users/lee/.dropbox/instance3'mode=0o40700 uid=501 gid=20parent mode=0o40700 uid=501 gid=20dropbox_path: '/Volumes/Dropbox/Dropbox'real_path='/Volumes/Dropbox/Dropbox'mode=0o40700 uid=501 gid=20parent mode=0o40755 uid=501 gid=20sys_executable: '/Applications/Other Applications/Dropbox.app/Contents/MacOS/Dropbox'real_path='/Applications/Other Applications/Dropbox.app/Contents/MacOS/Dropbox'mode=0o100755 uid=501 gid=20parent mode=0o40755 uid=501 gid=20trace.__file__: '/Applications/Other Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc'real_path='/Applications/Other Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc'not foundparent not foundtempdir: '/var/folders/19/j57lssl125bfn_l8212727tc0000gn/T'real_path='/private/var/folders/19/j57lssl125bfn_l8212727tc0000gn/T'mode=0o40700 uid=501 gid=20parent mode=0o40755 uid=501 gid=20Traceback (most recent call last):File "desktop/dropbox/fs_api/lifecycle.py", line 235, in clientFile "desktop/dropbox/fs_api/lifecycle.py", line 283, in _create_thin_clientFile "desktop/dropbox/fs_api/fs_api_adapter.py", line 50, in __init__File "desktop/extensions/fs_api/fs_api_python.pyx", line 63, in fs_api_python.FsApiServer.__cinit__fs_api_python.FsApiError: "Initializing fs api |>> Initializing application filesystem |>> Attempting to create new files directory for ApplicationFilesystem |>> Error making tempdir |>> mkdirat |>> mkdirat syscall |>> Unknown posix error (0x6)"The above exception was the direct cause of the following exception:Traceback (most recent call last):File "desktop/dropbox/client/main.py", line 866, in wrapperFile "desktop/dropbox/client/main.py", line 6792, in finish_dropbox_bootFile "desktop/dropbox/client/message_queue.py", line 306, in _wrappedFile "desktop/dropbox/client/main.py", line 6252, in _init_components_for_accountFile "desktop/dropbox/client/main.py", line 6175, in create_sync_engineFile "desktop/dropbox/sync_engine_boundary/factory.py", line 225, in make_sync_engineFile "desktop/dropbox/sync_engine/nucleus/classic_client/sync_engine.py", line 243, in __init__File "desktop/dropbox/sync_engine/nucleus/classic_client/modern_client/modern_client.py", line 282, in __init__File "desktop/dropbox/sync_engine/nucleus/classic_client/modern_client/base.py", line 242, in __init__File "../mac_arm64_dropbox_virtual_env/lib/python3.8/functools.py", line 967, in __get__File "desktop/dropbox/fs_api/lifecycle.py", line 259, in clientdropbox.fs_api.lifecycle.FsApiClientCreationException: "Initializing fs api |>> Initializing application filesystem |>> Attempting to create new files directory for ApplicationFilesystem |>> Error making tempdir |>> mkdirat |>> mkdirat syscall |>> Unknown posix error (0x6)"- HannahDropbox Staff
Hey leeharris, sorry to see that you're having this issue.
Since you posted on a thread that was about a different issue, I moved your post to a more relevant thread.
Can you give us some more info about when this issue started happening?
Was it after you updated your computer to Sonoma?
Also, did you update your Dropbox to the new Dropbox for macOS on File Provider?
- leeharrisHelpful | Level 5
HI as I wrote below a restart may have fixed it.
To answer your other questions just in case, yes this happened directly after upgrading to Sonoma and no I have not upgraded Dropbox as I believe there are issues if the DB folder is on an external device, I am not sure if this has been resolved.
- ЗдравкоLegendary | Level 20
leeharris wrote:...dropbox.fs_api.lifecycle.FsApiClientCreationException: "Initializing fs api |>> Initializing application filesystem |>> Attempting to create new files directory for ApplicationFilesystem |>> Error making tempdir |>> mkdirat |>> mkdirat syscall |>> Unknown posix error (0x6)"Hi leeharris and all support staff,
Again something is "unknown" for Dropbox!!! Actually, this error (ENXIO with code 6) means that for some reason the scheduled operation cannot be performed or not supported on particular device in general (partition in the particular case). The reason can be some incompatibility, but again - without info where new folder creation trying has been performed (where the 'at' handle points to) that fails and the underlying partition type (and mounting options could be helpful) nothing concrete can be said. Invite your development team to put some more information when unhandled exception brings up. If I have to bet, Dropbox application tries to create temporary folder on a partition where such creation is not supported and not allowed. Most probably some hidden bug, in configuration management, that comes up from time to time, and forces folder creation on "unusual" places instead of the normal one.
leeharris, To flush up entire configuration and start on clear, perform advanced reinstall if nothing else helps. Since the main temporary dir already exists, it's likely application and/or computer reboot to help. Did you try this? Try in advance...
Good luck.
- leeharrisHelpful | Level 5
Hi
I was busy today on a shoot but when I got back I had other issues when trying to save files in Capture One Pro and decided to do a restart, these seems to have fixed the Dropbox problem... I think and hope. I will test it again later just to be sure
.
About Create, upload, and share
Find help to solve issues with creating, uploading, and sharing files and folders in Dropbox. Get support and advice from the Dropbox Community.
Need more support
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!