ODBC Driver Causing Service Crash

Discussion of open issues, suggestions and bugs regarding usage of ODBC Drivers
Post Reply
jkaplan
Posts: 2
Joined: Tue 08 May 2018 16:16

ODBC Driver Causing Service Crash

Post by jkaplan » Tue 08 May 2018 16:37

Hello,

Our client is using your Salesforce ODBC driver in order to pull information from the Salesforce database in order to populate data in NetDocuments using the ndLink application from NetDocuments. The ODBC driver works fine when manually pushing the data using the ndLink application, however, the driver appears to cause the ndLink service to crash when it is set to sync the data automatically. The error details from the Windows log are:

Faulting application name: ndlink2service.exe, version: 1.0.0.0, timestamp: 0x591cc67c
Faulting module name: DevartODBCSalesforce.dll, version: 1.5.13.0, timestamp: 0x5a93c636
Exception code: 0xc0000005
Fault offset: 0x00004ef2
Faulting process id: 0x96c
Faulting application start time: 0x01d3e3076e5e2566
Faulting application path: C:\Program Files (x86)\NetDocuments Technical Services\ndLink2Service\ndLink2Service.exe
Faulting module path: C:\Progarm Files (x86)\Devart\ODBC\Salesforce\win32\DevartODBCSalesforce.dll
Report Id: b0a25810-4efa-11e8-80e1-3ca82a0dc6eb
Faulting package full name:
Faulting package-relative application ID:

That said, NetDocuments support suggested asking you if there is a particular user or user type that their service needs to be using to make use of the ODBC driver. By default their service runs as the Local System user.

Thanks,
Jeff

JEFF KAPLAN
Sr. Project Consultant
(612) 876-5432
http://ele-ment.com
TWIN CITIES | CHICAGO | NAPLES

MaximG
Devart Team
Posts: 930
Joined: Mon 06 Jul 2015 11:34

Re: ODBC Driver Causing Service Crash

Post by MaximG » Thu 10 May 2018 06:55

Thank you for providing the information. Unfortunately, the Windows log you provided is not enough to investigate the issue in our environment. For further issue investigation please
send us a log file containing the information on the performed operations. The log file can be obtained using the tracing mode in the ODBC Administrator utility. For this :


- run the ODBC Administrator utility and go to the "Tracing" tab
- specify the path to the log file and its name (for example, DEVARTSF.LOG)
- click the "Start Trace" button
- open the DSN configuration window of our driver and test the connection using the "Test Connection" button
- run ndLink2Service and perform the actions that lead to the error

Send us the obtained log file DEVARTSF.LOG)

jkaplan
Posts: 2
Joined: Tue 08 May 2018 16:16

Re: ODBC Driver Causing Service Crash

Post by jkaplan » Mon 14 May 2018 14:25

A portion of the requested log is below. I'm not able to paste in the whole log due to the limit on the number of characters in the post. If there is another way for me to submit the whole log to you, I would be happy to do so.

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

ndLink2 1724-1728 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08EF77B0

ndLink2 1724-1728 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08EF77B0 ( 0x058FD3C0)

ndLink2 1724-1728 ENTER SQLSetConnectAttrW
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

ndLink2 1724-1728 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F046D8

ndLink2 1724-1728 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F046D8 ( 0x058FD3C0)

ndLink2 1724-1728 ENTER SQLSetConnectAttrW
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

ndLink2 1724-1728 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F21CE8

ndLink2 1724-1728 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F21CE8 ( 0x058FD3C0)

ndLink2 1724-1728 ENTER SQLSetConnectAttrW
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

ndLink2 1724-1728 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F45E88

ndLink2 1724-1728 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F45E88 ( 0x058FD3C0)

ndLink2 1724-1728 ENTER SQLSetConnectAttrW
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

ndLink2 1724-1728 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F518D0

ndLink2 1724-1728 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F518D0 ( 0x058FD3C0)

ndLink2 1724-1728 ENTER SQLSetConnectAttrW
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

ndLink2 1724-1728 ENTER SQLFreeHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD3C0

ndLink2 1724-1728 ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F63D90

ndLink2 1724-1728 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x058FD340
SQLHANDLE * 0x08F63D90 ( 0x058FD3C0)

ndLink2 1724-1728 ENTER SQLSetConnectAttrW
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 EXIT SQLSetConnectAttrW with return code 0 (SQL_SUCCESS)
SQLHDBC 0x058FD3C0
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 15
SQLINTEGER -5

ndLink2 1724-1728 ENTER SQLDriverConnectW
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 EXIT SQLDriverConnectW with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0
HWND 0x00000000
WCHAR * 0x745B1F7C [ -3] "******\ 0"
SWORD -3
WCHAR * 0x745B1F7C <Invalid buffer length!> [-3]
SWORD -3
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>

ndLink2 1724-1728 ENTER SQLDisconnect
HDBC 0x058FD3C0

ndLink2 1724-1728 EXIT SQLDisconnect with return code 0 (SQL_SUCCESS)
HDBC 0x058FD3C0

Thanks,
Jeff

MaximG
Devart Team
Posts: 930
Joined: Mon 06 Jul 2015 11:34

Re: ODBC Driver Causing Service Crash

Post by MaximG » Thu 17 May 2018 13:23

Of course, you can send the log file using the e-support form (https://www.devart.com the "Support"\"Request Support" menu)

Post Reply