ID: Q137406
Microsoft SQL Server version 6.0 has added new flexibility for installations that require a migration path from SQL Server version 4.21a by allowing a side-by-side installation of both products on the same server. However, there is a conflict with the default console pipe that is used by SQL Administrator on version 4.21a. You may see the following message in either or both of the errorlogs for version 6.0 and version 4.21a, which indicates that there was a problem setting up the console pipe:
95/08/01 06:00:00.00 ksconsole: failed to initialize Console operation
The console pipe is primarily used for disk dumps where you are prompted to
insert and remove the disk. The console pipe is also used in SQL
Administrator to prompt you to insert and remove a tape from the tape
drive. By default, both SQL Server 6.0 and SQL Server 4.21a
will attempt to create the same console pipe - \\.\PIPE\SQL\CONSOLE.
This article details the steps required to change the console pipe to an alternate pipe on a SQL Server 6.0 installation already configured to use an alternate pipe.
NOTE: For additional information on setting up versions 6.0 and 4.21a side by side, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q134937
TITLE : INF: Running SQL Versions 6.0 and 4.21 Side by Side
The method for changing the default console pipe to use an alternate pipe requires the use of the REGEDT32.EXE program. Add the following value to the \\HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSSQLServer\MSSQLServer key in the Windows NT Registry:
Console REG_SZ SSNMPN60,\\.\pipe\sql60\console
After you add the key, shutdown and restart both SQL Servers.
Finally, the Console command line utility can then connect to either server using the -P parameter. For example, to connect to the 6.0 server listening on the console pipe above use the following command:
CONSOLE -P sql60
Additional query words: sql6 server console windows nt
Keywords : kbsetup SSrvInst
Version : 6.0
Platform : WINDOWS
Last Reviewed: May 2, 1997