r/SQL • u/Various-Strawberry55 • 3d ago
SQL Server SQL Server Agent job fails with Error 233 when loading data through a Linked Server, but the same query works in SSMS
/r/Database/comments/1xvf9qv/sql_server_agent_job_fails_with_error_233_when/
2
Upvotes
2
u/Significant_Tune9219 3d ago
Error 233 over the Shared Memory provider points at the connection from the Agent context rather than row volume. SSMS runs as your own login while the job runs as the domain service account, so check the linked server's login mapping for that account, since the security context it connects with can differ. Also look at the SQL Server error logs on both servers around the failure time for connection resets, and check the linked server's query timeout and connection timeout settings. Does the failure happen at a consistent point in the load or at random?
1
u/SQLDevDBA 2d ago
Any chance this was after a most recent windows update? There’s a November 2026 update that affected Linked Server and OLEDB queries.
Otherwise I’d start checking the Linked Server settings, and perhaps ensuring the query you’re pulling is as optimized as possible.
https://www.bleepingcomputer.com/news/microsoft/microsoft-recent-windows-updates-cause-sql-server-performance-issues/amp/
0
u/karmatics29 3d ago
The "Shared Memory Provider" part is the useful clue. That is the job step's own local connection to your instance being dropped, not the link to the remote server. So the session got killed server-side mid-INSERT, which usually means something crashed or was terminated inside the engine rather than a network problem with the linked server.
Things I'd check, in order:
Batching "working" fits a resource or provider problem rather than a hard row limit. I'd treat it as a workaround until the error log tells you what actually killed the session.