Re: Can I Upgrade

Best plan of attack here is to take on one issue at a time.

Yes, but almost your all problems is about connection =)

First and foremost is the fact that MSDE2000 (Microsoft Desktop Engine 2000) will not start the protocols TCP/IP or Named Pipes.

I've seen your log quote, the only thing I can guess you are looking at the wrong logs. Because no doubt MSDE supports this protocol. I set up a test machine and test it for you. The VM is Windows XP SP2. I installed MSDE and configured it as I told you previously and I'm able to connect to that instance from another machine.

You absolutely need to be seeing a message in the log such as: "SQL server listening on 127.0.0.1: 1433." So there's something wrong for sure. Last guess is you are configuring this port setting for another instance of SQL Server. Sorry, I'm out of ideas.

--
Ekrem Önsoy



"Thomas R Grassi Jr" <thomasgrassi@xxxxxxxxxxx> wrote in message news:%23wOnUIiXJHA.4384@xxxxxxxxxxxxxxxxxxxxxxx
Ekrem

Best plan of attack here is to take on one issue at a time.

First and foremost is the fact that MSDE2000 (Microsoft Desktop Engine 2000) will not start the protocols TCP/IP or Named Pipes.

Yes I am using the program svrnetcn to configure the protocols.

Yes I restart the sql service every time I make changes to the network config.

Here is my log

2008-12-14 14:11:45.57 server Microsoft SQL Server 2000 - 8.00.2050 (Intel X86)
Mar 7 2008 21:29:56
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 2)

2008-12-14 14:11:45.57 server Copyright (C) 1988-2002 Microsoft Corporation.
2008-12-14 14:11:45.57 server All rights reserved.
2008-12-14 14:11:45.57 server Server Process ID is 3760.
2008-12-14 14:11:45.57 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2008-12-14 14:11:45.59 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2008-12-14 14:11:45.64 server SQL Server configured for thread mode processing.
2008-12-14 14:11:45.64 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2008-12-14 14:11:45.67 spid3 Starting up database 'master'.
2008-12-14 14:11:46.18 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2008-12-14 14:11:46.18 server SQL server listening on Shared Memory.
2008-12-14 14:11:46.18 server SQL Server is ready for client connections
2008-12-14 14:11:46.18 spid5 Starting up database 'model'.
2008-12-14 14:11:46.21 spid3 Server name is 'TGCS001\SHAREPOINT'.
2008-12-14 14:11:46.21 spid3 Skipping startup of clean database id 4
2008-12-14 14:11:46.21 spid3 Skipping startup of clean database id 5
2008-12-14 14:11:46.21 spid3 Starting up database 'STS_tgcs001_1'.
2008-12-14 14:11:47.45 spid5 Clearing tempdb database.
2008-12-14 14:11:49.12 spid5 Starting up database 'tempdb'.
2008-12-14 14:11:49.45 spid3 Recovery complete.
2008-12-14 14:11:58.40 spid3 SQL global counter collection task is created.

As you can see SQL server is only listening on Shared Memory

So the big question of the day is why is Named Pipes and TCP/IP not starting?

Thanks

Tom






"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:9596EA9A-80CE-42CB-A64E-936F455683BA@xxxxxxxxxxxxxxxx
Hello Thomas,

I see that you open many topics in various NGs and all of them are about the same problem. For the sake of the solution of this problem, it would be the best to track it under the same topic.

First of all, Developer Edition of SQL Server can not be used as a production server. I mean, technically you can (even though I don't really remember technically if you can upgrade from MSDE 2000 to Developer Edition 2000); however it's against the license agreement.

Either MSDE and SQL Server Express Edition do not have SQL Server Agent. This is one of the restrictions of these free SQL Server editions. However, you can backup your databases using some alternative methods, such as writing a T-SQL script to backup your databases and run this script using OSQL \ SQLCMD and schedule it using Windows Scheduler.

I believe, you may have problems with setting up (enabling TCP/IP port). I just want to ensure that you perform this task appropriately. Are you sure you configure this port using the tool which I typed its path below?

C:\Program Files\Microsoft SQL Server\80\Tools\binn\svrnetcn.exe

Also, are you sure there are no another instance of SQL Server which uses this port? It may create a conflict so neither of the instances use this port?

Remember, you should restart the MSDE service after enabling TCP/IP port, otherwise this change would not take effect.

And, for the test purposes ensure that Windows Firewall is off. Later you may enable it according to your necessities.

Because, that's for sure that MSDE supports this protocol and it absolutely let remote users to connect to this edition of SQL Server remotely and through TCP/IP protocol. Believe me, I tried this many times...

And here I'm making a list from start to end to install and configure MSDE for remote connections:
- Install an MSDE 2000 instance.
- Connect to that instance using EM \ SSMSE and change the Authentication Mode to Mixed Mode.
- Run SQL Server Network Utility "C:\Program Files\Microsoft SQL Server\80\Tools\binn\svrnetcn.exe" and ensure that you choose the correct SQL Server instance from the server list and enable TCP/IP port.
- Start MSDE 2000' s service (I didn't say restart because it's not started by default after installation)
- Ensure that you configured Windows Firewall to let your MSDE' s port. Also, you can add this instance's executable as an exception. For the sake of the test, disable Windows Firewall.
- Now, you'll be able to connect to this SQL Server instance remotely in your LAN. For WAN, you may need to configure your firewall hardware or other devices.

--
Ekrem Önsoy



"Thomas R Grassi Jr" <thomasgrassi@xxxxxxxxxxx> wrote in message news:%233dw4yVXJHA.4852@xxxxxxxxxxxxxxxxxxxxxxx
Can I upgrade from Microsoft SQL Desktop Engine 2000 8.0.2050 to Microsoft SQL Server 2000 Developer Edition.

The MSDE2000 has way to many restrictions
1. No remote connections allowed
2. Can not run SQLAGENT
3. No Enterprise Manager

My SQL Server 2000 Developer Edition has all these features

I have been tring for over a week to get my enterprise manager to connect to the MSDE2000 server with no luck.

The MSDE2000 server is running on my Windows 2003 R2 Standard DC server. My enterpise manager is running on my Windows XP Pro SP3 workstation. No firewall issues checked used netstat portqry.

MSDE2000 will not start the protocols necessary to allow a remote connection TCP and Named Pipes do not start. I have checked the SQL logs and just Shared Memory is starting (Listening) on the Windows 2003 Server.

I have searched the web and these news groups for several days now and I keep going up with a major road block. MSDE2000 does not allow remote connections.
Even though you can configure TCP and Named Pipes it does not work, I also show in the folder where MSDE2000 was installed SQLAGENT but that program will not start either.

I installed SQL Server Studio Express but it does not work well with SQL2000 apps. cannot display logs can not create backup jobs to a disk file. etc.

So thats why I want to upgrade the MSDE2000 to use my Microsoft SQL Server 2000 Developer Edition CD

But I want to know if I can do this and how to do this

Any help would be great

Need to backup my databases and I have another application I am working on that will use a sql database


Thanks

Tom





.

Relevant Pages

  • How is SQL Server run state determined?
    ... Assume that a Windows XP SP2 client is configured to use the TCP/IP ... No other protocols are enabled on this client. ... Manager attempt to communicate with the SQL Server via the standard port ...
    (microsoft.public.sqlserver.connect)
  • RE: Problems connecting to MSDE server
    ... Thank you for your post regarding unable to connect to SQL Server. ... didn't specify to enable protocols when installing, ... run svrnetcn.exe which will bring up the Server Network configuration ... The client tools ship with a full copy of SQL Server, ...
    (microsoft.public.sqlserver.msde)
  • TCP/IP and security
    ... I need to change the protocols settings during installation or, ... is selected as the default port instead ... - whatever port I say to SQL Server to use, ... STILL do not use it!(errorlog after service start lists the protocols used, ...
    (microsoft.public.sqlserver.security)
  • Re: Can I Upgrade
    ... Yes I am using the program svrnetcn to configure the protocols. ... As you can see SQL server is only listening on Shared Memory ... So the big question of the day is why is Named Pipes and TCP/IP not ... Microsoft SQL Server 2000 Developer Edition. ...
    (microsoft.public.sqlserver.setup)
  • Re: Cant connect
    ... choose your SQL Server 2000 instance from the list and ensure that TCP/IP or Named Pipes protocol are in the Enabled protocols list. ... Then you can use this info to connect to this instance and to add this port to the exception list of Windows Firewall or any other firewall utility if there is any. ... Open up this utility where you SQL Server instance is installed and then go to SQL Server Network Configuration and choose your instance name then enable protocols accordingly. ...
    (microsoft.public.sqlserver.connect)