Start a Conversation

Unsolved

This post is more than 5 years old

1046

January 31st, 2007 16:00

MS SQL backups and named pipes

Hey all-

I have a Windows 2003 server running MS SQL Server 2005. I had the sysadmin install the MS Networker 5.0 module and set it all up on the Networker server. Normal file system backups work just fine from this client, but I can't seem to get the MS SQL database to back up by using the module. Here's the error I get:

01/31/07 15:45:56 Microsoft SQL Server Provider error:
01/31/07 15:45:56 Named Pipes Provider: Could not open a connection to SQL Server [2]. .
01/31/07 15:45:56 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
01/31/07 15:45:56 Login timeout expired.
01/31/07 15:45:56 Cannot login to SQL Server null.

The sysadmin for the client does NOT have named pipes turned on for SQL, since he doesn't like to use it. He's using standard TCP instead. From the client logs, Networker is successfully logging into the SQL box, it just doesn't seem to be talking to the SQL process. Does the MS SQL module require named pipes or will it work over plain old TCP?

86 Posts

February 1st, 2007 08:00

Is the account your using on the Legato side in the SA group on the SQL side?

2 Posts

February 1st, 2007 09:00

The Legato (server) side is a Solaris box, so the account is in Active Directory on the Windows side. I asked the sysadmin for the Windows box and he said the account does have system administrator access for SQL.

I'm more of a Unix guy than a Windows guy, so I hope that answered your question. =)
No Events found!

Top