{"id":1841,"date":"2015-11-25T00:33:09","date_gmt":"2015-11-25T08:33:09","guid":{"rendered":"http:\/\/www.coretechnologies.com\/blog\/?p=1841"},"modified":"2023-01-07T17:38:18","modified_gmt":"2023-01-08T01:38:18","slug":"dropbox-service-not-working-after-update","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/dropbox-service-not-working-after-update\/","title":{"rendered":"My Dropbox Windows Service no longer works after Updating Dropbox – Help!"},"content":{"rendered":"

Recently, a few of our customers running Dropbox as a windows service with AlwaysUp<\/a> have reported failures after manually updating to the latest version of Dropbox. These are happening because Dropbox changes the location of its executable file during the update.<\/b> Let’s dig into the details and see how to fix the problem<\/a>.<\/p>\n

The Old Dropbox Location<\/b><\/h2>\n

\nPrior to version 3.5.58<\/a>, released in April 2015, Dropbox stored its application executable file (Dropbox.exe) in a user-specific folder. If you installed Dropbox in the Administrator account, you could find the file in C:\\Users\\Administrator\\AppData\\Roaming\\Dropbox\\bin<\/span><\/b>:
\n
\n\"Dropbox<\/a>\n<\/p>\n

The New Dropbox Location<\/b><\/h2>\n

\nIf you install a fresh copy of version 3.5.58 or later, you will notice that Dropbox.exe now lives underneath the Program Files folder, in C:\\Program Files (x86)\\Dropbox\\Client<\/b> (or C:\\Program Files\\Dropbox\\Client<\/span> on 32-bit versions of Windows):
\n
\n\"Dropbox<\/a>\n<\/p>\n

\nWe have already noted the new location in our step-by-step tutorial<\/a> to guide future customers, but the story is more complicated for existing installations…\n<\/p>\n

Upgrading Dropbox Changes its Location (and Breaks your AlwaysUp Configuration)<\/b><\/h2>\n

\nUnfortunately the impact of this change to the file locations isn’t limited to new installations. Manually updating an existing Dropbox installation will cause the files to be moved to the new folder.<\/b> This isn’t a problem for Dropbox itself, but since AlwaysUp is blissfully unaware of the change, it will continue to run Dropbox.exe from its old location (as you originally specified in the Application field on the General tab):
\n
\n\"AlwaysUp<\/a>\n<\/p>\n

\nBecause the executable is no longer present there, AlwaysUp will fail to start Dropbox and report errors like this:
\n
\n\"AlwaysUp<\/a>\n<\/p>\n

<\/a><\/p>\n

The Fix: Set the New Dropbox Location in AlwaysUp<\/b><\/h2>\n

\nFortunately normal operation can be restored quite easily. Simply edit Dropbox in AlwaysUp and update the Application field on the General tab to specify the new path to the Dropbox executable<\/b> (C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe):
\n
\n\"Update<\/a>\n<\/p>\n

\nSave your settings and AlwaysUp should be able to start Dropbox normally again!\n<\/p>\n

\n
\n\n\n\n
Read more articles about Dropbox…<\/nobr><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n