Symptoms: The Report Portal page will not open. Instead, you get a Server Error that reads: "Could not connect to endpoint DesignerService.svc on the server. Please verify connectivity to the server and check the server configuration. HTTP request error"

Causes: The IIS Management Console is turned off by default, or WCF is not configured on your machine.

Solution 1: Turn on the IIS Management Console.

1. Open Control Panel and select Programs and Features.
2. On the left, select Turn Windows features on or off.
3. In the Windows Features window that appears, expand the Internet Information Services node, then the Web Management Tools node.
4. Ensure that the check box next to the IIS Management Console is selected and click OK.
   

Solution 2: Configure WCF on your machine.

1. From the Start menu, open a command prompt (cmd.exe).
2. In the command window, enter cd %SystemRoot%\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\ to change to the directory where the ServiceModel Registration Tool is installed.
3. For Framework 4 or 4.5, enter the command: ServiceModelReg.exe -ia to run the tool to install all WCF and WF components. (For Framework 3 or 3.5, the command is: ServiceModelReg.exe -ir.)

Solution 3: Add features to WCF Services on the server.

1. From the Start menu, select Server Manager.
2. On the Manage menu, select Add Roles and Features.
3. In the Add Roles and Features window, select the Features tab.
4. Under Features, expand the .NET Framework 4.5 (Installed) node, then the WCF Services (Installed) node.
5. Under WCF Services (Installed), select the following three features:
   • HTTP Activation
   • Named Pipe Activation
   • TCP Activation
6. Click the Install button.

Symptoms: The Administrator Dashboard and Report Portal pages will not open. Instead, you get HTTP Error 503.

Cause: The application pool for the service is stopped.

Solution: Restart the application pool.

1. Open IIS and expand your localhost node.
2. Select Application Pools.
3. In the Application Pools page that appears, find ASP.NET v4.0 AR_AppPool and check its Status.
4. If the Status is Stopped, right-click ASP.NET v4.0 AR_AppPool and select Start. 

Symptoms: The service will not start when you try to reinstall. Instead, you get "Service 'ActiveReports 12 Server' failed to start."

Cause: The previous version did not uninstall completely.

Solution: Uninstall the remnants of the previous version before reinstalling.

1. In Windows Explorer, delete the directory C:\ActiveReports 12 Server.
2. Open IIS, expand the localhost, then the Sites node, and delete the ActiveReports 12 Server site.
3. Right-click the installer and select Run as administrator and follow the installation instructions.

Symptoms: The report list is not displayed on the sample web page.

Cause: When deploying samples, two access options in the Internet Information Services (IIS) settings are selected: "Enable anonymous access" and "Integrated Windows authentication."

Solution: Change the IIS settings to use only a single authentication scheme, "Enable anonymous access."

1. In the Control Panel, open Administrative Tools, then Internet Information Services Manager.
2. In the Internet Information Services window that appears, expand the tree view in the left pane until you see the Web sites/sample node.
3. Right-click Web Sites/sample to open the Web Sites Properties dialog.
4. On the Directory Security tab, in the Authentication and access control section, click Edit.
   
   

5. In the Authentication Methods dialog that appears, ensure that only one authentication scheme is selected in the corresponding checkbox.
   
   

6. Click OK to apply the changes, and OK again to close the dialog.
7. Back in Visual Studio, run the sample again.

Symptoms: The service does not start when you try to install the agent. Instead, you get the "Service 'ActiveReports 12 Agent' failed to start" error.

Cause: You are using an IP address to connect a remote agent to a controller.

Solution: You must enter a server name "(server-name):4040" into the server list box.

1. Locate the agent installer ActiveReport 12 Server Agent in C:\ActiveReports 12 Server\Site\Admin.
2. Run the installer on Azure VM and follow the installation instructions.
3. On the Report Runner Agent Installation page, enter the server URL as "<server-name>:4040".
4. Complete the installation.

Symptoms: An ActiveReports report with a custom tile provider does not open in ActiveReports Server.

Cause: The ActiveReports Server does not consider a custom tile provider as a full trust assembly.

Solution: You must configure a custom tile provider to have full trust permission.

1. Create or use an existing custom tile provider, for example, MyCustomProvider.
2. Run Visual Studio and open the MyCustomProvider project.
3. Go to Project > MyCustomProvider Properties.
4. Go to Signing and sign the assembly with the public key.
5. Rebuild the project.
6. Copy the MyCustomProvider.dll from the project folder to the ActiveReports Server Agent folder located at C:\ActiveReports 12 Server\Agent.
7. Add the custom tile provider to GrapeCity.ActiveReports.configuration file located at C:\Program Files (x86)\Common Files\GrapeCity\ActiveReports 12 and copy it to C:\ActiveReports 12 Server\Agent.
8. Open the Visual Studio command prompt and navigate to C:\ActiveReports 12 Server\Agent.
9. Type sn -Tp MyCustomProvider.dll.
10. Copy the code you get.
11. Open the ActiveReports.Server.Agent.exe configuration file.
12. In the configuration file, add the following code to the <appSettings> section. Replace X with the code you get in the step 10.

    Add this code to the <appSettings> section	Copy Code
    <add key="RunnerService.FullTrustAssemblies" value="MyCustomProvider, 1.0.0.0, X"/>

     
13. Save and close the ActiveReports.Server.Agent.exe configuration file.
14. Restart the ActiveReports agent.