November 2, 2010 at 11:57 pm
Hi,
I am trying to configure Log shipping on two sql 2005 enterprise servers.
There is no error shows in the wizard.
But after the wizard get closed, Backup job is created on primary server but copy and restore job is not getting cretaed on secondary server.
The database is in Standby mode on Secondary database.
Shared folder is accessible from both the servers in read - write mode.
Check the event viewer on both the servers but could not get any much info.
Kindly let me know if anybody has faced similar type of issue.
Thanks in Advance,
Regards,
Chetan
November 3, 2010 at 12:32 am
chetanr.jain (11/2/2010)
Hi,I am trying to configure Log shipping on two sql 2005 enterprise servers.
There is no error shows in the wizard.
But after the wizard get closed, Backup job is created on primary server but copy and restore job is not getting cretaed on secondary server.
The database is in Standby mode on Secondary database.
Shared folder is accessible from both the servers in read - write mode.
Check the event viewer on both the servers but could not get any much info.
Kindly let me know if anybody has faced similar type of issue.
Thanks in Advance,
Regards,
Chetan
Chetan,
Can you check both servers sqlservers errorlog & OS errorlog too.
Try to create a the test job in Secondary server.
Make sure the agent is started.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
November 3, 2010 at 1:08 am
I am using SQL Authenication while connecting to secodary server.
Does that will have any issue.
The sql login is part of sysadmin group.
Also, i have created script from the log shipping wizard.
When i am running the secondary server's part in query analyzer window, it is getting executed successfully.
But the jobs are not getting cretaed.
November 3, 2010 at 1:36 am
chetanr.jain (11/3/2010)
I am using SQL Authenication while connecting to secodary server.Does that will have any issue.
The sql login is part of sysadmin group.
Also, i have created script from the log shipping wizard.
When i am running the secondary server's part in query analyzer window, it is getting executed successfully.
But the jobs are not getting cretaed.
Please post the sqlserver errolog entries..
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
November 3, 2010 at 2:45 am
Here are the error which i am getting on the primary server.
2010-11-03 13:45:49.77 Logon Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.1.11.125]
2010-11-03 13:45:59.80 Logon Error: 18456, Severity: 14, State: 11.
10.1.11.125 = is the IP address of my secondary server.
November 3, 2010 at 8:15 am
@ chetan
Make sure that sql agent is running on the secondary server.
Also, check on the primary server...
Go to database log shiping configuration, click on the seconday server instances ...( three dots)
Make sure you can connect to secondary server by specifying a login and a password.
If it can connect, then check the copy files destination, check if they are correct...
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
November 3, 2010 at 10:12 pm
@ SKYBVI - Sushant
1) Agent is running on secondary server.
2) I can connect to the database
3) Copy file destination is good. that folder is accessible from primary as well as from secondary.
November 4, 2010 at 3:27 am
The error message you got clearly says Logshipping failed due to Login failure.
Try to use a Domain account. Else use same windows NT account for Logshipping configuration
Hope this will reslove this issue,
November 4, 2010 at 6:22 am
Did you check the the log_shipping_alert job (which get created when we use wizard) ?
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
January 9, 2012 at 7:10 pm
Also check the owner of the job by right clicking the job and properties and see the owner field. I had an issue with using windows authentication because it made the job and put my account as the owner
January 10, 2012 at 7:59 am
chetanr.jain (11/2/2010)
Shared folder is accessible from both the servers in read - write mode.
accessible for which accounts?
are your sql server servcies running under domain or local accounts?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 10, 2012 at 8:05 am
Posted Wednesday, November 03, 2010 12:27 PM
January 10, 2012 at 8:13 am
yep, saw that after i'd posted 😀
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 10, 2012 at 8:47 am
Thanks Perry for answering this.....
BTW... it was pretty old thing.. even i can't remember that does it was solved or not.
Nice to see response on such a old post....
January 11, 2012 at 3:24 am
As others have said this is clearly logon error.
Create domain account - Add this account to user group SQLServer2005SQLAgentUser$DATA$MSSQLSERVER on both servers. Run SQLAGENT on both servers using this account.
Make sure domain account has access to required backup and copy area's (shares) - Logon to server as that domain user and try copying files to share on other server to test.
Use this domain account when setting up logshipping - all jobs should be created on both servers with no problems.:-)
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply