"Trusted for delegation".

MSSQL2K5
SP1
Im reading in BOL regarding Linked Servers:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/9e302c29-639d-4509-ba1e-cf45
2582c5c3.htm
and it says:
Requirements for the First/Middle Server (SQLSERVER1)
a.. The server must have an SPN registered by the domain administrator.
b.. The account under which SQL Server is running must be trusted for
delegation.
What is "trusted for delegation"? Where do I configure it?
TIA, ChrisRChrisR wrote:
> What is "trusted for delegation"? Where do I configure it?
This is a user object setting in Active Directory, usually set with
Active Directory Users & Computers.
http://support.microsoft.com/kb/305144/en-us|||Cool, thanks.
<tom.freedman@.gmail.com> wrote in message
news:1154456842.034250.326350@.i42g2000cwa.googlegroups.com...
> ChrisR wrote:
> This is a user object setting in Active Directory, usually set with
> Active Directory Users & Computers.
> http://support.microsoft.com/kb/305144/en-us
>

"Open Table Window" is read-only under SQL Query Analyzer

I have installed SQL Server 2000 with option "Client Tools Only"
I try to edit data using SQL Query Analyzer with Trusted Connection. I click on 'Open' of right-click on table objects. A "Open Table Window" is opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit data.
I am trying to edit data using Server Explorer under Microsoft .NET with Trusted Connection. It works!!!
Help, Help!
Maybe the table does not have a Primary Key, check this first.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Happy Programmer" <anonymous@.discussions.microsoft.com> wrote in message
news:9D59D138-BFAE-4CAB-A2C1-FF535B42F2C7@.microsoft.com...
> I have installed SQL Server 2000 with option "Client Tools Only"
> I try to edit data using SQL Query Analyzer with Trusted Connection. I
click on 'Open' of right-click on table objects. A "Open Table Window" is
opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit
data.
> I am trying to edit data using Server Explorer under Microsoft .NET with
Trusted Connection. It works!!!
> Help, Help!
|||I believe that you will only be able to modify data from the Open Table
function in Query Analyzer if the table has a primary key or unique
constraint or a unique index.
Steve Kass
Drew University
Happy Programmer wrote:

>I have installed SQL Server 2000 with option "Client Tools Only"
>I try to edit data using SQL Query Analyzer with Trusted Connection. I click on 'Open' of right-click on table objects. A "Open Table Window" is opened as read-only!!! "Add" and "Delete" are grey out!! I can't edit data.
>I am trying to edit data using Server Explorer under Microsoft .NET with Trusted Connection. It works!!!
>Help, Help!
>
|||I've tried it. It is able to modify if the table has primary key or unique index.
But is able to edit data using Server Explorer under Microsoft .NET with Trusted Connection even it has not any key or index.
Anyway, thanks a lot~!

"Not associated with a trusted SQL Server connection"

Hello,
Having some trouble here with a CRM installation, and I think there is
something wrong with our SQL Server, since we got the exact same issue with
another application.
Anyhow, we got a SQL Server 2000 SP4. Right now we are running databases for
Microsoft Navision 4.0 and a .NET webshop, and it works fine. Installed a new
server the otherday (Windows Server 2003 SP1) for Microosoft CRM, and want
the CRM-databases on our current SQL Server.
During installation we get the following error:
=====================
Microsoft CRM 3.0 Server Setup
Activating SQL Server Reporting Services failed.
Setup failed to validate specified Reporting Services Report Server
http://CRM1/ReportServer. Error: The report server cannot open a connection
to the report server database. A connection to the database is required for
all requests and processing.
=====================
I press "Ignore" just to finish the installation, and it continues. After
that, when trying to connect to http://crm1 to access the system (from the
CRM1 server), it just gives the following .NET-error:
=========================
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
=========================
Been Googleing and testing alot of stuff, but can't find the solution. I am
not that great on SQL Server, so we got a few other people to look at it, but
it just doesn't work.
Anyone know what to do, I'm clueless...
Problem solved.
On the SQL Server, in "local security policy" --> "access this computer from
the network" was only "domain/domain users" specified. I added CRM1 (the
server), and it started to work.
"joup" wrote:

> Hello,
> Having some trouble here with a CRM installation, and I think there is
> something wrong with our SQL Server, since we got the exact same issue with
> another application.
> Anyhow, we got a SQL Server 2000 SP4. Right now we are running databases for
> Microsoft Navision 4.0 and a .NET webshop, and it works fine. Installed a new
> server the otherday (Windows Server 2003 SP1) for Microosoft CRM, and want
> the CRM-databases on our current SQL Server.
> During installation we get the following error:
> =====================
> Microsoft CRM 3.0 Server Setup
> --
> Activating SQL Server Reporting Services failed.
> Setup failed to validate specified Reporting Services Report Server
> http://CRM1/ReportServer. Error: The report server cannot open a connection
> to the report server database. A connection to the database is required for
> all requests and processing.
> =====================
> I press "Ignore" just to finish the installation, and it continues. After
> that, when trying to connect to http://crm1 to access the system (from the
> CRM1 server), it just gives the following .NET-error:
> =========================
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> =========================
> Been Googleing and testing alot of stuff, but can't find the solution. I am
> not that great on SQL Server, so we got a few other people to look at it, but
> it just doesn't work.
> Anyone know what to do, I'm clueless...

"Not associated with a trusted SQL Server connection"

Hello,
Having some trouble here with a CRM installation, and I think there is
something wrong with our SQL Server, since we got the exact same issue with
another application.
Anyhow, we got a SQL Server 2000 SP4. Right now we are running databases for
Microsoft Navision 4.0 and a .NET webshop, and it works fine. Installed a ne
w
server the otherday (Windows Server 2003 SP1) for Microosoft CRM, and want
the CRM-databases on our current SQL Server.
During installation we get the following error:
=====================
Microsoft CRM 3.0 Server Setup
--
Activating SQL Server Reporting Services failed.
Setup failed to validate specified Reporting Services Report Server
http://CRM1/ReportServer. Error: The report server cannot open a connection
to the report server database. A connection to the database is required for
all requests and processing.
=====================
I press "Ignore" just to finish the installation, and it continues. After
that, when trying to connect to http://crm1 to access the system (from the
CRM1 server), it just gives the following .NET-error:
=========================
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
=========================
Been Googleing and testing alot of stuff, but can't find the solution. I am
not that great on SQL Server, so we got a few other people to look at it, bu
t
it just doesn't work.
Anyone know what to do, I'm clueless...Problem solved.
On the SQL Server, in "local security policy" --> "access this computer from
the network" was only "domain/domain users" specified. I added CRM1 (the
server), and it started to work.
"joup" wrote:

> Hello,
> Having some trouble here with a CRM installation, and I think there is
> something wrong with our SQL Server, since we got the exact same issue wit
h
> another application.
> Anyhow, we got a SQL Server 2000 SP4. Right now we are running databases f
or
> Microsoft Navision 4.0 and a .NET webshop, and it works fine. Installed a
new
> server the otherday (Windows Server 2003 SP1) for Microosoft CRM, and want
> the CRM-databases on our current SQL Server.
> During installation we get the following error:
> =====================
> Microsoft CRM 3.0 Server Setup
> --
> Activating SQL Server Reporting Services failed.
> Setup failed to validate specified Reporting Services Report Server
> http://CRM1/ReportServer. Error: The report server cannot open a connectio
n
> to the report server database. A connection to the database is required fo
r
> all requests and processing.
> =====================
> I press "Ignore" just to finish the installation, and it continues. After
> that, when trying to connect to http://crm1 to access the system (from the
> CRM1 server), it just gives the following .NET-error:
> =========================
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> =========================
> Been Googleing and testing alot of stuff, but can't find the solution. I a
m
> not that great on SQL Server, so we got a few other people to look at it,
but
> it just doesn't work.
> Anyone know what to do, I'm clueless...

"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!
>