October 31, 2007 at 9:46 am
Hi all,
I am trying to configure remote log shipping and getting following error.
I have checked everything on both the sides and looks perfect. Primary backup and secondary copy folders are also shared. Same agent accounts are used on both the sides. Same SQL Server builds. There is no issue from the log shipping configuration point of view, it is all checked. Firewall is also opened for both the boxes, cause I copied logs from primary only.
2007-10-31 13:41:16.98 *** Error: Could not retrieve copy settings for secondary ID '57aca123-d18b- 424e-a1e4- 37da8b80060a' .(Microsoft. SqlServer. Management. LogShipping) ***
2007-10-31 13:41:16.98 *** Error: The specified agent_id 57ACA123-D18B- 424E-A1E4- 37DA8B80060A or agent_type 1 do not form a valid pair for log shipping monitoring processing.( .Net SqlClient Data Provider) ***
2007-10-31 13:41:16.98 *** Error: Could not log history/error message.(Microsoft. SqlServer. Management. LogShipping) ***
2007-10-31 13:41:16.98 *** Error: The specified agent_id 57ACA123-D18B- 424E-A1E4- 37DA8B80060A or agent_type 1 do not form a valid pair for log shipping monitoring processing.( .Net SqlClient Data Provider) ***
2007-10-31 13:41:16.98 *** Error: Could not cleanup history.(Microsoft. SqlServer. Management. LogShipping) ***
2007-10-31 13:41:16.98 *** Error: The specified agent_id 57ACA123-D18B- 424E-A1E4- 37DA8B80060A or agent_type 1 do not form a valid pair for log shipping monitoring processing.( .Net SqlClient Data Provi
Can anyone tell me what is the problem in this?
November 29, 2007 at 2:29 am
Hi,
I too have faced the same problem......
N E one kindly suggest....
November 29, 2007 at 4:47 am
I think .. the agent does not have sufficient privileges.. check that
"More Green More Oxygen !! Plant a tree today"
November 29, 2007 at 5:06 am
hi,
but how to check the privileges for the agent......
November 29, 2007 at 5:39 pm
If the Agent is a domain account, check the permissions on the SQL Log directory on both servers. Also check for misconfiguration on the log shipping jobs. Maybe it's trying to log to a server/database that doesn't exist.
November 29, 2007 at 10:37 pm
hi,
I have set up logshipping using the sa credentials for all the servers... i.e the primary server,the secondary server and the monitor server. the situation is like this :
the logshiping is succeding for the primary server
it is failing for the secondary server...... the log copy and restore are failing.
can anyone suggest how to share the folders for copying the logs to the secondary server......
another question is that i have created SQLAdmin user and have given sqladmin rights to it..... do we need to change the owner of the jobs to the SQLAdmin ????
November 29, 2007 at 10:39 pm
Purnell is right follow that. Is it possible to resetup the Log shipping once again. That might help.
"More Green More Oxygen !! Plant a tree today"
November 29, 2007 at 11:35 pm
Change the log shipping configuration to run under the account of sql agent. then check the log shi[pping jobs also to run under the configuration of the sql agent account.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
November 30, 2007 at 3:17 am
Again the same message... though i recreated Logshipping....
Is this sugesh --- samuel ignatius's friend?
Message
2007-11-30 15:30:06.12*** Error: Could not retrieve copy settings for secondary ID 'bc37f819-c675-4ad4-b013-48ef941a1b64'.(Microsoft.SqlServer.Management.LogShipping) ***
2007-11-30 15:30:06.12*** Error: The specified agent_id BC37F819-C675-4AD4-B013-48EF941A1B64 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2007-11-30 15:30:06.17*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2007-11-30 15:30:06.17*** Error: The specified agent_id BC37F819-C675-4AD4-B013-48EF941A1B64 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2007-11-30 15:30:06.20*** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2007-11-30 15:30:06.20*** Error: The specified agent_id BC37F819-C675-4AD4-B013-48EF941A1B64 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provi
November 30, 2007 at 3:24 am
i have re setup transaction log shipping .....but no success....
i'm running 2 instances 2000 and 2005 2 dbs of each instance are to be logshipped...
is there anything to do with the updates or the service packs???
presently i'm having the following configuration
SQL2005 (primary server)
Microsoft SQL Server 2005 - 9.00.3175.00 (X64) Jun 14 2007 11:45:39 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)
log shipped to
SQL2005(secondary server)
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Kindly suggest
November 30, 2007 at 5:38 am
Is is possible you are trying Log shippng from 2000 to 2005 or vice versa?? In general, they are not compatible.
November 30, 2007 at 5:46 am
no the two instances are in 2005......
November 30, 2007 at 6:08 am
May be a new bug..not sure better contact support.
"More Green More Oxygen !! Plant a tree today"
August 19, 2008 at 12:59 am
Hi Everyone,
We faced the same problem as well. Have tried these:
Running with wizard vs script
Give Admin rights to SQL Agent Account
Put latest SQL 2005 Patches and Window patches.
Still can't figure out what cause it to failed. Any suggestions.
Best Regards,
C.W.Chan
January 12, 2009 at 2:41 am
Hi,
Sorry for hijacking, but I have exactly the same problem. If anyone found any solution to this please tell.
Viewing 15 posts - 1 through 15 (of 32 total)
You must be logged in to reply to this topic. Login to reply