sql server msde: Did you start the SQL Browser service?

--=20
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no =
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest =
book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-------------------------------------------------------------------------=
----------------------------------------------

[quoted text, click to view]
I'm getting the below error when I try and run a simple OSQL command =
to backup the database "TotalSpeech".
---------------------------------------------
C:\>OSQL -Usa -P -n -Q "BACKUP DATABASE TotalSpeech TO DISK =3D =
'C:\Program Files\
Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TotalSpeech-Full Database =
Backup.bak'"

[SQL Native Client]TCP Provider: No connection could be made because =
the
target machine actively refused it.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a =
connection to
the server. When connecting to SQL Server 2005, this failure may be =
caused by
the fact that under the default settings SQL Server does not allow =
remote
connections.

C:\>
---------------------------------------------

I've enabled TCP/IP and Named Pipes and also checked that "Allow =
remote connections" is enabled/ticked in the SQLEXPRESS svr. I've setup =
an ODBC connection which connects fine - am I doing something wrong. =

I'm getting the below error when I try and run a simple OSQL command to =
backup the database "TotalSpeech".
---------------------------------------------
C:\>OSQL -Usa -P -n -Q "BACKUP DATABASE TotalSpeech TO DISK =3D =
'C:\Program Files\
Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TotalSpeech-Full Database =
Backup.bak'"

[SQL Native Client]TCP Provider: No connection could be made because the
target machine actively refused it.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection =
to
the server. When connecting to SQL Server 2005, this failure may be =
caused by
the fact that under the default settings SQL Server does not allow =
remote
connections.

C:\>
---------------------------------------------

I've enabled TCP/IP and Named Pipes and also checked that "Allow remote =
connections" is enabled/ticked in the SQLEXPRESS svr. I've setup an =
ODBC connection which connects fine - am I doing something wrong. Help =

Yes I did and I also rebooted several times afterwards.
[quoted text, click to view]
Did you start the SQL Browser service?

--=20
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no =
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest =
book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
=
-------------------------------------------------------------------------=
----------------------------------------------

[quoted text, click to view]
I'm getting the below error when I try and run a simple OSQL command =
to backup the database "TotalSpeech".
---------------------------------------------
C:\>OSQL -Usa -P -n -Q "BACKUP DATABASE TotalSpeech TO DISK =3D =
'C:\Program Files\
Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TotalSpeech-Full Database =
Backup.bak'"

[SQL Native Client]TCP Provider: No connection could be made because =
the
target machine actively refused it.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a =
connection to
the server. When connecting to SQL Server 2005, this failure may be =
caused by
the fact that under the default settings SQL Server does not allow =
remote
connections.

C:\>
---------------------------------------------

I've enabled TCP/IP and Named Pipes and also checked that "Allow =
remote connections" is enabled/ticked in the SQLEXPRESS svr. I've setup =
an ODBC connection which connects fine - am I doing something wrong. =

It's fine now. I decided not to use OSQL and use the new advanced =
SQLCMD.exe with command switches. It works fine without errors. Thanks =
for the fast reply Bill.

Michael.
[quoted text, click to view]
Yes I did and I also rebooted several times afterwards.
"William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in =
message news:Oby3oWyaHHA.4520@TK2MSFTNGP06.phx.gbl...
Did you start the SQL Browser service?

--=20
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no =
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest =
book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
=
-------------------------------------------------------------------------=
----------------------------------------------

[quoted text, click to view]
I'm getting the below error when I try and run a simple OSQL =
command to backup the database "TotalSpeech".
---------------------------------------------
C:\>OSQL -Usa -P -n -Q "BACKUP DATABASE TotalSpeech TO DISK =3D =
'C:\Program Files\
Microsoft SQL Server\MSSQL.1\MSSQL\Backup\TotalSpeech-Full =
Database Backup.bak'"

[SQL Native Client]TCP Provider: No connection could be made =
because the
target machine actively refused it.
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a =
connection to
the server. When connecting to SQL Server 2005, this failure may =
be caused by
the fact that under the default settings SQL Server does not allow =
remote
connections.

C:\>
---------------------------------------------

I've enabled TCP/IP and Named Pipes and also checked that "Allow =
remote connections" is enabled/ticked in the SQLEXPRESS svr. I've setup =
an ODBC connection which connects fine - am I doing something wrong. =