servers

Hello,
I am having trouble with creating a linked server (as simple as it should
be).
My Setup:
Server A: runs under a specific account, the account can be delegated, I
have used setspn on this machine (as per BOL), I have also created a linked
server to Server B (mapping each user context as they connect)
Server B: runs under the same account (which can be delegated), I have not
used setspn as I only want people to connect remotely from Server A.
If I log onto Server A, run a query like select * from
serverb.database.owner.table everything runs fine, I can connect remotely,
now, here is the hitch:
I work on Client machine C, when I try and run the same query that worked on
server A, I get:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
What am I doing wrong?
Appreciate any insight into this
Malcolm.Mapping each user context to what? Sounds like the users are
authenticated using their Windows credentials and mapping is
set to their credentials so for their AD accounts, the
setting for:
Account is sensitive and cannot be delegated
needs to be turned off or deselected.
The server also needs to be trusted for delegation.
You also need to check your protocols and listening ports.
The books online article:
Security Account Delegation
has all of the requirements. If you are running on SP3 or
higher, make sure you are referencing the updated help
topic. You can also find it here:
http://msdn.microsoft.com/library/d...>
ity_2gmm.asp
-Sue
On Tue, 8 Nov 2005 12:21:17 -0500, "Malcolm Klotz"
<nonesuch23@.online.nospam> wrote:

>Hello,
>I am having trouble with creating a linked server (as simple as it should
>be).
>My Setup:
>Server A: runs under a specific account, the account can be delegated, I
>have used setspn on this machine (as per BOL), I have also created a linked
>server to Server B (mapping each user context as they connect)
>Server B: runs under the same account (which can be delegated), I have not
>used setspn as I only want people to connect remotely from Server A.
>If I log onto Server A, run a query like select * from
>serverb.database.owner.table everything runs fine, I can connect remotely,
>now, here is the hitch:
>I work on Client machine C, when I try and run the same query that worked o
n
>server A, I get:
>Msg 18452, Level 14, State 1, Line 1
>Login failed for user '(null)'. Reason: Not associated with a trusted SQL
>Server connection.
>What am I doing wrong?
>Appreciate any insight into this
>Malcolm.
>|||Hello,
To narrow down the issue, I suggest that you perform the following steps:
1. I assume both servers are SQL server 2000. If not, please provide more
detailed information about the linked server.
2. Set boh SQL server startup accounts to be a Domain account. Use SA to
connect to the SQL server A from the client, then check the issue again.
If it works fine, the cause is related to Security Account Delegation. If
so, please continue with the following steps:
3. Follow the steps on the following web site to set Delegation
Security Account Delegation
<http://msdn.microsoft.com/library/d...n-us/adminsql/a
d_security_2gmm.asp>
Run the "setspn -l" to verify it. For example, if you create an SPN for SQL
Server:
setspn -A MSSQLSvc/w2k3sqlsp4.test.com:1433
test\administrator
You can verify it by running
setspn -l test\administrator
It will return:
Registered ServicePrincipalNames for
CN= administrator, CN=users, DC=test, DC=com:
MSSQLSvc/envm-w2k3entsp1.test.com:1061
MSSQLSvc/w2k3sqlsp4:1433
MSSQLSvc/w2k3sqlsp4.test.com:1433
Please post here how you create the SPN for SQL Server and the results of
the "setspn -l".
4. Refer to the following article to troublshoot the issue:
http://support.microsoft.com/?id=319723#1
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you, this worked, I had used the wrong port for one of my instances.
Much appreciated.
Malcolm
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:O4UWYKR5FHA.1240@.TK2MSFTNGXA02.phx.gbl...
> Hello,
> To narrow down the issue, I suggest that you perform the following steps:
> 1. I assume both servers are SQL server 2000. If not, please provide more
> detailed information about the linked server.
> 2. Set boh SQL server startup accounts to be a Domain account. Use SA to
> connect to the SQL server A from the client, then check the issue again.
> If it works fine, the cause is related to Security Account Delegation. If
> so, please continue with the following steps:
> 3. Follow the steps on the following web site to set Delegation
> Security Account Delegation
> <[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a[/ur
l]
> d_security_2gmm.asp>
> Run the "setspn -l" to verify it. For example, if you create an SPN for
> SQL
> Server:
> setspn -A MSSQLSvc/w2k3sqlsp4.test.com:1433
> test\administrator
> You can verify it by running
> setspn -l test\administrator
> It will return:
> Registered ServicePrincipalNames for
> CN= administrator, CN=users, DC=test, DC=com:
> MSSQLSvc/envm-w2k3entsp1.test.com:1061
> MSSQLSvc/w2k3sqlsp4:1433
> MSSQLSvc/w2k3sqlsp4.test.com:1433
> Please post here how you create the SPN for SQL Server and the results of
> the "setspn -l".
> 4. Refer to the following article to troublshoot the issue:
> http://support.microsoft.com/?id=319723#1
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>

server Trouble to Oracle

I'm currently trying to establish a linked server to an Oracle
database.

Setup:
Connecting to 8x version of Oracle
Using 9i client tools (Net Manager)
SQL-Server 2000
Windows 2000

I installed the Oracle 9i client tools, and set up a Service for the
Oracle connection. Testing from the 9i client produces a successfull
connection.

I then opened SQL-Server and created a new Linked Server with the
following setup:

Name - PYR_Link
Provider - Microsoft OLE DB Provider for Oracle
Product Name - PYR
Data Source - PYR (9i Service Name)
Provider string - MSDAORA

I get the unspecific 7399 error that OLE DB provider MSDAORA reported
an error, trace 'Initialize returned 0x80004005'

I've searched through the archives, checked all of the relevant
Microsoft articles I could find, and still have no idea what is wrong.
SQL-Server reports that the provider is registered in the system, but I
can't figure out what I'm missing.

Help or a guide for troubleshooting would be much appreciated.

TimAn update - When I run sp_catalog in Query Analyzer, the error message
is more detailed. It says the provider could nor resolve the service
name. Still strange, considering the Net Manager client connects fine.|||Hi Tim, this error could occur when the oracle domain is not recognised.

Try to find out the Oracle domain (e.g. 'world') and change your linked
server to connect to that domain, like product name PYR.world and data
source PYR.world.

Good luck!
Maurits

<tim.pascoe@.cciw.ca> schreef in bericht
news:1123770210.158827.38320@.g47g2000cwa.googlegro ups.com...
> I'm currently trying to establish a linked server to an Oracle
> database.
> Setup:
> Connecting to 8x version of Oracle
> Using 9i client tools (Net Manager)
> SQL-Server 2000
> Windows 2000
> I installed the Oracle 9i client tools, and set up a Service for the
> Oracle connection. Testing from the 9i client produces a successfull
> connection.
> I then opened SQL-Server and created a new Linked Server with the
> following setup:
> Name - PYR_Link
> Provider - Microsoft OLE DB Provider for Oracle
> Product Name - PYR
> Data Source - PYR (9i Service Name)
> Provider string - MSDAORA
> I get the unspecific 7399 error that OLE DB provider MSDAORA reported
> an error, trace 'Initialize returned 0x80004005'
> I've searched through the archives, checked all of the relevant
> Microsoft articles I could find, and still have no idea what is wrong.
> SQL-Server reports that the provider is registered in the system, but I
> can't figure out what I'm missing.
> Help or a guide for troubleshooting would be much appreciated.
> Tim

server to Visual Foxpro

I am on a LAN and having trouble creating a linked server to a FoxPro
data source located on a server. When I use create a new linked server
and set the Provider String to use local directory things work fine -
that is I see a list of tables in the Tables view. If I specifiy a
directory located on a server in the provider string I see no tables.
This works:
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=c:\foxdbf.dbc;
These do not work:
(Network Drive)
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=G:\foxdbf.dbc;
(Network Path)
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=\\server\volume\foxdbf.dbc;
Similarly, when I run the following T-SQL statement it fails against a
server directory, is successful against a local directory!
Select * from openrowset('MSDASQL','Driver={Microsoft Visual FoxPro
Driver};SourceDB=G:\foxdbf.dbc;SourceType=DBF','select * from master')
Any Suggestions
Message posted via http://www.droptable.comHi Rameshwar,
I don't have a lot of experience with linked servers, but many times with
questions like this it's a permissions issue. The account that the server is
running under needs permissions to the external directory.
Also, I read your other post where you said "I get the ODBC driver error as
it cannot open the .dbc file." (BTW, you're better off keeping all your
questions in one thread.) All VFP tables for version 6 and below are
readable via the FoxPro and Visual FoxPro ODBC driver; the latest is
downloadable from http://msdn.microsoft.com/vfoxpro/downloads/updates/ .
However, new data features were added in versions 7 and above (the latest is
VFP9) and tables with those features can only be accessed via the VFP OLE DB
data provider, downloadable from the same page as above. From your question
in this post I'm assuming that you were able to read the tables, at least
locally. Is that the case?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"rameshwar elka via droptable.com" <forum@.droptable.com> wrote in message
news:9a658f3fe1834473ac99f66118dd2cbe@.SQ
droptable.com...
>I am on a LAN and having trouble creating a linked server to a FoxPro
> data source located on a server. When I use create a new linked server
> and set the Provider String to use local directory things work fine -
> that is I see a list of tables in the Tables view. If I specifiy a
> directory located on a server in the provider string I see no tables.

server to Visual Foxpro

I am on a LAN and having trouble creating a linked server to a FoxPro
data source located on a server. When I use create a new linked server
and set the Provider String to use local directory things work fine -
that is I see a list of tables in the Tables view. If I specifiy a
directory located on a server in the provider string I see no tables.
This works:
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=c:\foxdbf.dbc;
These do not work:
(Network Drive)
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=G:\foxdbf.dbc;
(Network Path)
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=\\server\volume\foxdbf.dbc;
Similarly, when I run the following T-SQL statement it fails against a
server directory, is successful against a local directory!
Select * from openrowset('MSDASQL','Driver={Microsoft Visual FoxPro
Driver};SourceDB=G:\foxdbf.dbc;SourceType=DBF','se lect * from master')
Any Suggestions
Message posted via http://www.sqlmonster.com
Hi Rameshwar,
I don't have a lot of experience with linked servers, but many times with
questions like this it's a permissions issue. The account that the server is
running under needs permissions to the external directory.
Also, I read your other post where you said "I get the ODBC driver error as
it cannot open the .dbc file." (BTW, you're better off keeping all your
questions in one thread.) All VFP tables for version 6 and below are
readable via the FoxPro and Visual FoxPro ODBC driver; the latest is
downloadable from http://msdn.microsoft.com/vfoxpro/downloads/updates/ .
However, new data features were added in versions 7 and above (the latest is
VFP9) and tables with those features can only be accessed via the VFP OLE DB
data provider, downloadable from the same page as above. From your question
in this post I'm assuming that you were able to read the tables, at least
locally. Is that the case?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"rameshwar elka via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:9a658f3fe1834473ac99f66118dd2cbe@.SQLMonster.c om...
>I am on a LAN and having trouble creating a linked server to a FoxPro
> data source located on a server. When I use create a new linked server
> and set the Provider String to use local directory things work fine -
> that is I see a list of tables in the Tables view. If I specifiy a
> directory located on a server in the provider string I see no tables.

server to Visual Foxpro

I am on a LAN and having trouble creating a linked server to a FoxPro
data source located on a server. When I use create a new linked server
and set the Provider String to use local directory things work fine -
that is I see a list of tables in the Tables view. If I specifiy a
directory located on a server in the provider string I see no tables.
This works:
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=c:\foxdbf.dbc;
These do not work:
(Network Drive)
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=G:\foxdbf.dbc;
(Network Path)
Provider string: Driver={Microsoft Visual FoxPro
Driver};SourceDB=\\server\volume\foxdbf.dbc;
Similarly, when I run the following T-SQL statement it fails against a
server directory, is successful against a local directory!
Select * from openrowset('MSDASQL','Driver={Microsoft Visual FoxPro
Driver};SourceDB=G:\foxdbf.dbc;SourceType=DBF','select * from master')
Any Suggestions
--
Message posted via http://www.sqlmonster.comHi Rameshwar,
I don't have a lot of experience with linked servers, but many times with
questions like this it's a permissions issue. The account that the server is
running under needs permissions to the external directory.
Also, I read your other post where you said "I get the ODBC driver error as
it cannot open the .dbc file." (BTW, you're better off keeping all your
questions in one thread.) All VFP tables for version 6 and below are
readable via the FoxPro and Visual FoxPro ODBC driver; the latest is
downloadable from http://msdn.microsoft.com/vfoxpro/downloads/updates/ .
However, new data features were added in versions 7 and above (the latest is
VFP9) and tables with those features can only be accessed via the VFP OLE DB
data provider, downloadable from the same page as above. From your question
in this post I'm assuming that you were able to read the tables, at least
locally. Is that the case?
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"rameshwar elka via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:9a658f3fe1834473ac99f66118dd2cbe@.SQLMonster.com...
>I am on a LAN and having trouble creating a linked server to a FoxPro
> data source located on a server. When I use create a new linked server
> and set the Provider String to use local directory things work fine -
> that is I see a list of tables in the Tables view. If I specifiy a
> directory located on a server in the provider string I see no tables.