January 20, 2021 at 8:14 pm
Does anybody know why existence of string sp_replwritetovarbin in the statement causes a transport-level error?
Any of the statement below completes with error:
Msg 64, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
select 'sp_replwritetovarbin'
go
select 'Ok' -- sp_replwritetovarbin
go
select 'Ok'
/*
sp_replwritetovarbin
*/
go
create table test ( name nvarchar(128) );
insert test values ('sp_replwritetovarbin');
drop table test;
go
create table test ( name nvarchar(128) );
insert test values ('spreplwritetovarbin'); -- sp_replwritetovarbin
drop table test;
go
create table test ( name nvarchar(128) );
insert test values ('spreplwritetovarbin');
/*
sp_replwritetovarbin
*/
drop table test;
go
January 21, 2021 at 9:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
January 21, 2021 at 11:35 pm
What version of SQL Server (@@VERSION)?
Using SSMS? Or another client?
Does it work using #test rather than test?
Are you in master or another database? Do other queries to same database work?
It works for me on SQL Server 2017 (RTM-CU22-GDR) (KB4583457) - 14.0.3370.1 (X64) using test or #test.
January 25, 2021 at 2:32 pm
What version of SQL Server (@@VERSION)? ..., 2017, 2019
Using SSMS? Or another client? SSMS
Does it work using #test rather than test? NO
Are you in master or another database? Do other queries to same database work? any database
It works when I execute statements locally on the server. But don't work when I connected remotely WFH and run them on my desktop using SSMS. It can be VPN or Firewall reaction on the string. Can anybody test and confirm?
January 25, 2021 at 4:13 pm
SSMS 18.5
Works fine for me on
14.0.2037 (RTM-GDR)
15.0.2080.9 (RTM-GDR)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply