January 24, 2017 at 3:08 am
Hi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
January 24, 2017 at 3:35 am
sc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
Whenever you get an "Operating system error", go to a command prompt and type net helpmsg and the error number. This particular error means "The network path was not found". Are you sure that's the correct path? What happens if you log on to the server and map a drive to \\WIN-UC7TSJO3UEM\Log shipping?
John
January 24, 2017 at 3:51 am
sc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
follow my article at this link for more info
Log shipping across workgroups
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 24, 2017 at 4:06 am
John Mitchell-245523 - Tuesday, January 24, 2017 3:35 AMsc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
Whenever you get an "Operating system error", go to a command prompt and type net helpmsg and the error number. This particular error means "The network path was not found". Are you sure that's the correct path? What happens if you log on to the server and map a drive to \\WIN-UC7TSJO3UEM\Log shipping?
John
Thanks for the reply John,
Are you saying have the mapping going from destination B to source A or source A to destination server B or both? When I looked through all the online articles there was no mention of drive mapping but it makes sense that that there is a connection issue with copying the files.
January 24, 2017 at 4:12 am
sc-w - Tuesday, January 24, 2017 4:06 AMAre you saying have the mapping going from destination B to source A or source A to destination server B or both? When I looked through all the online articles there was no mention of drive mapping but it makes sense that that there is a connection issue with copying the files.
I'm saying go to the server that isn't WIN-UC7TSJO3UEM, and try to map a drive to WIN-UC7TSJO3UEM. No, drive mapping isn't part of log shipping - I just wanted you to check that whether the path is correct by attempting to map the drive. And then maybe go through Perry's article - it sounds as if that will be quite helpful.
John
January 24, 2017 at 4:55 am
sc-w - Tuesday, January 24, 2017 4:06 AM😉
John Mitchell-245523 - Tuesday, January 24, 2017 3:35 AMsc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
Whenever you get an "Operating system error", go to a command prompt and type net helpmsg and the error number. This particular error means "The network path was not found". Are you sure that's the correct path? What happens if you log on to the server and map a drive to \\WIN-UC7TSJO3UEM\Log shipping?
John
Thanks for the reply John,
Are you saying have the mapping going from destination B to source A or source A to destination server B or both? When I looked through all the online articles there was no mention of drive mapping but it makes sense that that there is a connection issue with copying the files.
all detailed in my article 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 24, 2017 at 10:10 am
Perry Whittle - Tuesday, January 24, 2017 4:55 AMsc-w - Tuesday, January 24, 2017 4:06 AM😉
John Mitchell-245523 - Tuesday, January 24, 2017 3:35 AMsc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
Whenever you get an "Operating system error", go to a command prompt and type net helpmsg and the error number. This particular error means "The network path was not found". Are you sure that's the correct path? What happens if you log on to the server and map a drive to \\WIN-UC7TSJO3UEM\Log shipping?
John
Thanks for the reply John,
Are you saying have the mapping going from destination B to source A or source A to destination server B or both? When I looked through all the online articles there was no mention of drive mapping but it makes sense that that there is a connection issue with copying the files.
all detailed in my article 😉
Thanks Perry, it is a great article and I have my setup configured as the article describes but I am still getting the error in my originally post. From server A I can connect to SQL fine on Server B and from server B I can connect fine to SQL on Server A.
Any other tests I can run?
January 24, 2017 at 10:49 am
sc-w - Tuesday, January 24, 2017 10:10 AMPerry Whittle - Tuesday, January 24, 2017 4:55 AMsc-w - Tuesday, January 24, 2017 4:06 AM😉
all detailed in my article 😉
Thanks Perry, it is a great article and I have my setup configured as the article describes but I am still getting the error in my originally post. From server A I can connect to SQL fine on Server B and from server B I can connect fine to SQL on Server A.
Any other tests I can run?
it's not the sql connection, the copy job is a file copy process nothing to do with the sql instance
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 24, 2017 at 11:21 am
sc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
the network path cannot be found. Even though you can connect via sql server this does not mean there is no firewall running and this will by default block netbios ports which are required for file access.
Also, name resolution between the machines? Have you configured entries in your local hosts files to allow the name resolution, have you tried the IP address instead of computername?
Read my article carefully, you have missed a great deal of it i would think
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 24, 2017 at 1:58 pm
Perry Whittle - Tuesday, January 24, 2017 11:21 AMsc-w - Tuesday, January 24, 2017 3:08 AMHi,
I have a need to setup log shipping across two networks thathave no domain relationship. They aretwo separate work groups. I have been through every tutorial online to get thisworking but I am having an issue with what I believe is the permissions acrossthe two network/servers.
The actual setting up of the log shipping is fairly simple,I understand the logic. I can connect between the two SQL servers using IP addressport 1433 (I know this port is not secure I am just using it to get the logshipping working), so I can open databases from both sides no issues. So I don’tthink there is any firewall / connection related issues.
I have setup new window accounts on each server calledSQLSVC with the same passwords and set the SQL service Agents on both machineswith these new accounts (restarted the services also). I have given full readand write access to the two directories on each server that will hold the SQLlogs to these new accounts. On the primary server ‘A’ I have set the log foldedI created as shared with full permissions given to the local SQL service agent.I can allocate any additional permissions I need but I have even added (the everyone)account and given that full permission just to test.
Where it is falling over is when I do the ‘Save Log ShippingConfiguration’, it backs up the database on server ‘A’ ready to restore onserver ‘B’ and is at the restore step I get this error.
The SQL on both servers is exactly the same version. SQL 2008 R2
What am I missing? Any help would be really great thanks forlooking.
Restore backup to secondary database ….. ERROR….
TITLE: Microsoft SQL Server Management Studio
------------------------------
SQL Server Management Studio restore database ' testdb '
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQLstatement or batch. (SqlManagerUI)
------------------------------
Cannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
the network path cannot be found. Even though you can connect via sql server this does not mean there is no firewall running and this will by default block netbios ports which are required for file access.
Also, name resolution between the machines? Have you configured entries in your local hosts files to allow the name resolution, have you tried the IP address instead of computername?
Read my article carefully, you have missed a great deal of it i would think
Hi, I went back and checked your article and didn't see anything about NetBIOS ports but I had found this somewhere as I had tcp and udp ports open on both sevrers for ports 137,138 and 139.
I have only been using ip addresses not server names, I will take a look at the local host files as I am not familiar with these.
This one is certainly a tough one to solve.
January 24, 2017 at 7:11 pm
sc-w - Tuesday, January 24, 2017 3:08 AMCannot open backup device '\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'.Operating system error 53(failed to retrieve text for this error. Reason:15100).
RESTORE FILELIST is terminating abnormally. (Microsoft SQLServer, Error: 3201)
Is the Log Shipping folder shared? Can you connect to it from Server B using something like Windows Explorer?
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
January 26, 2017 at 9:29 am
sc-w - Tuesday, January 24, 2017 1:58 PMI have only been using ip addresses not server names, I will take a look at the local host files as I am not familiar with these.
How on earth is this classed as using IP address?
'\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 26, 2017 at 9:42 am
Perry Whittle - Thursday, January 26, 2017 9:29 AMsc-w - Tuesday, January 24, 2017 1:58 PMI have only been using ip addresses not server names, I will take a look at the local host files as I am not familiar with these.How on earth is this classed as using IP address?
'\\WIN-UC7TSJO3UEM\Log shipping\testdb.bak'
Good point! That is the name of the source server that the log shipping setup on. That resolves fine. I tested so much replacing names and ip's I copied the error with the server name not internal IP. Same issue no matter what I use.
January 26, 2017 at 11:30 am
sc-w
That is the name of the source server that the log shipping setup on.
And that is the default, it uses a local folder on the primary server and informs you during confighuration to share this folder for network access
Have you tried manually restoring a backup of the primary database to the secondary to pre stage rather than let LS setup perform this?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply