Couldn't Start Dropbox

Здравко thanks for the follow-up! I'm not sure if there is a difference. My current error message is: 
bn.BUILD_KEY: Dropbox
bn.VERSION: 155.4.5493
bn.constants.WINDOWS_SHELL_EXT_VERSION: 52
bn.is_frozen: True
machine_id: 18a51a83-5e05-4fd4-b71e-a8f354494112
pid: 22076
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\\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\\155.4.5493\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\155.4.5493\\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 6646, in finish_dropbox_boot
File "dropbox\client\message_queue.pyc", line 311, in _wrapped
File "dropbox\client\main.pyc", line 6170, in _init_components_for_account
File "dropbox\client\main.pyc", line 6094, 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"

Walter my error message after completing the advanced reinstall is the following. I confirmed the Dropbox folder has full permissions and the Dropbox app is allowed through my firewall. Unfortunately Dropbox still won't start and it's giving me a permissions error. I'm not sure if this error message is any different. Any further suggestions? Thank you!

bn.BUILD_KEY: Dropbox
bn.VERSION: 155.4.5493
bn.constants.WINDOWS_SHELL_EXT_VERSION: 52
bn.is_frozen: True
machine_id: 18a51a83-5e05-4fd4-b71e-a8f354494112
pid: 22076
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\\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\\155.4.5493\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\155.4.5493\\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 6646, in finish_dropbox_boot
File "dropbox\client\message_queue.pyc", line 311, in _wrapped
File "dropbox\client\main.pyc", line 6170, in _init_components_for_account
File "dropbox\client\main.pyc", line 6094, 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"

Could you temporarily disable any antivirus or firewall you may have running on your computer and let us know if you're still getting the same error jen1147?

Hi!

I have the same error message when Dropbox starts. I've tried all proposed solution without any success, including disabling Windows Defender.

I have Dropbox folder in another drive, not the default location but all permissions seem to be OK. This drive is a mounted VeraCrypt drive and I have this same setup in 2 PC for several years without issues. Now, only one of them has this problem (it's a recent issue for me).

If I restart Windows than Dropbox starts OK but after some time it gets stuck synching files. If I close Dropbox from the system tray and then start the app it displays that error message pointing to usually permissions error but I think my case may be different because my error file differs a bit from other users as you can see in the last lines below....

Any thoughts? I'm starting to think about replacing Dropbox after so many years of great experiences...

Thank you!

bn.BUILD_KEY: Dropbox
bn.VERSION: 155.4.5495
bn.constants.WINDOWS_SHELL_EXT_VERSION: 52
bn.is_frozen: True
machine_id: a060b326-d9d3-4c59-85fb-ed008080cb86
pid: 12928
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\\vitor.amorim\\AppData\\Local\\Dropbox\\instance1'
real_path='C:\\Users\\vitor.amorim\\AppData\\Local\\Dropbox\\instance1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
dropbox_path: 'Z:\\Dropbox'
real_path='Z:\\Dropbox'
mode=0o40555 uid=0 gid=0
parent mode=0o40555 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\\155.4.5495\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\155.4.5495\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
not found
parent not found
TMP: C:\Users\VITOR~1.AMO\AppData\Local\Temp
TEMP: C:\Users\VITOR~1.AMO\AppData\Local\Temp
tempdir: 'C:\\Users\\VITOR~1.AMO\\AppData\\Local\\Temp'
real_path='C:\\Users\\vitor.amorim\\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 6646, in finish_dropbox_boot
File "dropbox\client\message_queue.pyc", line 311, in _wrapped
File "dropbox\client\main.pyc", line 6170, in _init_components_for_account
File "dropbox\client\main.pyc", line 6094, 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 platform |>> File not found"

---

Vitor_Amorim wrote:

...
fs_api_python.FsApiError: "Initializing fs api |>> Initializing platform |>> File not found"

---

Hi Vitor_Amorim,

Yes, for sure your state is different and not the same as those reported before. Unfortunately, in many cases, the messages (like the above) are not clear enough. Here, for example, isn't clear what file, actually, is "not found"! 🤷 And so, you can't check actually what's wrong. This could be a signal for the developers of Dropbox application to format every error message more clear and complete (especially to Rust coders, responsible for the code  where this message originates from).

Hi Vitor_Amorim, sorry for jumping in here. 

Just to clarify and narrow down the issue, can you let me know if you’ve also tried an advanced reinstall? 

If so, did it seem to help at all?

Здравко and Walter thank you both for your help! I temporarily disabled Windows Defender and Dropbox started syncing again. Now my issue is, I still need Dropbox to sync while my antivirus is enabled. What’s odd to me is, under the control panel settings for Windows Defender Firewall, Dropbox is already checked off under "Allowed apps and features." Any other suggestions? Perhaps I need to "Add an exclusion" under Windows Security. If so, I would appreciate instructions. Thanks again.

Hi jen1147, can you take a look into this Help Center article on how you can whitelist Dropbox, and let me know if this does the trick for you? 

Hi jen1147,

To be honest, I don't use your software and don't know in details what you are seeing. Better read associated documentation; I believe there is detailed enough description what you can do. The most important is that you have found what's the reason. 😉

Good luck.

---

Megan wrote:

Hi jen1147, can you take a look into this Help Center article ...

---

---

The article:

...

• Allow Dropbox access to ports 80 (HTTP) and 443 (HTTPS), and 17600 and 17603 (to open files in third party applications).

...

---

Hi Megan,

I haven't noticed before, but in the article you linked to is a mistake. Actual loopback ports in use are NOT 17600 and 17603, but 3 port from 17600 to 17602 inclusive (i.e. ports 17600 and 17601, and 17602)! Dropbox application doesn't use port 17603. Most probably typing mistake. 🙂 I believe you will forward this to the person/people responsible for the pointed help article for corrections.

Have a nice day.

ADD: Megan, One more thing is completely missing! How/where LAN Sync comes through? 🧐 Doesn't some port engage especially for this? There is such port actually. 😜 It's missing in the article too. If Dropbox application can't open port 17500 (both TCP and UDP) LAN Sync will never get up. By the way, all other ports needed are TCP only (something that misses in the description too).

Megan thanks for the link to the article https://help.dropbox.com/installs/configuring-firewall. I already saw it previously, but unfortunately, I don't know how allow Dropbox access to ports 80 (HTTP) and 443 (HTTPS), and 17600 and 17603, or how to check if it already has access.