Can't run RAISERROR remotely - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

Transact-SQL (2008)

Can't run RAISERROR remotely

Author

Topic

GustiX
Starting Member

28 Posts

Posted - 2012-06-14 : 08:07:43

Hi

I am having problems running the RAISERROR command remotely,
i.e. if I log into the SQL server using SSMS on the computer
itself it works, if I log into the server using SSMS from another
computer it fails with the following error message:

Msg 121, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)

This is driving me nuts!!! please help

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2012-06-14 : 08:19:34

Are you running a stored procedure by default when logging in?

N 56°04'39.26"
E 12°55'05.63"

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2012-06-14 : 08:30:41

does the severity level make a difference?

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

GustiX
Starting Member

28 Posts

Posted - 2012-06-14 : 09:21:51

The severity doesn't matter, I tried from 0 to 16 and always the same result...

GustiX
Starting Member

28 Posts

Posted - 2012-06-14 : 09:22:22

quote:
Originally posted by SwePeso

Are you running a stored procedure by default when logging in?

N 56°04'39.26"
E 12°55'05.63"

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2012-06-14 : 09:44:45

Do you have a firewall between you and the remote system?

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

GustiX
Starting Member

28 Posts

Posted - 2012-06-14 : 09:57:11

quote:
Originally posted by nigelrivett

Do you have a firewall between you and the remote system?

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

There is no firewall on the server or the client computer but the computers are a 100 miles apart and go through all sort of routers which might have firewalls

GustiX
Starting Member

28 Posts

Posted - 2012-06-14 : 10:25:55

Is RAISERROR doing something that requires open ports
in a firewall (other than the standard 1433 sql port)?

We have 2 client computers, this works like a charm on
one of them, that computer is inhouse. It doesn't work
on the other computer which is a 100 miles away.
The setup on these 2 computers is pretty much identical

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2012-06-14 : 11:25:55

http://social.msdn.microsoft.com/Forums/en-US/transactsql/thread/145df575-0b0a-4aaa-a0c2-56ef50dacd7c/

That's the only thing I can find that looks applicable.
Could it be that your remote machine is trying to hold a distributed transaction that is getting terminated by the error?

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources