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

DAC not supported.

SQL2K5
SP1
Howdy all. I'm trying to open up Dedicated Admins Connection in Management
Studio and getting "DAC's are not supported. (Object Explorer)"
Any idea's?
TIA, ChrisRYou may need to enable the sp_configure option 'remote admin connections'.
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:E3F6FEC3-CFEC-4494-9742-B6AC1BA02242@.microsoft.com...
> SQL2K5
> SP1
> Howdy all. I'm trying to open up Dedicated Admins Connection in Management
> Studio and getting "DAC's are not supported. (Object Explorer)"
> Any idea's?
> TIA, ChrisR|||DAC is not supported for the object explorer, only for the query window.
--
HTH
Kalen Delaney, SQL Server MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:E3F6FEC3-CFEC-4494-9742-B6AC1BA02242@.microsoft.com...
> SQL2K5
> SP1
> Howdy all. I'm trying to open up Dedicated Admins Connection in Management
> Studio and getting "DAC's are not supported. (Object Explorer)"
> Any idea's?
> TIA, ChrisR|||Hi,
you may check my screencasts on my site, one topic is about enabling
DAC.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Thanks Kalen, that was it.
"Kalen Delaney" wrote:
> DAC is not supported for the object explorer, only for the query window.
> --
> HTH
> Kalen Delaney, SQL Server MVP
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:E3F6FEC3-CFEC-4494-9742-B6AC1BA02242@.microsoft.com...
> > SQL2K5
> > SP1
> >
> > Howdy all. I'm trying to open up Dedicated Admins Connection in Management
> > Studio and getting "DAC's are not supported. (Object Explorer)"
> >
> > Any idea's?
> >
> > TIA, ChrisR
>
>

DAC not supported.

SQL2K5
SP1
Howdy all. I'm trying to open up Dedicated Admins Connection in Management Studio and getting "DAC's are not supported. (Object Explorer)"
Any idea's?
TIA, cfrBy default, the DAC is only available via the SQLCMD command line utility. I think it can be opened up to other things, but MS figured that ocule be a security risk.|||Got it. It cant be used through MGMT Studio, only a query window.

Thanks.

DAC not supported.

SQL2K5
SP1
Howdy all. I'm trying to open up Dedicated Admins Connection in Management
Studio and getting "DAC's are not supported. (Object Explorer)"
Any idea's?
TIA, ChrisRYou may need to enable the sp_configure option 'remote admin connections'.
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:E3F6FEC3-CFEC-4494-9742-B6AC1BA02242@.microsoft.com...
> SQL2K5
> SP1
> Howdy all. I'm trying to open up Dedicated Admins Connection in Management
> Studio and getting "DAC's are not supported. (Object Explorer)"
> Any idea's?
> TIA, ChrisR|||DAC is not supported for the object explorer, only for the query window.
HTH
Kalen Delaney, SQL Server MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:E3F6FEC3-CFEC-4494-9742-B6AC1BA02242@.microsoft.com...
> SQL2K5
> SP1
> Howdy all. I'm trying to open up Dedicated Admins Connection in Management
> Studio and getting "DAC's are not supported. (Object Explorer)"
> Any idea's?
> TIA, ChrisR|||Hi,
you may check my screencasts on my site, one topic is about enabling
DAC.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Thanks Kalen, that was it.
"Kalen Delaney" wrote:

> DAC is not supported for the object explorer, only for the query window.
> --
> HTH
> Kalen Delaney, SQL Server MVP
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:E3F6FEC3-CFEC-4494-9742-B6AC1BA02242@.microsoft.com...
>
>