Cannot remotely connect on SQL Server Instances by name.

Hi all,

On my computer I have installed two instances of SQL Server 2000. The first one is the default instance of SQL Server Personal Edition and the second one is an MSDE instance.

From other PCs on the company LAN I can connect, by name, only to the first one and not to the MSDE instance.

I have tried the combination IP Address, TCP Port and it work fine.

Anyone any ideas?

Thanks in advance,

Stavros Makridis.

did you get this fixed ever?|||

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Jens K. Suessmeyer wrote:

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

If tcp port is specified in the connection string, the instance name value is ignored.|||UDP port 1434 must be blocked somehow. SQL Browser needs this port to resolve srv\instance to a valid server:tcp_port.|||He is using SQL 2000, so no SQL Browser.|||

Yes there is. Browser is handled by the first instance of sqlserver internally.

|||

I wasn′t aware of that, do you have some links about this topic and this internal feature ?

|||You can find it in bol and on technet.

Here is an excerpt from bol (ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/3cc00d3a-487c-4cd9-a155-655f02485fa0.htm):
"Background

Prior to Microsoft SQL Server 2000, only one instance of SQL Server could be installed on a computer. SQL Server listened for incoming requests on port 1433, assigned to SQL Server by the official Internet Assigned Numbers Authority (IANA). Only one instance of SQL Server can use a port, so when SQL Server 2000 introduced support for multiple instances of SQL Server, SQL Server Resolution Protocol (SSRP) was developed to listen on UDP port 1434. This listener service responded to client requests with the names of the installed instances, and the ports or named pipes used by the instance. To resolve limitations of the SSRP system, SQL Server 2005 introduces the SQL Server Browser service as a replacement for SSRP."

Cannot remotely connect on SQL Server Instances by name.

Hi all,

On my computer I have installed two instances of SQL Server 2000. The first one is the default instance of SQL Server Personal Edition and the second one is an MSDE instance.

From other PCs on the company LAN I can connect, by name, only to the first one and not to the MSDE instance.

I have tried the combination IP Address, TCP Port and it work fine.

Anyone any ideas?

Thanks in advance,

Stavros Makridis.

did you get this fixed ever?|||

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Jens K. Suessmeyer wrote:

Hi,

the named instance is accessible with MachineName\InstanceName,PortNumber in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

If tcp port is specified in the connection string, the instance name value is ignored.|||UDP port 1434 must be blocked somehow. SQL Browser needs this port to resolve srv\instance to a valid server:tcp_port.|||He is using SQL 2000, so no SQL Browser.|||

Yes there is. Browser is handled by the first instance of sqlserver internally.

|||

I wasn′t aware of that, do you have some links about this topic and this internal feature ?

|||You can find it in bol and on technet.

Here is an excerpt from bol (ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/3cc00d3a-487c-4cd9-a155-655f02485fa0.htm):
"Background

Prior to Microsoft SQL Server 2000, only one instance of SQL Server

could be installed on a computer. SQL Server listened for incoming requests on

port 1433, assigned to SQL Server by the official Internet Assigned Numbers

Authority (IANA). Only one instance of SQL Server can use a port, so when SQL

Server 2000 introduced support for multiple instances of SQL Server, SQL Server

Resolution Protocol (SSRP) was developed to listen on UDP port 1434. This

listener service responded to client requests with the names of the installed

instances, and the ports or named pipes used by the instance. To resolve

limitations of the SSRP system, SQL Server 2005 introduces the SQL Server

Browser service as a replacement for SSRP."

cannot register local SQL server

I had SQL Server running locally on my pc and now I
suddenly can't connect. I deleted the registration and
tried re-registering it in EM. When I use Windows
authentication I get a msg saying "cannot open default
database, using master database instead"..but it doesn't
register.
When I use SQL authentication using the sa login, I get a
msg saying "login failed for sa, not associated with a
trusted SQL Server connection". (The SQL Server service
is still running OK on my pc).
Any ideas as to how to fix it, and why it went wrong in
the first place?
Thanks
DaveLooks like you:
1. Run in Windows authentication mode, no sa is permitted
2. you deleted the database (or sent it offline) you specified as defautl
database for the
Windows user you try to connect.
TO sign on as sa change the reg key use this manual:
---
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q285097
---
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
---
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
HTH, Jens Süßmeyer.
"dave" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||dave
>When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
Do you have a login like (DOMAIN\Dave) ?
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection".
You can change an authentication settings of the server
Right click on the server ,then Properties ,then under Security Tab change
Authentication to SQL and Windows.
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||> You can change an authentication settings of the server
> Right click on the server ,then Properties ,then under Security Tab change
> Authentication to SQL and Windows.
But if you can´t register you are really f.... :)
Jens Süßmeyer.|||An alternative to change login mode to mixed is to login using ISQL.EXE (it will let you in even if
your default database doesn't exist) and use sp_defaultdb to change the default database to an
existing database.
I do not recommend changing default database for sysadmins (for the very reason we see here).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||Thanks Jens
Changed the registry setting to 2 and it worked using SQL authentication.
>--Original Message--
>Looks like you:
>1. Run in Windows authentication mode, no sa is permitted
>2. you deleted the database (or sent it offline) you specified as defautl
>database for the
>Windows user you try to connect.
>TO sign on as sa change the reg key use this manual:
>----
--
>http://support.microsoft.com/default.aspx?scid=3Dkb;EN-
US;q285097
>----
--
>INF: How to Change the Default Login Authentication Mode to SQL While
>Installing SQL Server 2000 Desktop Engine by Using Windows Installer
>----
--
><snip>
>Another way to change the security mode after installation is to stop
>SQL Server and set the appropriate registry key for your installation:
>Default instance:
>HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
>Named instance:
>HKLM\Software\Microsoft\Microsoft SQL Server\Instance
>Name\MSSQLServer\LoginMode
>to 2 for mixed-mode or 1 for integrated. (Integrated is the default
>setup for the SQL Server 2000 Data Engine.)
></snip>
>HTH, Jens S=FC=DFmeyer.
>
>
>"dave" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
>news:06d901c3b41f$68325220$a001280a@.phx.gbl...
>> I had SQL Server running locally on my pc and now I
>> suddenly can't connect. I deleted the registration and
>> tried re-registering it in EM. When I use Windows
>> authentication I get a msg saying "cannot open default
>> database, using master database instead"..but it doesn't
>> register.
>> When I use SQL authentication using the sa login, I get a
>> msg saying "login failed for sa, not associated with a
>> trusted SQL Server connection". (The SQL Server service
>> is still running OK on my pc).
>> Any ideas as to how to fix it, and why it went wrong in
>> the first place?
>> Thanks
>> Dave
>
>.
>|||just change the loginmode parameter in the register to sa..
It should work
--
Shaju Thomas
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave

Cannot register 2000 on 7 (HELP!)

I am running SQL 7 and trying to connect to a SQL2000
server on the network. I can ping the other machine, and
I have mapped a network drive, but I cannot register it.
It gives me a General Network error. Any Ideas?Brett,
If you try the Register Server Wizard on a SQL 7.0 server, you should see
the following message:
<SQL Server 2000 server name> - You must upgrade your SQL Enterprise Manager
and SQL-DMO(SQLOLE) to SQL Server 2000 (SQLDMO) to connect to this server.
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"Brett" <levi71@.swbell.net> wrote in message
news:0ec801c3d9ea$61c87e50$a301280a@.phx.gbl...

quote:

---

> I am running SQL 7 and trying to connect to a SQL2000
> server on the network. I can ping the other machine, and
> I have mapped a network drive, but I cannot register it.
> It gives me a General Network error. Any Ideas?

---

Cannot reconfigure UNION ALL task

If you add a "Union All" task to your Data Flow the output columns get configured by the first input you connect to it.

However, if you later want to modify the input columns on the inputs (perhaps after adding an upstream Data Conversion) there seems to be no way to get it to forget the original set of output columns.

Ideally, there would be a button you can press to reset the output columns based on the earliest added input. At the very least it ought to forget its output columns when the last input is removed.

Other tasks offer a dialogue to resolve input / output mismatches but not Union All.

or am I missing something?

jks

If you right-click on a column name underneath "Output Column Name" you are given the option to delete that column.

Is that what you want?

-Jamie

|||

I agree, while deleting or adding back one column is not the most painful process, many times while working on a package my upstream compenents changed a lot and I found myself deleting my Union All and Merge tasks and adding them back in because it was the easiest way to update them.

It would be nice if there was a refreash of some sort that would reexamine and update any added/deleted columns.

|||

Thanks Jamie,

That helps - I had seen Delete in the right-click menu but it was always disabled when I needed it. Probably because I was trying to delete a new column I had just added without saving the task in between. I guess I'm used to records being committed when you move off them.

However, I still think it would be useful if Union All offered the same sort of intelligent reconfiguration options presented by other tasks. Any columns you've added to a data flow upstream ought to be propogated through the first input of a Union All to its output.

regards

jks

|||

I can see why this (i.e. propogating the first input) would be useful but by the same token there may be people that would want the behaviour to be as it is now. As with most things you can't please all the people all of the time. Personally I think the functionality is fine as it is. Matter of opinion I guess.

Its worth saying that UNION ALL is an asynchronous component and this is the fundamental reason that any inputs don't automatically propogate through to the output. You'll find that the same is true of all asynchronous components.

-Jamie

|||

Ok - I hadn't appreciated the distinction between sync and async components. If this is a consistent architectural feature I'll bite my tongue until I understand the architecture a little better!

This is just SSIS day 3 for me.

regards

jks

|||

jks,

Well it sounds like you are headlong into it already. I recommend that you get your head around a few concepts pretty early. Namely:

The container hierarchysql

Cannot open user default Database login failed

Dear all,

I got the error message:

Error 27052 Could not connect to Microsoft SQL Server 'VPC' Cannot open User default Database login failed.

This error is happened when installing one application to Virtual Machine (Machine name: VPC).

Does anyone knows how to solve this problem? I checked from www.microsoft.com but i just got the limited information:

27502

The parameter is not valid.

Not applicable

SSCE_M_CMN_INVALIDPARAMETER

There is no further information.

Thanks & Regards,

Agus Suryadi

When you log in to SQL Server, SQL Server figures out who you are and then puts your session into a specific database. The database it puts you into is either the one you specified on your connection string (if you specified one) or into your default database, the database that your login has as its default.

If you can get into the SQL Server you could check the login you were connecting with to see what its default database is, then check to see if a database with that name currently exists.

Perhaps the application that is being installed expects a certain database to already be created, but apparently it's not there (or the Login/user doesn't have permissions to access it).

Don

Cannot open user database error message AFTER I connect and log in.

Ok so I'm using the Management Studio Express and was able to log in and get into the database server, but I had to click the "options>>" button and change database I wanted to connect to from <<default>> to my database on the server or else I get the "cannot open user database, login failed" error message.

Then I right click my database and it gives me the "Cannot open user database. Login failed" error message, even though I already connected to the database to login during the connect screen.

Also I'm able to interact with the database using SQL QUERIES in the Management Studio, like adding new tables with it, but if I right click the database and click "add table" I get that error.

What gives? I know I have permission since I was able to log on, and modify the database using SQL queries but if use the GUI I can't use it. I can't even right-click select "properties" without getting that error.

The reason I want to use the GUI is because I want to right click and use the backup feature of the database.

My guess is that Management Studio continues to point to the default database(which gives me that message) after I already logged in, so I have no idea how to change the default database that management studio points to, to the one I do have permission to use.

Thanks in advance.

What's the account you used to connect to SQL Database Engine in Management Studio Express? The 'Default Database' in SQL is a property of login, that means each login has a Default Database which will be accessed when connecting to SQL Server. You can check this property in the Security->login Properties. Just make sure your login has access on its default database.

Cannot open database requested in login...

Hi,

I am using ASP to connect to an MS SQL database. The script connects to the database OK and I can retrieve recordset data and add new rows without a problem.

However, when I try to edit a recordset (using the recordset.update command), I get the following error:

Cannot open database requested in login 'andthen_development'. Login fails.

My first thought was that it must be a permissions problem, but that doesn't explain why I can view and add rows, but not edit. Any ideas?

Thanks, Pauldid you try an "Update" command

objCommand.ActiveConnection = objConnection objCommand.CommandText = "Update Table tbl set ..."
Call objCommand.Execute

just see if this works with your login

or try updating with the QA and your login|||then we'll see why the RecordSet.Update doesn't work|||Just tried an "UPDATE TABLE..." command directly and it works fine. However, I have an ASP include file that I use to handle all database functionality centrally. Included in this is the following function:

Function editRow(sqlString, rowParameters)
'#-- UPDATES AN EXISTING DATABASE ROW

'#-- SET UP RECORDSET FOR EDITING A RECORD
Set recordSet = Server.CreateObject("ADODB.RecordSet")
recordSet.CursorLocation = adUseServer
recordSet.CursorType = adOpenForwardOnly
recordSet.LockType = adLockOptimistic

recordSet.Open sqlString, connection, , ,adCmdText

'#-- ITERATE THROUGH rowParameters TO UPDATE ITEM'S FIELDS
Dim rowField
For Each rowField In rowParameters
recordSet(rowField) = rowParameters.Item(rowField)
Next

'#--UPDATE RECORDSET (UPDATE RECORD)
recordSet.Update

End Function

The function accepts an SQL string to identify the row (e.g. "SELECT * FROM...") and a Dictionary object that contains keys relating to field names and values giving the new contents for the row.

This produces an error on the recordset.Update line.

Paul|||maybe it's the cursor location
or one of the option of the recordset

Set recordSet = Server.CreateObject("ADODB.RecordSet")
recordSet.CursorLocation = adUseServer
recordSet.CursorType = adOpenForwardOnly
recordSet.LockType = adLockOptimistic

Cannot open database requested in login 'northwind'. Login fails.

I work for DataDirect-Technologies. My customer is using our Connect for ODBC
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind and
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?
Actually, to update the issue: the customer can connect from a remote Windows
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/da...ools/snoop.jar) is running and
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connections
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:

> I work for DataDirect-Technologies. My customer is using our Connect for ODBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open database
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind and
> Master. He is using the sa login with a password. He is able to connect with
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?

Cannot open database requested in login 'northwind'. Login fails.

I work for DataDirect-Technologies. My customer is using our Connect for ODB
C
5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When h
e
tries to connect using a simple C application he gets the error
"[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open dat
abase
requested in login 'northwind'. Login fails." The customer has tried using
the IP Address and the machine name. He has tried connecting to Northwind an
d
Master. He is using the sa login with a password. He is able to connect with
the same information from a Windows machine either using Windows
Authentication or SQL Server authentication.
There must be some setting within his SQL Server database that does not
allow remote connections, is anyone aware of something like this?Actually, to update the issue: the customer can connect from a remote Window
s
client to his SQL Server 7 database using the MS ODBC driver. However, if he
takes that same data source on his remote Windows client and changes the
connection info to point to the machine name and port number of the Solaris
box where a TCP/IP packet sniffer
(ftp://ftp.datadirect.com/download/d...tools/snoop.jar) is running an
d
the packet sniffer re-routes the connection to the SQL Server database, he
sees the same error that he gets with the DataDirect ODBC driver on Solaris.
So it appears that SQL Server must be configured only to disallow connection
s
coming from that Solaris machine, not necessarily all remote connections.
Does anyone know what setting is controlling this?
"Pat Frost" wrote:

> I work for DataDirect-Technologies. My customer is using our Connect for O
DBC
> 5.00.0059 driver on Solaris 8 to connect to SQL Server 7 on Win 2000. When
he
> tries to connect using a simple C application he gets the error
> "[DataDirect][ODBC SQL Server Driver][SQL Server]Cannot open d
atabase
> requested in login 'northwind'. Login fails." The customer has tried using
> the IP Address and the machine name. He has tried connecting to Northwind
and
> Master. He is using the sa login with a password. He is able to connect wi
th
> the same information from a Windows machine either using Windows
> Authentication or SQL Server authentication.
> There must be some setting within his SQL Server database that does not
> allow remote connections, is anyone aware of something like this?

Cannot open database "xx" requested by the login. The login failed.

Hi,
we are running a webapplication, using IIS6, Windows 2003 64 bit in classic Asp.
In the asp pages we connect to our SQL server (SQL Server 2005 64bit,windows 2003 64 bit), mirrored on a third sql server (same software setup as the first sql server).

The mirroring is without witness.

This works perfectly but sometimes we get the following error :

Description: [Microsoft][SQL Native Client][SQL Server]Cannot open database

"OBJECTS" requested by the login. The login failed.

In the logs of sql, we see that the offending connection does not go the principal but to the mirror. Which would cause the problem of course..

The name of the database varies, and there is no consistent error. Most of the time there are no problems (95%), but sometimes we get these errors.

Connection from the asp to sql is done using ADO, using following driver in the connectionstring :

Driver="{SQL Native Client}"

Does anyone have an idea what could be the problem ?
We can of course increase timouts for the mirroring, but is this the solution ?

Greets
Tom

Looks like your application attempts to login using "OBJECTS" as the default database and the database does not exist. Is that database supposed to always exist or is it occasionally dropped and recreated? Your application should not attempt to connect to the database if it might not exist.

Thanks
Laurentiu

|||Hi Laurentiu,

the database always exists. So it must always be available for connection.
But for some reason SQL fails to see the database.

Also, it's not one and the same database that has this problems. We have more than 100 databases on the sql server, and the connection error popups randomly with other databases.

Greets
Tom|||

Can you check your server errorlog and post the errors that show up there? Also, does this happen during server startup by any chance? Is your database on a special volume, such that it would take longer to start up, for example, is it on an EFS volume?

Thanks
Laurentiu

|||Hi Laurentiu,

I'll check the correct SQL serverlogs when this error occurs.

The server is not starting up but running as normally. Remember, this is a production server.
No special volumes.

Additional information :

As told the connection is made in our ASP pages , using an ADO connectionstring.

Now it seems that the initial connection setup works :
e.g

set pCn = Server.CreateObject("ADODB.Connection")
pCn.connectionstring=lstr
pCn.Open

And the first executes always seem to work :
e.g.
pcn.Execute ("select * from thetable")

But in the same page, more executes are performed with the same connection (pC).
And after some executes, it fails with the above error.

Again, this does not happen always, and not with the same database !
And we are not starting up the server, or doing special tasks (aka backups,etc) which would add an extra load on the server.
The moments that this error occures are random, as are the databases with which the error occurs.

Greetings
Tom

|||

If you hit the error again, can you please provide the errorlog entries?

Thanks
Laurentiu

|||

Hi Laurentiu,

sorry for the delay in getting back to you.

There are no error entries in the primary sql server error logs
Only an error pops up in the secondary (mirror) server, stating the login failed.
And this of cours makes sense, as the connection does not go to the primary but to the secondary, which is acting as mirror. And therefore can not be accessed.

The question is : why does the connection sometimes jumps in stead from the primary server, to the mirror server ? Nowhere in my code I give a secondary server as reference.

The connection is made through ODBC in an ASP web application (IIS6) , simelar to :

Set oCn = Server.CreateObject("ADODB.Connection")
oCn.CommandTimeout = 180
oCn.Open lconstirng lconstring

where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
where the dsn file contains following info :

[ODBC]
DRIVER={SQL Native Client}
UID=myuserid
pwd=mypwd
Address=xxx.yyy.zzz.qqq,myport
Network=DBMSSOCN
DATABASE=MyDatabaseName
WSID=xxx.yyy.zzz.qqq
APP=Microsoft Open Database Connectivity
SERVER=xxx.yyy.zzz.qqq
Description=blabla

I tried the above without the DSN, so a dsnless connection string. Nothing changed.
I tried following drivers :{SQL Native Client} and SQLNCLI
Nothing changed

Any ideas ?

Greets
Tom|||

Hi Tom,

For these questions, I suggest trying the Database Mirroring forum or the SQL Server Data Access forum. These are the forums that address issues related to mirroring and server connections.

Thanks
Laurentiu

Cannot open database "xx" requested by the login. The login failed.

Hi,
we are running a webapplication, using IIS6, Windows 2003 64 bit in classic Asp.
In

the ASP pages we connect to our SQL server (SQL Server 2005

64bit,windows 2003 64 bit), mirrored on a third sql server (same

software /hardware setup as the first sql server).

The mirroring is without witness.

This works but sometimes we get the following ODBC error in our ASP application :

Description: [Microsoft][SQL Native Client][SQL Server]Cannot open database

"OBJECTS" requested by the login. The login failed.

No error can be seen in the principal SQL error logs.
But a failed authorization can be found on the mirror server..
And this of course this makes

sense, as the connection does not go to the primary but to the

secondary, which is acting as mirror. And therefore can not be accessed.

The question is : why

does the connection sometimes jumps in stead from the primary server,

to the mirror server ? Nowhere in the code I give a secondary server as

reference.

Most of

the time there are no problems (97%), but sometimes we get these errors.

The moments that this error occures are random, as are the databases with which the error occurs.

The connection is made through ODBC in an ASP web application (IIS6) , simelar to :

Set oCn = Server.CreateObject("ADODB.Connection")
oCn.CommandTimeout = 180
oCn.Open lconstring

where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
where the dsn file contains following info :

[ODBC]
DRIVER={SQL Native Client}
UID=myuserid
pwd=mypwd
Address=xxx.yyy.zzz.qqq,myport
Network=DBMSSOCN
DATABASE=MyDatabaseName
WSID=xxx.yyy.zzz.qqq
APP=Microsoft Open Database Connectivity
SERVER=xxx.yyy.zzz.qqq
Description=blabla

I tried the above without the DSN, so a dsnless connection string. Nothing changed.
I tried following drivers :{SQL Native Client} and SQLNCLI
Nothing changed

Does anyone have an idea what could be the problem ?
We can of course increase timouts for the mirroring, but is this the solution ?
Before we started using SQL 2005 and mirroring this problem did not occur.

Greets

Tom

This will occur if you client has intermittent problems accessing the principal. The mirroring principal will send the name of the mirror server to the client after the first connection. If the client loses connection, it does not know if the principal has failed (it could have been destroyed by a natural disaster for example) so it will try to connect to the mirror to see if there has been a failover to the mirror. Since there was no server side failover in this case, you will get the connection failure logged on the mirror server. I recommend you monitor your network to see if there are intermittent problems causing this behavior.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||At this point we can't find any immediate problems.

What information could help us to identify the reason causing the 'intermittent problems accessing the principal' ?

Are there logs I can consult ?

Greetings

Tom|||

I found an interesting link, which could be the reason for our problem.

But we are unaware that we disbled pooling :

http://groups-beta.google.com/group/microsoft.public.sqlserver.odbc/browse_thread/thread/9c79f6f4e8adce7b/f99b340d2fd76aef

Would this fix help even when pooling is enabled ?

Greetings,
Tom

|||Any solution for this with SP2 for 2005 ?

Cannot open database "xx" requested by the login. The login failed.

Hi,
we are running a webapplication, using IIS6, Windows 2003 64 bit in classic Asp.
In

the ASP pages we connect to our SQL server (SQL Server 2005

64bit,windows 2003 64 bit), mirrored on a third sql server (same

software /hardware setup as the first sql server).

The mirroring is without witness.

This works but sometimes we get the following ODBC error in our ASP application :

Description: [Microsoft][SQL Native Client][SQL Server]Cannot open database

"OBJECTS" requested by the login. The login failed.

No error can be seen in the principal SQL error logs.
But a failed authorization can be found on the mirror server..
And this of course this makes

sense, as the connection does not go to the primary but to the

secondary, which is acting as mirror. And therefore can not be accessed.

The question is : why

does the connection sometimes jumps in stead from the primary server,

to the mirror server ? Nowhere in the code I give a secondary server as

reference.

Most of

the time there are no problems (97%), but sometimes we get these errors.

The moments that this error occures are random, as are the databases with which the error occurs.

The connection is made through ODBC in an ASP web application (IIS6) , simelar to :

Set oCn = Server.CreateObject("ADODB.Connection")
oCn.CommandTimeout = 180
oCn.Open lconstring

where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
where the dsn file contains following info :

[ODBC]
DRIVER={SQL Native Client}
UID=myuserid
pwd=mypwd
Address=xxx.yyy.zzz.qqq,myport
Network=DBMSSOCN
DATABASE=MyDatabaseName
WSID=xxx.yyy.zzz.qqq
APP=Microsoft Open Database Connectivity
SERVER=xxx.yyy.zzz.qqq
Description=blabla

I tried the above without the DSN, so a dsnless connection string. Nothing changed.
I tried following drivers :{SQL Native Client} and SQLNCLI
Nothing changed

Does anyone have an idea what could be the problem ?
We can of course increase timouts for the mirroring, but is this the solution ?
Before we started using SQL 2005 and mirroring this problem did not occur.

Greets

Tom

This will occur if you client has intermittent problems accessing the principal. The mirroring principal will send the name of the mirror server to the client after the first connection. If the client loses connection, it does not know if the principal has failed (it could have been destroyed by a natural disaster for example) so it will try to connect to the mirror to see if there has been a failover to the mirror. Since there was no server side failover in this case, you will get the connection failure logged on the mirror server. I recommend you monitor your network to see if there are intermittent problems causing this behavior.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||At this point we can't find any immediate problems.

What information could help us to identify the reason causing the 'intermittent problems accessing the principal' ?

Are there logs I can consult ?

Greetings

Tom|||

I found an interesting link, which could be the reason for our problem.

But we are unaware that we disbled pooling :

http://groups-beta.google.com/group/microsoft.public.sqlserver.odbc/browse_thread/thread/9c79f6f4e8adce7b/f99b340d2fd76aef

Would this fix help even when pooling is enabled ?

Greetings,
Tom

|||Any solution for this with SP2 for 2005 ?

Cannot open database "xx" requested by the login. The login failed.

Hi,
we are running a webapplication, using IIS6, Windows 2003 64 bit in classic Asp.
In

the ASP pages we connect to our SQL server (SQL Server 2005

64bit,windows 2003 64 bit), mirrored on a third sql server (same

software /hardware setup as the first sql server).

The mirroring is without witness.

This works but sometimes we get the following ODBC error in our ASP application :

Description: [Microsoft][SQL Native Client][SQL Server]Cannot open database

"OBJECTS" requested by the login. The login failed.

No error can be seen in the principal SQL error logs.
But a failed authorization can be found on the mirror server..
And this of course this makes

sense, as the connection does not go to the primary but to the

secondary, which is acting as mirror. And therefore can not be accessed.

The question is : why

does the connection sometimes jumps in stead from the primary server,

to the mirror server ? Nowhere in the code I give a secondary server as

reference.

Most of

the time there are no problems (97%), but sometimes we get these errors.

The moments that this error occures are random, as are the databases with which the error occurs.

The connection is made through ODBC in an ASP web application (IIS6) , simelar to :

Set oCn = Server.CreateObject("ADODB.Connection")
oCn.CommandTimeout = 180
oCn.Open lconstring

where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
where the dsn file contains following info :

[ODBC]
DRIVER={SQL Native Client}
UID=myuserid
pwd=mypwd
Address=xxx.yyy.zzz.qqq,myport
Network=DBMSSOCN
DATABASE=MyDatabaseName
WSID=xxx.yyy.zzz.qqq
APP=Microsoft Open Database Connectivity
SERVER=xxx.yyy.zzz.qqq
Description=blabla

I tried the above without the DSN, so a dsnless connection string. Nothing changed.
I tried following drivers :{SQL Native Client} and SQLNCLI
Nothing changed

Does anyone have an idea what could be the problem ?
We can of course increase timouts for the mirroring, but is this the solution ?
Before we started using SQL 2005 and mirroring this problem did not occur.

Greets

Tom

This will occur if you client has intermittent problems accessing the principal. The mirroring principal will send the name of the mirror server to the client after the first connection. If the client loses connection, it does not know if the principal has failed (it could have been destroyed by a natural disaster for example) so it will try to connect to the mirror to see if there has been a failover to the mirror. Since there was no server side failover in this case, you will get the connection failure logged on the mirror server. I recommend you monitor your network to see if there are intermittent problems causing this behavior.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||At this point we can't find any immediate problems.

What information could help us to identify the reason causing the 'intermittent problems accessing the principal' ?

Are there logs I can consult ?

Greetings

Tom|||

I found an interesting link, which could be the reason for our problem.

But we are unaware that we disbled pooling :

http://groups-beta.google.com/group/microsoft.public.sqlserver.odbc/browse_thread/thread/9c79f6f4e8adce7b/f99b340d2fd76aef

Would this fix help even when pooling is enabled ?

Greetings,
Tom

|||Any solution for this with SP2 for 2005 ?

Cannot open database "xx" requested by the login. The login failed.

Hi,
we are running a webapplication, using IIS6, Windows 2003 64 bit in classic Asp.
In the asp pages we connect to our SQL server (SQL Server 2005 64bit,windows 2003 64 bit), mirrored on a third sql server (same software setup as the first sql server).

The mirroring is without witness.

This works perfectly but sometimes we get the following error :

Description: [Microsoft][SQL Native Client][SQL Server]Cannot open database

"OBJECTS" requested by the login. The login failed.

In the logs of sql, we see that the offending connection does not go the principal but to the mirror. Which would cause the problem of course..

The name of the database varies, and there is no consistent error. Most of the time there are no problems (95%), but sometimes we get these errors.

Connection from the asp to sql is done using ADO, using following driver in the connectionstring :

Driver="{SQL Native Client}"

Does anyone have an idea what could be the problem ?
We can of course increase timouts for the mirroring, but is this the solution ?

Greets
Tom

Looks like your application attempts to login using "OBJECTS" as the default database and the database does not exist. Is that database supposed to always exist or is it occasionally dropped and recreated? Your application should not attempt to connect to the database if it might not exist.

Thanks
Laurentiu

|||Hi Laurentiu,

the database always exists. So it must always be available for connection.
But for some reason SQL fails to see the database.

Also, it's not one and the same database that has this problems. We have more than 100 databases on the sql server, and the connection error popups randomly with other databases.

Greets
Tom|||

Can you check your server errorlog and post the errors that show up there? Also, does this happen during server startup by any chance? Is your database on a special volume, such that it would take longer to start up, for example, is it on an EFS volume?

Thanks
Laurentiu

|||Hi Laurentiu,

I'll check the correct SQL serverlogs when this error occurs.

The server is not starting up but running as normally. Remember, this is a production server.
No special volumes.

Additional information :

As told the connection is made in our ASP pages , using an ADO connectionstring.

Now it seems that the initial connection setup works :
e.g

set pCn = Server.CreateObject("ADODB.Connection")
pCn.connectionstring=lstr
pCn.Open

And the first executes always seem to work :
e.g.
pcn.Execute ("select * from thetable")

But in the same page, more executes are performed with the same connection (pC).
And after some executes, it fails with the above error.

Again, this does not happen always, and not with the same database !
And we are not starting up the server, or doing special tasks (aka backups,etc) which would add an extra load on the server.
The moments that this error occures are random, as are the databases with which the error occurs.

Greetings
Tom

|||

If you hit the error again, can you please provide the errorlog entries?

Thanks
Laurentiu

|||

Hi Laurentiu,

sorry for the delay in getting back to you.

There are no error entries in the primary sql server error logs
Only an error pops up in the secondary (mirror) server, stating the login failed.
And this of cours makes sense, as the connection does not go to the primary but to the secondary, which is acting as mirror. And therefore can not be accessed.

The question is : why does the connection sometimes jumps in stead from the primary server, to the mirror server ? Nowhere in my code I give a secondary server as reference.

The connection is made through ODBC in an ASP web application (IIS6) , simelar to :

Set oCn = Server.CreateObject("ADODB.Connection")
oCn.CommandTimeout = 180
oCn.Open lconstirng lconstring

where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
where the dsn file contains following info :

[ODBC]
DRIVER={SQL Native Client}
UID=myuserid
pwd=mypwd
Address=xxx.yyy.zzz.qqq,myport
Network=DBMSSOCN
DATABASE=MyDatabaseName
WSID=xxx.yyy.zzz.qqq
APP=Microsoft Open Database Connectivity
SERVER=xxx.yyy.zzz.qqq
Description=blabla

I tried the above without the DSN, so a dsnless connection string. Nothing changed.
I tried following drivers :{SQL Native Client} and SQLNCLI
Nothing changed

Any ideas ?

Greets
Tom|||

Hi Tom,

For these questions, I suggest trying the Database Mirroring forum or the SQL Server Data Access forum. These are the forums that address issues related to mirroring and server connections.

Thanks
Laurentiu

Cannot open database "xx" requested by the login. The login failed.

Hi,
we are running a webapplication, using IIS6, Windows 2003 64 bit in classic Asp.
In

the ASP pages we connect to our SQL server (SQL Server 2005

64bit,windows 2003 64 bit), mirrored on a third sql server (same

software /hardware setup as the first sql server).

The mirroring is without witness.

This works but sometimes we get the following ODBC error in our ASP application :

Description: [Microsoft][SQL Native Client][SQL Server]Cannot open database

"OBJECTS" requested by the login. The login failed.

No error can be seen in the principal SQL error logs.
But a failed authorization can be found on the mirror server..
And this of course this makes

sense, as the connection does not go to the primary but to the

secondary, which is acting as mirror. And therefore can not be accessed.

The question is : why

does the connection sometimes jumps in stead from the primary server,

to the mirror server ? Nowhere in the code I give a secondary server as

reference.

Most of

the time there are no problems (97%), but sometimes we get these errors.

The moments that this error occures are random, as are the databases with which the error occurs.

The connection is made through ODBC in an ASP web application (IIS6) , simelar to :

Set oCn = Server.CreateObject("ADODB.Connection")
oCn.CommandTimeout = 180
oCn.Open lconstring

where lconstring is a dsn param : e.g. "filedsn=c:\data\dsn\mastercon.dsn"
where the dsn file contains following info :

[ODBC]
DRIVER={SQL Native Client}
UID=myuserid
pwd=mypwd
Address=xxx.yyy.zzz.qqq,myport
Network=DBMSSOCN
DATABASE=MyDatabaseName
WSID=xxx.yyy.zzz.qqq
APP=Microsoft Open Database Connectivity
SERVER=xxx.yyy.zzz.qqq
Description=blabla

I tried the above without the DSN, so a dsnless connection string. Nothing changed.
I tried following drivers :{SQL Native Client} and SQLNCLI
Nothing changed

Does anyone have an idea what could be the problem ?
We can of course increase timouts for the mirroring, but is this the solution ?
Before we started using SQL 2005 and mirroring this problem did not occur.

Greets

Tom

This will occur if you client has intermittent problems accessing the principal. The mirroring principal will send the name of the mirror server to the client after the first connection. If the client loses connection, it does not know if the principal has failed (it could have been destroyed by a natural disaster for example) so it will try to connect to the mirror to see if there has been a failover to the mirror. Since there was no server side failover in this case, you will get the connection failure logged on the mirror server. I recommend you monitor your network to see if there are intermittent problems causing this behavior.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||At this point we can't find any immediate problems.

What information could help us to identify the reason causing the 'intermittent problems accessing the principal' ?

Are there logs I can consult ?

Greetings

Tom|||

I found an interesting link, which could be the reason for our problem.

But we are unaware that we disbled pooling :

http://groups-beta.google.com/group/microsoft.public.sqlserver.odbc/browse_thread/thread/9c79f6f4e8adce7b/f99b340d2fd76aef

Would this fix help even when pooling is enabled ?

Greetings,
Tom

|||Any solution for this with SP2 for 2005 ?

Cannot login using 'sa' user name and password

Used configuration and enabled IP and is fiexed. Thanks.
--
Mike
"Mike9900" wrote:

> Hello,
> When I try to connect it give the following message I copied from the log:
> Source Logon
> Message
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. [CLIENT: <local machine>]
>
> I am using Win 2003 Ent. and is domain controller. I use administrator
> login in win 2003. I recently installed a new win2003, but I had Win2003
> before and was fine.
> In SQL Server, it is a mixed mode and everything seems to be fine.
> What could be the other problems?
> Thanks
> --
> MikeHello,
When I try to connect it give the following message I copied from the log:
Source Logon
Message
Login failed for user 'sa'. The user is not associated with a trusted SQL
Server connection. [CLIENT: <local machine>]
I am using Win 2003 Ent. and is domain controller. I use administrator
login in win 2003. I recently installed a new win2003, but I had Win2003
before and was fine.
In SQL Server, it is a mixed mode and everything seems to be fine.
What could be the other problems?
Thanks
Mike|||Used configuration and enabled IP and is fiexed. Thanks.
--
Mike
"Mike9900" wrote:

> Hello,
> When I try to connect it give the following message I copied from the log:
> Source Logon
> Message
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. [CLIENT: <local machine>]
>
> I am using Win 2003 Ent. and is domain controller. I use administrator
> login in win 2003. I recently installed a new win2003, but I had Win2003
> before and was fine.
> In SQL Server, it is a mixed mode and everything seems to be fine.
> What could be the other problems?
> Thanks
> --
> Mike

Cannot log-in to SQL Server

I've got SQL Server Express 2005 running as a backend and a front-end
made with microsoft access. I can connect when I run the front-end on
the same machine as the SQL Server but as soon as I try to set up a
network ODBC connection I get these errors. (The access front-end can
see the SQL Server - just not login to it).
This is the error I get:
Connection failed.
SQLState. '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'sa'. The user is not associated with a trusted SQL Server connection.
I have tried this with several different user name/password
combinations with varying degrees of permissions but none of them can
login. There is norton protection on but I set it to allow this type of
connection.
I went through the SQL Server 2005 connection FAQ with no result.Perhaps one of these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/defaul...kb;EN-US;914277
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/ar.../23/192044.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"p" <p.macrae@.gmail.com> wrote in message
news:1165358176.124238.273490@.73g2000cwn.googlegroups.com...
> I've got SQL Server Express 2005 running as a backend and a front-end
> made with microsoft access. I can connect when I run the front-end on
> the same machine as the SQL Server but as soon as I try to set up a
> network ODBC connection I get these errors. (The access front-end can
> see the SQL Server - just not login to it).
> This is the error I get:
> Connection failed.
> SQLState. '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'sa'. The user is not associated with a trusted SQL Server connection.
> I have tried this with several different user name/password
> combinations with varying degrees of permissions but none of them can
> login. There is norton protection on but I set it to allow this type of
> connection.
> I went through the SQL Server 2005 connection FAQ with no result.
>

Cannot log-in to SQL Server

I've got SQL Server Express 2005 running as a backend and a front-end
made with microsoft access. I can connect when I run the front-end on
the same machine as the SQL Server but as soon as I try to set up a
network ODBC connection I get these errors. (The access front-end can
see the SQL Server - just not login to it).
This is the error I get:
Connection failed.
SQLState. '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'sa'. The user is not associated with a trusted SQL Server connection.
I have tried this with several different user name/password
combinations with varying degrees of permissions but none of them can
login. There is norton protection on but I set it to allow this type of
connection.
I went through the SQL Server 2005 connection FAQ with no result.
Perhaps one of these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"p" <p.macrae@.gmail.com> wrote in message
news:1165358176.124238.273490@.73g2000cwn.googlegro ups.com...
> I've got SQL Server Express 2005 running as a backend and a front-end
> made with microsoft access. I can connect when I run the front-end on
> the same machine as the SQL Server but as soon as I try to set up a
> network ODBC connection I get these errors. (The access front-end can
> see the SQL Server - just not login to it).
> This is the error I get:
> Connection failed.
> SQLState. '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. The user is not associated with a trusted SQL Server connection.
> I have tried this with several different user name/password
> combinations with varying degrees of permissions but none of them can
> login. There is norton protection on but I set it to allow this type of
> connection.
> I went through the SQL Server 2005 connection FAQ with no result.
>

cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scottsorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David|||many thanks for reply.
i think you are right about this.
Cheers
Scott