Very Computer

>At the begin I make a BIG mistake and run some <.BAT> file instead
Setup.exe
>from SQL Server's CD. This bat-file made attempt to install SQL Server with
>all
>default settings, but it can't do this and I receive <Not Responding>
>message in task list.
>After this I try to set up server with Setup.exe, but it hang-up too, when
>Setup receive "Connect to server"
>message. From the second attempt, server was installed, but it can't work
>properly. First strange thing is
>that it can't open system database from location where server installed:
>1999-02-16 19:40:27.15 spid1    Opening file L:\MSSQL7\data\master.mdf.
>1999-02-16 19:40:27.26 spid1    Opening file L:\MSSQL7\data\mastlog.ldf.
>1999-02-16 19:40:27.50 spid1    Loading SQL Server's  Unicode collation.
>1999-02-16 19:40:27.61 spid1    Loading SQL Server's  non-Unicode sort orde
>1999-02-16 19:40:27.96 spid1    1 transactions rolled forward in database '
>1999-02-16 19:40:28.00 spid1    0 transactions rolled back in database 'mas
>1999-02-16 19:40:28.20 spid1    Starting up database 'model'.
>1999-02-16 19:40:28.21 spid1    Opening file c:\mssql7\data\model.mdf.
>1999-02-16 19:40:28.37 spid1    Opening file c:\mssql7\data\modellog.ldf.
>I had to copy database to disk c to start server.
>Now I can to start server, but Enterprise Manager can't connect to him.
>If I use TCP/IP protocol I receive "Cannot generate SSPI context" message
>wiht ASSERT caused from MMC.EXE. If I use "multiprotocol" i have "General
>Network Error" message with some addition about RpcBinding.
>How to fix this problems? (How to correctly uninstall all server components
>from system?)
>Under NT all works just great.

>--

>I opened a support incident with Microsoft a while back and it turns out
you
>have to install Microsoft Client for Networks via the Network applet in
>Control Panel, make it your Primary Network Logon and then install Sql 7
>Desktop.  This information should show up soon in a Knowledge Base article.

>P.S. Once you have SQL 7 installed, you must leave Microsoft Client for
>Networks installed, but it does not need to be your Primary Network Logon.
>I've switched back to Microsoft Family Logon as my preferred type.

>PP.SS.  If you are using the Office 2000 beta 2, you'll need to do a repair
>install on Outlook 2000 beta 2 which stops working after you install SQL 7
>Desktop on Win 98.

>>At the begin I make a BIG mistake and run some <.BAT> file instead
>Setup.exe
>>from SQL Server's CD. This bat-file made attempt to install SQL Server
with
>>all
>>default settings, but it can't do this and I receive <Not Responding>
>>message in task list.
>>After this I try to set up server with Setup.exe, but it hang-up too, when
>>Setup receive "Connect to server"
>>message. From the second attempt, server was installed, but it can't work
>>properly. First strange thing is
>>that it can't open system database from location where server installed:
>>1999-02-16 19:40:27.15 spid1    Opening file L:\MSSQL7\data\master.mdf.
>>1999-02-16 19:40:27.26 spid1    Opening file L:\MSSQL7\data\mastlog.ldf.
>>1999-02-16 19:40:27.50 spid1    Loading SQL Server's  Unicode collation.
>>1999-02-16 19:40:27.61 spid1    Loading SQL Server's  non-Unicode sort
orde
>>1999-02-16 19:40:27.96 spid1    1 transactions rolled forward in database
'
>>1999-02-16 19:40:28.00 spid1    0 transactions rolled back in database
'mas
>>1999-02-16 19:40:28.20 spid1    Starting up database 'model'.
>>1999-02-16 19:40:28.21 spid1    Opening file c:\mssql7\data\model.mdf.
>>1999-02-16 19:40:28.37 spid1    Opening file c:\mssql7\data\modellog.ldf.
>>I had to copy database to disk c to start server.
>>Now I can to start server, but Enterprise Manager can't connect to him.
>>If I use TCP/IP protocol I receive "Cannot generate SSPI context" message
>>wiht ASSERT caused from MMC.EXE. If I use "multiprotocol" i have "General
>>Network Error" message with some addition about RpcBinding.
>>How to fix this problems? (How to correctly uninstall all server
components
>>from system?)
>>Under NT all works just great.

>>--

>I opened a support incident with Microsoft a while back and it turns out
you
>have to install Microsoft Client for Networks via the Network applet in
>Control Panel, make it your Primary Network Logon and then install Sql 7
>Desktop.  This information should show up soon in a Knowledge Base article.