Hi Peter,

Thanks for your reply. I tried the options suggested. The problem was
that the Sql server port was 49158 rather than 1433. So if I specified the
port no. in osql command it worked. I changed it to 1433 but still I have to
specify the port no. as follows:

osql -Stcp:AVACTA-N31M-1\VIO-VEDB,1433 -E

Then it is connecting but if I do not specify the port then it gives the
following error:

[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance
Specified [xFFFFFFFF].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occured while establishing a connection to
the server. When connecting to SQL Server2005, this faliure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

I am sending you the errorlog.

Cheers.

Manjree.







""Peter Yang[MSFT]"" wrote:

> Hello Manjree,
>
> Since you use named instance, please check if SQL Browser service is
> enabled and started properly by running services.msc.
>
> Also, since you use Windows authentication, username is not necessary under
> the situaiton and you should use -E switch. Please try the following
> commands and let me know the detailed result:
>
> osql -Snp:AVACTA-N31M-1\VIO-VEDB -E
>
> osql -Stcp:AVACTA-N31M-1\VIO-VEDB -E
>
> osql -Slpc:AVACTA-N31M-1\VIO-VEDB -E
>
> If you encounter any error messages, please note them and post back. Also,
> please collect the sql error log and send it to me at petery@microsoft.com
>
> You could find the log under
> C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG
>
> I suspect the issue is related to named pipes and it might be blocked by
> firewall. If lpc (shared memory protocal) works, you may want to tempoarily
> disable firewall to test.
>
> Please refer to the following article for more details about different
> protocols of sql connection
>
> How to: Connect to the Database Engine Using sqlcmd.exe
> http://msdn2.microsoft.com/en-us/library/ms188247.aspx
>
> If you have any update, please feel free to let's know. Thank you.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
>
> ================================================== ===
>
> When responding to posts, please "Reply to Group" via your
> newsreader so that others may learn and benefit from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hello Manjree,

Thank you for your update!

From the symptom, it seems SQL Browser service is not started or it's
blocked by firewall. Please make sure it's started. Also, if firewall is
on, please enable UDP 1434 so that client could access sql browser service.

http://blogs.msdn.com/sql_protocols/...24/473502.aspx

INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932

Since it's not a default instance, client will not try 1433 directly and it
will contact browser service to get the proper port to use.

To work around this issue, you could also create alias for the server in
sql client network utility to test
http://blogs.msdn.com/sql_protocols/...ion-alias.aspx

If you have any update, please feel free to let's know. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Manjree,

I'm still interested in this issue. If you have any comments or questions,
please feel free to let's know. We look forward to hearing from you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ==
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Peter,

Thanks for the follow up. I tried the suggestions that you gave. The SQL
Browser service is started and I enabled UDP 1434. but still I have to define
the port no. 1433 to connect to other wise it does not connect.
I checked in SQL Server Configuration manager under Client Protocols the
Default TCP/IP port is 1433.

If I define an alias for TCP/IP port which is 1433, Do I need to give the
alias name to connect to it? If so what is the point of defining aliases; I
can give the port no. 1433 as defining aliases can cause some problems too.

cheers.

Manj.


""Peter Yang[MSFT]"" wrote:

> Hello Manjree,
>
> I'm still interested in this issue. If you have any comments or questions,
> please feel free to let's know. We look forward to hearing from you.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
>
> ================================================== ==
> When responding to posts, please "Reply to Group" via your
> newsreader so that others may learn and benefit from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hello Manjree,

Thank you for your reply. You could define an alias by using the following
methods:

1. In SQL configuration manager

Under SQL native client configuration->Alias, and define alias
name/port/servername.

This defines a alias using SQL native client to connect SQL 2005

2. Run cliconfg.exe and add alias/port which uses sql server (not native
client) to connect to sql server.

You don't need to add port number after alias since port is configured in
alias.

To check the network status of the machine, please run the following
command to get more information:
netstat -nba > netstat.txt

Also, if you run osql command without port number from local console of SQL
Server, what't the result? Did you try to temporarily disable firewall on
the server to test?

You may need also add Sql Browser service to Firewall exception list
besides the upd port 1434.

I'm looking forward to your update. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.