Cannot reference new attribute in Active Directory

We have had an existing linked server that we used to query AD and everything was working as expected. We had to add a new attribute so the AD schema was extended.

Now when I try to reference the new field I get the following error:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'ADsDSOObject' reported an error. The provider did not give any information about the error.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' IColumnsInfo::GetColumnsInfo returned 0x80004005: The provider did not give any information about the error.].

Here is the code that gives the error:

SELECT employeeNumber as Employee_Number,
NECASupervisor
FROM OpenQuery(ADSI,
'SELECT employeeNumber,NECASupervisor
from ''LDAP://OU=NECA,OU=UserAccounts,DC=neca,DC=pri''
')

This query works fine:

SELECT employeeNumber as Employee_Number
FROM OpenQuery(ADSI,
'SELECT employeeNumber
from ''LDAP://OU=NECA,OU=UserAccounts,DC=neca,DC=pri''
')

Note: The field NECASupervisor is the new AD attribute. It is in the UserAccounts OU. If I run the same type of query using VB script it finds the attribute.

Anyone have any ideas on this?

Thanks

It turns out that once the Sql Server was rebooted, the query was able to reference the new AD attributes.

Cannot reference new attribute in Active Directory

We have had an existing linked server that we used to query AD and everything was working as expected. We had to add a new attribute so the AD schema was extended.

Now when I try to reference the new field I get the following error:

Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'ADsDSOObject' reported an error. The provider did not give any information about the error.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' IColumnsInfo::GetColumnsInfo returned 0x80004005: The provider did not give any information about the error.].

Here is the code that gives the error:

SELECT employeeNumber as Employee_Number,
NECASupervisor
FROM OpenQuery(ADSI,
'SELECT employeeNumber,NECASupervisor
from ''LDAP://OU=NECA,OU=UserAccounts,DC=neca,DC=pri''
')

This query works fine:

SELECT employeeNumber as Employee_Number
FROM OpenQuery(ADSI,
'SELECT employeeNumber
from ''LDAP://OU=NECA,OU=UserAccounts,DC=neca,DC=pri''
')

Note: The field NECASupervisor is the new AD attribute. It is in the UserAccounts OU. If I run the same type of query using VB script it finds the attribute.

Anyone have any ideas on this?

Thanks

It turns out that once the Sql Server was rebooted, the query was able to reference the new AD attributes.

Cannot propogate to subscriber

I'm getting this error when I try to replicate
The schema script
'\\CVTDEESQL005\ETMSData\unc\CVTDEESQL005_ZenithSQ L_L_060104_ZenithSQL_L_060104\20070120231902\tblCa ll_1.sch'
could not be propagated to the subscriber. The step failed.
I can find this row in sysMergeSchemaChange but I'm not sure why it's
causing a problem. Can someone give me some guidance?
kr
Spike
I'd do some logging and see if this records more info
(http://support.microsoft.com/?id=312292).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||"Paul Ibison" wrote:

> I'd do some logging and see if this records more info
> (http://support.microsoft.com/?id=312292).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
> Message: The process could not read file '\\CVTDEESQL005\ETMSData\unc\CVTDEESQL005_ZenithSQ L_L_060104_ZenithSQL_L_060104\20070120231902\tblCa ll_1.sch' due to OS error 53.
53 is a network error, so I quess either the file is not there or I've lost
access to the directory. If I were to remove this line from
sysMergeSchemeChange would that sort it? Or be a very bad idea?
The row in question is the second one after exec.sp_MsChange_Retention etc.
|||I'd run the snapshot once again. Perhaps there are also other files that
went missing, and if there's an underlying problem it'd be best to sort it
out systematically.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||"Paul Ibison" wrote:

> I'd run the snapshot once again. Perhaps there are also other files that
> went missing, and if there's an underlying problem it'd be best to sort it
> out systematically.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
> Okay I'll try that but one thing I don't understand is why I'm the only person affected. All my other users can replicate ok but even if I create a new database and set up a new pull subscription I still get that error.
|||OK - if it is reproducible, then let's look a little deeper. After the
snapshot agent runs, does the file exist? Does the account that sql server
agent runs under (are you using push or pull?) have access to the repldata
share? Is there enough space on the subscriber?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||"Paul Ibison" wrote:

> OK - if it is reproducible, then let's look a little deeper. After the
> snapshot agent runs, does the file exist? Does the account that sql server
> agent runs under (are you using push or pull?) have access to the repldata
> share? Is there enough space on the subscriber?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
> Hi Paul
I've tried to run the snapshot agent but it fails with "The Agent is
suspect. No response after 30 minutes. I'm using pull subscription. I need
to get access to the server via PCAnywhere to verify that the file/path is
acessible by the SQLAgent account but that may take some time. So I'll get
back to you.
all the best
spike
|||Hi,
Have you downloaded the SP4 hotfix (if your on SP4 that is!)
I downloaded and installed this;
http://support.microsoft.com/kb/916287
TIM
"Spike" wrote:

>
> "Paul Ibison" wrote:
> I've tried to run the snapshot agent but it fails with "The Agent is
> suspect. No response after 30 minutes. I'm using pull subscription. I need
> to get access to the server via PCAnywhere to verify that the file/path is
> acessible by the SQLAgent account but that may take some time. So I'll get
> back to you.
> all the best
> spike
|||"Paul Ibison" wrote:

> OK - if it is reproducible, then let's look a little deeper. After the
> snapshot agent runs, does the file exist? Does the account that sql server
> agent runs under (are you using push or pull?) have access to the repldata
> share? Is there enough space on the subscriber?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
> We've rebooted the server and that seems to have cleared everything up!
Thanks for your help, cheers spike

Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO"

I see others having this problem when trying to run a query across a link from 2005 to a 2000 server. But we are already running SP4 on our 2000 server. What gives?

OLE DB provider "SQLNCLI" for linked server "s-1" returned message "Unspecified error".

OLE DB provider "SQLNCLI" for linked server "s-1" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".

Msg 7311, Level 16, State 2, Line 5

Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "s-1". The provider supports the interface, but returns a failure code when it is used.

Is your server 64-bit? There was a discussion of that case http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1|||64 bit. And I have tested the link against several sql server 2000 instances which report they are all SP4 buy yield the same error messages.

Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO"

I see others having this problem when trying to run a query across a link from 2005 to a 2000 server. But we are already running SP4 on our 2000 server. What gives?

OLE DB provider "SQLNCLI" for linked server "s-1" returned message "Unspecified error".

OLE DB provider "SQLNCLI" for linked server "s-1" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".

Msg 7311, Level 16, State 2, Line 5

Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "s-1". The provider supports the interface, but returns a failure code when it is used.

Is your server 64-bit? There was a discussion of that case http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1|||64 bit. And I have tested the link against several sql server 2000 instances which report they are all SP4 buy yield the same error messages.