Connection is busy with results for another hstmt

I am working on Sql Server 2000 and Delphi 5. When I try to open a table :

Table1.open;

I get the following error message :

Connection is busy with results for another hstmt.

I am new to Sql Server so please keep the explanation simple !!!

I have already read this got something to do with forward-only, read-only cursor. But I don't know what a forward-only, read-only cursor mean. Please explain !!

Thanks
KarenHowdy

A cursor collects a record set from a database. The cursor has a pointer that can move around in the record set to read a particular row etc. A forward only cursor can only read down ( i.e. forward ) through the record set, so if you are trying to go backwards through the record set it may not let you.

I dont know anything about Delphi, but from SQL Books on Line :

----------

SQLTables
When restricted to the current database, SQLTables executes the Transact-SQL procedure sp_tables to report table catalog data for Microsoft SQL Server.

The following table shows SQLTables parameter mapping for sp_tables stored procedure execution.

SQLTables parameter name sp_tables parameter name
CatalogName table_qualifier
SchemaName table_owner
TableName table_name
TableType table_type

SQLTables can be executed on a static server cursor. An attempt to execute SQLTables on an updatable (dynamic or keyset) cursor will return SQL_SUCCESS_WITH_INFO indicating that the cursor type has been changed.

SQLTables reports tables from all databases when the CatalogName parameter is SQL_ALL_CATALOGS and all other parameters contain default values (NULL pointers). SQLTables does not make use of sp_tables in this special case.

To report available catalogs, schemas, and table types, SQLTables makes special use of empty strings (zero-length byte pointers). Empty strings are not default values (NULL pointers).

The SQL Server ODBC driver supports reporting information for tables on linked servers by accepting a two-part name for the CatalogName parameter: Linked_Server_Name.Catalog_Name.

SQLTables returns information about any tables whose names match TableName and are owned by the current user.

Example
// Get a list of all tables in the current database.
SQLTables(hstmt, NULL, 0, NULL, 0, NULL, 0, NULL,0);
// Get a list of all tables in all databases.
SQLTables(hstmt, (SQLCHAR*) "%", SQL_NTS, NULL, 0, NULL, 0, NULL,0);
// Get a list of databases on the current connection's server.
SQLTables(hstmt, (SQLCHAR*) "%", SQL_NTS, (SQLCHAR*)"", 0, (SQLCHAR*)"",
0, NULL, 0);

Cheers,

SG

Connection handshake failed: Unexpected or badly formatted message.

Hello,

I am unable to send a message to a target service on a different SQL Server instance. Using the SQL Profiler, I get the following error from the target machine:

Broker::Connection: Connection handshake failed: An OS call failed: (80090326) 0x80090326(The message received was unexpected or badly formatted.). State 106.

On the initiator side, the transmission_status shows the following error:

An error occurred while receiving data: '64(The specified network name is no longer available.)'.

Any ideas on why the target thinks the message is "unexpected or badly formatted"? Btw, I am specifying the default message type and contract for the services.

Thanks.

The problem is in the NTLM/Kerberos authentification sequence and I reckon I never saw it before. If you only want to get this to work, you can change the endpoint authentication from WINDOWS to CERTIFICATE. If you want to see why is this failing in the first place, I suggest you follow up using the MS Connect site at https://connect.microsoft.com/SQLServer/Feedback?wa=wsignin1.0. A netmon capture of the handhsake sequence would be needed to investigate this.

Connection handshake failed.

Hi.

I created two instances of SQL Server Dev Edition on the same machine.

The two instances acted as the sender / receiver.

However, when the message is transmitted from "Sender" to "Receiver", the following errors are
displayed in "SQL Profiler".

「Connection handshake failed. There is no compatible authentication protocol. State 21.」

How should be dealt with with this?
My best regards.

piknik

Seems like there is a problem with how you've setup your endpoints. Could you paste the script which you used for creating the endpoints? If you don't have that, could you paste the results from this query run on both instances?

select * from sys.service_broker_endpoints

|||

One machine is configured to use CERTIFICATE authentication, the other is configured to use WINDOWS. (or one is configured to use WINDOWS KERBEROS and the other WINDOWS NTLM).

Configure the endpoints to have at least one compatible authentication protocol and it will work.

HTH,
~ Remus

|||

Thank you for the reply.

I used following Script.

[Sender]

USE master
GO

-- Create master key in the master database
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password62374'

-- Create the certificate for transport security
CREATE CERTIFICATE TransportCert1
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert1.cer'
WITH PRIVATE KEY (
FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert1.pvk',
DECRYPTION BY PASSWORD = 'password62374'
)
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create a user in the master db to be associated with
-- the public key from the remote certificate (TestCert2.cer)
CREATE LOGIN remcert WITH PASSWORD = 'password62374'
CREATE USER remcert FOR LOGIN remcert

-- remcert has to have connect priviliges
GRANT CONNECT TO remcert

-- Install the public key from the remote cert in master
CREATE CERTIFICATE TransportCert2
AUTHORIZATION remcert
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert2.cer'
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Switch to the user database
USE SuperMarketServer
GO

-- Create a master key
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password62374'

-- Create a certificate for dialog security
CREATE CERTIFICATE DialogCert1
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert1.cer'
WITH PRIVATE KEY (
FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert1.pvk',
DECRYPTION BY PASSWORD = 'password62374'
)
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create user that holds the remote public key for the dialog security certificate
CREATE USER remcert FOR LOGIN remcert

CREATE CERTIFICATE DialogCert2
AUTHORIZATION remcert
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert2.cer'
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create a remote service binding associating the remcert user
-- with the remote service
CREATE REMOTE SERVICE BINDING [SellItemBinding]
TO SERVICE 'SellItemService'
WITH USER = remcert,
ANONYMOUS = Off

-- The user has to have SEND permissions
GRANT SEND ON SERVICE::[SoldItemService] TO remcert
go

-- Enable communication between instances by creating an endpoint
CREATE ENDPOINT ServerEndpoint
STATE = STARTED
AS TCP
(
LISTENER_PORT = 5024
)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE TransportCert1)

-- Finally grant connect permission to user used to secure the dialog
USE master
GO

GRANT CONNECT ON ENDPOINT::ServerEndpoint TO remcert
GO

SELECT * FROM sys.endpoints
--

It is set to "CERTIFICATE authentication" as which Sender and Reciver are the
same.

The sample of Script is put.
http://enterpriselibrary.jp/SampleDemo.zip

My Best Regards.

piknik.

connection from the pool

I build an asp.net 2.0 (VS 2005) web application and put it on the server. The installed SQL server is SQL server 2003. I get this error message when i keep the application running for 10 or 15 mins. "Timeout expired. The timeout period elapsed prior obtaining a connection from the pool. This may have occure because all pooled connections were in use and max pool size was reached."

I made the server timeout unlimited but the error keeps coming up after some time of openning the application. The application session time out redirects the user to the login page and doesn't throw an error like the one i mentioned above.

Any idea. Thanks in advance.

designstudio,

try increasing the number of connections in the pool. in your connection string, here is an example

conn.ConnectionString = "integratedsecurity=SSPI;SERVER=YOUR_SERVER;DATABASE=YOUR_DB_NAME;Min Pool Size=5;Max PoolSize=60;Connect Timeout=2;";

see where it says max pool size = ...have you tried that?

hope this helps -- jp

|||

Thanks jdingo,

I haven't tried that. I think it will work.

I'll let you know if it doesn't work.

|||

Thanks jdingo,

I haven't tried that. I think it will work.

I'll let you know if it doesn't work.

|||

You might also want to ensure that you really are closing all connections. The best way to ensure this is to use the 'using' statement in C#, or a try-finally combination where you explicitly close the connection in the finally block.

string connectionString = GetConnectionString(); // Gets the connection string in some way defined by youusing (SqlConnection connection =new SqlConnection(connectionString)){ connection.Open();// Do whatever needs to be doing. When the using-block is exited, the connection // objects Dispose() method will be called, ensure that the connection is returned // to the pool. Even if an exception occurs.}

Connection from other domain failes

Hi,
i like to use my Excel pivot from other domain, but I always get the error message "Cannot find repository". I tried a ping on IP of analysis server, no problem. The connection string includes the IP adress as well. Anybody knows the clue ?
Thx
dajmI have to re-post my question, hopefully anybody got same problem.

Here my problem again:

A client from other (trusted) domain can ping to my analysis server, but cannot use the excel pivot table using the cube of same analysis server. It is saying "Cannot find repository".
Pivottable is working fine from same domain as analysis server.

Any clue ?

dajm|||Where is repository of your Analysis Server located? In access file msmdrep in Binn directory of AS (default) or in SQL Server msdb database (after migration)? mojza|||Thx. for reply.

repository path is standard path of SQL server.

Anyway, I made this workaround:

I have chosen authentication over http protocol and it works fine now.
Any disadvantages I can expect from this solution ?

dajm

Connection failed to local SQL server

Hello,
One day when i try to open my database om my local computer (Win 2000
server, SQL 2000 EE, sp3) i get message:
A connection could not be established to (LOCAL)
Reason: cannot open user default database. Login faied..
Please verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the (LOCAL) node) and try again.
SQL Server is running and right-clicking produces just the same message.
Can anybody say what happend and what to do.
Thanks a lot.1. check which database is default database for your login
2. default database exist on server?
3. check permissons on your default database
"olsh" wrote:
> Hello,
> One day when i try to open my database om my local computer (Win 2000
> server, SQL 2000 EE, sp3) i get message:
> A connection could not be established to (LOCAL)
> Reason: cannot open user default database. Login faied..
> Please verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the (LOCAL) node) and try again.
> SQL Server is running and right-clicking produces just the same message.
> Can anybody say what happend and what to do.
> Thanks a lot.|||Sorry, how can i check these if i have no access to SQL Server?
"Aleksandar Grbic" wrote:
> 1. check which database is default database for your login
> 2. default database exist on server?
> 3. check permissons on your default database
>
> "olsh" wrote:
> > Hello,
> > One day when i try to open my database om my local computer (Win 2000
> > server, SQL 2000 EE, sp3) i get message:
> > A connection could not be established to (LOCAL)
> > Reason: cannot open user default database. Login faied..
> > Please verify SQL Server is running and check your SQL Server
> > registration properties (by right-clicking on the (LOCAL) node) and try again.
> >
> > SQL Server is running and right-clicking produces just the same message.
> >
> > Can anybody say what happend and what to do.
> >
> > Thanks a lot.|||use ISQL
sample
ISQL -S<server> -U<user> -P<password>
if your default database not exist on server, isql will use master database
then, check your default database
select name,dbname from syslogins where name='<yourlogin>'
go
...
and if shall
exec sp_defaultdb 'login','database'
go
"olsh" wrote:
> Sorry, how can i check these if i have no access to SQL Server?
>
> "Aleksandar Grbic" wrote:
> > 1. check which database is default database for your login
> >
> > 2. default database exist on server?
> >
> > 3. check permissons on your default database
> >
> >
> > "olsh" wrote:
> >
> > > Hello,
> > > One day when i try to open my database om my local computer (Win 2000
> > > server, SQL 2000 EE, sp3) i get message:
> > > A connection could not be established to (LOCAL)
> > > Reason: cannot open user default database. Login faied..
> > > Please verify SQL Server is running and check your SQL Server
> > > registration properties (by right-clicking on the (LOCAL) node) and try again.
> > >
> > > SQL Server is running and right-clicking produces just the same message.
> > >
> > > Can anybody say what happend and what to do.
> > >
> > > Thanks a lot.|||Thanks, everything is OK now!!
"Aleksandar Grbic" wrote:
> use ISQL
> sample
> ISQL -S<server> -U<user> -P<password>
> if your default database not exist on server, isql will use master database
> then, check your default database
> select name,dbname from syslogins where name='<yourlogin>'
> go
> ...
> and if shall
> exec sp_defaultdb 'login','database'
> go
>
> "olsh" wrote:
> > Sorry, how can i check these if i have no access to SQL Server?
> >
> >
> > "Aleksandar Grbic" wrote:
> >
> > > 1. check which database is default database for your login
> > >
> > > 2. default database exist on server?
> > >
> > > 3. check permissons on your default database
> > >
> > >
> > > "olsh" wrote:
> > >
> > > > Hello,
> > > > One day when i try to open my database om my local computer (Win 2000
> > > > server, SQL 2000 EE, sp3) i get message:
> > > > A connection could not be established to (LOCAL)
> > > > Reason: cannot open user default database. Login faied..
> > > > Please verify SQL Server is running and check your SQL Server
> > > > registration properties (by right-clicking on the (LOCAL) node) and try again.
> > > >
> > > > SQL Server is running and right-clicking produces just the same message.
> > > >
> > > > Can anybody say what happend and what to do.
> > > >
> > > > Thanks a lot.

Connection failed between PC

Hello, i ahve a problem to connect a pc to another with MSDE installed.
The response message of this failure is:
'Server not exists'

Can help me?

Thanks!Hai,

I dont exactly trap 'What u mentaioned is the os server or sql
server.

Any way if you want to access a machine from u r machine , the
followings must exits.

1. Network among them.
2. if , so u can access other machines from u r command prompt(run).

like, \\node-x\e$

..if it does not work , share the other machine's drives

Raghu|||alessandro_chiodo@.hotmail.com (Alex) wrote in message news:<c7bf0032.0312040727.29186bc9@.posting.google.com>...
> Hello, i ahve a problem to connect a pc to another with MSDE installed.
> The response message of this failure is:
> 'Server not exists'
> Can help me?
> Thanks!

One possibility is that you're using the wrong authentication method:

http://support.microsoft.com/defaul...0&Product=sql2k

Another possibility is that it's MSDE SP3a, which disables network
access to MSDE by default:

http://support.microsoft.com/defaul...for _msde_d3jb

Simon

Connection failed

Hello, I'm trying to set up a New Data Source to SQL Server through ODBC and
am getting the following error message after trying to supply correct SQL
Login ID and Password:
Connection failed:
SQLState: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'xxxxxxxxx'
Any help would be appreciated. Thanks.
Just for kicks, try to connect to SQL Server via Query Analyzer using that
login and password
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:ujWBaRJWIHA.5816@.TK2MSFTNGP06.phx.gbl...
> Hello, I'm trying to set up a New Data Source to SQL Server through ODBC
> and am getting the following error message after trying to supply correct
> SQL Login ID and Password:
> Connection failed:
> SQLState: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'xxxxxxxxx'
>
> Any help would be appreciated. Thanks.
>
|||Kind of strange in that after a while with really no changes it ended up
working. We were trying it from a wireless laptop first which then we
physically plugged in the network cable into the laptop and still didn't
work...but after about 10 minutes later the same steps did allow the ODBC
setup to finish logging in successfully. Kind of weird but I'm not
complaining.
Thanks a bunch for your speedy reply Kevin. Much appreciated. Take cares
:-)
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:u1L2GKTWIHA.2304@.TK2MSFTNGP06.phx.gbl...
> Just for kicks, try to connect to SQL Server via Query Analyzer using that
> login and password
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:ujWBaRJWIHA.5816@.TK2MSFTNGP06.phx.gbl...
>

connection failed

Hello,
I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
But I cannot connect to sql server. I receive this message "Unable to
connect to server xxxxxx: SQL Server does not exist or access denied"; or
Login failed for user xxxxx. With QA same problem... I created the alias
with client network utility... but no way... i cannot access sql server.
anyone have an idea?
Thanks in advance
Alex
You would want to start with this article and the links it
references - the problems depend on protocols, what the
exact full error message is, what ports you have opened (if
any), etc:
How to configure Windows XP Service Pack 2 (SP2) for use
with SQL Server
http://support.microsoft.com/?id=841249
-Sue
On Fri, 11 Mar 2005 09:15:54 +0200, ".:alex:."
<alex_77ro@.yahoo.com> wrote:

>Hello,
> I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
>But I cannot connect to sql server. I receive this message "Unable to
>connect to server xxxxxx: SQL Server does not exist or access denied"; or
>Login failed for user xxxxx. With QA same problem... I created the alias
>with client network utility... but no way... i cannot access sql server.
>anyone have an idea?
>Thanks in advance
>Alex
>

connection failed

Hello,
I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
But I cannot connect to sql server. I receive this message "Unable to
connect to server xxxxxx: SQL Server does not exist or access denied"; or
Login failed for user xxxxx. With QA same problem... I created the alias
with client network utility... but no way... i cannot access sql server.
anyone have an idea?
Thanks in advance
AlexYou would want to start with this article and the links it
references - the problems depend on protocols, what the
exact full error message is, what ports you have opened (if
any), etc:
How to configure Windows XP Service Pack 2 (SP2) for use
with SQL Server
http://support.microsoft.com/?id=841249
-Sue
On Fri, 11 Mar 2005 09:15:54 +0200, ".:alex:."
<alex_77ro@.yahoo.com> wrote:

>Hello,
> I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
>But I cannot connect to sql server. I receive this message "Unable to
>connect to server xxxxxx: SQL Server does not exist or access denied"; or
>Login failed for user xxxxx. With QA same problem... I created the alias
>with client network utility... but no way... i cannot access sql server.
>anyone have an idea?
>Thanks in advance
>Alex
>

connection failed

This is a multi-part message in MIME format.
--=_NextPart_000_0006_01C83047.CA2BAB90
Content-Type: text/plain;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection = Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, = and after
entering it - it works. But only for the current transaction. Next time = it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC = drivers, tried different usernames, but the same error returns.
What could be the problem ?
Thanks.
--=_NextPart_000_0006_01C83047.CA2BAB90
Content-Type: text/html;
charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
I have a program using ms sql. It = worked fine for some time, but
now each time the program access the = databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, = Login failed for user 'sa'".
After pressing OK it gives an option to = input a new password manually, and after
entering it - it works. But only for = the current transaction. Next time it'll prompt again.

I've tried to change the password, I've = chaned it in the system ODBC drivers, tried
different usernames, but the = same error returns.

What could be the problem = ?
Thanks.
--=_NextPart_000_0006_01C83047.CA2BAB90--It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.

connection failed

When i try to connect from remote computer to sequel
server i get the followin message
connection failed.
i'm connecting using odbc, i'm new to this so all help
thanks in advance.HI,
Create you create a Alias name for your sql server remote machine using the
"Client Network Utility" by providing
Protocol as TCP/IP, IP address of sql server machine and port number.
After this use this Alias name to connect to sql server machine.
Thanks
Hari
MCDBA
"mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a0c501c43475$557426f0$a101280a@.phx.gbl...
> When i try to connect from remote computer to sequel
> server i get the followin message
> connection failed.
> i'm connecting using odbc, i'm new to this so all help
> thanks in advance.

Connection failed

Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
--
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection error after copying an rdl

Whenever I make a copy of an existing report (.rdl) in order to use it as a
template for a new report, I get the following error message when I try to
preview it:
An error has occurred during report processing.
Cannot create a connection to data source 'Prospect'
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
The originial copy of the report - in the same project - works without
error. Why is this happening. This requires me to start every report from
scratch, and since I have a lot of parameters and data sources, this is very
tedious.Since specific credential information is not stored in the .rdl so when you
attempt to preview the copied report you'll see this error until you modify
your report DataSource. If you modify your report DataSets to use a shared
DataSource, I don't believe you'll run into this.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jody Z" <Jody Z@.discussions.microsoft.com> wrote in message
news:B95FFD30-F0D5-4FAC-B6C9-6A91DD5DFAA0@.microsoft.com...
> Whenever I make a copy of an existing report (.rdl) in order to use it as
> a
> template for a new report, I get the following error message when I try to
> preview it:
> An error has occurred during report processing.
> Cannot create a connection to data source 'Prospect'
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL
> Server connection.
> The originial copy of the report - in the same project - works without
> error. Why is this happening. This requires me to start every report
> from
> scratch, and since I have a lot of parameters and data sources, this is
> very
> tedious.

Connection Error 18452 - Login failed for user '(null)'

Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
This is always an authentication problem somewhere. The null indicates that
user cannot be validated and a null is being passsed to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Rand, what about a solution or al least pointing to one?
"Rand Boyd [MSFT]" wrote:

> This is always an authentication problem somewhere. The null indicates that
> user cannot be validated and a null is being passsed to SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||It really depends on where the process is failing. You would
want to check the event logs on the PC having the problems
connecting. Check for any network related issues or
problems. Make sure that PC is contacting the domain
controllers without any problems and that they are
successfully logging into the network.
-Sue
On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
<JC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Rand, what about a solution or al least pointing to one?
>"Rand Boyd [MSFT]" wrote:
|||Login failed for user <null> usually means that on the SQL box, the user
account could not be found in the local security database or in the domain
controller's user database.
For example, on machine1 I log in as machine1\user1. Then I try to log into
SQL on machine2. On machine2 SQL takes the SID of the user and calls
LookupAccountSID API. This attempts to convert the SID to the user name.
LookupAccountSID first looks in local security database on machine2, and
does not find machine1\User1, then looks on domain controller, and still
does not find the SID.
So in general this points to problems with the user account. Perhaps the
user has the same account name defined on their local machine and when they
log in they don't realize that they are logging in as the local User1 versus
the domain User1. Go to the problematic machine and check the user
accounts. If this does not work, perhaps have the domain admin drop the
user account and recreate it.
Matt
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:jd4sr0ds5vna1pc5ph4ri66j5hmri6d51p@.4ax.com...
> It really depends on where the process is failing. You would
> want to check the event logs on the PC having the problems
> connecting. Check for any network related issues or
> problems. Make sure that PC is contacting the domain
> controllers without any problems and that they are
> successfully logging into the network.
> -Sue
> On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
> <JC@.discussions.microsoft.com> wrote:
>

Connection Error 18452 - Login failed for user '(null)'

Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus WolffThis is always an authentication problem somewhere. The null indicates that
user cannot be validated and a null is being passsed to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand, what about a solution or al least pointing to one?
"Rand Boyd [MSFT]" wrote:

> This is always an authentication problem somewhere. The null indicates tha
t
> user cannot be validated and a null is being passsed to SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||It really depends on where the process is failing. You would
want to check the event logs on the PC having the problems
connecting. Check for any network related issues or
problems. Make sure that PC is contacting the domain
controllers without any problems and that they are
successfully logging into the network.
-Sue
On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
<JC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Rand, what about a solution or al least pointing to one?
>"Rand Boyd [MSFT]" wrote:
>|||Login failed for user <null> usually means that on the SQL box, the user
account could not be found in the local security database or in the domain
controller's user database.
For example, on machine1 I log in as machine1\user1. Then I try to log into
SQL on machine2. On machine2 SQL takes the SID of the user and calls
LookupAccountSID API. This attempts to convert the SID to the user name.
LookupAccountSID first looks in local security database on machine2, and
does not find machine1\User1, then looks on domain controller, and still
does not find the SID.
So in general this points to problems with the user account. Perhaps the
user has the same account name defined on their local machine and when they
log in they don't realize that they are logging in as the local User1 versus
the domain User1. Go to the problematic machine and check the user
accounts. If this does not work, perhaps have the domain admin drop the
user account and recreate it.
Matt
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:jd4sr0ds5vna1pc5ph4ri66j5hmri6d51p@.
4ax.com...
> It really depends on where the process is failing. You would
> want to check the event logs on the PC having the problems
> connecting. Check for any network related issues or
> problems. Make sure that PC is contacting the domain
> controllers without any problems and that they are
> successfully logging into the network.
> -Sue
> On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
> <JC@.discussions.microsoft.com> wrote:
>
>

Connection Error 18452 - Login failed for user '(null)'

Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
I have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:

> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the server
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the message
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>

Connection Error 18452 - Login failed for user '(null)'

Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus WolffI have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:

> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the serv
er
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the messa
ge
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>

Connection Broken when executing select statement

Hi,
I have written a query that gives the following message
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I have seen several posts with this problem but none seem to match mine.
here is the query
select distinct
case
when 'ct' = 'CT' then 'CTM'
when 'ct' = 'SD' then 'SDM'
when 'ct' = 'TFVT' then 'VTM'
end, null, 'L', 'AV-A196', 'AV-A196', null, null, Service_Area,
Locality, Location,
Segment_Ref, Vicinity, Map_Ref, Service_Status, Condition_Status,
Charge_Key,
Asset_Owner, Resp_Area, Resp_Position, Data_Changed, null, GIS_Tile,
Note_Text, Asset_Region, Asset_Ranking
from asset
where category = 'ct'
and asset_Id not in (60325, 60377,60274, 60397)
and ((len(local_id) < 6 and local_id = 'AV-A196')
or (len(local_id) >= 6 and substring(local_id, 1, len(local_id)-6) = 'AV-A196'))
I have tested this on a SQL Server 2000 machine by creating a new database,
importing the asset table of 66000 records. Then created new indexes on
Asset_id (clustered primary key)
Local_id (unique index)
Category (index)
If I remove any of the conditions in the where statement it runs fine.
However with them all in their it breaks.
I am running 8.00.859 (sp3)
Any Suggestions
BenBenJamin wrote:
> Hi,
> I have written a query that gives the following message
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I have seen several posts with this problem but none seem to match
> mine. here is the query
> select distinct
> case
> when 'ct' = 'CT' then 'CTM'
> when 'ct' = 'SD' then 'SDM'
> when 'ct' = 'TFVT' then 'VTM'
> end, null, 'L', 'AV-A196', 'AV-A196', null, null, Service_Area,
> Locality, Location,
> Segment_Ref, Vicinity, Map_Ref, Service_Status, Condition_Status,
> Charge_Key,
> Asset_Owner, Resp_Area, Resp_Position, Data_Changed, null,
> GIS_Tile, Note_Text, Asset_Region, Asset_Ranking
> from asset
> where category = 'ct'
> and asset_Id not in (60325, 60377,60274, 60397)
> and ((len(local_id) < 6 and local_id = 'AV-A196')
> or (len(local_id) >= 6 and substring(local_id, 1, len(local_id)-6) => 'AV-A196'))
> I have tested this on a SQL Server 2000 machine by creating a new
> database, importing the asset table of 66000 records. Then created
> new indexes on Asset_id (clustered primary key)
> Local_id (unique index)
> Category (index)
> If I remove any of the conditions in the where statement it runs fine.
> However with them all in their it breaks.
> I am running 8.00.859 (sp3)
> Any Suggestions
> Ben
Maybe I'm reading the SQL statement incorrectly, but how would this
statement ever be true:
(len(local_id) < 6 and local_id = 'AV-A196')
That would seem to imply the lengh of the column must be 5 or less _and_
it must be equal to a 7 character string, at the same time.
Just curious.
David Gugick
Imceda Software
www.imceda.com|||"David Gugick" wrote:
> BenJamin wrote:
> > Hi,
> >
> > I have written a query that gives the following message
> > [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> > (CheckforData()).
> > Server: Msg 11, Level 16, State 1, Line 0
> > General network error. Check your network documentation.
> >
> > Connection Broken
> >
> > I have seen several posts with this problem but none seem to match
> > mine. here is the query
> > select distinct
> > case
> > when 'ct' = 'CT' then 'CTM'
> > when 'ct' = 'SD' then 'SDM'
> > when 'ct' = 'TFVT' then 'VTM'
> > end, null, 'L', 'AV-A196', 'AV-A196', null, null, Service_Area,
> > Locality, Location,
> > Segment_Ref, Vicinity, Map_Ref, Service_Status, Condition_Status,
> > Charge_Key,
> > Asset_Owner, Resp_Area, Resp_Position, Data_Changed, null,
> > GIS_Tile, Note_Text, Asset_Region, Asset_Ranking
> > from asset
> > where category = 'ct'
> > and asset_Id not in (60325, 60377,60274, 60397)
> > and ((len(local_id) < 6 and local_id = 'AV-A196')
> > or (len(local_id) >= 6 and substring(local_id, 1, len(local_id)-6) => > 'AV-A196'))
> >
> > I have tested this on a SQL Server 2000 machine by creating a new
> > database, importing the asset table of 66000 records. Then created
> > new indexes on Asset_id (clustered primary key)
> > Local_id (unique index)
> > Category (index)
> >
> > If I remove any of the conditions in the where statement it runs fine.
> > However with them all in their it breaks.
> >
> > I am running 8.00.859 (sp3)
> > Any Suggestions
> > Ben
> Maybe I'm reading the SQL statement incorrectly, but how would this
> statement ever be true:
> (len(local_id) < 6 and local_id = 'AV-A196')
> That would seem to imply the lengh of the column must be 5 or less _and_
> it must be equal to a 7 character string, at the same time.
> Just curious.
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
Fair Call,
That part is just there as a means to stop the statement trying to process
Local_ID's less than 6 characters long with the second part of the condition
statement. It is meant to always be false.
I was gettting incorrect length to the substring function. I tried to get it
to process the conditions in the order that they are written to exclude the
unwanted rows. Maybe there is a way, I don't know.
But thanks for the quick response though...|||Hi
Check your SQL Server log. You may find that your process was terminated at
a server level. If it was, try to go to 8.00.0878 and if that does not solve
it, open a call with PSS.
Regards
Mike
"BenJamin" wrote:
>
> "David Gugick" wrote:
> > BenJamin wrote:
> > > Hi,
> > >
> > > I have written a query that gives the following message
> > > [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> > > (CheckforData()).
> > > Server: Msg 11, Level 16, State 1, Line 0
> > > General network error. Check your network documentation.
> > >
> > > Connection Broken
> > >
> > > I have seen several posts with this problem but none seem to match
> > > mine. here is the query
> > > select distinct
> > > case
> > > when 'ct' = 'CT' then 'CTM'
> > > when 'ct' = 'SD' then 'SDM'
> > > when 'ct' = 'TFVT' then 'VTM'
> > > end, null, 'L', 'AV-A196', 'AV-A196', null, null, Service_Area,
> > > Locality, Location,
> > > Segment_Ref, Vicinity, Map_Ref, Service_Status, Condition_Status,
> > > Charge_Key,
> > > Asset_Owner, Resp_Area, Resp_Position, Data_Changed, null,
> > > GIS_Tile, Note_Text, Asset_Region, Asset_Ranking
> > > from asset
> > > where category = 'ct'
> > > and asset_Id not in (60325, 60377,60274, 60397)
> > > and ((len(local_id) < 6 and local_id = 'AV-A196')
> > > or (len(local_id) >= 6 and substring(local_id, 1, len(local_id)-6) => > > 'AV-A196'))
> > >
> > > I have tested this on a SQL Server 2000 machine by creating a new
> > > database, importing the asset table of 66000 records. Then created
> > > new indexes on Asset_id (clustered primary key)
> > > Local_id (unique index)
> > > Category (index)
> > >
> > > If I remove any of the conditions in the where statement it runs fine.
> > > However with them all in their it breaks.
> > >
> > > I am running 8.00.859 (sp3)
> > > Any Suggestions
> > > Ben
> >
> > Maybe I'm reading the SQL statement incorrectly, but how would this
> > statement ever be true:
> >
> > (len(local_id) < 6 and local_id = 'AV-A196')
> >
> > That would seem to imply the lengh of the column must be 5 or less _and_
> > it must be equal to a 7 character string, at the same time.
> >
> > Just curious.
> >
> >
> >
> > --
> > David Gugick
> > Imceda Software
> > www.imceda.com
> >
> >
> Fair Call,
> That part is just there as a means to stop the statement trying to process
> Local_ID's less than 6 characters long with the second part of the condition
> statement. It is meant to always be false.
> I was gettting incorrect length to the substring function. I tried to get it
> to process the conditions in the order that they are written to exclude the
> unwanted rows. Maybe there is a way, I don't know.
> But thanks for the quick response though...|||Ben
Add option (loop join) in your select statement
"BenJamin" <BenJamin@.discussions.microsoft.com> wrote in message
news:81A67F85-4D1E-4109-8090-6AFFE437DA63@.microsoft.com...
>
> "David Gugick" wrote:
> > BenJamin wrote:
> > > Hi,
> > >
> > > I have written a query that gives the following message
> > > [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> > > (CheckforData()).
> > > Server: Msg 11, Level 16, State 1, Line 0
> > > General network error. Check your network documentation.
> > >
> > > Connection Broken
> > >
> > > I have seen several posts with this problem but none seem to match
> > > mine. here is the query
> > > select distinct
> > > case
> > > when 'ct' = 'CT' then 'CTM'
> > > when 'ct' = 'SD' then 'SDM'
> > > when 'ct' = 'TFVT' then 'VTM'
> > > end, null, 'L', 'AV-A196', 'AV-A196', null, null, Service_Area,
> > > Locality, Location,
> > > Segment_Ref, Vicinity, Map_Ref, Service_Status, Condition_Status,
> > > Charge_Key,
> > > Asset_Owner, Resp_Area, Resp_Position, Data_Changed, null,
> > > GIS_Tile, Note_Text, Asset_Region, Asset_Ranking
> > > from asset
> > > where category = 'ct'
> > > and asset_Id not in (60325, 60377,60274, 60397)
> > > and ((len(local_id) < 6 and local_id = 'AV-A196')
> > > or (len(local_id) >= 6 and substring(local_id, 1, len(local_id)-6) => > > 'AV-A196'))
> > >
> > > I have tested this on a SQL Server 2000 machine by creating a new
> > > database, importing the asset table of 66000 records. Then created
> > > new indexes on Asset_id (clustered primary key)
> > > Local_id (unique index)
> > > Category (index)
> > >
> > > If I remove any of the conditions in the where statement it runs fine.
> > > However with them all in their it breaks.
> > >
> > > I am running 8.00.859 (sp3)
> > > Any Suggestions
> > > Ben
> >
> > Maybe I'm reading the SQL statement incorrectly, but how would this
> > statement ever be true:
> >
> > (len(local_id) < 6 and local_id = 'AV-A196')
> >
> > That would seem to imply the lengh of the column must be 5 or less _and_
> > it must be equal to a 7 character string, at the same time.
> >
> > Just curious.
> >
> >
> >
> > --
> > David Gugick
> > Imceda Software
> > www.imceda.com
> >
> >
> Fair Call,
> That part is just there as a means to stop the statement trying to process
> Local_ID's less than 6 characters long with the second part of the
condition
> statement. It is meant to always be false.
> I was gettting incorrect length to the substring function. I tried to get
it
> to process the conditions in the order that they are written to exclude
the
> unwanted rows. Maybe there is a way, I don't know.
> But thanks for the quick response though...|||Check the traffic on your network, the query maybe
overloading it.
Peter
"A politician needs the ability to foretell what is going
to happen tomorrow, next week, next month, and next year.
And to have the ability afterwards to explain why it
didn't happen."
Winston Churchill
>--Original Message--
>
>"David Gugick" wrote:
>> BenJamin wrote:
>> > Hi,
>> >
>> > I have written a query that gives the following
message
>> > [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionCheckForData
>> > (CheckforData()).
>> > Server: Msg 11, Level 16, State 1, Line 0
>> > General network error. Check your network
documentation.
>> >
>> > Connection Broken
>> >
>> > I have seen several posts with this problem but none
seem to match
>> > mine. here is the query
>> > select distinct
>> > case
>> > when 'ct' = 'CT' then 'CTM'
>> > when 'ct' = 'SD' then 'SDM'
>> > when 'ct' = 'TFVT' then 'VTM'
>> > end, null, 'L', 'AV-A196', 'AV-A196', null,
null, Service_Area,
>> > Locality, Location,
>> > Segment_Ref, Vicinity, Map_Ref, Service_Status,
Condition_Status,
>> > Charge_Key,
>> > Asset_Owner, Resp_Area, Resp_Position,
Data_Changed, null,
>> > GIS_Tile, Note_Text, Asset_Region, Asset_Ranking
>> > from asset
>> > where category = 'ct'
>> > and asset_Id not in (60325, 60377,60274, 60397)
>> > and ((len(local_id) < 6 and local_id = 'AV-A196')
>> > or (len(local_id) >= 6 and substring(local_id, 1, len
(local_id)-6) =>> > 'AV-A196'))
>> >
>> > I have tested this on a SQL Server 2000 machine by
creating a new
>> > database, importing the asset table of 66000 records.
Then created
>> > new indexes on Asset_id (clustered primary key)
>> > Local_id (unique index)
>> > Category (index)
>> >
>> > If I remove any of the conditions in the where
statement it runs fine.
>> > However with them all in their it breaks.
>> >
>> > I am running 8.00.859 (sp3)
>> > Any Suggestions
>> > Ben
>> Maybe I'm reading the SQL statement incorrectly, but
how would this
>> statement ever be true:
>> (len(local_id) < 6 and local_id = 'AV-A196')
>> That would seem to imply the lengh of the column must
be 5 or less _and_
>> it must be equal to a 7 character string, at the same
time.
>> Just curious.
>>
>> --
>> David Gugick
>> Imceda Software
>> www.imceda.com
>>
>Fair Call,
>That part is just there as a means to stop the statement
trying to process
>Local_ID's less than 6 characters long with the second
part of the condition
>statement. It is meant to always be false.
>I was gettting incorrect length to the substring
function. I tried to get it
>to process the conditions in the order that they are
written to exclude the
>unwanted rows. Maybe there is a way, I don't know.
>But thanks for the quick response though...
>.
>

Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü�meyer" wrote:
> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> > Hi all, in one of my newly configured SQL server logs, I found a error
> > message like this:
> > Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> > Server
> > connection.
> >
> > Also in both of my new servers , SQL server logs following message
> > repeated
> > all the time with differefnt date.
> >
> > Login succeeded for user 'domain\user1'. Connection: Trusted.
> >
> > And I couldn't find any similar log messages from the current production
> > server.
> > Any ideas? did I do something wrong when I set up new servers?
> >
> > Thanks a lot.
>
>|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.|||You are right, I set different audit trace for the two servers, but I how can
I find if I set to log successful logins '
Thanks a lot!
"Scott Morris" wrote:
> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the other
> is set to audit successful logins.
>
>|||Documentation? BOL -> Search -> "login failure"|||Thnaks, I found it.
"Scott Morris" wrote:
> Documentation? BOL -> Search -> "login failure"
>
>