I Could not install SQL successfully, gave an error log

2007-03-22 09:36:52.39 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: )

2007-03-22 09:36:52.45 server Copyright (C) 1988-2000 Microsoft Corporation.
2007-03-22 09:36:52.45 server All rights reserved.
2007-03-22 09:36:52.45 server Server Process ID is 1516.
2007-03-22 09:36:52.45 server Logging SQL Server messages in file 'd:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-03-22 09:36:52.57 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2007-03-22 09:36:53.26 server SQL Server configured for thread mode processing.
2007-03-22 09:36:53.48 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2007-03-22 09:36:54.31 server Attempting to initialize Distributed Transaction Coordinator.
2007-03-22 09:36:56.46 spid3 Warning ******************
2007-03-22 09:36:56.46 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2007-03-22 09:36:56.60 spid3 Starting up database 'master'.
2007-03-22 09:36:57.26 spid3 Server name is 'PRECISE'.
2007-03-22 09:36:57.26 server Using 'SSNETLIB.DLL' version '8.0.194'.
2007-03-22 09:36:57.26 spid5 Starting up database 'model'.
2007-03-22 09:36:57.60 spid5 Clearing tempdb database.
2007-03-22 09:36:57.74 spid7 Starting up database 'msdb'.
2007-03-22 09:36:57.85 server SuperSocket Info: Bind failed on TCP port 1433.
2007-03-22 09:36:57.89 server SuperSocket Info: Bind failed on TCP port 1433.
2007-03-22 09:36:57.89 server SuperSocket Info: Bind failed on TCP port 1433.
2007-03-22 09:36:57.89 server SuperSocket Info: Bind failed on TCP port 1433.
2007-03-22 09:36:58.31 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-03-22 09:36:58.31 server SQL server listening on 195.195.195.2:1433, 127.0.0.1:1433.
2007-03-22 09:36:58.31 server SQL Server is ready for client connections
2007-03-22 09:36:58.35 spid7 Starting up database 'pubs'.
2007-03-22 09:36:58.64 spid7 Starting up database 'Northwind'.
2007-03-22 09:37:00.18 spid5 Starting up database 'tempdb'.
2007-03-22 09:37:00.32 spid3 Recovery complete.
2007-03-22 09:37:00.32 spid3 Warning: override, autoexec procedures skipped.
2007-03-22 09:37:07.95 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.

be sure to read all the requirments

hardware and software.

hypertext links & SQL 7 databases

I have arrived at a site and been thrown this curve ball.
This company have an Access 97 application which
successfully stores hypertext links. A consultancy came
into to try and Xfer all the functionality to SQL 7 (a
financial decision & because it's there!!). The
consultancy's conclusion was for the company to upgrade
SQL from 7 to 2000 in order for hyperlinks to be stored
(or used) successfully. The consultancy did not give a
definite reason for their conclusion & the company person
involved needs a reason why SQL7 is not a viable option.
Anyone out there know why?
I have trawled the KB and searched the web for answers
without success.
Thanks in advance,
Euan.There is no such thing as a hyperlink datatype in either SQL 7 or SQL 2000.
You're going to have to code the <a href=> part yourself, either in the
query or in the front-end application.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Euan" <anonymous@.discussions.microsoft.com> wrote in message
news:002901c4a0b7$afb4d660$a301280a@.phx.gbl...
> I have arrived at a site and been thrown this curve ball.
> This company have an Access 97 application which
> successfully stores hypertext links. A consultancy came
> into to try and Xfer all the functionality to SQL 7 (a
> financial decision & because it's there!!). The
> consultancy's conclusion was for the company to upgrade
> SQL from 7 to 2000 in order for hyperlinks to be stored
> (or used) successfully. The consultancy did not give a
> definite reason for their conclusion & the company person
> involved needs a reason why SQL7 is not a viable option.
> Anyone out there know why?
> I have trawled the KB and searched the web for answers
> without success.
> Thanks in advance,
> Euan.|||Hi
Neither SQL 7 or 2000 have a "hyperlink" data type. You would have to store
it in a char/varchar field and it would be up to the application to display
it as a hyperlink.
Regards
Mike
"Euan" wrote:
> I have arrived at a site and been thrown this curve ball.
> This company have an Access 97 application which
> successfully stores hypertext links. A consultancy came
> into to try and Xfer all the functionality to SQL 7 (a
> financial decision & because it's there!!). The
> consultancy's conclusion was for the company to upgrade
> SQL from 7 to 2000 in order for hyperlinks to be stored
> (or used) successfully. The consultancy did not give a
> definite reason for their conclusion & the company person
> involved needs a reason why SQL7 is not a viable option.
> Anyone out there know why?
> I have trawled the KB and searched the web for answers
> without success.
> Thanks in advance,
> Euan.
>