We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Kester
10 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
- roberto l.110 years agoExplorer | Level 3
OK, bizarrely, I logged out and logged back in again with a local Administrator account (not a Microsoft Account) and installed Dropbox again from there, and this time it worked! I logged out and logged back into the original Administrator account with which I´d had problems, and Dropbox is working there too! No idea why, but there it is. Will try on the other 2 laptops now...
- Kester10 years agoCollaborator | Level 8
Hi Roberto,
Now you have Dropbox working (at least on one of your laptops), do you still get an error in the Event Viewer on startup followed by Windows recovering the situation and allowing the Dropbox service to run? If you get no error, it looks like you've solved the situation and perhaps pbuco and I will get over our Event Viewer neurosis :relieved: and others who have posted on this thread will get some relief too.
What a shame nobody from Dropbox has, as yet, come forward with any suggestions.
- pbuco10 years agoExplorer | Level 4
Hi roberto,
and thx for the information! I updated out of the Win 10 Dropbox App using a Microsoft Account...
Gonna try your proceding.
Keeping you in the loop
- Kester10 years agoCollaborator | Level 8
Unfortunately installing Dropbox in a new administrator user account did not eradicate the Event Viewer error on startup although, as previously, the Dropbox program works correctly afterwards. Perhaps roberto's problem with Dropbox was additional to the Event Viewer error - perhaps roberto could clarify if his fix has cleared the Event Viewer problem for him as well.
- pbuco10 years agoExplorer | Level 4
Same here too - didn't work.
Gonna have a visit at S. Freud's Museum next we... :wink:
- Kester10 years agoCollaborator | Level 8
Must be handy for you pbuco living in Vienna. Here in the UK we just bash our heads against the wall for a little light relief (can't get the treatment through the National health Service though). :grimacing: Oh well, let's see what develops.
- orion4410 years agoHelpful | Level 6
Any ETA to Production for the fix?
- Kester10 years agoCollaborator | Level 8
Hi Orion,
Dropbox have been rather quiet about the problem and, as far as I know, have not recognised that it exists. Emails I get from Dropbox Support have been spasmodic and suggestions given have related to possible problems with my system rather than the Dropbox program itself. Clearly, when this forum thread suggests the problem is fairly widespread, there must be a program bug. It is disappointing that, as yet, no Dropbox technical staff have contributed to this thread and appear not to have read any of the posts despite the fact that you submitted a bug report. Did you get any feedback afterwards?
So there appears to be no estimated time of arrival for a fix because the problem has not been officially recognised.
- roberto l.110 years agoExplorer | Level 3Hi, our Dropbox installation problem is not related to the Event Logs problem, the Event Logs continue showing "Failed to connect to the driver: (-2147024894) The system cannot find the file specified."
We have been able to get Dropbox working on all laptops now - we revised the driver installation and tweaked a couple of things, this seems more likely to have caused the installation issues.
Clearly, the Event Log Id 320 is totally unrelated and still exists. - Kester10 years agoCollaborator | Level 8
Hi Roberto,
That's good news regarding Dropbox running on your laptops - let's hope that Dropbox technical staff can sort this Event Viewer problem soon. At least we can all use the program despite the irritating error message.
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!