I'm new NT 4 and to SQL Server, but I have to give myself a crash course in
both.  The problem is, I can't get the Developer edition of SQL Server that
comes with VB5 installed on my machine (P166 with 32 MB RAM).  Obviously
there are some things that I don't have configured properly.  SQL Server
setup will take me through the following (to pick up midway through the
process):

(1) "Setup is now creating your master database device."
(2) "Setup is now updating the Server Control Manager."
(3)"Setup is now starting SQL Server and verifying its state."

This is where I get a dial-up prompt: "Cannot reach <computer name>.  Do
you want to dial a remote network?"

Whether I dial-in or not (and I don't know why the heck I should have to
dial out to get to my own computer!), the next thing that happens is I get
the dialog box with the following message:

"The SQL Server installation could not be successfully completed.  Setup
could not connect to the SQL Server."

So, what do I need to do to get this all to work?

Richard Wattenbarger

I think SQL Server only runs on NT Server.

--
Eric Muzzy

Roy

On Tue, 01 Apr 1997 06:52:16 -0800, "Richard Wattenbarger"

I'm having exactly the same problem trying to install SQL Server 6.5
Developer Ed.  from the new Visual Studio package.  Stops at same
point as you describe.  I'm trying to install from new Visual Studio
package.

My System
---------------
WinNT 4.0 Server 1381., SP2
Micron P133
64 MB RAM

The funny thing is, I had previously had successfully installed the
downloaded 120 trial version of SQLServer 6.5 with no problem.

I uninstalled it prior to installing the developer edition.

If you find the answer to this, I'd appreciate your letting me know.

Thanks.

Alan

Alan Z. Scharf
GrapeVine Systems
New York City
_________________________
http://www.grapevines.com

I'm also new to Win NT 4.0, but I have the workstation version on a
single PPro 200.  I have no network card.  I've been looking for days
for an answer, but can't get any help from anywhere.  I did get a
message from someone who installed SS 6.5 on a 4.0 workstation
successfully.  He said he had some problems, but couldn't remember what
the fixes were.  Let me know if you hear anything.

TIA

Brent Neuhaus

Richard,

Do you have network software installed? If not, install the MS loopback
adapter (a software only "NIC" that ships with NT). This is needed during
setup because setup.exe connects using a Named Pipe (not a local, as it
used to do).

At least, this is as I understand it :-)
--

Instructor (MCT, MCSE, MCSD)
Cornerstone Sweden AB

Agreed, You need to install NT server before installing SQL Server

Thanks, Alan, for your interesting fix!

I still had problems after implementing your suggestion, however, but I
think I was dealing with two problems on my machine.  The second problem
had to do with setting up a user correctly so that SQL Server could use
it to log on.  I went into the control panel/services and changed
MSSQLServer to start-up using the newly created ID.  After getting all
that coordinated, SQL setup worked fine.

I feel like I won the lottery, but I had to pay M$ a thousand dollars to
enter.

Thanks again!

Brent Neuhaus

On Tue, 01 Apr 1997 06:52:16 -0800, "Richard Wattenbarger"

I found the answer.

1. For some reason, the installation isn't completing posting of the
 information to the registry before it tries to start SQLServer. Using
RegSearch confirmed the absence of registry entries for MSSQL.

2. To get past the problem,

A. Go into the SQL6.5/i386 directory on the CD.
B. Run setup.exe with the rebuild registry swith on

      setup /t RebuildRegistry = ON

C. This will take you through the setup screens again.  There will be
noticably long periods where just the Blue setup screen and the
hourglass are showing with no other visible response.

Finally, it will finish and tell you SQLServer is installed and take
you into the Install SQLServer SP2 screen.

You may have to do this through the DOS Prompt window.  I ran Setup
using the File Run command in Norton File Manager.

Good luck.

Alan

Alan Z. Scharf
GrapeVine Systems
New York City
_________________________
http://www.grapevines.com

I made a typo in the command I gave.  Sorry.

Here is correct command:

     setup /t RegistryRebuild = ON

Alan

Alan Z. Scharf
GrapeVine Systems
New York City
_________________________
http://www.grapevines.com

Is this package SQL SERVER or SQL Workstation?  The difference is
whether you install on a NT Server or NT Workstation.  SQL Server
requires a NT Server to handle some aspects of the security.  

I have recently encountered a similar problem at work.  We bought 3
copies of SQL Server 6.5 to install on NT 4 Workstations and were not
able to bring the systems up.  If we point the systems back towards
our NT Test box then everything works fine.  However, since the NT
Server is a test system we cannot guarantee the availablity of the
system; thus if the server shuts down so does the SQL Server
databases.  We later found out that the wrong software was ordered.

A long winded way of saying if you do not have a server then you
cannot use the system.  Furthermore, if you do not install SQL Server
directly on the server then you must take all steps possible to
guarantee that a NT Server is "visible" otherwise the database shuts
down.

Rob

On Tue, 01 Apr 1997 06:52:16 -0800, "Richard Wattenbarger"

No, I thought so too (reading the WEB pages), but I am running SQL Server
6.5 evaluation copy, downloaded from Microsoft, on NT Workstation 4.0 with
no problem.

SQL server works fine on NT workstation.

Looks like you need to setup your networking and try disabling all network
protocols for SQL server except for named pipes.

It has to do with networking.  If you have no network device defined, but
you do have a modem, the system tries to dial out, looking for itself, so
to speak.  While you're in NT, go to the control panel, networking, and
the device MS Loopback something or other.  Go to bindings, and it will
bind to whatever protocol your modem is using (probably TCP/IP), give it
some dummy IP address for now, use the default subnet mask. Restart your
machine, and in all likelyhood, SS will now install fine.  In my case, it
installed, but the Enterprise Manager would not work.  After installing
Loopback device, everything is just fine, thank you.

Speaking of thanks, don't thank me for this solution.  I got it from
Stephen Wynkoop.  Hell of a guy!

Larry Mohr

Larry Mohr