Unknown Token Received From SQL Server

• TerryS

  SSCommitted

  Points: 1802

  More actions

  February 13, 2025 at 8:14 pm

  #4537017

  I have not worked on a fix as our failing jobs are non-essential at this time.

  Perhaps use Windows Task Scheduler and SQLCMD instead of SQL Agent?

• bmcmeans76

  SSC Enthusiast

  Points: 176

  More actions

  February 13, 2025 at 10:31 pm

  #4537132

  That's a good thought. For the time being, I was able to remove the updated ODBC driver and re-apply the most current 13.1 version found on the MS site. The agent services started fine and the job I had a problem with worked fine. So it's definitely in the ODBC driver. No idea why

• mightierthor

  Grasshopper

  Points: 11

  More actions

  March 4, 2025 at 4:21 pm

  #4551054

  Just chiming in that we are also using this version, are getting the same error through SS Agent, but are getting the error when running interactively.   We are going through a linked server (to CRM, FYI).  Have not yet checked ODBC.

  • This reply was modified 3 months ago by mightierthor.
  • This reply was modified 3 months ago by mightierthor.

• as_1234

  SSCrazy

  Points: 2871

  More actions

  May 29, 2025 at 5:33 pm

  #4599497

  We've been having the same problem and I found this 'KB5046855 - Description of the security update for SQL Server 2016 SP3 GDR: November 12, 2024 - Microsoft Support'

  Particularly the section on 'Fix for "unknown token" error'.

  We weren't able to install that patch so I don't know if it works but I thought I'd share it in case it's useful.

  Apologies if the link doesn't work correctly. If I use the "insert/edit" link option then my post doesn't appear for some reason.