SQL Server Performance Forum – Threads Archive

File Will not copy

I am trying to set up an environment with log shipping using the Wizard. First of all I restored the database on the secondary machine and the transaction backup files did not copy or restore. No errors just no copy. I decided to Create and initialize the db from the primary machine. The backup works fine but I get the following error when copying the backup file. Unable to copy the initialization file to the secondary server ‘Credient-Net' The setup I have is as follows. Primary Server File Structure \SharedDatabaseLog Files \SharedDatabaseData Files \SharedDatabaseBackup Files Services Run as SQLSERVERAGENT INFINITYDownsJ MSSQLSERVER INFINITYDownsJ The above user is administrator of both machines. Secondary Server File Structure \SharedDatabaseLog Files \SharedDatabaseData Files \SharedDatabaseBackup Files Services Run as SQLSERVERAGENT INFINITYDownsJ MSSQLSERVER INFINITYDownsJ The above user is administrator of both machines. Please please Please can you come up with any suggestions to what the problem might be.[<img src=’/community/emoticons/emotion-6.gif’ alt=’

‘ />!]

Follow the workaround mentioned in this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;811890] Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Hi Satya, I did try what the Support site said. I was unable to register the secondary server as they are in the same domain and the other srtuff is already done. Do you have any other suggestions? Thanks Jamie.

What was the error while registering the secondary server? From FAQ
Do I have to start SQL Server related services under a domain account as opposed to a local Windows NT account? A3: It is possible to configure SQL Server services to start under a local Windows NT account, unless SQL Server is configured to run as a virtual server in conjunction with Microsoft Cluster Service. You can use Windows NT pass-through security for this purpose. Follow these steps to configure pass-through security:
Create a Windows NT account on the primary, secondary and monitor computers with the same name and passwords.
Configure SQL Server related services to start under these Windows NT accounts on all computers.
The SQL Server services must be started under a domain account if SQL Server is configured to run as a virtual server with Microsoft Cluster Service. Even if SQL Server is a virtual server, Microsoft recommends that you use a domain account to start the services when SQL Server computers are in a domain. You gain the following advantage by having SQL Server related services start under a domain account:
Change of password for the SQL Server start up account will not result in a failure of log shipping jobs. To successfully continue log shipping in a pass-through security situation, all the servers must have the password changed for the Windows NT start up account, at the same time.
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

The error was the following: INFINITY.CREDIENT-NET – SQL Server does not exist or access is denied.|ConnectionOpen(Connect()

Then follow this KBA http://support.microsoft.com/?kbid=328306] for the potential causes on this issue. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Why does it need the Domain name if both machines are in the same domain? I just tried registering another machine in the damain with the daomain name and that failed too.

If SQL Server is not listening on the protocol or port that you are using to connect. The Server Network Utility on the server determines which protocols SQL Server will use and on which TCP/IP ports SQL Server will listen. The Client Network Utility, an MDAC data source name (DSN), or your connection string determines which protocol and port your client uses when it connects. Other causes would be :
The security policy for your Windows account does not allow access from the network. The "Access this Computer from Network" policy must be permitted. Your name resolution is not working. Check your settings in the name resolution system that you use (such as DNS, WINS, hosts, or lmhosts). Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Hi Satya, At last. I have fixed the problem but am not sure which bit fixed but the main things I altered were as follows. Within the local security policy for: Local Policies>User Rights Assignment
Ensure the user that the SQL Server services is run as are included in the following:
Act as part of the operating system
Logon as a batch job
log on as a service
replace a process level token Also rebooted the secondary server. Thanks for your help and good luck to anyone else that suffers this misery Jamie.

]]>