Background:

Installation of the Reporting Services Add-in for Microsoft SharePoint fails and you see an error message that resembles the following:

2009-11-30 15:43:44: SSRSCustomActionError: SharePoint is installed, but not configured.



If you review the SharePoint trace logs you will see messages indicating the specific cause of the failed installation. The rest of this article describes specific error messages and possible resolutions.

For more information about SharePoint trace logs, see How to: Turn on Reporting Services events for the SharePoint trace log (ULS) in the TechNet Library.

For more information about how to install the add-in, see How to: Install or Uninstall the Reporting Services Add-in in the TechNet Library.

Firewall configuration

If your environment uses a firewall you may want to add rules. When you review the SharePoint trace log you see a message that resembles the following:

Cannot connect to SQL Server. <ServerName> not found. Additional error information from SQL Server is included below. The timeout period elapsed prior to completion of the operation or the server is not responding.


Workaround:

• Create appropriate firewall rules for the port number that is configured for Microsoft SQL Server remote connections to the database. The default port number is 1433. You may want to create both inbound and outbound firewall rules.

• Reinstall the add-in.

---

Insufficient permissions to install

When you review the SharePoint trace log you see a message that resembles the following:

SQL database login for 'SharePoint_Config_4514.1009' on instance '<InstanceName>' failed. Additional error information from SQL Server is included below. Login failed for user '<Domain\UserName>'

Workaround:

• Run the installation as a user who has SharePoint farm administrator permissions.

• Reporting Services Add-in for Microsoft SharePoint
• Reporting Services Add-in for Microsoft SharePoint 2010

See Also

• SQL Server Reporting Services
• (SSRS) Troubleshooting Issues and Errors