I read scott's tutorial for Deploying database to Hoster's server
"Recipe: Deploying a SQL Database to a Remote Hosting Environment (Part 1)"
bt cud nt upload n get the user login functinality wrking..
so plz help me..
hi,whats the actual problem, not being to upload or to connect ? What is the error message you are getting ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
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
after creating Analysis service projects using SQL server Business Intelligence Development Studio when the project is deployed it gives following error.........
Error 1 The project could not be deployed to the 'Solversa-201\SQL2005' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server. 0 0
connection to the server problem doesnt come at the time of creating data base,at that time it is accepting server name and displaying the database list...............
even test connection is also sucessful...................
problem is only at the time of deployment of project
Please make sure that the instance name in the Deployment tab refers to your Analysis Services instance and not your SQL Server 2005 database server instance.Hello! You do not need to be an domain adminstrator in order to access Reporting Services and Analysis Services. It is sufficient to be a local administrator on the server running these two applications.
In Reporting Services you have the option to run a report with windows authentication or an assigned account for Reporting Services access to Analysis Services.
If you run with the first option each user need to mapped to a role in Analysis Services which can be done with individual accounts or windows groups. For the second option it is only the Reporting Services(AS2005) account that needs to mapped to a role in Analysis Services.
You can do this both in BIDS, Report Manager or Management Studio.
This is true for a server where both these applications are running. If Reporting Services is on a separate server things are a little bit more complicated. In this case you will have to set up account delegation in Active Directory. The key word for this setup is 'Kerberos' .
HTH
Thomas Ivarsson
|||Can you give me some more detail on the configuration please? Are there any guides available on the web? Thanks!|||Hello! I have not found any best official practices regarding SSRS2005 and SSAS2005 integration.
My advice is based on customer cases/practises that I have used and some good writing in a reporting services book.
Regards
Thomas Ivarsson
|||http://technet.microsoft.com/en-us/library/ms175386(SQL.90).aspxThis website provides what I needed.
Hello! You do not need to be an domain adminstrator in order to access Reporting Services and Analysis Services. It is sufficient to be a local administrator on the server running these two applications.
In Reporting Services you have the option to run a report with windows authentication or an assigned account for Reporting Services access to Analysis Services.
If you run with the first option each user need to mapped to a role in Analysis Services which can be done with individual accounts or windows groups. For the second option it is only the Reporting Services(AS2005) account that needs to mapped to a role in Analysis Services.
You can do this both in BIDS, Report Manager or Management Studio.
This is true for a server where both these applications are running. If Reporting Services is on a separate server things are a little bit more complicated. In this case you will have to set up account delegation in Active Directory. The key word for this setup is 'Kerberos' .
HTH
Thomas Ivarsson
|||Can you give me some more detail on the configuration please? Are there any guides available on the web? Thanks!|||Hello! I have not found any best official practices regarding SSRS2005 and SSAS2005 integration.
My advice is based on customer cases/practises that I have used and some good writing in a reporting services book.
Regards
Thomas Ivarsson
|||http://technet.microsoft.com/en-us/library/ms175386(SQL.90).aspxThis website provides what I needed.sql
Here's my problem. I have an SSRS report with subreports on it. The main report and subreports work fine on my machine when I run the main report. However, when I deploy them to our test server and change the server name of the shared datasource, only the main report brings back data. The subreports show an error of something like "Error in displaying the subreport" for each subreport. The subreports require parameters that I believe I am supplying from the main report. What am I doing wrong? Is it really necessary to deploy the subreports with the main report to the new server. With Crystal Reports, I didn't have to do this. Any thoughts or suggestions would be appreciated.
Are you sure that the subreports are using the shared datasource? Can you run any of the subreports by themself?
|||SteffoS,
Thanks for replying. Yes, I can run the subreports individually and get data. Thanks again. Any other suggestions?
|||Hi All,
I found the answer to my problem. When I right clicked on the subreport and chose properties then went to the parameters tab, I chose the Fields.fieldName.Value for the the value of my parameter. This is incorrect. What I needed to do and did was choose the <expression> item in the dropdown box then click on parameters and choose the correct parameter from the main report to be the value for the parameters in my subreport. Worked like a charm, but I'm not getting too excited. I've read too much that things just started working for people and they could not explain why. That's scary too. Thanks.
Here's my problem. I have an SSRS report with subreports on it. The main report and subreports work fine on my machine when I run the main report. However, when I deploy them to our test server and change the server name of the shared datasource, only the main report brings back data. The subreports show an error of something like "Error in displaying the subreport" for each subreport. The subreports require parameters that I believe I am supplying from the main report. What am I doing wrong? Is it really necessary to deploy the subreports with the main report to the new server. With Crystal Reports, I didn't have to do this. Any thoughts or suggestions would be appreciated.
Are you sure that the subreports are using the shared datasource? Can you run any of the subreports by themself?
|||
SteffoS,
Thanks for replying. Yes, I can run the subreports individually and get data. Thanks again. Any other suggestions?
|||Hi All,
I found the answer to my problem. When I right clicked on the subreport and chose properties then went to the parameters tab, I chose the Fields.fieldName.Value for the the value of my parameter. This is incorrect. What I needed to do and did was choose the <expression> item in the dropdown box then click on parameters and choose the correct parameter from the main report to be the value for the parameters in my subreport. Worked like a charm, but I'm not getting too excited. I've read too much that things just started working for people and they could not explain why. That's scary too. Thanks.
Hello, I am trying to deploy a SSIS package (using deployment utility create at build time) to a different server and ran into problem wonder if someone and direct me to the right path.
development environment: WIN XP, SQL 2005. package is built using server buisiness intelligence. Package content: connect to a "target"SQL2005server using OLE DB using SQL Login authentication to process data. The SQL 2005 DB is on a Win 2003 server (R2) as OS platform.
The package was built, install ( SQL not file system)and ran fine on the development environement; when attempt to deploy the package to the SQL 2005 server where data reside and should be processed (also install to SQL), I receive error " 0x80004005 ...description TCP Provider: No connection could be made because the target machine activily refuse it". which is an odd error since the package is on the server that it try to connect to the data base on it.
If anyone can give me some hint at what cause this problem, appreciate the help.
Not sure, but have you checked that the SQL Server Integration Services service is running on the target machine?|||Yes, that the first thing I check, via surface area configuration and administration tools -> Services both confirmed that the Ingergrated services is started and running.
I have a couple of questions. I've gotten Our SSAS Running against SS 2000 where the Server is separate from the Web Server running IIS by installing SSAS on the Web Server and Pointing it to the instance on the Database Server. This works on both mine and my bosses systems and I finally got it working on our internal server (the described situation above, our dev computers have all running on one box).
When I implement this on one of our client configurations that is the same as the first above (DB + SSAS and connected to IIS Server with SSAS as well) I cannot get it to connect and return the data.
The error I get via my Asp.net 2.0 webpage is :
A connection cannot be made. Ensure that the server is running.
I have checked every possible setting between the two sets of servers and I'm about to lose it
Everything seems identical. Do you have any suggestions. I checked the services to see if the SSAS was running on the web server and it is.
Suggestions?
SSAS authenticates using windows authentication. In order to get an ASP.NET application to connect to SSAS, it needs to be running under an account that is in a role in SSAS that has rights to view the cube you want to query.
There are a couple of ways to do this:
For IIS6, you are best to setup an application pool running under a domain account, run your ASP.NET in that application pool and put that domain account in a role in SSAS.
For IIS5 instead of using an application pool you can set the account using the <Identity> tag in the web.config
Note: to SSAS, it will see all requests as coming from a single user so you cannot use role based security with this sort of setup. If you need role based security you would need to maybe look into setting up HTTP authentication.
|||
Ok I'm a bit confused. Sorry.
I've got on Server 1
IIS & Analysis Services
On Server 2
SQL Server 2000 & Analysis Services
As far as I got was installing Analysis Services on the Web Server.
There is an Application Pool that the website is running under but I'm not sure how to setup the Roles for that Pool.
I added user roles under the SSAS on the web server but it's still not working. Sorry for my confusion, I took over this project from another developer and have never worked with this before. Thank you so much for your assistance.
|||So why are there 2 AS servers? and which one has the database you want to connect to?
If you just want your web server to connect to the second server with AS and SQL on it then you don't need AS on the web server, you just need the OLEDB provider for Analysis Services (version 8.0 for AS 2000). The typical problem with web servers is that NTLM credentials will not do 2 hops. What this means is that the client can authenticate to the web server, but the web server cannot pass those credentials along to the second server (for security reasons).
There are actually 2 ways around this you can configure Kerberos authentication (there are a couple of whitepapers from MS on this, they should not be too hard to find). The only other thing you need is to have <Identity Impersonate="True" /> in your web.config.
Using the original method I described, I would actually create a new app pool, just for this application. In the app pool settings I think there is an Identity tab, you would set this to run as a specific domain user. Then on your AS server create a role with the same domain account and give it access to the database/cubes that the web app needs.
|||I tried setting up Application Pool, didn't work. I'm not sure the client wants Kerberos installed on the machine. I have this working on our internal computers (2 workstations) and our development servers. I'm trying to put it on theirs and having difficulty.
I setup Roles on the AS server (I'd rather not use the same one as on the database server) on the IIS Server (running Windows Server 2003). I can connect to the DataMart and see the data. I can get to the page but it wont' connect from IIS to AS it seems.
Using <Identity...> blows it up says it's not recognized (I'm assuming you need IIS 5 or Kerberos for that to work).
I setup every way I could imagine in the App Pool settings. It defaults as Network. I tried that. Then I tried various user configurations.
So the DB server is on SQL 2000, our test was on SQL 2005.
Thanks for your help. Any more ideas?
|||If you want to use the AS on the IIS box, then that makes things a bit easier. You only need Kerberos when IIS and AS are on separate machines.
The <Identity ...> tag is an ASP.NET setting and works for both IIS 5 and 6, but it is case sensitive and needs to be under the right section of the web.config file. But if you are using IIS 6 and don't need role based security then you are better off just using the app pool identity.
If you left the App Pool set to Network, you would need to go into the Role Manager for your database and either create a new role or add the "NETWORK" user to an existing role.
It's a lot simpler if IIS and AS are on the same box, the main "trick" is that it is the app pool account that connects to AS and needs to be in an appropriate role. If they are on the same machine you should not have trouble with firewalls and identities not crossing machine boundaries.
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.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.
I have an application that involves 3 components one of which is
Reports.
My system's configuration:
SQL 2000 - Default instance
SQL 2005 - Named instance (Instance1).
I provide the user with an option of selecting the SQL Server instance.
If the user chooses Instance1, then I need to deply the reports in SQL
2005.
The exceptions encountered during installation are logged in the Event
log.
When I do the installation for the in a machine, I always
get the following error in the event log:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.
I tried giving the rs.exe options from commandline. I got an error like:
Error in DetermineReportUrlSecurity().
I don't have the exact error with me now.
Note that I do not get this error when I do the installation in a
machine where both default and named instances are SQL 2005.
Can anyone tell me why this happens?
Thanks,
Sandhya
Are you installing RS2005 on the same machine as RS 2000? If so you should be prompted to do a files only install, is that the case? If it is then I am not sure when you are seeing this error. During configuration? If you could provide the error message and a better description of exactly what you are doing, perhaps I can offer some help.|||Hi,
I am deploying my reports during the time of installation of my application i.e., throwugh an msi. I deploy the reports using rs.exe command and any error encountered would be logged in event log.
While installing SQL 2005. I selected the option 'Install and configure' for Reporting Services component. I also verified that I am able to browse to the Reports page. So there is no problem with the configuration. Someone had a similar problem which I saw in another forum. There a solution was given as to disable the firewall/create exceptions for report server. But in my system the firewall is already disabled.
I am deploying my reports from the installer by giving the rs.exe command wherein I get the following error:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.
I tried giving the rs.exe from the command line with -t parameter to trace the error.
Folowing is the exact error that I am getting:
Microsoft.ReportingServices.ScriptHost.ScriptHost.DetermineServerUrlSecuri
ty()
at Microsoft.ReportingServices.ScriptHost.ScriptHost.InstanceMain()
at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
BaseCmdLine instance)
Why do I get this error?
Thanks,
Sandhya
|||
You need to connect to http://machinename/ReportServer/ReportingServices.asmx.
I hope this help.s
|||Hi,Hi,
For Yukon, the default configuration for the Report page would be:
Default instance - http://<machinename>/reports
Named Instance - http://<machinename>/reports$<InstanceName>
In my case, I have Yukon in the named instance(Instance1). Hence I need to connect to http://<machinename>/reports$Instance1 and I verified that I am able to browse to this page. I get the Reports homepage.
When I browse to http://machinename/reportserver$Instance1, I get the following displayed in the page:
chnshl13423/ReportServer$Instance1 - /
Microsoft SQL Server Reporting Services Version 9.00.1399.00
So what might be the problem?
Thanks,
Sandhya
|||you should pass in -s http://machinename/reportserver$Instance1 to rs.exe.|||
Hi,
I am already giving the following:
rs.exe -i "C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -s "http://chnshl13423/reportserver$Instance1" -v parentFolder="DCM Reports For Yukon" -v reportLocation="C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -v serverName="chnshl13423\Instance1" -v databaseName="DCMSolution"
Thanks,
Sandhya
|||Any suggestions?|||Hmm, It looks like you are doing everything that you should be. All the script host does at this point is call the soap method ListSecureMethods, using the ReportService2005.asmx endpoint. Your command looks correct and the server is up and running. I really don't know what would be causing this error.
The only thing I can think of is if the user you are running rs.exe as can not be authenticated with RS or RS is setup to use forms or basic auth. You could try using a different user, or if you are using basic auth, pass in the username and password options.
I have an application that involves 3 components one of which is
Reports.
My system's configuration:
SQL 2000 - Default instance
SQL 2005 - Named instance (Instance1).
I provide the user with an option of selecting the SQL Server instance.
If the user chooses Instance1, then I need to deply the reports in SQL
2005.
The exceptions encountered during installation are logged in the Event
log.
When I do the installation for the in a machine, I always
get the following error in the event log:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.
I tried giving the rs.exe options from commandline. I got an error like:
Error in DetermineReportUrlSecurity().
I don't have the exact error with me now.
Note that I do not get this error when I do the installation in a
machine where both default and named instances are SQL 2005.
Can anyone tell me why this happens?
Thanks,
Sandhya
Are you installing RS2005 on the same machine as RS 2000? If so you should be prompted to do a files only install, is that the case? If it is then I am not sure when you are seeing this error. During configuration? If you could provide the error message and a better description of exactly what you are doing, perhaps I can offer some help.|||Hi,
I am deploying my reports during the time of installation of my application i.e., throwugh an msi. I deploy the reports using rs.exe command and any error encountered would be logged in event log.
While installing SQL 2005. I selected the option 'Install and configure' for Reporting Services component. I also verified that I am able to browse to the Reports page. So there is no problem with the configuration. Someone had a similar problem which I saw in another forum. There a solution was given as to disable the firewall/create exceptions for report server. But in my system the firewall is already disabled.
I am deploying my reports from the installer by giving the rs.exe command wherein I get the following error:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.
I tried giving the rs.exe from the command line with -t parameter to trace the error.
Folowing is the exact error that I am getting:
Microsoft.ReportingServices.ScriptHost.ScriptHost.DetermineServerUrlSecuri
ty()
at Microsoft.ReportingServices.ScriptHost.ScriptHost.InstanceMain()
at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
BaseCmdLine instance)
Why do I get this error?
Thanks,
Sandhya
|||
You need to connect to http://machinename/ReportServer/ReportingServices.asmx.
I hope this help.s
|||Hi,Hi,
For Yukon, the default configuration for the Report page would be:
Default instance - http://<machinename>/reports
Named Instance - http://<machinename>/reports$<InstanceName>
In my case, I have Yukon in the named instance(Instance1). Hence I need to connect to http://<machinename>/reports$Instance1 and I verified that I am able to browse to this page. I get the Reports homepage.
When I browse to http://machinename/reportserver$Instance1, I get the following displayed in the page:
chnshl13423/ReportServer$Instance1 - /
Microsoft SQL Server Reporting Services Version 9.00.1399.00
So what might be the problem?
Thanks,
Sandhya
|||you should pass in -s http://machinename/reportserver$Instance1 to rs.exe.|||
Hi,
I am already giving the following:
rs.exe -i "C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -s "http://chnshl13423/reportserver$Instance1" -v parentFolder="DCM Reports For Yukon" -v reportLocation="C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -v serverName="chnshl13423\Instance1" -v databaseName="DCMSolution"
Thanks,
Sandhya
|||Any suggestions?|||Hmm, It looks like you are doing everything that you should be. All the script host does at this point is call the soap method ListSecureMethods, using the ReportService2005.asmx endpoint. Your command looks correct and the server is up and running. I really don't know what would be causing this error.
The only thing I can think of is if the user you are running rs.exe as can not be authenticated with RS or RS is setup to use forms or basic auth. You could try using a different user, or if you are using basic auth, pass in the username and password options.
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
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
