Deployment issues for SQL Server report Service

Recently in the study of SSRS deployment issues, because previously also used the SSRS report, but the report was developed at that time there is a dedicated integrated system, do not need my own deployment, so the deployment of this piece is not familiar with, I remember when I was directly developed a SSRS report, It is then uploaded to Microsoft's dynamic CRM system via automatic uploading, with its own integrated deployment. And now, it seems that we have to go back to the bad to fill the information of the deployment. After countless mistakes of the wrong attempt, eventually will hurdles hurdles passed the test, not easy AH ~ ~. Below I will be in the deployment of the problems encountered in the statistics, for the future when the prawns encounter the same problem can be resolved.

First of all, the environment, I use the WIN8 system, and then the database environment for the SQL Service R2 version, when we install this version of the database, remember, when choosing the database Login authentication method, do not choose the default Windows authentication method, You can choose a mixed authentication method, which I'll mention later. The next point is the database version of the problem, starting with the SQL 2008, it is not the same as the previous deployment, do not need to deploy on IIS, but to anonymous access to the report. How to set Anonymous access, the problem is, the default system of the file configuration is Windows, so this requires us to change some of the system's configuration files to modify the anonymous access permissions:

First locate the location where you want to modify the file: (Please find the address of the default instance you set when installing)

1. C:\Program Files\Microsoft SQL Server\msrs10. Web. config, RSReportServer.config, rssrvpolicy.config under Mssqlserver\reporting services\reportserver

2. C:\Program Files\Microsoft SQL Server\msrs10. Web. config under mssqlserver\reporting Services\ReportManager

Configuration process:

1. Locate the following code in the two Web. config file:

<authentication mode= "Windows"/>

<identity impersonate= "true"/>

Replace with:

<authentication mode= "None"/>

<identity impersonate= "false"/>

2. Locate the following code in the RSReportServer.config file:

<Authentication>

<AuthenticationTypes>

<RSWindowsNegotiate/>

<RSWindowsNTLM/>

</AuthenticationTypes>

<EnableAuthPersistence>true</EnableAuthPersistence>

</Authentication>

Replace with:

<Authentication>

<AuthenticationTypes>

<Custom/>

</AuthenticationTypes>

<EnableAuthPersistence>true</EnableAuthPersistence>

</Authentication>

3. Put the file Microsoft.Samples.ReportingServices.AnonymousSecurity.dll to C:\Program Files\Microsoft SQL Server\msrs10. Mssqlserver\reporting Services\ReportServer\bin Directory (note: The directory depends on the specific installation situation)

4. Locate the following code in the RSReportServer.config file:

<Security>

<extension name= "Windows" type= "Microsoft.ReportingServices.Authorization.WindowsAuthorization, Microsoft.ReportingServices.Authorization "/>

</Security>

<Authentication>

<extension name= "Windows" type= "Microsoft.ReportingServices.Authentication.WindowsAuthentication, Microsoft.ReportingServices.Authorization "/>

</Authentication>

Replace with:

<Security>

<extension name= "None" type= "Microsoft.Samples.ReportingServices.AnonymousSecurity.Authorization, Microsoft.Samples.ReportingServices.AnonymousSecurity "/>

</Security>

<Authentication>

<extension name= "None" type= "Microsoft.Samples.ReportingServices.AnonymousSecurity.AuthenticationExtension, Microsoft.Samples.ReportingServices.AnonymousSecurity "/>

</Authentication>

5. Locate the following code in the file Rssrvpolicy.config:

</NamedPermissionSets>

<codegroup

Class= "FirstMatchCodeGroup"

version= "1"

Permissionsetname= "Nothing" >

<imembershipcondition

Class= "AllMembershipCondition"

version= "1"

/>

Add The following code (note that the URL address may be different):

<codegroup class= "Unioncodegroup"   version= "1"                                                                    Permissionsetname= "FullTrust"   name= "private_assembly"  description= "This code group grants Custom code Full trust. " >                             <imembershipcondition class= " UrlMembershipCondition "       version=" 1 "  url=" C:\Program files\ Microsoft SQL Server\msrs10. Mssqlserver2008\reporting Services\reportserver\bin\microsoft.samples.reportingservices.anonymouSSecurity.dll "/>

</CodeGroup>

6. Restart the reporting service.

The above is the setting for anonymous access permissions.

Next, let's talk about some of the setup issues in the report file:

We need a credential when we set up the data source, but in the previous we have set the default access mode to anonymous access, is no longer able to use Windows integrated access, I also tried to do not need credentials, or error, it can only choose to use the user name and password to access the way, That's why, as I mentioned earlier, it's best to use mixed mode when installing the database, and we need to access the database by using the user name and password that we set up when we install it.

Otherwise, it will be an error.

Next is the setting of the report system properties, I will not list, directly send a map:

Note that the value of each property is set, and the problem is not estimated.

After the report is finished, we should deploy it to the corresponding report server, that is, the time to configure the report, first:

The default service account is half of the built-in accounts, I choose LocalSystem, this is not a problem, the corresponding Web service URL settings is the report file in the TargetUrl, please ensure consistent, here we can adopt the system's own default, do not need to make any changes, Of course, you can also sit on your own changes, such as change the port what, the next is the Report Manager URL settings, and the Web service URL is similar, you can use the default. It should be noted here, because we used to be anonymous access, so we need to specify an execution account, this must not fall, or it will be problematic, in the development of the execution of the account, you have to be the system database has a corresponding account, you can not get a name out of thin air, This requires that you set the account name in the database security and configure a certain role permissions for it.

To do this, the entire process is almost there, so we can view the results of the report:

Alas, the whole process of walking through the ~ ~ in the middle of what may appear in the Assembly can not find the problem, in the final analysis or the user and permissions are not set the problem, so do not think about to download what the assembly get in, first put the account and permissions set the right path ~ ~ ~

Deployment issues for SQL Server report Service