We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
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
254 Replies
Replies have been turned off for this discussion
Hi Mark,
Unfortunately the resolution is out of the user's hands but we are told that the Dropbox development team are working to find a solution. Fortunately, at least formost of us, we are still able to use Dropbox as normal.
Hi all,
received Dropbox 16.4.29 today - the error still persists...
Greetings
- Luke, if you are reading this, you're in the right place.
- I fast fix error drive start whithout copy file or edit regedit:
MKLINK "C:\Windows\System32\drivers\dbx.sys" "C:\Windows\System32\drivers\dbx-canary.sys"
It's work end drive normal start:
The file is signed and the signature was verified: C:\Program Files (x86)\Dropbox\Client\Dropbox.exe
Certificate match for file: C:\Program Files (x86)\Dropbox\Client\Dropbox.exe
Accepting connection from client: C:\Program Files (x86)\Dropbox\Client\Dropbox.exe
Алексей Д.1 schrieb:
I fast fix error drive start whithout copy file or edit regedit:
MKLINK "C:\Windows\System32\drivers\dbx.sys" "C:\Windows\System32\drivers\dbx-canary.sys"
It's work end drive normal start:
The file is signed and the signature was verified: C:\Program Files (x86)\Dropbox\Client\Dropbox.exe
Certificate match for file: C:\Program Files (x86)\Dropbox\Client\Dropbox.exe
Accepting connection from client: C:\Program Files (x86)\Dropbox\Client\Dropbox.exeHi,
How you did it? Please explain us the steps.
Thanks
Vik
- open CMD (press win+r and write CMD)
Check windows folder disk letter (defualt C)
Copy and paste, then press enter and relauch dropbox:
MKLINK "C:\Windows\System32\drivers\dbx.sys" "C:\Windows\System32\drivers\dbx-canary.sys" - HI:
I have teh same error:
Failed to connect to the driver: (-2147024894) El sistema no puede encontrar el archivo especificado.
Try run with all compatibilities, an make the las solution make the link, nothing... I try and if have solution tell us... Regards - One detail more....
When try to use, stay in configure form and this are balnk... con eat all procesors Hi to everyone:
I resolve this download the version:
https://www.dropbox.com/downloading?build=14.4.19&plat=win&type=full
14.4.19
I have a re-build machine whit this details:
Processors
-------------------------------------------------------------------------Number of processors 1
Number of threads 2APICs
-------------------------------------------------------------------------Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1Timers
-------------------------------------------------------------------------ACPI timer 3.580 MHz
Perf timer 3.085 MHz
Sys timer 1.000 KHz
Processors Information
-------------------------------------------------------------------------Processor 1 ID = 0
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name Intel Core 2 Duo E8500
Codename Wolfdale
Specification Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
Package (platform ID) Socket 775 LGA (0x0)
CPUID 6.7.A
Extended CPUID 6.17
Core Stepping E0
Technology 45 nm
TDP Limit 65.0 Watts
Core Speed 1995.0 MHz
Multiplier x Bus Speed 6.0 x 332.5 MHz
Rated Bus speed 1330.0 MHz
Stock frequency 3166 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, EM64T, VT-x
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 6144 KBytes, 24-way set associative, 64-byte line size
Max CPUID level 0000000Dh
Max CPUID ext. level 80000008h
Cache descriptor Level 1, D, 32 KB, 1 thread(s)
Cache descriptor Level 1, I, 32 KB, 1 thread(s)
Cache descriptor Level 2, U, 6 MB, 2 thread(s)
FID/VID Control yes
FID range 6.0x - 9.5x
Max VID 1.288 VTemperature 0 37 degC (98 degF) (Core #0)
Temperature 1 34 degC (93 degF) (Core #1)
Clock Speed 0 1995.02 MHz (Core #0)
Clock Speed 1 1995.02 MHz (Core #1)
Chipset
-------------------------------------------------------------------------Northbridge Intel Q45/Q43 rev. 03
Southbridge Intel 82801JB (ICH10) rev. 02
Memory Type DDR3
Memory Size 8 GBytes
Channels Dual, (Symmetric)
Memory Frequency 532.0 MHz (5:8)
CAS# latency (CL) 7.0
RAS# to CAS# delay (tRCD) 7
RAS# Precharge (tRP) 7
Cycle Time (tRAS) 20
Row Refresh Cycle Time (tRFC) 86
Command Rate (CR) 2T
Host Bridge 0x2E10Memory SPD
-------------------------------------------------------------------------DIMM # 1
SMBus address 0x50
Memory type DDR3
Module format UDIMM
Manufacturer (ID) (00000000000000000000)
Size 2048 MBytes
Max bandwidth PC3-10700 (667 MHz)
Part number V01D3L82GB26826813
Manufacturing date Week 16/Year 15
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP no
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-17-23 @ 457 MHz
JEDEC #3 7.0-7-7-20-27 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-24-33 @ 666 MHz
JEDEC #6 10.0-9-9-24-33 @ 666 MHzDIMM # 2
SMBus address 0x51
Memory type DDR3
Module format UDIMM
Manufacturer (ID) (00000000000000000000)
Size 2048 MBytes
Max bandwidth PC3-10700 (667 MHz)
Part number V01D3L82GB26826813
Manufacturing date Week 16/Year 15
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP no
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-17-23 @ 457 MHz
JEDEC #3 7.0-7-7-20-27 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-24-33 @ 666 MHz
JEDEC #6 10.0-9-9-24-33 @ 666 MHzDIMM # 3
SMBus address 0x52
Memory type DDR3
Module format UDIMM
Manufacturer (ID) (00000000000000000000)
Size 2048 MBytes
Max bandwidth PC3-10700 (667 MHz)
Part number V01D3L82GB26826813
Manufacturing date Week 16/Year 15
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP no
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-17-23 @ 457 MHz
JEDEC #3 7.0-7-7-20-27 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-24-33 @ 666 MHz
JEDEC #6 10.0-9-9-24-33 @ 666 MHzDIMM # 4
SMBus address 0x53
Memory type DDR3
Module format UDIMM
Manufacturer (ID) (00000000000000000000)
Size 2048 MBytes
Max bandwidth PC3-10700 (667 MHz)
Part number V01D3L82GB26826813
Manufacturing date Week 16/Year 15
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP no
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-17-23 @ 457 MHz
JEDEC #3 7.0-7-7-20-27 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-24-33 @ 666 MHz
JEDEC #6 10.0-9-9-24-33 @ 666 MHzThe machine is very old.
Maybe some old isntructions are out from thye new binaries.
Hi,
the error is still present with the latest DB version (16.4.30). I did some research for the error code -2147024894, which if converted to a 32 bit hexadecimal value results to 0x80070002. I found a registry for those values at Symantec, and it revealed it to be of type "Win32 Error Codes for ADSI". Additional Research at Microsofts Developer Network showed a bit more details: Looks like it is the error code for a failed LDAP request (LDAP_NO_SUCH_OBJECT). So the questions seems to be: Why does DB do LDAP (or Active Directory with Windows) requests? And will the observed error within Event Viewer only happen with Windows PCs that are not members of an Active Directory?
I did some further investigation and figured out that the error was safely reproducible every time the "DbxSvc" service starts. Hence inside service manager I stopped this service and started Wireshark and SysInternal's Process Monitor in order to see what happens after I have started the service again (this way provoking the error to happen once more).
These are the results: During service start no network activity could be observed. All file and registy access of the process named "DbxSvc.exe" didn't reveal any hints that something went wrong (no results more critical (but normal) than "NAME NOT FOUND" or "BUFFER OVERFLOW" with registy access or "FILE LOCKED WITH ONLY READERS" with file access).
Only the last registry access asks for the value of "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\WMR\Disable", probably to check if errors should be reported to Microsoft.
Hence, it's still a mystery why this error happens. This thread says, that this service isn't even needed to use DB:
"You noted sync still appears to work correctly without this service however should you encounter any sync issues with the service removed it will limit our ability to resolve the issue."
Btw: The OP reported about ESENT messages he believes cause a recovery from the error state. With my PC I also see these ESENT messages but they happen at other times than the DbxSvc.exe error - hence, I believe they are independent from each other.
