Had a deployment this week where we needed to get the Lync 2013 monitoring reports deployed however the environment was a bit different than i was accustomed to.
The LCSCDR and QoeMetrics were hosted on the backend SQL database Server A with non default SQL port, however the SSRS Web frontend was hosted on Server B and the reports DB was hosted on Server C with non default SQL port.
We have a Lync Service account that we are using to administer Lync, from the Lync Server 2013 Deployment Wizard we selected Deploy Monitoring reports and entered the following:
- SSRS Instance
At first we received the error : Exception calling “Create” with “0” argument(s): “Create failed for Login ” could not assign ReportsOnlyRole for user lyncadmin.
To ensure that when we were deploying the reports the Lync Frontend could speak to the SSRS instance correctly , and also when the SSRS server tries to connect to the backend SQL server where the LCSCDR and QoEMetrics databases are stored we needed to create an SQL Alias for:
- The SSRS server port and instance on Lync Front end server we are deploying the reports from
- The backend SQL server port and instance where the LCSCDR and QoEMetrics databases are located on the SSRS server where the reports will be stored and connected to the backend database.
See previous post located here how to set that up.
We tried to deploy the reports again however now we received the error: Lync 2013 Error “Exception calling “Create” with “0″ argument(s)” when installing Lync monitoring reports
So here is what we did:
- We added the SSRS admin account to the RTCUniversalServerAdmins,CSAdministrator Activedirectory Groups
- We added the SSRS admin account to the local administrator group on the Lync Front End server
- We gave the lyncadmin account dbOwner rights on the LCSCDR and QoEMetrics databases on the backend SQL server
- We logged into the Lync Front End server as the SSRS admin account
- Ran the deployment wizard
- Entered SSRS Alias name we created
- Entered the Lyncadmin account – when specifying credentials
- Entered RTCUniversalReadOnlyAdmins for the group to specify
The reports were able to deploy correctly, once completed we then:
- Removed the SSRS admin account from the RTCUniversalServerAdmins,CSAdministrator Activedirectory Groups
- Removed the SSRS admin account from the local administrator group on the Lync Front End server
- Removed the dbOwner rights for the Lyncadmin account on the LCSCDR and QoEMetrics databases on the backend SQL server
- Added the lyncadmin account to the RTCUniversalReadOnlyAdmins active directory group
Validated that we were able to connect to the Lync Reports url and view the historical data.
One thought on “Lync server 2013 Monitoring Reports Deployment Errors”
T-SQL Tuesday time again, and this is my post for #33. The host is Jeff Smith and his topic is Trick Shots, which is an interesting one. I’m not a trckiy guy, and I tend to lean towards common, practical