Problem with SQL Service Pack 4

I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
install says it completed but after I rebooted and did a select @.@.version it
still shows SP3. I only have a default instance so I know that it installed
on the right instance. Could anyone help me out with this?You can review the setup log for any errors (file called sqlsp.log in the
windows directory). It is perfectly safe to run SP4 again to try and make it
stick (assuming you have the system database backups just in case you need
to regress)
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||I tried it several times but got the same result.
I've attached a copy of my sqlsp.log file. I looked at the sqlsp.log file
and it only listed one non-fatal error...I can't see this being the problem
considering it was nonfatal.
Jasper Smith wrote:
>You can review the setup log for any errors (file called sqlsp.log in the
>windows directory). It is perfectly safe to run SP4 again to try and make it
>stick (assuming you have the system database backups just in case you need
>to regress)
>>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
>> install says it completed but after I rebooted and did a select @.@.version
>> it
>> still shows SP3. I only have a default instance so I know that it
>> installed
>> on the right instance. Could anyone help me out with this?|||What does the following query return?
SELECT SERVERPROPERTY('ProductLevel')
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||SP3....
Dan Guzman wrote:
>What does the following query return?
> SELECT SERVERPROPERTY('ProductLevel')
>>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
>> install says it completed but after I rebooted and did a select @.@.version
>> it
>> still shows SP3. I only have a default instance so I know that it
>> installed
>> on the right instance. Could anyone help me out with this?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200606/1sql

Problem with Sql Server 2000 error

I am using VWD with Sql Server 2000. My application was running smoothly till I rebooted both my local box and the Machine where sql Server 2000 resides and now I am getting this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

like I said before I am using Sql Server 2000 and not 2005. I don't really understand the problem. The application was running smoothly before rebooting it, so I know there is nothing wrong with the code. Maybe I need to start some service within IIS or something.

If anyone has any idea please let me know.

Thanks in advance for your help

Hi,

I do not have an idea why you catch this error while working with a SQL2K database.

But to enable remote connections, open the SQL Server Surface Area Configuration tool. Then drill down the Services and Connections, open the Database Engine. Then enable remote connections from this configuration tool.

eralper

http://www.kodyaz.com

|||

Could be a number of issues.

First, I rarely let SQL Server use named pipes. I hate them, I force SQL Server to TCP/IP always, unless it's a local connection then shared memory.

A firewall blocking the connection could do it.

Putting in the wrong server name could do it.

Configuring SQL Server to deny remote connections could do it (That is what the error message is saying).

There was a problem with SP2 and SQL Server 2000. Check the SP readme.txt to make sure you've configured it correctly for use with XP SP2.