2025 sparked some incredible conversations across our community 👩💻. Discover the highlights and see what’s ahead in 2026.
Forum Discussion
Kester
9 years agoCollaborator | Level 8
Windows 7 Event Viewer Error "Failed to connect to the driver: (-2147024894)"
Onthe last few startups of my Windows 7 desktop, the EventViewer has shown the following error and subsequent information logs as the error is corrected by Windows:
Record Number: X 95916
Log Type: Application
Event Type: Error
Source: DbxSvc
Category: 3
Event ID: 320
Failed to connect to the driver: (-2147024894) The system cannot find the file specified.
--------------------------------------------------------------------------------
Record Number: 95931
Log Type: Application
Event Type: Information
Source: ESENT
Category: 3
Event ID: 300
Windows (2500) Windows: The database engine is initiating recovery steps.
---------------------------------------------------------------------------------
Record Number: 95932
Log Type: Application
Event Type: Information
Source: ESENT
Category: 3
Event ID: 301
Windows (2500) Windows: The database engine has begun replaying logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS.log.
---------------------------------------------------------------------------------
Record Number: 95933
Log Type: Application
Event Type: Information
Source: ESENT
Category: 3
Event ID: 302
Windows (2500) Windows: The database engine has successfully completed recovery steps.
--------------------------------------------------------------------------------
Record Number: i 95915
Log Type: Application
Event Type: Information
Source: DbxSvc
Category: 2
Event ID: 258
Pipe server thread started.
--------------------------------------------------------------------------------
It seems as if the Dropbox service may be trying to start too soon as, after the initial error, Windows seems to be able to correct the problem and everything works correctly. This is a very recent happening and I cannot relate the change to any system changes. Is there anything I can do to stop the error - if I didn't regularly check the Event Viewer I would be none the wiser so perhaps I'm being too sensitive.
Thanks.
Hi everyone!
Sorry for the delay here -- I usually hang out on the client builds forum and missed this.
This error is expected and harmless. We are optimistically checking for features currently in development and logging an error when we don't find them enabled. We shouldn't be logging it as an error, however, perhaps as an Informational-level event and I'll make sure we clean this up in a future release.
If you're suspicious that this has been causing instability -- this hasn't really changed since last summer so it's probably not the droids you are looking for (combined with the fact that the error is indicative of things not happening, rather than things happening that are potentially destabilizing).
-Ben
- Hi all,First: Many apologies for the delay in jumping in here, I wanted to make sure I had a concrete update for you all.So, for context: What is Dbxsvc? :I've added a section to the help center article: https://help.dropbox.com/desktop-web/smart-sync (I say section, it's more of a note at the bottom under the driver FAQ).The file dbxsvc.exe is a file that we use to install the Smart Sync driver. Should you not be a business user, or not have Smart Sync, then this file will never start operating. It is, however, created at install for all users so if you are not a Smart Sync this file will still appear there.I see we have a number of pretty interesting, creative suggestions on how to disable, coupled with queries if it's safe to disable it. I'm of course not going to endorse a process that disables part of our software, should a feature or functionality cause user pain then we would want to know. Fixability and timeframes can vary depending on the in-depth technical nature of the problem.Should you decide to disable it with one of the solutions here, it will prevent the smart sync feature from working in some cases. We need the service to update the driver, as well as to establish new driver<->client connections. This is the services current functionality. Additional functionality could be added over time. My main concern around anyone disabling it is that in the future you may need this process, Smart Sync won't work correctly, you can reach out to support but this custom change you've made will be hard for us to diagnose as the root cause of whatever issue you experience.Why is it failing to connect / what's going wrong?:It should be failing to connect. This is by design, the actual issue you’re facing is due to the frequency we're writing to the logs. To address any concerns around error with the application, these errors are in no way indicative of a software issue and do not point to any issues with backing up you data. Because it fails to connect, Windows treats this as a trigger to write to the log. Your data is safe, this process is just used to install a driver. As covered in the above section we expect it to do what you are seeing.With that in mind, we understand that some of you do wish to see this behaviour.Why aren't we fixing this?:We are, we take our user feedback very seriously and we have spent many hours working on this. As fixes have many dependencies, and are just one components of a version release, I'm always reluctant to jump onto a thread and give a firm release date for a fix as these are regularly subject to change.You may have noticed that we took the original connection attempt frequency down from every 1 second to every minute. This was an improvement we took onboard based on the feedback you've supplied here and also via other channels. Our new release, 31.3.15, has further improved this, the process will run 3 times daily. This should reduce the errors written to the logs and not clutter the report.The new beta version is the first to include a fix:
254 Replies
Replies have been turned off for this discussion
- ecobags d.8 years agoNew member | Level 2
From 7/10/17 untill noon on 7/13/17 I have an event logged by DbxSvc every second saying "Failed to connect to the driver: (-2147024894) retrying in 1000 miliseconds". These events are still occuring but the retry time has become 86400000 milliseconds (24 hours). In the event properties of these entries it says the "Event 320, DbxSvc". I am using Windows 7 64 bit.
This odd event behavior is very similar to that of virus behavior. Looks like it might be an underflow error? Can someone explain what the software is attempting to do that is causing this event to be logged?
- Kester8 years agoCollaborator | Level 8
Hi,
This issue still drags on with only half-hearted part solutions offered by the developer. Contrast this with one of their competitors, Box.
To find a replacement service I checked reviews on-line and decided to give Box a try. Their free service is more generous than that of Dropbox in that they provide 10 gb of storage. All went well with Box for several days until on booting my system one morning, I had an error message to say that the sync program could not contact the website. I could still access my files on-line but just could get any communication between my computer and the website.
Using the Box community forum did not provide a solution so I was advised to set up a ticket with the Box support facility. I was contacted by email after a little delay (obviously free service users are prioritised lower than the paying customers as one would expect). It was suggested that I undertake various checks to rule out anything on my computer as the cause. When these did not resolve the issue I was emailed again to submit logfiles and so on. I was always contacted by the same member of the support staff who kept me updated on a regular basis. The box internal team kept working on the problem until yesterday, when I booted the system, the sync was working perfectly once more.
The notable difference between Box and my experience with Dropbox is the interest that Box takes in their users, their willingness to communicate and their effort to find a solution. I really feel that Dropbox takes its users for granted and has little interest in making its service run smoothly for users while it has some other agenda to explore.
I have also been trying pCloud which, like Box offers 10 gb of free storage. pCloud is interesting in that its on computer folder is in the form of a virtual drive so does not use up more than minimal drive space. So far pCloud is running very smoothly for me. Whilst I am not posting here as an advertising campaign for these alternatative products, Dropbox would do well to realise that users of their free service may well consider the alternatives as better options particularly as they offer considerably more free storage and they should recognize too that users of free services may well move on to paid for services if they like what they experience.
Right now, I cannot see any reason to stay with Dropbox and may therefore be closing my account shortly
- jcholcomb8 years agoExplorer | Level 4
Well, it's back again, getting the "Failed to connect to the driver: -2147024894, retrying in 1000 milliseconds" event every second for some time now, after getting rid of it for a few weeks by disabling service DbxSvc. Then, for no apparent reason, it dropped to once per minute, but that's still too often for my liking, as that is 1440 unnecessary events per day. I will try disabling DbxSvc again, and if I ever see it again, my next step will be to uninstall Dropbox. Dropbox version is 30.4.22.
- orion448 years agoHelpful | Level 6
Here is the solution to this problem:
Step 1: Back up your data
Step 2: Migrate to another cloud storage provider
Step 3: There is no step 3!
- urle8 years agoNew member | Level 2
since that error (thousends of them in eventviewer on 2 PCs ) i'm on Onedrive, fortunatly , or luckly... i dont know yet
- amfm848 years agoExplorer | Level 4Dropbox just updated itself to 31.4.24. Right after it relaunched it created a single event for "failed to connect to the driver", but after about 6 minutes there hasn't been another instance. I will be checking periodically to see how frequently Dropbox creates this event now.
- Tom W.408 years agoHelpful | Level 5Looks like the same thing here, 31.4.24 seems to have fixed it.
- Kester8 years agoCollaborator | Level 8
Hi,
Version 31.4.24 has not really provided a fix but it has decreased the nuisance level to a tolerable position. On my Windows 7 system, Event Viewer actually shows two instances of 'Failed to connect to the driver: (-2147024894) The system cannot find the file specified. , retrying...' after each system startup. The two instances are 30 seconds apart. So the issue is still there but no lonbger irritating enough for me to disable dbxsvc. Dropbox has a little more time now before I decide whether or not to get rid of it.
- jcholcomb8 years agoExplorer | Level 4
The problem does seem to at least be vastly improved, if not completely fixed, with version 31.4.24 on my Windows 10 system. I've had less than 10 events reported with DbxSvc as the source in the past 24 hours, and those have been at random times, or system startup. About half of those events have also been more normal things, like "Server started," or "Pipe server thread started." I am satisfied with that, as long as the original problem stays away.
- Kester8 years agoCollaborator | Level 8
Hi,
I receive email notifications when a new post is added to this thread so I was surprised to receive the following today (Monday 14 August 2017) which does not appear to have been added to this thread so I have included it in italics below :
-----------------------------------------------------------------------------------------------
Hi all,First: Many apologies for the delay in jumping in here, I wanted to make sure I had a concrete update for you all.So, for context: What is Dbxsvc? :I've added a section to the help center article: https://help.dropbox.com/desktop-web/smart-sync (I say section, it's more of a note at the bottom under the driver FAQ).The file dbxsvc.exe is a file that we use to install the Smart Sync driver. Should you not be a business user, or not have Smart Sync, then this file will never start operating. It is, however, created at install for all users so if you are not a Smart Sync this file will still appear there.I see we have a number of pretty interesting, creative suggestions on how to disable, coupled with queries if it's safe to disable it. I'm of course not going to endorse a process that disables part of our software, should a feature or functionality cause user pain then we would want to know. Fixability and timeframes can vary depending on the in-depth technical nature of the problem.Should you decide to disable it with one of the solutions here, it will prevent the smart sync feature from working in some cases. We need the service to update the driver, as well as to establish new driver<->client connections. This is the services current functionality. Additional functionality could be added over time. My main concern around anyone disabling it is that in the future you may need this process, Smart Sync won't work correctly, you can reach out to support but this custom change you've made will be hard for us to diagnose as the root cause of whatever issue you experience.Why is it failing to connect / what's going wrong?:It should be failing to connect. This is by design, the actual issue you’re facing is due to the frequency we're writing to the logs. To address any concerns around error with the application, these errors are in no way indicative of a software issue and do not point to any issues with backing up you data. Because it fails to connect, Windows treats this as a trigger to write to the log. Your data is safe, this process is just used to install a driver. As covered in the above section we expect it to do what you are seeing.With that in mind, we understand that some of you do wish to see this behaviour.Why aren't we fixing this?:We are, we take our user feedback very seriously and we have spent many hours working on this. As fixes have many dependencies, and are just one components of a version release, I'm always reluctant to jump onto a thread and give a firm release date for a fix as these are regularly subject to change.You may have noticed that we took the original connection attempt frequency down from every 1 second to every minute. This was an improvement we took onboard based on the feedback you've supplied here and also via other channels. Our new release, 31.3.15, has further improved this, the process will run 3 times daily. This should reduce the errors written to the logs and not clutter the report.The new beta version is the first to include a fix:-----------------------------------------------------------------------------------------------I don't know who wrote it, there was no name attached, but I presume it was Ross as his name appears in the versions table at https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016. The contents are a bit confusing too. For example the reference 'Our new release, 31.3.15, has further improved this, the process will run 3 times daily' does not tie up the versions table.There are several versions listed in the table, both beta builds and stable versions, that are later versions than the quoted 31.3.15.
I would presume that later versions would include any debugging and improvements from earlier versions.
About Apps and Installations
Have a question about a Dropbox app or installation? Reach out to the Dropbox Community and get solutions, help, and advice from members.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
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, Facebook or Instagram.
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!