"not a trusted connection", means what EXACTLY?

There's no explaination of this error on MS or any of the documentation that
I can find. Yes, I know some of the cases that cause it, but that's a
different issue entirely.
I'm getting this error on a new SQL Server install. All of the permissions
are copied from the older server. About 2/3rds of the machines in the office
can log in fine, but the other 1/3rd return this error. There is no obvious
difference between the machines. We use Windows Authentication for everything.
So, does this error mean "I cannot verify you with the domain controller"?
Or perhaps "your domain credentials do no allow you to log in"? Or something
else entirely? Depending on the exact nature of the error, the steps to
correct it will be very different.
This part of the error message mean that there is no trust (or the trust
cannot be confirmed) between the account thatt is logging in and the SQL
Server machine. The first part of the message is the most important. What
is the complete message that the users are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||"Rand Boyd [MSFT]" wrote:

> Server machine. The first part of the message is the most important. What
> is the complete message that the users are getting?
SQLState '28000'
SQL Server Error 18452
[...] Login failed for user '(null)'. Reason: not associated with a trusted
SQL Server connection.
Thanks!
|||Are you using a .NET application?
Sasan Saidi,
MSc in CS, MCSE (NT4), IBM Certified MQ Administrator
Senior DBA
Brascan Business Services
"Maury Markowitz" wrote:

> "Rand Boyd [MSFT]" wrote:
>
> SQLState '28000'
> SQL Server Error 18452
> [...] Login failed for user '(null)'. Reason: not associated with a trusted
> SQL Server connection.
> Thanks!
>
|||"Sasan Saidi" wrote:

> Are you using a .NET application?
No. I'm simply trying to set up the DSN in the Data Sources (ODBC) control
panel.
|||Has the user logged onto the domain? Does the user account have an
associated SQL login?
Jeff
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:F095B40F-78FB-4096-89CA-7E9E1F9E0580@.microsoft.com...
> "Sasan Saidi" wrote:
>
> No. I'm simply trying to set up the DSN in the Data Sources (ODBC) control
> panel.
|||My guess is that the SQL Server is setup to allow only Windows logins and you try to login using a
SQL server login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in message
news:BAD981FB-7BB8-46BB-A297-80DE6CF7B543@.microsoft.com...
> "Rand Boyd [MSFT]" wrote:
>
> SQLState '28000'
> SQL Server Error 18452
> [...] Login failed for user '(null)'. Reason: not associated with a trusted
> SQL Server connection.
> Thanks!
>

"not a trusted connection", means what EXACTLY?

There's no explaination of this error on MS or any of the documentation that
I can find. Yes, I know some of the cases that cause it, but that's a
different issue entirely.
I'm getting this error on a new SQL Server install. All of the permissions
are copied from the older server. About 2/3rds of the machines in the office
can log in fine, but the other 1/3rd return this error. There is no obvious
difference between the machines. We use Windows Authentication for everythin
g.
So, does this error mean "I cannot verify you with the domain controller"?
Or perhaps "your domain credentials do no allow you to log in"? Or something
else entirely? Depending on the exact nature of the error, the steps to
correct it will be very different.This part of the error message mean that there is no trust (or the trust
cannot be confirmed) between the account thatt is logging in and the SQL
Server machine. The first part of the message is the most important. What
is the complete message that the users are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||"Rand Boyd [MSFT]" wrote:

> Server machine. The first part of the message is the most important. What
> is the complete message that the users are getting?
SQLState '28000'
SQL Server Error 18452
[...] Login failed for user '(null)'. Reason: not associated with a trus
ted
SQL Server connection.
Thanks!|||Are you using a .NET application?
Sasan Saidi,
MSc in CS, MCSE (NT4), IBM Certified MQ Administrator
Senior DBA
Brascan Business Services
"Maury Markowitz" wrote:

> "Rand Boyd [MSFT]" wrote:
>
> SQLState '28000'
> SQL Server Error 18452
> [...] Login failed for user '(null)'. Reason: not associated with a tr
usted
> SQL Server connection.
> Thanks!
>|||"Sasan Saidi" wrote:

> Are you using a .NET application?
No. I'm simply trying to set up the DSN in the Data Sources (ODBC) control
panel.|||Has the user logged onto the domain? Does the user account have an
associated SQL login?
Jeff
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:F095B40F-78FB-4096-89CA-7E9E1F9E0580@.microsoft.com...
> "Sasan Saidi" wrote:
>
> No. I'm simply trying to set up the DSN in the Data Sources (ODBC) control
> panel.|||My guess is that the SQL Server is setup to allow only Windows logins and yo
u try to login using a
SQL server login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in messag
e
news:BAD981FB-7BB8-46BB-A297-80DE6CF7B543@.microsoft.com...
> "Rand Boyd [MSFT]" wrote:
>
> SQLState '28000'
> SQL Server Error 18452
> [...] Login failed for user '(null)'. Reason: not associated with a tr
usted
> SQL Server connection.
> Thanks!
>

"not a trusted connection", means what EXACTLY?

There's no explaination of this error on MS or any of the documentation that
I can find. Yes, I know some of the cases that cause it, but that's a
different issue entirely.
I'm getting this error on a new SQL Server install. All of the permissions
are copied from the older server. About 2/3rds of the machines in the office
can log in fine, but the other 1/3rd return this error. There is no obvious
difference between the machines. We use Windows Authentication for everything.
So, does this error mean "I cannot verify you with the domain controller"?
Or perhaps "your domain credentials do no allow you to log in"? Or something
else entirely? Depending on the exact nature of the error, the steps to
correct it will be very different.This part of the error message mean that there is no trust (or the trust
cannot be confirmed) between the account thatt is logging in and the SQL
Server machine. The first part of the message is the most important. What
is the complete message that the users are getting?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||"Rand Boyd [MSFT]" wrote:
> Server machine. The first part of the message is the most important. What
> is the complete message that the users are getting?
SQLState '28000'
SQL Server Error 18452
[...] Login failed for user '(null)'. Reason: not associated with a trusted
SQL Server connection.
Thanks!|||Are you using a .NET application?
--
Sasan Saidi,
MSc in CS, MCSE (NT4), IBM Certified MQ Administrator
Senior DBA
Brascan Business Services
"Maury Markowitz" wrote:
> "Rand Boyd [MSFT]" wrote:
> > Server machine. The first part of the message is the most important. What
> > is the complete message that the users are getting?
> SQLState '28000'
> SQL Server Error 18452
> [...] Login failed for user '(null)'. Reason: not associated with a trusted
> SQL Server connection.
> Thanks!
>|||"Sasan Saidi" wrote:
> Are you using a .NET application?
No. I'm simply trying to set up the DSN in the Data Sources (ODBC) control
panel.|||Has the user logged onto the domain? Does the user account have an
associated SQL login?
Jeff
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:F095B40F-78FB-4096-89CA-7E9E1F9E0580@.microsoft.com...
> "Sasan Saidi" wrote:
> > Are you using a .NET application?
> No. I'm simply trying to set up the DSN in the Data Sources (ODBC) control
> panel.|||My guess is that the SQL Server is setup to allow only Windows logins and you try to login using a
SQL server login.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in message
news:BAD981FB-7BB8-46BB-A297-80DE6CF7B543@.microsoft.com...
> "Rand Boyd [MSFT]" wrote:
> > Server machine. The first part of the message is the most important. What
> > is the complete message that the users are getting?
> SQLState '28000'
> SQL Server Error 18452
> [...] Login failed for user '(null)'. Reason: not associated with a trusted
> SQL Server connection.
> Thanks!
>

"No more data available to read" error

Hi All
"No more data available to read" error is thrown by database driver when
connections max out on SQL Server. Does any one know what this means and ho
w
can i resolve this issue? An application developed in Java uses SQL Server
for data storage. Thank you in advance.This is not a sql server error message. It is an error message that is
raised by the jdbc driver itself.
It could be caused by several things that I know of, but each is sort of
application dependent.
1) Thread contention (non-thread safe) code within the app. 2 thread
competing for the same data in memory on the server
2) BLOB types, I read a bit that having BLOB types within your result set
can lead to this type of problem
3) Trying to scroll backward, or through a forward-only result set for a
second time.
I'd recommend contacting the JDBC driver manufacturer, as they would have
more details. I would be surprised if it was really related to not enough d
b
connections.
Sorry I can't be of more help.
--
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"MittyKom" wrote:

> Hi All
> "No more data available to read" error is thrown by database driver when
> connections max out on SQL Server. Does any one know what this means and
how
> can i resolve this issue? An application developed in Java uses SQL Server
> for data storage. Thank you in advance.
>

"New transaction is not allowed because there are other threads running in the session." -

That is a SqlException I got at a...

at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()

Anyone an idea what THAT means? How do I cause it? How can I work around it?

I think you probably have an open connection somewhere. See if you can start the transaction after you close the connection.|||

I have about 25 open connections. Because that is - quess what - an ASP.NET application.

Once connection per page.

And every page has - one thread. No multi threading at all.

Plus it is legal for a thread to have multiple open connections.

|||

Have you enabled Multiple Active Resultsets (MARS)?

For connections with MARS enabled, manual transactions started via TSQL BEGIN TRAN must end (COMMIT or ROLLBACK) within the same scope that started the transaction

If your issue meets the the aboving conditions, you can try this work aroud:

To begin tansactions that are not required to be scoped under
MARS-enabled connections, use the client driver API constructs to begin and end transactions. If existing code relies on BEGIN TRAN operations without
corresponding COMMIT/ROLLBACK, MARS can be turned off until the application can be modified to use the client driver transaction APIs

|||Nope, no MARS. Actually that was (not is) old SQL Server 2000 code from .NET 1.1 that was traansported over. Worked flawlessly under .NET 1.1, and looks flawless to me still.

multiple schema report

tnx in advance for any help.
I have a multiple enterprise system in which every enterprise is being
modeled as a schema in the DB. This means that schemas are identical in
structure and when you connect to one schema, you are connecting to one
logical enterprise.
Now, I need to write a bunch of reports with the ability to connect
indiferently to on Enterprise or another (the user selects against which
Enterprise he wants to run the report to).
RS allows to define one or more Datasets for every report. But that has to
be an SQL instruction with schema qualifying "hardcoded" for every table you
use.
I've thought about dynamic SQL inside a stored procedure, and the enterprise
(schema) being passed as a parameter, but that's not such an elegant
solution.
So any suggestion will be gratefully welcome...
regardsIn RS 2005 you can base a data source on an expression. This sounds like
your scenario is exactly what this feature was put in for.
From Books Online:
Data Source Expressions
You can put an expression into a connection string to allow users to select
the data source at run time. For example, suppose a multinational firm has
data servers in several countries. With an expression-based connection
string, a user who is running a sales report can select a data source for a
particular country before running the report.
The following example illustrates the use of a data source expression in a
SQL Server connection string. The example assumes you have created a report
parameter named ServerName:
Copy Code
="data source=" & Parameters!ServerName.Value & ";initial
catalog=AdventureWorks
Data source expressions are processed at run time or when a report is
previewed. The expression must be written in Visual Basic. Use the following
guidelines when defining a data source expression:
a.. Design the report using a static connection string. A static
connection string refers to a connection string that is not set through an
expression (for example, when you follow the steps for creating a
report-specific or shared data source, you are defining a static connection
string). Using a static connection string allows you to connect to the data
source in Report Designer so that you can get the query results you need to
create the report.
b.. When defining the data source connection, do not use a shared data
source. You cannot use a data source expression in a shared data source. You
must define a report-specific data source for the report.
c.. Specify credentials separately from the connection string. You can use
stored credentials, prompted credentials, or integrated security.
d.. Add a report parameter to specify a data source. For parameter values,
you can either provide a static list of available values (in this case, the
available values should be data sources you can use with the report) or
define a query that retrieves a list of data sources at run time.
e.. Be sure that the list of data sources shares the same database schema.
All report design begins with schema information. If there is a mismatch
between the schema used to define the report and the actual schema used by
the report at run time, the report might not run.
f.. Before publishing the report, replace the static connection string
with an expression. Wait until you are finished designing the report before
you replace the static connection string with an expression. Once you use an
expression, you cannot execute the query in Report Designer. Furthermore,
the field list in the Datasets window and the Parameters list will not
update automatically.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Edmundo J. Davila" <edavila@.monisa.com> wrote in message
news:19A56F20-96FE-4751-846F-9E8B2D5CF689@.microsoft.com...
> tnx in advance for any help.
> I have a multiple enterprise system in which every enterprise is being
> modeled as a schema in the DB. This means that schemas are identical in
> structure and when you connect to one schema, you are connecting to one
> logical enterprise.
> Now, I need to write a bunch of reports with the ability to connect
> indiferently to on Enterprise or another (the user selects against which
> Enterprise he wants to run the report to).
> RS allows to define one or more Datasets for every report. But that has to
> be an SQL instruction with schema qualifying "hardcoded" for every table
> you
> use.
> I've thought about dynamic SQL inside a stored procedure, and the
> enterprise
> (schema) being passed as a parameter, but that's not such an elegant
> solution.
> So any suggestion will be gratefully welcome...
> regards
>
begin 666 copycode.gif
M1TE&.#EA#P`/`.9F`).BM[+"V*[$\(&NY:Z_U'.AWER,VIBKQBE4JIFLQ_S]
M_LO/U)*P[8JN_,73\JFXSF2%R=;>[/;Y_>OO]BM7L6Z<VB)&CZ:]["!!AJ"Y
M[VB7U9RPSM+;\9>FNZ.RR"-(EOGZ_")%CIRKP;+)\*[0_Z^^U#5EQ2E4K*FY
MSX*?V,_9YM+6W9JMRFZ7YV".Y\S7[-'ZINOS)"JX+K:_^KO^R5,FR=0HIJN
MRI:FN^;J\^#F\25-G25*F+_+W=+>\,#*X,+.Y/7V^[K%U/O]_B-'DG^G\_#T
M^\?2X7.2T4=NNI_%^B%#B=OD]_?X^Z_#[?#R^)>IQ*K![XZX\"%#BIRUYZ*Q
MQV:"I?#S^*.RQYJNS*O"[]/>]55YP2I7LW*:ZH6GZR=0I%MRC[[.\#5)8U&#
MT?_______P``````````````````````````````````````````````````
M`````````````````````````````````````````````````"'Y! $``&8`
M+ `````/``\```>?@.&:"@.X2%AH>"`0$$! \>*X@.!99-E558+AR64"CA"89B%
M*&4S)#X``EI1&0P,+X)8DR!/.0*495\F0&8B94I2`P47MEXC%#\="D$3.A%4
M90T-'"Y=)V `3< 5&C*41DP.63L`5S J1STI944M!F1D-SP`8_/S2&5#-%MB
F3@.E$AA!EVKDC<R"$(2X2-L1@.D> `E"6&DB! 8*/&!PM3, 0"`#L`
`
end|||Hello Edmundo,
Have you got the the problem sorted? I am having the same trouble. In my
case, I need to select a db schema at the run time. Here are methods I've
tried:
1. create a parameter to contain the db name. Add in the ODBC connection
string "database=Parameters!db_name.Value", this doesnt work. The alert
"database-Parameters!db_name.Value doesn't exist" turns up.
2. delete the "database = XXX" part from the connection string, so no
specific database in the DB server will be connected, a connection to the DB
server itself is established. create a parameter to contain the db name. in
the query use ?.attr_name=XXX. By doing this, I expect the parameter can
specify the DB name at the run time. this doesnt work either.
So if you have the solution, could you please post it up. It'll be really
appreciated!
cheers,
P
"Bruce L-C [MVP]" wrote:
> In RS 2005 you can base a data source on an expression. This sounds like
> your scenario is exactly what this feature was put in for.
> From Books Online:
> Data Source Expressions
> You can put an expression into a connection string to allow users to select
> the data source at run time. For example, suppose a multinational firm has
> data servers in several countries. With an expression-based connection
> string, a user who is running a sales report can select a data source for a
> particular country before running the report.
> The following example illustrates the use of a data source expression in a
> SQL Server connection string. The example assumes you have created a report
> parameter named ServerName:
> Copy Code
> ="data source=" & Parameters!ServerName.Value & ";initial
> catalog=AdventureWorks
> Data source expressions are processed at run time or when a report is
> previewed. The expression must be written in Visual Basic. Use the following
> guidelines when defining a data source expression:
> a.. Design the report using a static connection string. A static
> connection string refers to a connection string that is not set through an
> expression (for example, when you follow the steps for creating a
> report-specific or shared data source, you are defining a static connection
> string). Using a static connection string allows you to connect to the data
> source in Report Designer so that you can get the query results you need to
> create the report.
>
> b.. When defining the data source connection, do not use a shared data
> source. You cannot use a data source expression in a shared data source. You
> must define a report-specific data source for the report.
>
> c.. Specify credentials separately from the connection string. You can use
> stored credentials, prompted credentials, or integrated security.
>
> d.. Add a report parameter to specify a data source. For parameter values,
> you can either provide a static list of available values (in this case, the
> available values should be data sources you can use with the report) or
> define a query that retrieves a list of data sources at run time.
>
> e.. Be sure that the list of data sources shares the same database schema.
> All report design begins with schema information. If there is a mismatch
> between the schema used to define the report and the actual schema used by
> the report at run time, the report might not run.
>
> f.. Before publishing the report, replace the static connection string
> with an expression. Wait until you are finished designing the report before
> you replace the static connection string with an expression. Once you use an
> expression, you cannot execute the query in Report Designer. Furthermore,
> the field list in the Datasets window and the Parameters list will not
> update automatically.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Edmundo J. Davila" <edavila@.monisa.com> wrote in message
> news:19A56F20-96FE-4751-846F-9E8B2D5CF689@.microsoft.com...
> > tnx in advance for any help.
> >
> > I have a multiple enterprise system in which every enterprise is being
> > modeled as a schema in the DB. This means that schemas are identical in
> > structure and when you connect to one schema, you are connecting to one
> > logical enterprise.
> >
> > Now, I need to write a bunch of reports with the ability to connect
> > indiferently to on Enterprise or another (the user selects against which
> > Enterprise he wants to run the report to).
> >
> > RS allows to define one or more Datasets for every report. But that has to
> > be an SQL instruction with schema qualifying "hardcoded" for every table
> > you
> > use.
> >
> > I've thought about dynamic SQL inside a stored procedure, and the
> > enterprise
> > (schema) being passed as a parameter, but that's not such an elegant
> > solution.
> >
> > So any suggestion will be gratefully welcome...
> >
> > regards
> >
>
>