Error’s Deploying Lync Monitoring and Archiving

0
3237

Script failed (code “ERROR_CREATE_DB”) when installing “MonitoringStore
While deploying a new Lync 2010 Monitoring and Archiving server in the “Setup or Remove Lync Server Components” phase, the databases fail to install with the following error message:

“Script failed (code “ERROR_CREATE_DB”) when installing “MonitoringStore”. If you check the log files referenced by the installer you will see something similar to the following:
Running script: C:Windowssystem32cscript.exe //Nologo “C:Program FilesCommon FilesMicrosoft Lync Server 2010DbSetupRtcCdrDbSetup.wsf” /dbexists /sqlserver:<SQLServer> /serveracct:<Domain>RTCComponentUniversalServices /logsize:1024 /verbose
—————
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on <SQLServer>
SqlMajorVersion : 10
SqlMinorVersion : 50
SqlBuildNo : 4000
SQL version is acceptable: 10.50.4000.0
Default database data file path is D:MSSQLData
Default database log file path is F:MSSQLLogs
Database does not exist.
—————
Exit code: ERROR_NO_DATABASE_EXISTS (-23)
When running /dbexists, non-zero exit codes are not necessarily errors
—————
Running script: C:Windowssystem32cscript.exe //Nologo “C:Program FilesCommon FilesMicrosoft Lync Server 2010DbSetupRtcCdrDbSetup.wsf” /sqlserver:<SQLServer> /serveracct:<Domain>RTCComponentUniversalServices;”RTC Component Local Group” /dbpath:”D:CsDataMonitoringStore(default)dbpath” /logpath:”D:CsDataMonitoringStore(default)logpath” /logsize:1024 /verbose
—————
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on <SQLServer>
SqlMajorVersion : 10
SqlMinorVersion : 50
SqlBuildNo : 4000
SQL version is acceptable: 10.50.4000.0
(Database doesn’t exist. Performing clean install.)
Creating database LcsCDR
DbFile : PhysicalName = d:csdatamonitoringstore(default)dbpathlcscdr.mdf
LogFile: PhysicalName = d:csdatamonitoringstore(default)logpathlcscdr.ldf
Failed to create database LcsCDR
Error (
name:        Error
description:
number:      -2147221242
message:
)
—————
Exit code: ERROR_CREATE_DB (-4)
—————
Research led me to a few posts referencing this KB Article, however in my case this was not the problem. It was actually much simpler – The DBA had not given my account enough permissions to create the new databases. I was very surprised that the installer didn’t report a permission issue! The amount of global man hours that could be saved if developers spent a little more time on friendly errors messages!! 😉

All the setup logs can be found here –  %UserProfile%AppDataLocalTemp

Cannot get the ReportServerWebService URL
“Cannot get the ReportServerWebService URL. Verify that Reporting Services is deployed and configured properly on the target SQL instance:”<SQLServer>”, and that WMI is included on the exception list of firewall setting on the server that is running Reporting Services”

This is most likely caused because the Report Server web services have not been configured or your firewall is preventing access. Open “Reporting Services Configuration Manager” and check for the following:

Once configured correctly make sure you can browse to the Report Server URL’s which can be found in the Configuration Manager:

ReportServerCannot grant ReportsReadOnlyRole to user
ReportServerCannot grant ReportsReadOnlyRole to user “<UserAccount>”. For details, see the following error message:Exception calling “Create” with “0” argument(s): “Create failed for Login ‘<Domain><UserAccount>’. ”

Check the the Report Server databases have been configured and that the account you are running the installer with has sysadmin permissions to SQL.

If the database has not been configured you will see the following error when browsing Report Manager:

 

LEAVE A REPLY