Next I selected the Microsoft SQL Server database that was restored earlier, and then select the organization database in the Organization database list - following the Organization Name step.
Next step is to provide the Reporting Server url, in my case SQL Server instance was another physical machine - so I provided the url accordingly. At this stage the setup denied continuing further (failed) and it turned out that CRM Reporting Extensions were not installed on SQL Server instance.
Installing CRM Reporting Extensions was another challenge - the setup splash screen was showing an option to simply install extensions but failed to proceed. Later I thought to to run it directly but what? I didn't find any installer inside setup media related to extensions. Upon further investigation I've come to know that earlier CRM Reporting Extensions came as "SrsDataConnector", and upon searching the media folders I found "SrsDataConnector" folder - this way I was able to install.
Next I switched back to CRM instance and continued till "Mapping Users" screen.
Still writing...
Next step is to provide the Reporting Server url, in my case SQL Server instance was another physical machine - so I provided the url accordingly. At this stage the setup denied continuing further (failed) and it turned out that CRM Reporting Extensions were not installed on SQL Server instance.
Installing CRM Reporting Extensions was another challenge - the setup splash screen was showing an option to simply install extensions but failed to proceed. Later I thought to to run it directly but what? I didn't find any installer inside setup media related to extensions. Upon further investigation I've come to know that earlier CRM Reporting Extensions came as "SrsDataConnector", and upon searching the media folders I found "SrsDataConnector" folder - this way I was able to install.
Next I switched back to CRM instance and continued till "Mapping Users" screen.
Still writing...
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.