Log Shipping problem saving secondary destination configuration in SQL 2005

Question

Post reply

Log Shipping problem saving secondary destination configuration in SQL 2005

Viewing 7 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

ac2 Old Hand Points: 345 More actions · Answer 1

any insight would be greatly appreciated, thanks.

samir 8855 SSC Enthusiast Points: 142 More actions · Answer 2

I am having the same issue of logging to SQLServer 2005.

"User Action

Make sure that you have configured the firewall on the server instance of SQL Server to accept connections."

I have not firewall configured. Please help.

ps. One Orange Chip Points: 29423 More actions · Answer 3

from the primary, can u connect to secondary and fire queries?

Pradeep Singh

Silverfox SSC-Insane Points: 23150 More actions · Answer 4

Can you script out your log shipping configuration and run the procs one by one to help further

I take it that, checking @@servername on both instances reports everything correctly and that sysservers is ok

--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]

Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]

samir 8855 SSC Enthusiast Points: 142 More actions · Answer 5

Unable to connect to SQLServer Database? Please help. URGENT.

http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2

Winsolin.

Rajat Jaiswal-337252 SSCommitted Points: 1779 More actions · Answer 6

Hi

i have same problem

"The specified @server_name ('WIN-xxx) does not exist.

SQL Server Management Studio could not save the configuration of 192.168.1.

119 as a Secondary. (Microsoft SQL Server Management Studio)"

i have tried @@serverName and SELECT * FROM servername

are same.

Please its urgent.

Thanks

Rajat

IgorAmato Newbie Points: 1 More actions · Answer 7

I know this is an old post, but today I had the same problem (btw it took me 4 hours to find a solution). What I did was create the log shipping with SSMS and then create a log shipping script to check the procs. When I was looking i had an idea instead put the name on @primary_server I put the ip and success.

Hope this can help someone else.

tks.

Igor Amato.