Friday, February 17, 2012

Error while linking server to Active Directory service (advance)

I read that I can ignore this problem (it's normal!),
but I have another error.
I run SQL Server service with my domain account, I add my SQL Server istance
to Active directory inside Enterprise Manager, I create the linked server how
documented with access by my domain account.
Finally, I execute this query in Query Analyzer:
SELECT * FROM OpenQuery( ADSI, 'SELECT *
FROM "LDAP://" ')
having this error:
Message 7321, Level 16, State 2, Row 1
OLE DB error trace [OLE/DB Provider 'MSOLAP' ICommandPrepare::Prepare
returned 0x80040e14]
Any suggests to solve this issue?

> I need to retrieve information from LDAP in SQL Server 2000.
> I have installed SQL Server 2000 on a machine with Windows XP Professional
> (SP2).
> When I execute this script inside Query Analyzer:
> EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
> 'ADSDSOObject', 'adsdatasource'
> GO
> and then I open tables or views of linked server this error appears:
> "Error 7301: It is impossible to obtain from OLE DB provider 'ADSDSOObject'
> a necessary interface..."
> Can I solve this issue?
> Where I can find a good documentation about SQL Server 2000 and LDAP?
> Many thanks
>
The right error message is:
Message 7321, Level 16, State 2, Row 1
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandPrepare::Prepare
returned 0x80040e14].
Sorry!
[vbcol=seagreen]
> I read that I can ignore this problem (it's normal!),
> but I have another error.
> I run SQL Server service with my domain account, I add my SQL Server istance
> to Active directory inside Enterprise Manager, I create the linked server how
> documented with access by my domain account.
> Finally, I execute this query in Query Analyzer:
> SELECT * FROM OpenQuery( ADSI, 'SELECT *
> FROM "LDAP://" ')
> having this error:
> Message 7321, Level 16, State 2, Row 1
> OLE DB error trace [OLE/DB Provider 'MSOLAP' ICommandPrepare::Prepare
> returned 0x80040e14]
> Any suggests to solve this issue?
>

No comments:

Post a Comment