I create 2 instances SQL Server in the same server using port 1433, unluckily when i connect they from the remote pc, it doesn't connect and alert "Invalid Instance". How can i use many instances? And what special when i replicate them?Check out KB #287932 (http://support.microsoft.com/default.aspx?scid=kb;en-us;287932). It explains what you need in more detail than I care to retype!
-PatP|||What a pity PatP, it happens even all clients and the server in a Lan group with a hub without firewall on server.|||So it isn't the remote clients as you originally posted? Did the local clients work and then stop, or never work at all? Can you connect from any machine except the server itself? Can you connect to the instances on the server itself?
-PatP|||All clients can't connect to but the server can.|||I suspect that the problem may be because you've set up two instances to use the same TCP port. If you check the KB article I cited, each instance normally has its own port, and the port usages are arbitrated by port 1434. Only the default (unnamed) instance of SQL Server should use port 1433.
I'd suggest that you try to reconfigure the server that way to see if it works.
-PatP
Showing posts with label port. Show all posts
Showing posts with label port. Show all posts
Wednesday, March 21, 2012
Wednesday, March 7, 2012
HELP:SQL Port lost or never set on new install
I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility
.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:
> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utili
ty.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
>
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility
.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:
> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utili
ty.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
>
HELP:SQL Port lost or never set on new install
I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>
|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:
> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>
|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>
|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:
> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>
|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
Subscribe to:
Posts (Atom)