Showing posts with label localhost. Show all posts
Showing posts with label localhost. Show all posts

Saturday, February 25, 2012

newbie: telnet localhost 1433 fails

I don't understand why.
My SQL Server 2005 is called PC\SQLEXPRESS. I use PC\Robert (administrator)
account on Windows XP Professional. I use Windows Authentication. Remote
connections are switched on ("Using both TCP/IP and names pipes.")
Please help. Thank you.
/RAM/Since this is a named instance, the port is not 1433. The SQL Server error
log will list the listening network protocols, interfaces and ports.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"R.A.M." <r_ahimsa_m@.poczta.onet.plwrote in message
news:ejeg8o$oiv$1@.news.onet.pl...

Quote:

Originally Posted by

>I don't understand why.
My SQL Server 2005 is called PC\SQLEXPRESS. I use PC\Robert
(administrator)
account on Windows XP Professional. I use Windows Authentication. Remote
connections are switched on ("Using both TCP/IP and names pipes.")
Please help. Thank you.
/RAM/
>

|||I see no port number in C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG.
Could you help me please?

Uzytkownik "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.netnapisal w
wiadomosci news:wLE6h.7391$6t.4871@.newssvr11.news.prodigy.com ...

Quote:

Originally Posted by

Since this is a named instance, the port is not 1433. The SQL Server
error log will list the listening network protocols, interfaces and ports.

|||You should have a log entry like the example below if the server is
listening on TCP/IP:

2006-11-15 08:11:39.68 Server Server is listening on [ 'any' <ipv4>
10489].

In this case, the port is 10489.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"R.A.M." <r_ahimsa_m@.poczta.onet.plwrote in message
news:ejfqcn$42h$1@.news.onet.pl...

Quote:

Originally Posted by

>I see no port number in C:\Program Files\Microsoft SQL
>Server\MSSQL.1\MSSQL\LOG.
Could you help me please?
>
Uzytkownik "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.netnapisal w
wiadomosci news:wLE6h.7391$6t.4871@.newssvr11.news.prodigy.com ...

Quote:

Originally Posted by

>Since this is a named instance, the port is not 1433. The SQL Server
>error log will list the listening network protocols, interfaces and
>ports.


>
>

|||Thank you I found.
Some application I need uses SQL Server 2005. I need to provide connection
string (that's why I need port number).
If I have named instance, shall I have to change my connection string every
time I run Windows?
/RAM/

Uzytkownik "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.netnapisal w
wiadomosci news:yoQ6h.6288$IR4.968@.newssvr25.news.prodigy.net ...

Quote:

Originally Posted by

You should have a log entry like the example below if the server is
listening on TCP/IP:
>
2006-11-15 08:11:39.68 Server Server is listening on [ 'any' <ipv4>
10489].
>
In this case, the port is 10489.

|||If I have named instance, shall I have to change my connection string

Quote:

Originally Posted by

every time I run Windows?


You don't need to hard-code the port in the connection string if you enable
the SQL Browser service. This will allow clients to discover the port
dynamically based in the instance name.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"R.A.M." <r_ahimsa_m@.poczta.onet.plwrote in message
news:ejh2j5$lao$1@.news.onet.pl...

Quote:

Originally Posted by

Thank you I found.
Some application I need uses SQL Server 2005. I need to provide connection
string (that's why I need port number).
If I have named instance, shall I have to change my connection string
every time I run Windows?
/RAM/
>
Uzytkownik "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.netnapisal w
wiadomosci news:yoQ6h.6288$IR4.968@.newssvr25.news.prodigy.net ...

Quote:

Originally Posted by

>You should have a log entry like the example below if the server is
>listening on TCP/IP:
>>
>2006-11-15 08:11:39.68 Server Server is listening on [ 'any' <ipv4>
>10489].
>>
>In this case, the port is 10489.


>
>

Monday, February 20, 2012

Newbie: MSDE no longer listens to outside request. Event id 19011.

Hi
I've had a MSDE 2000 instance running a couple of months without any
problems. Now all of a sudden I can only connect to it from localhost.
When I restart the sql-server using the Service Manager it gives a
warning in the event log with event-ID 19011. Error code 1355.
Also I have a bunch of informational events with event-id 3 and
something about some missing file. I'm not sure if the two event-types
have something to do with each other, though.
I believe my problems started after installing a very simple program
called Dyndns Updater. Looking in the install-log I found that it only
installs the main exe, some txt-files and a normal run-parameter in the
registry. To me it seems unlikely that it should interfere with MSDE in
any way. Uninstalling doesn't help either.
All other services on my server are working normally from another computer.
I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
Any pointers?
Regards
dne Hovda
GTR AS
NORWAY
Michael C# wrote:
> How about firewalls? Are you running MSDE on Win XP and have you installed
> SP 2 recently? The Windows Firewall will, by default, prevent responses to
> inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
> problem, try opening up these two ports on your Windows Firewall.
Sorry, I forgot to specify.
We have a pretty simple network of 6 machines, no internal firewalls.
MSDE runs on W2KSP4. I've tried both with and without firewall on the
client-machines that all run XPSP2. It doesn't seem to be a
firewall-related problem. Also, I checked that IP-filtering is turned
off on the server.
Looking deeper into the logs, I found that the program I before
mentioned has definetely nothing to do with it, as I see the same error
(19011) at least two more times, exactly one and two weeks ago, to be
specific.
dne
|||Chris V. wrote:
> What is the size of the MDF file, or the LDF ?
> If I remember properly, the max size is 2Gb, and if I am still right, the
> 2Gb apply to the physical file, to the size of the active pages.
The total size of all databases in the instance is 58MB...
This is very strange: All of a sudden it just started working again! I
can now connect from all clients. I haven't changed anything.
Hm. This problem might not be MSDE related after all. Still I'm
wondering what those error messages mean, though.
Anyway, thanks for your help, guys.
dne

Newbie: MSDE no longer listens to outside request. Event id 19011.

Hi
I've had a MSDE 2000 instance running a couple of months without any
problems. Now all of a sudden I can only connect to it from localhost.
When I restart the sql-server using the Service Manager it gives a
warning in the event log with event-ID 19011. Error code 1355.
Also I have a bunch of informational events with event-id 3 and
something about some missing file. I'm not sure if the two event-types
have something to do with each other, though.
I believe my problems started after installing a very simple program
called Dyndns Updater. Looking in the install-log I found that it only
installs the main exe, some txt-files and a normal run-parameter in the
registry. To me it seems unlikely that it should interfere with MSDE in
any way. Uninstalling doesn't help either.
All other services on my server are working normally from another computer.
I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
Any pointers?
Regards
dne Hovda
GTR AS
NORWAYMichael C# wrote:
> How about firewalls? Are you running MSDE on Win XP and have you installe
d
> SP 2 recently? The Windows Firewall will, by default, prevent responses t
o
> inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
> problem, try opening up these two ports on your Windows Firewall.
Sorry, I forgot to specify.
We have a pretty simple network of 6 machines, no internal firewalls.
MSDE runs on W2KSP4. I've tried both with and without firewall on the
client-machines that all run XPSP2. It doesn't seem to be a
firewall-related problem. Also, I checked that IP-filtering is turned
off on the server.
Looking deeper into the logs, I found that the program I before
mentioned has definetely nothing to do with it, as I see the same error
(19011) at least two more times, exactly one and two weeks ago, to be
specific.
dne|||Chris V. wrote:
> What is the size of the MDF file, or the LDF ?
> If I remember properly, the max size is 2Gb, and if I am still right, the
> 2Gb apply to the physical file, to the size of the active pages.
The total size of all databases in the instance is 58MB...
This is very strange: All of a sudden it just started working again! I
can now connect from all clients. I haven't changed anything.
Hm. This problem might not be MSDE related after all. Still I'm
wondering what those error messages mean, though.
Anyway, thanks for your help, guys.
dne

Newbie: MSDE no longer listens to outside request. Event id 19011.

Hi
I've had a MSDE 2000 instance running a couple of months without any
problems. Now all of a sudden I can only connect to it from localhost.
When I restart the sql-server using the Service Manager it gives a
warning in the event log with event-ID 19011. Error code 1355.
Also I have a bunch of informational events with event-id 3 and
something about some missing file. I'm not sure if the two event-types
have something to do with each other, though.
I believe my problems started after installing a very simple program
called Dyndns Updater. Looking in the install-log I found that it only
installs the main exe, some txt-files and a normal run-parameter in the
registry. To me it seems unlikely that it should interfere with MSDE in
any way. Uninstalling doesn't help either.
All other services on my server are working normally from another computer.
I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
Any pointers?
Regards
Ådne Hovda
GTR AS
NORWAYHow about firewalls? Are you running MSDE on Win XP and have you installed
SP 2 recently? The Windows Firewall will, by default, prevent responses to
inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
problem, try opening up these two ports on your Windows Firewall.
Thx
"Ådne Hovda" <aadne@.hovda.no> wrote in message
news:eK4kSdRFFHA.392@.TK2MSFTNGP14.phx.gbl...
> Hi
> I've had a MSDE 2000 instance running a couple of months without any
> problems. Now all of a sudden I can only connect to it from localhost.
> When I restart the sql-server using the Service Manager it gives a warning
> in the event log with event-ID 19011. Error code 1355.
> Also I have a bunch of informational events with event-id 3 and something
> about some missing file. I'm not sure if the two event-types have
> something to do with each other, though.
> I believe my problems started after installing a very simple program
> called Dyndns Updater. Looking in the install-log I found that it only
> installs the main exe, some txt-files and a normal run-parameter in the
> registry. To me it seems unlikely that it should interfere with MSDE in
> any way. Uninstalling doesn't help either.
> All other services on my server are working normally from another
> computer.
> I'm kind of stuck here, not wanting to uninstall/reinstall MSDE.
> Any pointers?
> Regards
> Ådne Hovda
> GTR AS
> NORWAY|||Michael C# wrote:
> How about firewalls? Are you running MSDE on Win XP and have you installed
> SP 2 recently? The Windows Firewall will, by default, prevent responses to
> inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If this is your
> problem, try opening up these two ports on your Windows Firewall.
Sorry, I forgot to specify.
We have a pretty simple network of 6 machines, no internal firewalls.
MSDE runs on W2KSP4. I've tried both with and without firewall on the
client-machines that all run XPSP2. It doesn't seem to be a
firewall-related problem. Also, I checked that IP-filtering is turned
off on the server.
Looking deeper into the logs, I found that the program I before
mentioned has definetely nothing to do with it, as I see the same error
(19011) at least two more times, exactly one and two weeks ago, to be
specific.
Ådne|||What is the size of the MDF file, or the LDF ?
If I remember properly, the max size is 2Gb, and if I am still right, the
2Gb apply to the physical file, to the size of the active pages.
Chris
"Ådne Hovda" <aadne@.hovda.no> a écrit dans le message de news:
eFSW7zRFFHA.1564@.TK2MSFTNGP09.phx.gbl...
> Michael C# wrote:
>> How about firewalls? Are you running MSDE on Win XP and have you
>> installed SP 2 recently? The Windows Firewall will, by default, prevent
>> responses to inbound traffic from Ports 1433 (TCP) and 1434 (UDP). If
>> this is your problem, try opening up these two ports on your Windows
>> Firewall.
> Sorry, I forgot to specify.
> We have a pretty simple network of 6 machines, no internal firewalls.
> MSDE runs on W2KSP4. I've tried both with and without firewall on the
> client-machines that all run XPSP2. It doesn't seem to be a
> firewall-related problem. Also, I checked that IP-filtering is turned off
> on the server.
> Looking deeper into the logs, I found that the program I before mentioned
> has definetely nothing to do with it, as I see the same error (19011) at
> least two more times, exactly one and two weeks ago, to be specific.
> Ådne|||Chris V. wrote:
> What is the size of the MDF file, or the LDF ?
> If I remember properly, the max size is 2Gb, and if I am still right, the
> 2Gb apply to the physical file, to the size of the active pages.
The total size of all databases in the instance is 58MB...
This is very strange: All of a sudden it just started working again! I
can now connect from all clients. I haven't changed anything.
Hm. This problem might not be MSDE related after all. Still I'm
wondering what those error messages mean, though.
Anyway, thanks for your help, guys.
Ådne