You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
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 T...
- 8 years ago
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
- 8 years agoHi 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:
Kester
Collaborator | Level 8
Hi glatzfront,
From what you say it appears that the Task Scheduler problems are not related to EventID 320 DbxSvc (-2147024894) so, if you want Dropbox, reinstalling it should not be a problem other than the appearance of the Event Viewer error on each startup. It may be worth you posting on a Windows 7 forum such as http://www.sevenforums.com/ regarding your Task Scheduler problem.
glatzfront
9 years agoExplorer | Level 4
Does this reply mean that you have checked your Task scheduler?
- orion449 years agoHelpful | Level 6Dropbox support advised to uninstall and reinstall Dropbox. No effect - error still occurs.
- Kester9 years agoCollaborator | Level 8
Hi glatzfront,
All I've checked in in the Task Scheduler is the tasks I have scheduled and they are running correctly (including Dropbox) - I have not attempted to import a task or modify a task. Did your Task Scheduler problem occur at the same time that you first installed Dropbox? If so, it is possible that Dropbox may have corrupted a file in the Task Scheduler. It is also possible that a Windows update may have corrupted a Task Scheduler file or, if you upgraded to Windows 10 and then returned to Windows 7, the Task Scheduler may have been upset (there are reports of this happening). Does the Event Viewer report any problems after you try to use the Task Scheduler?
You may like to investigate the following web page: http://windowsdiscussions.com/task-scheduler-windows-7-has-been-corrupted-77320.html - it may be helpful.
- glatzfront9 years agoExplorer | Level 4
Kester wrote:Hi glatzfront
All I've checked in in the Task Scheduler is the tasks I have scheduled and they are running correctly (including Dropbox) - I have not attempted to import a task or modify a task. Did your Task Scheduler problem occur at the same time that you first installed Dropbox? If so, it is possible that Dropbox may have corrupted a file in the Task Scheduler. It is also possible that a Windows update may have corrupted a Task Scheduler file or, if you upgraded to Windows 10 and then returned to Windows 7, the Task Scheduler may have been upset (there are reports of this happening). Does the Event Viewer report any problems after you try to use the Task Scheduler?
You may like to investigate the following web page: http://windowsdiscussions.com/task-scheduler-windows-7-has-been-corrupted-77320.html - it may be helpful.
Best way to find out is to check "Properties" for any task in the scheduler. If others have the problem?
I found several solutions(?) at this thread. Below is the one that worked for me.
Task Scheduler crashed
To resolve the problem,
1.Run regedit
2.Go to HKLM\Software\Microsoft\Windows NT\CurrentVersion\NetworkList
3.Delete everything under the following path,
Nla->Cache
Nla->IntranetEnabled
Nla->Wireless
Profiles
Signatures->Managed
Signatures->Unmanaged
4.Reboot - Kester9 years agoCollaborator | Level 8
Hi glatzfront,
Glad you have resolved your Task Scheduler problem and good of you to share your resolution. Let's hope Dropbox sort out the Event Viewer error soon as it has been going on since the end of October and posters on this thread have provided possible clues - Dropbox seem to be ignoring the thread and have not responded here, a poor show I feel.
- Ed9 years agoDropbox StaffHi all,
Quick update to let you know our team is investigating this. I'll share updates as soon as I hear back from them.
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.
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!