ODBC fails after changing pc date

0

We have a girl here who runs a report successfully, then changes the date on her pc, then tries the report again and gets a Connection failed error.

  • The report is ran in MS Access 2003
  • The ODBC itself uses Windows Authentication
  • The linked table uses a UID different than her Windows login
  • The error when running the report: SQLState '28000' SQL Server Error: 18452 "[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection."
  • Error received when testing the ODBC: SQLState '08004' SQL Server Error: 4060 "Server rejected the connection; Access to selected database has been denied."
  • The SQL Log had this error: "SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: ##.##.##.##]"
  • I am able to recreate the failure on my machine.

I'm thinking it's something between the Windows Authentication/Active Directory/ODBC but I'm not very experienced in the first 2.

And yes, I know this isn't an ideal situation. This will all be converted to C#.NET at some point.

TIA for any ideas.

sql-server
ms-access
odbc
system-clock
asked on Stack Overflow Jan 24, 2013 by pkfuss • edited Jan 24, 2013 by Fionnuala

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0