Showing posts with label own. Show all posts
Showing posts with label own. Show all posts

Wednesday, March 7, 2012

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...

Sunday, February 12, 2012

Alternative to Reporting Services

Hi,

I need a report writer in which I can create some standard reports and also let end user create their own against an SQL Server 2005 database. The writer must have a web interface for users to create and run reports. Crystal Reports was considered too complex for end users.

I've been trying with Reporting Services and MS's Report Builder, but it's been crashing on large data sets.

Can anyone recommend an alternative that I could look at?

Thanks,

Frank

I understand that the concept of allowing end-users to design reports is a popular one in the industry. However, there is a problem, end-users don't know squat about designing databases, data, or reports in general. There are end-user tools that allow them to do this, but if they want something more than a simple list of data from a single table they are all still difficult to use, not to mention dangerous. Imagine the impact on server based reports if an ignorant user tries to pull out large sums of data to create a gigantic report (because they dont have a clue). I can just a imagine a user trying to create a sales report by loading every invoice or general ledger item out the business database. Meanwhile, no one else can work because everything has slowed to a crawl while the server is trying to process their 50 million row report! I think you ought create reports for users and make sure to enable interactive sorting so they can see the data the way they want. Unleasing users into the database is just a bad idea if you ask me.

Any way, I guess you really didnt ask for my opinion, you asked for an application to make it possible. Nearly all versions of SQL Server 2005 (Workgroup, Standard, Enterprise) ship with a program called 'Report Builder'. It is a ClickOnce deployed Winforms app that allows end-user to build their own reports. If I were you I would simply tell your users that no such product exists and save your self from the fiery hell you are sure to enter once they begin meddling with your database.