by We've been having an issue with a third-party application, where an
unnecessary and annoying sql login prompt keeps popping up. The back
end is SQL 2000, SP3, nothing exotic, using mixed security. Per the
application's install instructions, a system dsn (mdac 2.7 sp1) is
utilized, with a SQL login name and password that is successfully
tested (the app, when launched, will prompt for which dsn to use, and
the user can check a box to have it automatically use that dsn in the
future..this works ok and the user is not again requested to do this).
The application has a feature whereby it can launch, in a window, a
crystal reports query to the database, and the user should not be
prompted for a password. However they are prompted, a sql login
dialog box pops up and requires the user to enter the password already
input into the dsn.
This only happens for a particular set of crystal reports that contain
"duration" formulas, these are customized formulas represented by
custom dll's on the workstation. These duration formulas are for
calculation of time duration between a beginning and ending date based
on a business day calendar in the database (in essence, it excludes
non-business hours from the calulations).
Is there any sql configuration setting on the client or server side
that anyone can think of that might be causing this? The vendor and
VAR don't have an answer for us...
I tried again using an odbc trace, below are snippets from that, the
first when starting the application, and it's successful connection,
and the second from the failed connection when launching the report
from within the app.
Hope you all have a good holiday!
===================Successful Connection (when starting
application)=================
CallLog32 1bc-43c ENTER SQLDriverConnectW
HDBC 010015E8
HWND 000801D4
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7B1D38
SWORD 8
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
CallLog32 1bc-43c EXIT SQLDriverConnectW with return code 1
(SQL_SUCCESS_WITH_INFO)
HDBC 010015E8
HWND 000801D4
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7B1D38
SWORD 8
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed
database context to 'Heat'. (5701)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Changed
language setting to us_english. (5703)
===========unsuccessful connection (when running report from within
app)===============
CallLog32 43c-300 ENTER SQLConnectW
HDBC 01001478
WCHAR * 0x01001DC8 [ -3] "HDHEAT\ 0"
SWORD -3
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
CallLog32 43c-300 EXIT SQLConnectW with return code -1
(SQL_ERROR)
HDBC 01001478
WCHAR * 0x01001DC8 [ -3] "HDHEAT\ 0"
SWORD -3
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
DIAG [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'heat'. (18456)
CallLog32 43c-300 ENTER SQLDriverConnectW
HDBC 01001478
HWND 0003020A
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7B1D38
SWORD 8
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
CallLog32 43c-300 EXIT SQLDriverConnectW with return code -1
(SQL_ERROR)
HDBC 01001478
HWND 0003020A
WCHAR * 0x1F7B1D38 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7B1D38
SWORD 8
SWORD * 0x00000000
UWORD 0 <SQL_DRIVER_NOPROMPT>
DIAG [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'heat'. (18456)
DIAG [01S00] [Microsoft][ODBC SQL Server Driver]Invalid connection
string attribute (0)