February 13, 2025 at 8:14 pm
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?
February 13, 2025 at 10:31 pm
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
March 4, 2025 at 4:21 pm
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.
May 29, 2025 at 5:33 pm
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.
Viewing 4 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy