Microsoft KB Archive/136800

{|
 * width="100%"|

BUG: instdist.sql Script Fails From SEM on Alternate Pipe Name

 * }

Q136800

-

The information in this article applies to:


 * Microsoft SQL Server version 6.0

-

BUG# NT: 11356 (6.00)

SYMPTOMS
When you install the distribution database from the Server menu (choose Replication Configuration, then Install Publishing) in SQL Enterprise Manager (SEM), the INSTDIST.SQL script will fail if SQL Server version 6.0 is configured to listen on an alternate named pipe. The following errors can be found in the INSTDIST.OUT file located in the SQL60\INSTALL directory.

  If SQL Server version 4.21a is running and installed on the default named pipe, the following error is displayed:

Error 911, Attempt to locate entry in Sysdatbases for database

distribution by name failed- no entry found under that name. Make

sure that name is entered properly.

  If SQL Server version 4.21a is not running or not installed, the following error will be displayed:

DB-Library: Unable to Connect: SQL Server is unavailable or does not

exist. Specified SQL server not found. Net-Library error 2:

ConnectionOpen (Createfile).



CAUSE
The command used to execute the INSTDIST.SQL script is an xp_cmdshell. The script is:

'''xp_cmdshell C:\sql60\binn\isql /S /Usa /P /ddistribution

/iC:\sql60\install\instdist.sql /oC:\sql60\install\instdist.out'''

The /S parameter will cause the isql session to try to connect over the default local pipe. If version 4.21a is up and running on the default pipe, the instdist script will fail because the distribution database will not exist. If 4.21a is not running, then the isql script will not be able to find the default pipe and will give the 'SQL server is unavailable' error.

WORKAROUND
Run the xp_cmdshell command from a command line on the distribution server. Modify the /S parameter to give the correct server name. For example:

'''isql /S /Usa /P /ddistribution

/iC:\sql60\install\instdist.sql /oC:\sql60\install\instdist.out'''

Edit the following registry key and put the name of the distribution database, usually 'distribution,' in the DistributionDB value:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\Replication

STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: sql6 prompt

Keywords : kbsetup kbtool

Issue type :

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600