DATA ACCESS

The network admins did some OS security patches (and who
knows what else) and today we're getting the following
error on a few established processes:
Microsoft OLE DB Provider for SQL Server -2147217900
Server 'SERVER123' is not configured for DATA ACCESS.
We believe this is a cross server issue. Anyway, this
error msg looks familiar, but I can't quite place it.
Any help would be much appreciated.
Joe,
Try..
exec sp_serveroption SERVER123, 'data access', 'true'
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>
|||Hi,
Execute the below procedure with correct linked server name.
sp_serveroption 'Linked_server_name','data access',true
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>
|||Before I run this, I've got a question:
1. I've already got a link server set up. Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Joe,
>Try..
>exec sp_serveroption SERVER123, 'data access', 'true'
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>
>.
>
|||Before I run this, I've got a few questions:
1. I've already got a linked server set up and it seems
to be working for reads at least (but the developers are
claiming it's not working for updates). Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Hi,
>Execute the below procedure with correct linked server
name.
>sp_serveroption 'Linked_server_name','data access',true
>
>Thanks
>Hari
>MCDBA
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>
>.
>
|||Hi,
1. I've already got a link server set up. Does this just "enable" that
linked server?
Enables and disables a linked server for distributed query access.
2. If I am running this on serverA, do I put in 'serverB' for the first
argument, i.e. the linked server that I am trying to connect to?
You have to put SERVERB (Which is the remote server)
3. How could this get set to false? I certainly didn't do it! Have you
ever seen MS installs hose this up?
No Idea
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> message
|||Joe,
#1.Correct. 'True' enables the linked server for data access.
#2.Yes.
#3.How it was set to false, I dont know.May be, one of those patches did
that.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> message

DATA ACCESS

The network admins did some OS security patches (and who
knows what else) and today we're getting the following
error on a few established processes:
Microsoft OLE DB Provider for SQL Server -2147217900
Server 'SERVER123' is not configured for DATA ACCESS.
We believe this is a cross server issue. Anyway, this
error msg looks familiar, but I can't quite place it.
Any help would be much appreciated.Joe,
Try..
exec sp_serveroption SERVER123, 'data access', 'true'
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Hi,
Execute the below procedure with correct linked server name.
sp_serveroption 'Linked_server_name','data access',true
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Before I run this, I've got a question:
1. I've already got a link server set up. Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?
>--Original Message--
>Joe,
>Try..
>exec sp_serveroption SERVER123, 'data access', 'true'
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>> The network admins did some OS security patches (and who
>> knows what else) and today we're getting the following
>> error on a few established processes:
>> Microsoft OLE DB Provider for SQL Server -2147217900
>> Server 'SERVER123' is not configured for DATA ACCESS.
>> We believe this is a cross server issue. Anyway, this
>> error msg looks familiar, but I can't quite place it.
>> Any help would be much appreciated.
>
>.
>|||Before I run this, I've got a few questions:
1. I've already got a linked server set up and it seems
to be working for reads at least (but the developers are
claiming it's not working for updates). Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?
>--Original Message--
>Hi,
>Execute the below procedure with correct linked server
name.
>sp_serveroption 'Linked_server_name','data access',true
>
>Thanks
>Hari
>MCDBA
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
>> The network admins did some OS security patches (and who
>> knows what else) and today we're getting the following
>> error on a few established processes:
>> Microsoft OLE DB Provider for SQL Server -2147217900
>> Server 'SERVER123' is not configured for DATA ACCESS.
>> We believe this is a cross server issue. Anyway, this
>> error msg looks familiar, but I can't quite place it.
>> Any help would be much appreciated.
>
>.
>|||Hi,
1. I've already got a link server set up. Does this just "enable" that
linked server?
Enables and disables a linked server for distributed query access.
2. If I am running this on serverA, do I put in 'serverB' for the first
argument, i.e. the linked server that I am trying to connect to?
You have to put SERVERB (Which is the remote server)
3. How could this get set to false? I certainly didn't do it! Have you
ever seen MS installs hose this up?
No Idea
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> >--Original Message--
> >Joe,
> >
> >Try..
> >
> >exec sp_serveroption SERVER123, 'data access', 'true'
> >
> >--
> >Dinesh
> >SQL Server MVP
> >--
> >--
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> >> The network admins did some OS security patches (and who
> >> knows what else) and today we're getting the following
> >> error on a few established processes:
> >>
> >> Microsoft OLE DB Provider for SQL Server -2147217900
> >> Server 'SERVER123' is not configured for DATA ACCESS.
> >>
> >> We believe this is a cross server issue. Anyway, this
> >> error msg looks familiar, but I can't quite place it.
> >>
> >> Any help would be much appreciated.
> >>
> >
> >
> >.
> >|||Joe,
#1.Correct. 'True' enables the linked server for data access.
#2.Yes.
#3.How it was set to false, I dont know.May be, one of those patches did
that.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx.gbl...
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
> >--Original Message--
> >Joe,
> >
> >Try..
> >
> >exec sp_serveroption SERVER123, 'data access', 'true'
> >
> >--
> >Dinesh
> >SQL Server MVP
> >--
> >--
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1d0e801c42308$ddd0b690$a401280a@.phx.gbl...
> >> The network admins did some OS security patches (and who
> >> knows what else) and today we're getting the following
> >> error on a few established processes:
> >>
> >> Microsoft OLE DB Provider for SQL Server -2147217900
> >> Server 'SERVER123' is not configured for DATA ACCESS.
> >>
> >> We believe this is a cross server issue. Anyway, this
> >> error msg looks familiar, but I can't quite place it.
> >>
> >> Any help would be much appreciated.
> >>
> >
> >
> >.
> >

DATA ACCESS

The network admins did some OS security patches (and who
knows what else) and today we're getting the following
error on a few established processes:
Microsoft OLE DB Provider for SQL Server -2147217900
Server 'SERVER123' is not configured for DATA ACCESS.
We believe this is a cross server issue. Anyway, this
error msg looks familiar, but I can't quite place it.
Any help would be much appreciated.Joe,
Try..
exec sp_serveroption SERVER123, 'data access', 'true'
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Hi,
Execute the below procedure with correct linked server name.
sp_serveroption 'Linked_server_name','data access',true
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
> The network admins did some OS security patches (and who
> knows what else) and today we're getting the following
> error on a few established processes:
> Microsoft OLE DB Provider for SQL Server -2147217900
> Server 'SERVER123' is not configured for DATA ACCESS.
> We believe this is a cross server issue. Anyway, this
> error msg looks familiar, but I can't quite place it.
> Any help would be much appreciated.
>|||Before I run this, I've got a question:
1. I've already got a link server set up. Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Joe,
>Try..
>exec sp_serveroption SERVER123, 'data access', 'true'
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
>
>.
>|||Before I run this, I've got a few questions:
1. I've already got a linked server set up and it seems
to be working for reads at least (but the developers are
claiming it's not working for updates). Does this
just "enable" that linked server?
2. If I am running this on serverA, do I put in 'serverB'
for the first argument, i.e. the linked server that I am
trying to connect to?
3. How could this get set to false? I certainly didn't
do it! Have you ever seen MS installs hose this up?

>--Original Message--
>Hi,
>Execute the below procedure with correct linked server
name.
>sp_serveroption 'Linked_server_name','data access',true
>
>Thanks
>Hari
>MCDBA
>"JoeMan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:1d0e801c42308$ddd0b690$a401280a@.phx
.gbl...
>
>.
>|||Hi,
1. I've already got a link server set up. Does this just "enable" that
linked server?
Enables and disables a linked server for distributed query access.
2. If I am running this on serverA, do I put in 'serverB' for the first
argument, i.e. the linked server that I am trying to connect to?
You have to put SERVERB (Which is the remote server)
3. How could this get set to false? I certainly didn't do it! Have you
ever seen MS installs hose this up?
No Idea
Thanks
Hari
MCDBA
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx
.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
>
> message|||Joe,
#1.Correct. 'True' enables the linked server for data access.
#2.Yes.
#3.How it was set to false, I dont know.May be, one of those patches did
that.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"JoeMan" <anonymous@.discussions.microsoft.com> wrote in message
news:188d201c4230b$6b192940$a001280a@.phx
.gbl...[vbcol=seagreen]
> Before I run this, I've got a question:
> 1. I've already got a link server set up. Does this
> just "enable" that linked server?
> 2. If I am running this on serverA, do I put in 'serverB'
> for the first argument, i.e. the linked server that I am
> trying to connect to?
> 3. How could this get set to false? I certainly didn't
> do it! Have you ever seen MS installs hose this up?
>
> message

Customizing Security

Hello,
I was wondering if its possible to have database user authenticate
against an external database or directory server? The client has a
centralized repository system that they would like all systems to
authenticate against. If this is feasible, can offer any suggestions
on how we can achieve this?
Thanks in advance
TomHi Tom,
Are you asking about central authentication using SQL Security or
Windows Authentication?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I have a similar situation and need to plan for centralized security around
Windows/AD. Furthermore I need to leverage the AD groups/roles in the
architecture. ANy insite or direction would me appriciated.
"Kevin McDonnell [MSFT]" wrote:

> Hi Tom,
> Are you asking about central authentication using SQL Security or
> Windows Authentication?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Previous post:
I have a similar situation and need to plan for centralized security around
Windows/AD. Furthermore I need to leverage the AD groups/roles in the
architecture. ANy insite or direction would me appriciated.
Reply;
We use Domain based groups or local groups to base our security on. We can
publish objects to
Active Directory, but our security is not tied to AD like Exchange 2000 for
example. We can authenticate via
Trusted Connections using NTLM or Kerberos. Kerberos based authentication
requires that the Server Principal Name is
set for SQL. See Books Online for the example.
Our Security Model is discussed here:
http://www.microsoft.com/technet/pr...n/sp3sec01.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.