Re: Unable to connect to SQLExpress Remotely - no matter what

After reading your posting, I decided to go check the event log once
again. Even though I was not previously getting messages from the
sqlbrowser, I now get this:

The configuration of the AdminConnection\TCP protocol in the SQL
instance SQLEXPRESS is not valid.

Maybe this goes with the OLAP error I'm getting? I'm researching to
see if I can find a resolution . . .

On Oct 30, 10:51 am, "Roger Wolter[MSFT]"
<rwol...@xxxxxxxxxxxxxxxxxxxx> wrote:
Hard to speculate since the last time I suggested browser was a potential
cause you said it was running fine. If you do a netstat -abn does
sqlbrowser show up as listening on UDP port 1434? If you look in the
service tab of SQL Server Configuration Manager does the browser service
show up as started? Is there something else listening on port 1434? Are
there and errors in the Windows application log that show up right after the
SQL Browser starting messages?

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified athttp://www.microsoft.com/info/cpyright.htm

"karlag92" <karla...@xxxxxxxxxxx> wrote in messagenews:1162218591.182756.25480@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Roger,

I made some progress this morning. As I suspected, it was not a
network/firewall issue. It has something to do with the SQL Server
Browser service not operating correctly.

If I go into SQL Server Configuration Manager, drill down to "Protocols
for SQL Express", select properties for the TCP/IP protocol, look under
IPAll at which dynamic port it selected, I can connect with no problems
-- as long as I specify the port number on connection.

I then decided to simply hard code the TCP port under IPAll which
allows me to work around the problem. Not ideal in my environment as I
still have to specify a port number, but something I can work with. I
can then turn off the browser service as it is doing me no good.

Any ideas on why the browser service is not behaving?

Thanks!!!!

Karl
Roger Wolter[MSFT] wrote:
If there is no error in the SQL Server error log when the login fails
then
that would indicate that the connection is not getting to SQL Server.
This
would indicate that you're trying to fix the wrong problem because
reinstalling SQL is not going to affect a network issue which is
preventing
you from getting to SQL Server.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"karlag92" <karla...@xxxxxxxxxxx> wrote in message
news:1162170577.987035.214360@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sorry, I forgot to note that there is nothing unusual in the error log.
When I compare it to another machine's log, it looks identical to all
extents and purposes.

Karl

On Oct 27, 10:33 pm, "Roger Wolter[MSFT]"
<rwol...@xxxxxxxxxxxxxxxxxxxx> wrote:
Do you have SQLBrowser enabled and running? what's the error you get
when
connecting and are there errors put into the SQL Server error log file
when
you try to connect?

--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified
athttp://www.microsoft.com/info/cpyright.htm

<karla...@xxxxxxxxxxx> wrote in
messagenews:1161989112.797814.70790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi all,

I've been fighting to get sql server express on my machine to be
accessible remotely. I've tried many times and quadruple checked
all
of the instructions in KB article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

I have even performed a full uninstall and reinstall, then applied
KB
914277 (once again).

I've turned off all firewalls and virus scan.

I've compared to other machines that work.

We've installed to other machines and followed KB 914277 and they've
worked.

Nothing helps. My Sql server express instance remains unavailable
from
other machines.

Any ideas? I've spent a whole day on this and I'm frustrated as can
be! I need this machine to work as moving to another machine for my
work is not practical.

Thanks!

Karl- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -

.

Relevant Pages

  • Re: SQL 2000 & 2005 installed side by side
    ... SQL Server 2000 has to be on at least service pack 3, to talk to the Browser service and reliably give up port 1433. ... If you simply conncet to your server, say MYSQLSERVER - by default you will connect to the version that you chose to install as a default install. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Connection in Workgroup
    ... I will try and open UDP port 1434 ... Where can I get the SQL Server Client connectivity? ... SQL Server Browser Service on the XP computer uses UDP port 1434 to send ... but you might want to install the SQL Server 2005 client ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to connect to SQLExpress Remotely - no matter what
    ... Hard to speculate since the last time I suggested browser was a potential ... sqlbrowser show up as listening on UDP port 1434? ... It has something to do with the SQL Server ... Browser service not operating correctly. ...
    (microsoft.public.sqlserver.connect)
  • Re: Odbc connection doesnt work for named instance
    ... Certainly you can try stopping the SQL Server 2000, and then restarting the SQL Server 2005 Browser Service and see if all is well. ... But if you are on SQL Server 2000 SP4, then the Browser service should be cooperating with SQL Server 2000 so this probably isn't your problem. ... As for starting SQL Server 2005, unless you configure it to a fixed port, your SQL Server 2005 may return to it's last used port which might not be 1433. ... >>> When I tried to run a crystal reports against the named instance ...
    (microsoft.public.sqlserver.connect)
  • Re: default port of MSDE
    ... MSDE uses port 1433 by default. ... You can see what port it used by looking in the SQL Server ... This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.sqlserver.msde)
Loading