Active Directory as Linked Server no data being returned

We're having problems establishing a Linked Server that points at
Active Directory in SQL Server 2000. We've executed
sp_addlinkedserver and have created a view of active directory users.
However, when querying the view, no data is returned. Are we maybe
not connecting correctly? We are not receiving any error messages.
Any help would be appreciated.
Here is how we created our view:
CREATE VIEW AD_USERS AS
SELECT * FROM OpenQuery(
ADSI,'<LDAP://DC=domain,DC=com>;(& (objectCategory=Person)(objectClass=user
))
;sn,
name, adspath,title;subtree')
(except domain is replaced with our domain name)
Thanx in advance for any help!!Try querying the same OU etc. from a command line tool to make sure that
the query is returning data.
The command line tool is a Windows tools called ldifde.
Example:
ldifde -d "CN=Users,DC=<domain>" -l servicePrincipalName -F
<NewoutputUsers>.txt This syntax creates a file named NewoutputUsers.txt
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||We get data returned with the command line tool when
replacing <domain> in your example with our domain name.
What do we need to change in our OpenQuery statement to
get results with SQL Server?

quote:

---

>--Original Message--
>Try querying the same OU etc. from a command line tool

---

to make sure that

quote:

---

>the query is returning data.
>The command line tool is a Windows tools called ldifde.
>Example:
>ldifde -d "CN=Users,DC=<domain>" -l

---

servicePrincipalName -F

quote:

---

> <NewoutputUsers>.txt This syntax creates a file

---

named NewoutputUsers.txt

quote:

---

>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

---

confers no rights.

quote:

---

>
>.
>

---

|||So, I tried to create a view to use for querying Active
Directory:
CREATE VIEW AD_USERS AS
SELECT *
FROM OPENQUERY( ADSI,
'SELECT *
FROM ''LDAP://CN=users,DC=<domain>,DC=com''')
When I query the AD_USERS view using query analyzer on
a client workstation running Enterprise Manager, there
are errors produced. When I query the same view using
query analyzer on the SQL Server server, no errors are
produced. However, even though I am selecting * from the
view, the only field to come back is adsPath. When I try
to specify another field name in the query that creates
the view, I receive the following error:
Could not get the data of the row from the OLE DB
provider 'ADSDSOObject'. Could not convert the data value
due to reasons other than sign mismatch or overflow.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject'
IRowset::GetData returned 0x80040e21: Data status
returned from the provider: [COLUMN_NAME=cn
STATUS=DBSTATUS_E_CANTCONVERTVALUE]].
Is there something that needs to be changed in the query?
Help, please.

quote:

---

>--Original Message--
>Try querying the same OU etc. from a command line tool

---

to make sure that

quote:

---

>the query is returning data.
>The command line tool is a Windows tools called ldifde.
>Example:
>ldifde -d "CN=Users,DC=<domain>" -l

---

servicePrincipalName -F

quote:

---

> <NewoutputUsers>.txt This syntax creates a file

---

named NewoutputUsers.txt

quote:

---

>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

---

confers no rights.

quote:

---

>
>.
>

---

Accessing Reports Once Deployed?

I have created several reports in SRS and I deploy them by establishing a VPN connection than deploying. That much works fine.

Now I want to allow user of my website to access the reports by clicking on a link. Do I need to establish user level access for the reports for each user or just one public access account? How do I pass login and credential information with the link so that users can access the report.

Thanks in advance

Hi there,

Reporting Services uses AD out of the box. You can add individual user accounts or groups to the Report Manager as browsers or content managers.

If you are using SOAP access you can pass the credentials in from code, otherwise they'll have to type their info in.

If you want to use forms based or custom security, it is a bit complex but can be done.

Here's a link to more info.

http://msdn2.microsoft.com/en-us/library/aa274428(SQL.80).aspx

cheers,

Andrew

|||Thanks for the link. I think that is the clue I needed