Installing multiple instances of MSDE2000

Hello
I installed 2 instances of msde , installation passed ok but noone can
connect to my machine , i portscanned host machine and port 1443 is not
opened ,can it be becaus i installed it on a VmWare console, any help is
apriciated.
PS I didn't forget to set DISABLENETWORKPROTOCOLS=0.
Thx in advance
__________
TomislavFist you need to find out what the instance names are and whether one is a
default instance (both are probably named instances as no-one is listening
to port 1433).
Use either server network utility, svrnetcn.exe, or check the services in
the machine. After you know the instance names, you connect using:
machinename\instancename
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tomislav Zemljak" <tomislav.zemljak@.*maknime*bj.tel.hr> wrote in message
news:c3rn9s$ksm$1@.sunce.iskon.hr...
> Hello
> I installed 2 instances of msde , installation passed ok but noone can
> connect to my machine , i portscanned host machine and port 1443 is not
> opened ,can it be becaus i installed it on a VmWare console, any help is
> apriciated.
> PS I didn't forget to set DISABLENETWORKPROTOCOLS=0.
> Thx in advance
> __________
> Tomislav
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:
> Fist you need to find out what the instance names are and whether one is a
> default instance (both are probably named instances as no-one is listening
> to port 1433).
One is default instance , other is named "second"
> Use either server network utility, svrnetcn.exe, or check the services in
> the machine. After you know the instance names, you connect using:
> machinename\instancename
That didn't solve it ... both instances are started and appear to be
working on host machine , remote users still cant connect and portscann
shows that port 1443 isn't open .Thx for trying thou.|||You don't say whether these instances are both named or one is a default def
ault instance. You cannot have two
default instances. My guess is that you have two names instance. A named ins
tance does NOT listen on 1433.
Please follow my direction closely to find out whether these are default or
named instances and the name of
the instance.
This is what I write in my earlier post:

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tomislav Zemljak" <tomislav.zemljak@.*maknime*bj.tel.hr> wrote in message news:c3s99i$4ge$1
@.sunce.iskon.hr...
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:
> One is default instance , other is named "second"
> That didn't solve it ... both instances are started and appear to be
> working on host machine , remote users still cant connect and portscann
> shows that port 1443 isn't open .Thx for trying thou.
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:
> You don't say whether these instances are both named or one is a default
default instance.
As i already wrote (look below) one is default instance , other is named
"second".
I "fixed" the problem by reinstalling both instances , now they work , thx
for tryng to help !
You cannot have two
> default instances. My guess is that you have two names instance. A named
instance does NOT listen on 1433.
> Please follow my direction closely to find out whether these are default
or named instances and the name of
> the instance.
> This is what I write in my earlier post:
>
in
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Tomislav Zemljak" <tomislav.zemljak@.*maknime*bj.tel.hr> wrote in message
news:c3s99i$4ge$1@.sunce.iskon.hr...
wrote:
is a
listening
in
>

Installed SQL Server, yet not listening on any port

Hi all,

I'm working on a school project on web and mobile applications, and had decided to use MS SQL Server for my backend database.

However, after I've installed MS SQL Server 2000, I ran a port scan and I couldn't find the server running on any ports (MySQL is running on my port 3306, but I guess it doesn't matter) Can something drop some hints on how to debug the problem?

I'm running on Athlon XP 2000+ w/ Windows XP Professional SP2

Thanks a lot!SQL Server runs on port 1433 by default, I believe. In your SQL Server group on the machine running SQL Server, there is a Client Network Utility. Go into that and ensure that TCP/IP is enabled.|||yes i went to the Enterprise Manager, under my Server Group's properties, went to Network Configuration and enabled both TCP/IP on port 1433 and Named Pipes. It still didn't work though.

Another thing I've noticed is that my server is named "(LOCAL) (Windows NT)." Could this be a hint that it's not listening for external connections?|||No, local is an alias for the machine you are on.

Are you certain that SQL Server is running? In Enterprise Manager, can you see the any databases?|||Yes I could see all the databases from the master database to the NorthWind and tempdb database.

The Distributed Transaction Coordinator, SQL Server and SQL Server Agent are all enabled.

Update: I've checked the Event Log. I think I probably know what's the problem.. Here is the message from the log:

You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with this version of Windows. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.asp

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I'll go patch up and reply if I had any more problems. Thanks for the help douglas.reilly!|||This is just to say that the problem is resolved after patching the SQL Server to SP3. Sorry for the trouble and thanks!sql

Installation of the SQL 2000 after SQL 2005

Hello,

We got a problem, we have default instance of the SQL 2005, and it owns 1433 port. We need to install named instance of the SQL 2000, problem that it installs using port 1304, that is not default. Of course we can use this port in the connection string, but may be some sort of the solution exists?

Bydefault default instance uses 1433. So next instance has to have someother port. WHat is the problem in using 1304. If you want to use 1433 for SQL Server 2000, then you can change the port of default instance manually to someother port and you can use 1433 for sql server 2000

Madhu

Installation of IS to Server

Hi,

Is there a need to install the Integration Services to a Server? Isn't it enough to just port the .dtsx file from my local drive to the server and execute it by SQL Agent using DTExec /f command?

thanks,

cherriesh

cherriesh wrote:

Hi,

Is there a need to install the Integration Services to a Server? Isn't it enough to just port the .dtsx file from my local drive to the server and execute it by SQL Agent using DTExec /f command?

thanks,

cherriesh

You won't have dtexec.exe without installing SSIS. And SSIS is required to be installed regardless, as dtexec.exe would require the SSIS dlls to execute anyway. SSIS isn't redistributable like the old DTS was.