Microsoft Dynamics CRM 2013 Beta Refresh – Installation Issues
Microsoft released the revised version of its ‘CRM 2013 Beta’ titled ‘Microsoft Dynamics CRM 2013 Beta Refresh’ on 20th August 2013.
This build is available for download for Microsoft Partners on the Microsoft Connect site.
The ‘Beta Refresh’ is intended as an ISV/Partner/IT Team-centric build which promises to have the resolution fixes to issues which were raised in the ‘Microsoft Dynamics CRM 2013 Beta’ build which was released on 27th July 2013
We were able to download the latest version from the Connect website and install it on our VM (virtual machine).
The installation process of ‘MSCRM 2013 Beta Refresh’ is fairly straightforward and similar to the process which existed for MSCRM 2011. We got thru all the installation wizard screens smoothly until the last screen (screenshot below) which does the final system checks before proceeding with the install.
Note:
Installation was done as a single server deployment (Everything on a single VM including the Domain/SQL Server & Reporting Services).
There were a couple of errors reported related to the SQL & Reporting Service.
Issue #1: Microsoft SQL Server: The instance name must be the same as the computer name.
This occurs when your SQL Server instance name is not the same as your computer name and usually happens if your computer has been renamed after SQL has been installed.
SQL server stores the computer name in the ‘sysservers’ table during installation. However, when the computer name is changed manually, the above table is not updated.
The good news is there is a simple fix to get the above issue resolved.
Step 1:
Right click ‘My Computer’ and go to the properties options. You should be able to find the Computer Name here.
Step 2:
Open SQL Server management studio Query window and execute the command below
select @@servername
This should provide you with the instance name registered within SQL query
We need to ensure that the name retrieved in step 2 is similar to the one available in step 1.
Within the SQL Server management studio Query window execute the command below (the text highlighted in yellow should be the name which was retrieved in step 2 above)
SP_DROPSERVER ‘MUM-VHD-52’
On receiving a success message execute the command below (the text highlighted in yellow should be the name which was retrieved in step 1 above)
SP_ADDSERVER ‘MUM-VHD-215’, local
Restart the SQL Server Service.
To confirm the changes execute the query below (this should now return back the name which was available in step 1)
select @@servername
Issue #2: Microsoft SQL Reporting Service: Setup failed to validate specified Reporting Services Report.
This usually occurs when the SQL Reporting Service has not been properly configured after installation.
The screenshot below provides more details on the actual issue we had faced on our environment.
To fix this open ‘Reporting Service Configuration Manager’ tool on your SQL Server. (In our case SQL Server was installed on the same machine)
Ensure that the below 3 sections have been properly configured (Refer screenshots below)
a. Web Service URL
Configure the Virtual Directory Name/port/SSL port etc. and click on the ‘Apply’ button.
Once successfully configured the ‘Apply’ button would be disabled.
b. Report Manager URL
Configure the Virtual Directory Name and click on the ‘Apply’ button.
Once successfully configured the ‘Apply’ button would be disabled.
c. Database
Since Report Server stores all report server content and data in a database we need to configure the same here.
If the database is already configured you should see the database details here.
If not click the ‘Change Database’ to configure the database then click on the ‘Apply’ button.
Once successfully configured the ‘Apply’ button would be disabled.
After successful completion of all the above steps, you should be able to browse the URL’s defined within the Web Service URL & Report Manager URL
If you are able to browse the URL’s, Reporting Service is working as expected. (Refer screenshot below).
You can now go ahead and re-start your CRM installation.