An attempt has been made to use a data extension 'DLLName' that is not registered for this

Hello,

I've created my own data extension which uses ADODB.NET (OleDB Provider) and connects to the named SQL instance. During the development phase of the report I can connect to my data source, retrieve data from it and display it in the report preview with no problems. But as soon as I want to deploy this report and my data source I get the message: “An attempt has been made to use a data extension 'DLLName' that is not registered for this report server.". I went thru all *.config files and set up them up as per instructions how to. I can see my extension in the combo box during designing my report which tells me that this is done correctly. I can create the report in the preview as well. But whatever I do, when I want to deploy it I'm always getting this message.

I've come across one post where it says that Reporting Services are limited to the default, unnamed instance of SQL Server (local). I don't think it should matter to me in this case because I'm using my OleDB Provider to connect to the database. Report doesn't know anything about it. It gets data from my extension, not directly from the database. But I've tried switching from my named instance to (local) just to see if it is going to work, but no luck.

I'd appreciate somebody giving me some suggestions on this issue.

Thanks...

did you update rssrvpolicy.config to grant fulltrust to your extension? Usually this error message appears when report server gets an exception when loading the extension, and this usually happens when extension is not trusted or it fails in constructor. The fact that it works in report designer (which runs everything in fulltrust by default) most likely means that extension is not getting fulltrust when loaded on server.|||

Yes I did. Here is the code from the rssrvpolicy.config:

<CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Name="MyCodeGroup" Description="Code group My data processing extension">

<IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportServer\bin\My.dll"/>

</CodeGroup>

But it still doens't work. I still am getting the same message when I try to deploy my report.

Any suggestions would be appreciated.

Thanks...

Alternatives to ODBC in Access 2000

Hello All,

Have a bit of a problem that I hope someone will be able to clarify. I have an Access 2000 mdb that connects to two SQL Servers by way of ODBC. Now due to several failures with OBDC (Would get ODBC errors when the connection to SQL was proven not to be down), my boss wants me to eliminate ODBC from the equation and directly connect to the SQL Servers. Now he has suggested I use SQLOLEDB as an alternative, but thus far I seem to only be able to implement this on the VB side of it, which would mean I'd have to send all my SELECTS UPDATES DELETES etc manually, which would turn a minor update into a complete overhaul. I know there is a way to link tables directly with SQL in Access 2002, is there a similar option in 2000, and how would I go about it?

Thanks!Did a little research and it seems possible to use ADP files with SQLOLEDB, but I don't know how or even what ADP files are.