Problem in deployment of packages into 2 different servers

I have 2 servers. DWTEST and DWSQL1. I developed my packages connecting to DWTEST in the design time. I have 32 packages, one of them is the master one and the others are child packages.

package PM calls P1, P2, P3,.......P31

i have 2 data source in my project. RDS and S0, both setup to connect DWTEST in the design. i defined rds_connection_string and s0_connection_string variables in my master package and created an XML config file and put those variables into that config file.

C:\PROJECTS\DEVELOPMENT\SSIS Configurations\SERVER.dtsConfig

<DTSConfiguration>

- <DTSConfigurationHeading>

<DTSConfigurationFileInfo GeneratedBy="TC\tsql" GeneratedFromPackageName="PM" GeneratedFromPackageID="{CBE946D0-279F-44F6-80A3-83D056C1E36C}" GeneratedDate="11/10/2006 10:50:44 AM" />

</DTSConfigurationHeading>

- <Configuration ConfiguredType="Property" Path="\Package.Variables[User::rds_connection_str].Properties[Value]" ValueType="String">

<ConfiguredValue>Data Source=DWTEST;Initial Catalog=RDS;Provider=SQLNCLI.1;Integrated Security=SSPI;</ConfiguredValue>

</Configuration>

- <Configuration ConfiguredType="Property" Path="\Package.Variables[User::s0_connection_str].Properties[Value]" ValueType="String">

<ConfiguredValue>Data Source=DWTEST;Initial Catalog=S0;Provider=SQLNCLI.1;Integrated Security=SSPI;</ConfiguredValue>

</Configuration>

</DTSConfiguration>

built the project into directory C:\PROJECTS\DEVELOPMENT\S1_REUSABLE_DATA_STORE\S1_REUSABLE_DATA_STORE\bin\Deployment

when i deploy my packages into DWTEST and run them as a SQL Server Agent job they work because data sources are signing to DWTEST already.

when i am deploying them(using the same manifest file in the deployment directory i wrote above) into the server DWSQL1, i select config file source as:

C:\PROJECTS\TESTING\SSIS Configurations\SERVER.dtsConfig

and update data source strings in it to DWSQL1:

- <DTSConfiguration>

- <DTSConfigurationHeading>

<DTSConfigurationFileInfo GeneratedBy="TC\tsql" GeneratedFromPackageName="PM" GeneratedFromPackageID="{CBE946D0-279F-44F6-80A3-83D056C1E36C}" GeneratedDate="11/10/2006 10:50:44 AM" />

</DTSConfigurationHeading>

- <Configuration ConfiguredType="Property" Path="\Package.Variables[User::rds_connection_str].Properties[Value]" ValueType="String">

<ConfiguredValue>Data Source=DWSQL1;Initial Catalog=RDS;Provider=SQLNCLI.1;Integrated Security=SSPI;</ConfiguredValue>

</Configuration>

- <Configuration ConfiguredType="Property" Path="\Package.Variables[User::s0_connection_str].Properties[Value]" ValueType="String">

<ConfiguredValue>Data Source=DWSQL1;Initial Catalog=S0;Provider=SQLNCLI.1;Integrated Security=SSPI;</ConfiguredValue>

</Configuration>

</DTSConfiguration>

When i run SQL Server Agent Job i defined in DWSQL1(forcing it to use DWSQL1 data source in step definition), my master package PM connects to DWSQL1, and my child packages don't use my config definitions and connect to DWTEST which is defined in the design time.

How can i force all my packages to connect DWSQL1 server using the same built files in deployment directory WITHOUT editing my packages(recreating config files or changing the definition of Data Sources and then built the project again) in Visual Studio?

Thanks to you for reading my long question...

I got a solution for my problem from a friend.

Now, i am using XML configuration file in my Master package, and Parent Package Variables in child packages. Child packages gets their data source connection strings from these variables.

Then i am keeping two different copies of XML config file in different servers(DWTEST and DWSQL1) physically.

In design environment my data source conenctions setup to connect to DWTEST. I build my project, then using the Deployment Manifest i deploy my packages into server DWTEST.

In SQL Server Agent Job Definition, in Step definition, at Configurations Tab page i add a config file and navigate to the config file stored in DWTEST(which is using DWTEST in values) and it works in DWTEST. all my child packages also connects to DWTEST.

Then i deploy my packages into DWSQL1 server using the same Deployment Manifest without editing anything in visual studio an building the project again.

in DWSQL1, in SQL Server Agent Job Definition, in Step definition, at Data Sources Tab page i check the checkboxes and edit the strings to connect to DWSQL1, and at Configurations Tab Page, i add a config file and navigate to the config files stored in server DWSQL1(which is using DWSQL1 in values). Then my packages are all working well and connecting to DWSQL1.

So it seems my problem has been solved.

|||

I was just thinking, why not make all the packages p1,p2...p30 point to the same configuration file as that's used by PM?

When you deploy using deploymentmanifest, you'll only change the config file once, and since all the packages are looking at the same package, they'll pick up the new settings.

That way, in case you make changes to the config file on DWTEST during development, you don't need to worry about forgetting to update the xml file in dwsql.

Just thinking out loud. :)

sql

problem in deploying the website developed in visual web developer 2005

Hi,

I am new to asp.net.I am trying to deploy the website on IIS created in visual web developer 2005 express.I am having problem with the aspnetdb.mdf for login.
I have copied my entire contents to the physical directory( shared floder),from where the iis virtual directory can access the contents.I can see my login form but when i enter my username and password and click login it gives my error
"error occured in establishing the connection".

I am using the sql server 2005.I don't know what should i do with aspnetdb.mdf?

thanks and urgent help needed

The following article mentions similar issue, you can take a look to see if it solves your problem.

http://forums.asp.net/1257344/ShowPost.aspx

problem in crystal report printing

i have developed a report in crystal report having field object with multiple lines. preview is perfect but it doesn't print in some dot matrix printer. please help me in this regard. thanks in advance.if printer is different then output may vary. use different printer setting for different printers.

Problem displaying report services in client browsers

Hi all

I'm working on a project where we've developed a number of reports using SQL Reporting Services. Everything works fine on the developer PCs and when they cannect to the reporting services URL they can see all the reports listed and everything works fine. When the testers connect, they can see the basic reporting services homepage with the contents and properties tabs. But when they click on the contents tab nothing is displayed.

The tester pcs are locked down and the user profiles wouldnt have the same access rights as the developers who are all local admins on their PCs.

My question is what would prevent the reports from being listed? Is there an activex control that is possibly being blocked by the local security policy for the tester profiles? If this is the case is there anything that can be pre installed on the client pcs to get around this problem?

Any thoughts or assistance that anyone could provide would be grately approeciated

Thanks

Mark
Make sure that these users have the proper roles assigned for the report server. There is Browser, Content Manager (that can pretty much do everything), Report Builder, My Reports and Publisher. There is also a way to define custom roles if needed. The Report server manager can set up users, groups and role assignments.

Problem deploying site developed with Sql Ex. To server running Sql Server 2005.

Can someone show me, or direct me, to a source,that shows me how, and what to change,when deploying a website from a development server running Sql Ex to a production server running Sql server 2005.I can’t get the sites to run under Sql server 2005.

They work in Sql Ex. what must I change?The connection string, to what format?and what else?I attached the dB to Sql 2005 and browsed the content in the Sql manager.But can’t get the aspx pages to work on the server.

Help please

What is the error code you get from your ASP application?

When connecting to SQL Express, you normally specify server as <servername>\sqlexpress. When you switch to sqlserver 2005, depending on it instance name, you need to change your connection string if you hard-code the connection string in your ASP app. For default instance, you can use <servername>, for named instance, you can use <servername>\<instancename>.

If you can't resolve your issue, please post your connection string, error message from ASP application and server connectivity configuration, such as whether it is name instance or default instance, whether you have TCP up or browser up and etc.

|||

Thanks Nan Tu for the assistance

This is the connection string error i get:

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

But i have setup the virtual drive as a app in the root.

This is theconnection string:

<connectionStrings>

<add name="ConnectionStringGetSomeThing" connectionString="Data Source=localhost;initial catalog =getsomething.mdf;Integrated Security=True" providerName="System.Data.SqlClient"/>

</connectionStrings>

also TCP and browser are enabled

|||The errormsg is not from connectivity driver, you probably need to ask either in ASP or IIS forums.

Problem deploying site developed with Sql Ex. To server running Sql Server 2005.

Can someone show me, or direct me, to a source, that shows me how, and what to change, when deploying a website from a development server running Sql Ex to a production server running Sql server 2005. I can't get the sites to run under Sql server 2005.

They work in Sql Ex. what must I change? The connection string, to what format? and what else? I attached the dB to Sql 2005 and browsed the content in the Sql manager. But can't get the aspx pages to work on the server.

Help please

The connection string format of SQL 2005 should be the same as SQL Ex, only the change should be the data source name and user/password. What the error you got after change to SQL2005?|||

It's configured properly as a application, And it is in the root of the application

Parser Error Message:It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

|||Your new error message seems to be an IIS issue, we'd better get help from IIS expert.|||As far as I know, the exception is thrown when an element that is only allowed in the application root is set in a web.config file that is in a subfolder. Please check.|||

We have the files in the root and we believe its some connection issue because of all the test we've run. This is a more detailed explanation of what me and my partner have been working on.

Any help would be very very much appreciated as I am about 15 hours into this :(

Background is a development system with ASP.NET 2.0 and SQL express 2005. The server is SQL 2005 standard edition. Any ASPX pages that connect to a database results in errors.

I have 2 identical servers with Windows server 2003, one has SQL Express and the other has SQL Server 2005 standard. that is the only difference between these systems. The scripts that work seamlessly when uploaded to the SQL Express server dont work on the SQL Server 2005

My connection string is

<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Datasource=servername;Integrated Security=SSPI;initial catalog=C:\INETPUB\WWWROOT\test\app_data\aspnet.MDF;"
providerName="System.Data.SqlClient" />

two interesting tidbits

1.) No matter what the initial catalog is pointing to, I get the same error. EVEN if the database doesnt exist

Cannot open database "C:\INETPUB\WWWROOT\test\app_data\aspnwet.MDF" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

2.) second interesting thing is this, if I change the datasource to "MSSQLSERVER" which is the instance name of SQL 2005. the error changes to

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I have reinstalled SQL server 2005

I have verified that under SQL Server 2005 Surface Area Configuration that remote connections has Both TCP and Named Pipes enabled

I have verified that under the Network Configuration that the protocols for TCP/IP and Named pipes are enabled.

I have tried atleast 20 different variations of Connectionstrings

I have ran aspnet_regsql against the database

I have verified that the SQL Server Browser is started

I have verified that the TCP/IP is set in Network Configuration to default port 1433

I have gave all authentication rights to Network Service and ASPNET accounts for testing against both the MASTER and ASPNET databases using Management Studio and attaching the Database

I have created a custom SQL account with access to the database in question and added the username password syntax to the connectionstring and get the same login failed message.

If anyone can give any insight that would be MUCH appreciated!! thanks in advance.

|||

You are using SQL 2005 Express default connection for ASPNETDB.MDF which is sitting in App_Data folder within your application. It will not work when you switch to sql 2005 standard because you don't have the SQL 2005 Express version anymore.

This is not for you to use under SQL Server 2005 or 2000.

<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Datasource=servername;Integrated Security=SSPI;initial catalog=C:\INETPUB\WWWROOT\test\app_data\aspnet.MDF;"
providerName="System.Data.SqlClient" />

You need a new customized connection to point to this database ASPNETDB.MDFor (all tables from this one). Useaspnet_regsql.exe to generate this database in your target database.

I assume you may combine this one with your database.

After the database is ready, create a connection in your web.config file. Importantly, you need to add customized role and membership provider to point back to your database.

I'll copy some code at the end that works.

<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

<connectionStrings>

<add name="yourDB" connectionString="Data Source=yourDBServer;Integrated Security=false;Initial Catalog=YourDBwithASPNETDB.MDF;User ID=yourUser;Password=yourUserPwd" providerName="System.Data.SqlClient" />
</connectionStrings



<system.web>

<roleManager enabled="true"
defaultProvider="CustomizedRoleProvider">
<providers>
<add name="CustomizedRoleProvider"
type="System.Web.Security.SqlRoleProvider"
connectionStringName="yourDB" />
</providers>
</roleManager>

<membership defaultProvider="CustomizedMembershipProvider">
<providers>
<add name="CustomizedMembershipProvider"
type="System.Web.Security.SqlMembershipProvider"
connectionStringName="yourDB"
applicationName="/"
/>
</providers>
</membership>

</system.web>

</configuration>

Please try this.

Let me know if this works or new issues come out.

Have a good sleep and we will be there.

problem deploying report - can't connect to server?

Hello,
I am relatively new to reporting services. I was experimenting with some
already developed reports on a workstation and trying to figure out how
things work. The reports run fine, and I can deploy them from the solution
folder where the reports exist.
Then I tried creating my own report in my own solution folder. I was able
to create a basic report with a paramenter and run it in the IDE. But when I
tried to deploy it, I got an error message that the service could not connect
to the server. Is this like asp/aspx where you need a virtual directory or
something like that in IIS? What do I need to do to deploy my test report
from my new solution folder?
Thanks,
RichOK. I figured out how to deploy my report. I had to go to the solution
explorer, right-clicked on the ReportProject name, selected properties and
entered the name of the server machine where ReportServer resides. My report
successfully deployed.
But how can I access my report on the company intranet? Any suggestions
appreciated.
"Rich" wrote:
> Hello,
> I am relatively new to reporting services. I was experimenting with some
> already developed reports on a workstation and trying to figure out how
> things work. The reports run fine, and I can deploy them from the solution
> folder where the reports exist.
> Then I tried creating my own report in my own solution folder. I was able
> to create a basic report with a paramenter and run it in the IDE. But when I
> tried to deploy it, I got an error message that the service could not connect
> to the server. Is this like asp/aspx where you need a virtual directory or
> something like that in IIS? What do I need to do to deploy my test report
> from my new solution folder?
> Thanks,
> Rich|||OK. Figured this one out also. For posterity I share what I did. I went
back to the solution explorer and right-clicked on the Project Name, selected
properties. In the same dialog where I had to change the server name from
localhost to my server's name, apparently, by default, the startItem is set
to Report1.rdl. My report's name was RptTest1.rdl. The startItem has a
dropdown box where RptTest1.rdl was listed, so I selected it. Then I
re-deployed my report and viola! It showed up on IE along with the parameter
box. It ran fine. Yay!
"Rich" wrote:
> OK. I figured out how to deploy my report. I had to go to the solution
> explorer, right-clicked on the ReportProject name, selected properties and
> entered the name of the server machine where ReportServer resides. My report
> successfully deployed.
> But how can I access my report on the company intranet? Any suggestions
> appreciated.
>
> "Rich" wrote:
> > Hello,
> >
> > I am relatively new to reporting services. I was experimenting with some
> > already developed reports on a workstation and trying to figure out how
> > things work. The reports run fine, and I can deploy them from the solution
> > folder where the reports exist.
> >
> > Then I tried creating my own report in my own solution folder. I was able
> > to create a basic report with a paramenter and run it in the IDE. But when I
> > tried to deploy it, I got an error message that the service could not connect
> > to the server. Is this like asp/aspx where you need a virtual directory or
> > something like that in IIS? What do I need to do to deploy my test report
> > from my new solution folder?
> >
> > Thanks,
> > Rich

Problem deploying data processing extension

I have developed a data processing extension that extends an ADO.NET
provider so that it works with reporting services. That is, it works in the
designer, but when I try to deploy the application, I run into a little
problem.
It loads my wrapper (the actual extension) just fine, but then the log
reports a failure to load the dependency dll. (The ADO.NET provider that my
wrapper extends.)
I'm sure what I need to do is somehow setup the rssrvpolicy.config file so
that it provides correct permissions to both my wrapper and the dependency,
but I cannot find ANY documentation that explains how to do this sort of
thing.
Here is the relevant portion of my config file:
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="FusionWareCodeGroup"
Description="Code group for FusionWare Direct Reporting Services Provider">
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
ervices\ReportServer\bin\FusionWare.DirectADO.ReportingServicesProvider2005.dll"
/>
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\FusionWare.DirectADO.dll" />
</CodeGroup>
</PolicyLevel>
</policy>
</security>
</mscorlib>
</configuration>
Note that I've tried to tell it about the second dependency but this is not
working and may, in fact be invalid. I've tried every imaginable
combination to get this going, including multiple CodeGroup elements, but I
still get the following error every time:
aspnet_wp!library!1!2/6/2006-15:34:51:: i INFO: Call to RenderFirst(
'/Report Project1/Report1' )
aspnet_wp!extensionfactory!1!2/6/2006-15:34:52:: e ERROR: Exception caught
instantiating FusionWare report server extension:
System.IO.FileLoadException: Could not load file or assembly
'FusionWare.DirectADO, Version=5.0.61.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies. Failed to grant minimum
permission requests. (Exception from HRESULT: 0x80131417)
File name: 'FusionWare.DirectADO, Version=5.0.61.0, Culture=neutral,
PublicKeyToken=null' --> System.Security.Policy.PolicyException: Required
permissions cannot be acquired.
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
PermissionSet& denied, Int32& securitySpecialFlags, Boolean
checkExecutionPermission)
at System.Reflection.Assembly.GetType(String name, Boolean throwOnError,
Boolean ignoreCase)
at
Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.CreateExtensionObject(Extension
extConfig)
.
aspnet_wp!processing!1!2/6/2006-15:34:52:: e ERROR: The connection object of
the data source type FusionWare does not implement any of the required
interfaces.
aspnet_wp!library!1!2/6/2006-15:34:52:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
An attempt has been made to use a data extension 'FusionWare' that is not
registered for this report server., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
An attempt has been made to use a data extension 'FusionWare' that is not
registered for this report server.
aspnet_wp!processing!1!2/6/2006-15:35:03:: e ERROR: Data source
'DataSource1': An error has occurred. Details:
Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
An attempt has been made to use a data extension 'FusionWare' that is not
registered for this report server.
at
Microsoft.ReportingServices.DataExtensions.ReportDataSource.CreateConnection()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource
dataSourceObj, ReportProcessingContext pc)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
aspnet_wp!processing!1!2/6/2006-15:35:03:: e ERROR: An exception has
occurred in data source 'DataSource1'. Details:
Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
An attempt has been made to use a data extension 'FusionWare' that is not
registered for this report server.
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object
threadSet)
aspnet_wp!processing!1!2/6/2006-15:35:03:: i INFO: Merge abort handler
called for ID=-1. Aborting data sources ...
aspnet_wp!processing!1!2/6/2006-15:35:03:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing. -->
Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
An attempt has been made to use a data extension 'FusionWare' that is not
registered for this report server.
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object
threadSet)
-- End of inner exception stack trace --
aspnet_wp!library!5!2/6/2006-15:44:46:: i INFO: Cleaned 0 batch records, 0
policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running
jobs, 0 persisted streams
Any help would be appreciated!I hate it when I find a question that matches something I'm looking for but
don't see a response, so I'll post my own response:
First a better explanation of the problem:
I have a DPE that extends another dll (an ADO.NET provider).
Designer always worked, but CAS under SSRS would not load the underlying dll
due to permissions. Here is what I had to do to fix it:
First, I had to change the underlying assembly (not the DPE itself) to
Assert FullTrust rights and the right to run for a PartiallyTrusted caller:
In the underlying dll's AssemblyInfo.cs file I added this line:
[assembly: System.Security.AllowPartiallyTrustedCallers()]
Then, for any class that would get called at run-time I added the following
at the top:
using System.Security.Permissions;
and decorated the class itself with this line:
[PermissionSetAttribute(SecurityAction.Assert, Name="FullTrust")]
Then, I had to modify the rssrvpolicy.config file. The tricky part here is
that there are two levels of CodeGroup elements.
There is a top level CodeGroup element that contains a bunch of CodeGroup
elements inside it. The top level default one says that anything you run
into has no permissions. Then inside it, you define exceptions - things
that are allowed to run with various permissions. I had to add a CodeGroup
element that granted my *underlying* dll FullTrust. It looked like this:
</NamedPermissionSets>
<CodeGroup
class="FirstMatchCodeGroup"
version="1"
PermissionSetName="Nothing">
<IMembershipCondition
class="AllMembershipCondition"
version="1"
/>
<!-- Added by RHOU -->
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="FusionWareBaseCodeGroup"
Description="Code group for FusionWare Direct ADO.NET Provider">
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\FusionWare.DirectADO.dll" />
</CodeGroup>
The normal entry, as documented, for my DPE had to be a new, top-level
CodeGroup element. In otherwords, unlike the one I added above, it was a
sibling of the top-level CodeGroup element, not a child of it. It looked
like this, btw:
</CodeGroup>
</CodeGroup>
</CodeGroup>
<!-- Added by RHOU -->
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="FusionWareCodeGroup"
Description="Code group for FusionWare Direct Reporting
Services Provider">
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\FusionWare.DirectADO.ReportingServicesProvider2005.dll"
/>
</CodeGroup>
This combination worked both in SSRS 2005 and the equivalent in SSRS 2000.
I find it interesting that a non DPE had to be defined as part of the
default CodeGroup (nested in it), while the DPE had to be defined separately
from the default CodeGroup. If I moved either CodeGroup element to where
the other was the whole house of cards fell down.
I find that information about how CAS works is really hard to find,
incomplete and contradictory. I also find the complete lack of diagnostic
tools to let me see what permissions were requested, allowed/denied, when
and by whom, is a huge deficit. This is far too important to be left in
this "WAG" condition! Just my thoughts...
FWIW, it worked for me!
"Raoul James" <raoulj456@.hotmail.com> wrote in message
news:OdneBe3KGHA.720@.TK2MSFTNGP14.phx.gbl...
>I have developed a data processing extension that extends an ADO.NET
>provider so that it works with reporting services. That is, it works in
>the designer, but when I try to deploy the application, I run into a little
>problem.
> It loads my wrapper (the actual extension) just fine, but then the log
> reports a failure to load the dependency dll. (The ADO.NET provider that
> my wrapper extends.)
> I'm sure what I need to do is somehow setup the rssrvpolicy.config file so
> that it provides correct permissions to both my wrapper and the
> dependency, but I cannot find ANY documentation that explains how to do
> this sort of thing.
> Here is the relevant portion of my config file:
> <CodeGroup class="UnionCodeGroup"
> version="1"
> PermissionSetName="FullTrust"
> Name="FusionWareCodeGroup"
> Description="Code group for FusionWare Direct Reporting Services
> Provider">
> <IMembershipCondition class="UrlMembershipCondition"
> version="1"
> Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> ervices\ReportServer\bin\FusionWare.DirectADO.ReportingServicesProvider2005.dll"
> />
> <IMembershipCondition class="UrlMembershipCondition"
> version="1"
> Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportServer\bin\FusionWare.DirectADO.dll" />
> </CodeGroup>
> </PolicyLevel>
> </policy>
> </security>
> </mscorlib>
> </configuration>
> Note that I've tried to tell it about the second dependency but this is
> not working and may, in fact be invalid. I've tried every imaginable
> combination to get this going, including multiple CodeGroup elements, but
> I still get the following error every time:
> aspnet_wp!library!1!2/6/2006-15:34:51:: i INFO: Call to RenderFirst(
> '/Report Project1/Report1' )
> aspnet_wp!extensionfactory!1!2/6/2006-15:34:52:: e ERROR: Exception caught
> instantiating FusionWare report server extension:
> System.IO.FileLoadException: Could not load file or assembly
> 'FusionWare.DirectADO, Version=5.0.61.0, Culture=neutral,
> PublicKeyToken=null' or one of its dependencies. Failed to grant minimum
> permission requests. (Exception from HRESULT: 0x80131417)
> File name: 'FusionWare.DirectADO, Version=5.0.61.0, Culture=neutral,
> PublicKeyToken=null' --> System.Security.Policy.PolicyException: Required
> permissions cannot be acquired.
> at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
> PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
> PermissionSet& denied, Boolean checkExecutionPermission)
> at System.Security.SecurityManager.ResolvePolicy(Evidence evidence,
> PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset,
> PermissionSet& denied, Int32& securitySpecialFlags, Boolean
> checkExecutionPermission)
> at System.Reflection.Assembly.GetType(String name, Boolean throwOnError,
> Boolean ignoreCase)
> at
> Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.CreateExtensionObject(Extension
> extConfig)
> .
> aspnet_wp!processing!1!2/6/2006-15:34:52:: e ERROR: The connection object
> of the data source type FusionWare does not implement any of the required
> interfaces.
> aspnet_wp!library!1!2/6/2006-15:34:52:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
> An attempt has been made to use a data extension 'FusionWare' that is not
> registered for this report server., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
> An attempt has been made to use a data extension 'FusionWare' that is not
> registered for this report server.
> aspnet_wp!processing!1!2/6/2006-15:35:03:: e ERROR: Data source
> 'DataSource1': An error has occurred. Details:
> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
> An attempt has been made to use a data extension 'FusionWare' that is not
> registered for this report server.
> at
> Microsoft.ReportingServices.DataExtensions.ReportDataSource.CreateConnection()
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource
> dataSourceObj, ReportProcessingContext pc)
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
> aspnet_wp!processing!1!2/6/2006-15:35:03:: e ERROR: An exception has
> occurred in data source 'DataSource1'. Details:
> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
> An attempt has been made to use a data extension 'FusionWare' that is not
> registered for this report server.
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object
> threadSet)
> aspnet_wp!processing!1!2/6/2006-15:35:03:: i INFO: Merge abort handler
> called for ID=-1. Aborting data sources ...
> aspnet_wp!processing!1!2/6/2006-15:35:03:: e ERROR: Throwing
> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException:
> An error has occurred during report processing., ;
> Info:
> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException:
> An error has occurred during report processing. -->
> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException:
> An attempt has been made to use a data extension 'FusionWare' that is not
> registered for this report server.
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
> at
> Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object
> threadSet)
> -- End of inner exception stack trace --
> aspnet_wp!library!5!2/6/2006-15:44:46:: i INFO: Cleaned 0 batch records, 0
> policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running
> jobs, 0 persisted streams
> Any help would be appreciated!
>
>

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

Problem deploying custom report item. Items shows in preview screen in VS, but not in server dep

I have developed a custom report item that works fine in design and preview mode while in Visual Studio. I cannot get it to show up on my deployed reports. Here's what I have done so far:

1. Deployed the report using Visual Studio

2. updated the rsreportserver.config file with the following entry:

<ReportItems>
<ReportItem Name="PedigreeChart" Type="Uabr.Rap.PedigreeChart.PedigreeChartRenderer, Uabr.Rap.PedigreeChart" />
</ReportItems>

3. Updated the rssrvpolicy.config file with the following entry.

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Description="This code group grants Uabr.Rap.PedigreeChart.dll FUllTrust permission. ">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Uabr.Rap.PedigreeChart.dll" />
</CodeGroup>

I've also tried using the StrongNameMembershipCondition with no better results.

4. The dll and its dependencies are copied to the bin directory of the report server.

5. When I load a report with this custom report item on it, the report loads fine with no errors or warnings in the log file (even with verbose tracing). The area where the custom item should be is just white. It's almost like Reporting Services isn't registering the item correctly.

This is particularly frustrating because the report works fine in Visual Studio - apparently I configured that correctly. Any suggestions would be greatly appreciated. I'm stumped.

Hello,

I'm having the exact same problem that you describe. I am also stumped and was wondering if you've found a solution to this problem?

Thanks

|||I got it working, but I'm honestly not sure what I did to get it to work. I ended up granting all assemblies on the server fulltrust, which wasn't my preference but seemed to take care of the issue. However I'm still not sure if that was the item that fixed things. What I am sure about was that is was some configuration issue and not an assembly problem in my case because all I did was srcrew with the configuration for a while. It was a frustrating experience and I'm sorry I can't help more.|||

Hi,

I hab the same problem in the beginning. What solved it for me was that ALL assemblies being used by the CRI have to be trusted, including unmanaged C++ DLLs if there are any. First I listed each DLL but then I gave all my DLLs a strong name and now it works with only the strong name membership condition.

For debugging I enabled something named like 'assembly load logging' on the local report server. I also tried attaching to the worker process in order to read the debugging messages in VS if I remember that right.

Hth,

Thomas

problem creating assembly using other assemblies

Hi,

I have developed a Stored procedure to output text to a text file, after doing a lot of reading here.
I want to be able to output data to a Postgres database, to be used for web mapping. I have referenced an Assembly Npgsql.dll so I can send updates to the postgres database when my ms sql database is updated. However, after building my class library, when I try to CREATE ASSEMBLY in sql server 2005 express, it sends out a message:
Msg 10301, Level 16, State 1, Line 1
Assembly 'ClassLibrary1' references assembly 'system.drawing, version=2.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a.', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: 2(error not found)). Please load the referenced assembly into the current database and retry your request.
The error seems to be in the Npgsql.dll assembly, can anybody please shed some light on this.
I tried to load the system.drawing assembly, and can do so in Unrestricted mode. It then spits out the same problem for System.Windows.Forms.dll.
I am still very new to all of this so any help would be appreciated.
Cheers,
Jatz91.

I got around this problem.

I used CREATE ASSEMBLY with PERMISSION_SET=UNSAFE and put the Microsoft.NET Framework Assemblies in the same folder where my built assembly was.

When I used CREATE ASSEMBLY, a warning was spat out for each assembly saying:

Warning: The Microsoft .Net frameworks assembly 'system.drawing, version=2.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in SQL Server hosted environment.

So now I run my CLR in UNSAFE mode

Cheers