SQL Server 2000 Startup of Default instance reading Netbios Alias

• Dax Lawless

  SSC Enthusiast

  Points: 115

  More actions

  May 3, 2005 at 1:46 pm

  #86124

  Hello,

  I am wondering if the other SQL Server Experts might be able to suggest solutions to a perplexing problem that I am currently researching:

  We have 2 production boxes (win2k) in which one is the primary and the 2nd is a backup/failover box.  SQL Server and various other data sources are mirrored from machine_011 to machine_012.  The machines are mirrored and the failover mechanism is regulated through Legato AAM.  There is also a netbios and DNS alias (machine_01) that allows for access over the web to whichever box is currently primary.

  The current situation is that upon starting of the SQLServer service, the "Server name" entry in the SQL Server 2000 logs will come up as the netbios/DNS alias name ("machine01") instead of the default instance name of the machine (should be "machine_011").  Since the default instance name and the "server name" entry of the machine are different, this prevents SQLServer service from listening at the default port of 1433.  Additionally, MSDTC errors out with a XACT_E_CONNECTION_DOWN message. (whether this error is coincidental or not, I can't tell).

  In the error logs for the server, the following errors come up every time this happens:

  MS DTC is unable to communicate with MS DTC on a remote system.  No common RPC

  protocol is supported between the two systems.  Please ensure that one or more

   of the following RPC protocols are common  to both systems: TCP/IP, SPX, or

   NetBEUI.  Error Specifics: .\iomgrclt.cpp:203, CmdLine:

   C:\WINNT\System32\msdtc.exe, Pid: 672

  (this error occurs twice)

  String message: Primary: Session Bind Failed.              Protocol Not Supported.

  SuperSocket info: gethostbyname(MSAFD Tcpip [TCP/IP]) : Error 11001.

   

   RPC Net-Library listening on: ncacn_np:\\\\machine_01[\\pipe\\WMIEP_2cc].

  RPC Net-Library listening on: ncalrpc:machine_01[LRPC000002cc.00000001].

  RPC Net-Library listening on: ncacn_ip_tcp:machine_011.xxxxxxx.com[2699].

  SuperSocket info: (SpnRegister) : Error 1355.

  19013 :

  SQL server listening on Shared Memory, Named Pipes, Rpc.

  We are running a Windows 2000 Server on both production boxes, we do not have any Windows 2003 boxes that are connected to any production boxes...we have 2 other linked servers that are also both Windows 2000 boxes with SQL Server 2000 on them.  Our Primary Domain Controller is a NT 4 machine.

  In named pipes, we are using \\.\pipe\sql\query as the default pipe. 

  Everything else seems to be standard.  For the life of me, I cannot figure out why SQL Server comes up with the netbios alias upon startup most of the time (it takes somewhere between 5-6 reboots of the server for SQL Server to pick up the right name).

  Originally, these machines were NT4 with SQL Server 7 installed but were upgraded.

  If there are any additional details needed, I will happily provide them,

  ----------------------------------------

  New information:

  In Enterprise manager, there is only 1 server registered and is named "(local).  Under the registry key Hk_Users\...\Software\Microsoft\MSSQLServer\SQLEW\Registered Servers X ...the name is the Netbios alias we use and not the actual Windows 2000 Machine name.  Is it possible that this may be the origination of the alias being used in the startup routine?  If so, will the registration need to be changed, and will this have any negative impact if the registration is changed while the default instance is actually running?