Failed to backup

• 
  One situation where the login may fail is if you are using Windows 2000, and the SQL Server instance name is identical to that of your machine name or cluster's virtual server name.
  
  Is your setup similar to this?

  petey June 18, 2006 03:16

  - 0 +
• 

  petey wrote:

  One situation where the login may fail is if you are using Windows 2000, and the SQL Server instance name is identical to that of your machine name or cluster's virtual server name. This is addressed in
  
  Is your setup similar to this?

  
  Yes. Any solutions for this?

  daniel_c June 18, 2006 18:27

  - 0 +
• 
  Pls contact support for a patch to version 4.2 for this. Version 4.5 will contain the fix.

  petey June 18, 2006 22:10

  - 0 +
• 
  I got the patch for 4.2, but even after I applied it, I still got the same error message. Any more ideas?
  
  My environment:
  Windows 2000 Server
  SQL Server 2000

  daniel_c June 26, 2006 13:04

  - 0 +
• 
  Could you pls use the command line interface and post the entire output (if it doesn't backup) e.g.
  
  sqlbackupc -sql "BACKUP DATABASE pubs TO DISK = 'c:\pubs.sqb' WITH INIT"
  
  If using a named instance:
  
  sqlbackupc -sql "BACKUP DATABASE pubs TO DISK = 'c:\pubs.sqb' WITH INIT" -I <instance name>
  
  Thanks.

  petey June 26, 2006 21:00

  - 0 +
• 
  Yes, and here is the snapshot of the error
  

  daniel_c June 27, 2006 10:56

  - 0 +
• 
  What is the name of the SQL Server instance, and the name of the server? Is this SQL Server instance running as a cluster resource? Thanks.

  petey June 27, 2006 11:02

  - 0 +
• 
  The SQL Server Instance Name: ERESDEV02
  The Server Name: (LOCAL)
  
  
  Not a cluster resource, it is just one server (Win2K server) with SQL Server 2000 installed in it.

  daniel_c June 27, 2006 14:48

  - 0 +
• 
  You mean the host name of the server is actually (LOCAL) ?

  petey June 27, 2006 21:50

  - 0 +
• 
  I must be sleepy when I typed it.
  I meant:
  The SQL Server Instance Name: (LOCAL)
  The Server Name: ERESDEV02

  daniel_c June 29, 2006 01:23

  - 0 +
• 
  The problem was finally traced to a setting in the Client Network Settings, where an alias was created for the local server, on the server itself.

  petey July 02, 2006 12:30

  - 0 +

Add comment

Please sign in to leave a comment.