Here are Common tasks related to Environment movement of CRM
How to change SQL server instance name:
Go
SQL server backup and restore
Windows server Backup using Windows server feature:
How to Re-connect MSCRM to New MSCRM_CONFIG and Org DB
Install SSRS Connector:
1. In
the ..\Server\amd64\SrsDataConnector folder [CRM Installer], double-click SetupSrsDataConnector.exe.
Update Web service URL
Common Issues Related to Environment
How to change SQL server instance name:
Check server instance name
select @@servername
Drop Old server:
sp_dropserver
<old_name>;Go
Create new server
sp_addserver
<new_name>, local;
Go
Restart sql service is advisable
SQL server backup and restore
1. Back up the Organization_MSCRM database
and the MSCRM_Config database. To do this, follow these steps:
a.
On the computer that
is running SQL Server, click Start, point to All Programs, point
to Microsoft SQL Server 2008 r2, and then click SQL Server Management
Studio.
b.
Expand Databases,
right-click the Organization_MSCRM database, point to Tasks,
and then click Back Up.
c.
Under Destination,
add the location to save the backup file, and then click OK.
d.
Repeat steps 1b and 1c
for the MSCRM_Config database.
Note If you must move more than one organization, repeat steps 1a-1d
for each organization database.
1. Restore the Organization_MSCRM database
and the MSCRM_Config database on the new computer that is running SQL Server.
To do this, follow these steps:
a.
On the new computer,
click Start, point to All Programs, point to Microsoft SQL
Server 2008 r2, and then click SQL Server Management Studio.
b.
Right-click Databases,
and then click Restore Database.
c.
Under Destination
to restore, type the name of the Organization_MSCRM database in the To
database box.
d.
Under Source for
restore, click From device, click the ellipsis button (...),
add the Organization_MSCRM database, and then click OK.
e.
Click to select the Restore
check box, and then click OK.
f.
Repeat steps 2b-2e for
the MSCRM_Config database.
Note If you must move more than one organization, repeat steps 2a-2f
for each organization database.
Windows server Backup using Windows server feature:
Go to Windows back up tool
Add
system state and C:\Program Files\Microsoft CRM\ for backup
Recovery
of the specific will available as per the demand
Configure SSRS:
1. Open
SSRS Configuration wizard
Try to access report server
- Update the following registry subkeys on the computer
that is running Microsoft Dynamics CRM Server:
o
configdb
o
database
o
metabase
To do this, follow these steps:
j. On the computer that is running Microsoft
Dynamics CRM Server, click Start, click Run, type regedit
in the Open box, and then click OK.
k. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
l. Right-click configdb, and then click Modify.
m. In the Value data box, change the data
source to the name of the new SQL Server, and then click OK. For
example, the string value in the Value data box should resemble the
following:
Data Source=NewSQLServer;Initial
Catalog=MSCRM_CONFIG;Integrated Security=SSPI
n. Follow steps 3b-3d for the database subkey and
for the metabase subkey.
Notes
o
If multiple Microsoft
Dynamics CRM Roles are in your deployment, you must update the registry keys
for all the server roles.
o
If you use the Microsoft
Dynamics CRM Data Connector for SQL Server Reporting Services and if you are
not moving the SQL Server Reporting Services server, you must update the
configdb subkey on the computer on which the Microsoft Dynamics CRM Data
Connector for SQL Server Reporting Services is installed.
1. Configure the Microsoft Dynamics CRM
Application to point to the new SQL Server and SQL Server Reporting Services.
To do this, follow these steps:
a. On the computer that is running Microsoft
Dynamics CRM Server, click Start, point to All Programs, point to
Microsoft Dynamics CRM, and then click Deployment Manager.
b. Click Organizations.
c. Right-click the organization that you moved to
the new computer that is running SQL Server, and then click Disable.
d. Right-click the organization that you
disabled, and then click Edit Organization.
e. Type the new name of the SQL Server and the
new URL for the SQL Server Reporting Services server.
Note This step publishes the reports that are in Microsoft Dynamics CRM to the new computer that is running SQL Server Reporting Services server that you specify.
Note This step publishes the reports that are in Microsoft Dynamics CRM to the new computer that is running SQL Server Reporting Services server that you specify.
f. Click Next two times, and then click Apply.
g. Right-click the organization that you disabled
in step 4c, click Enable, and then click Yes.
configDB
|
Data
Source=<servername>;Initial Catalog=MSCRM_CONFIG;Integrated
Security=SSPI
|
metabase
|
Provider=SQLOLEDB;Data
Source=[SQLSERVER];Initial Catalog=[CRMDATABASE];Integrated Security=SSPI
|
database
|
Provider=SQLOLEDB;Data
Source=[SQLSERVER];Initial Catalog=[CRMDATABASE];Integrated Security=SSPI
|
2. On
the Welcome to Microsoft Dynamics CRM Reporting Extensions Setup page,
select whether you want to update Microsoft Dynamics CRM Server Setup. We
recommend that, if updates are available, you let Setup download the latest
version. To do this, click Update installation files, wait until the
update process is complete, and then click Next.
3. On
the License Agreement page, review the information and, if you accept
the license agreement, click I accept this license agreement, and then
click I Accept.
4. If
Setup detects that components are missing, the Install Required Components
page appears.
a. If
you have already installed the required components, this page will not appear.
b. If
you have not installed the required components listed, you can install them
now. Click Install. When the components are installed, the status column
will change from Missing to Installed, and you can click Next
to continue.
5. On
the Specify Configuration Database Server page, if you are using the
default instance of the SQL Server, enter the name of the computer that is
running SQL Server and contains the Microsoft Dynamics CRM configuration
database that is named MSCRM_CONFIG, and then click Next.
6. On
the Specify SSRS Instance Name page, select a Microsoft SQL Server
Reporting Services instance that will be used for Microsoft Dynamics CRM
reporting, and then click Next.
7. On
the Select Microsoft Update OptIn page, select whether you want to use
Microsoft Update for checking for updates for your Microsoft products, and
click Next. We recommend that you use the Microsoft Update to check for
updates because this keeps your computer up-to-date and secure.
8. On
the Select Installation Location page, click Browse, and select a
path where you want to install CRM Reporting Extensions, and then click Next.
9. The
System Checks page appears. This page is a summary of the requirements for
a successful CRM Reporting Extensions installation. Errors must be corrected
before installation can continue. All errors must be resolved. If no errors or
only warnings appear, you can continue with the installation. To do this, click
Next.
10. Review
the Ready to Install Microsoft Dynamics CRM Reporting Extensions page,
and then click Back to correct any errors. When you are ready to
continue, click Install.
11. When
Setup completes successfully, the Microsoft Dynamics CRM Reporting
Extensions Setup Completed page appears. Click Finish.
Update Web service URL
UPDATE
|
ConfigSettings
|
SET
|
[HelpServerUrl] = 'http://YourServerName:5555/'
|
UPDATE
|
Organization
|
SET
|
[ConnectionString] = 'Provider=SQLOLEDB;Data
Source=YourDatabaseServerName;Initial Catalog=YourOrganizationDatabase;Integrated
Security=SSPI',
|
[SqlServerName]
|
= 'YourDatabaseServerName',
|
[SrsUrl]
|
= 'http://YourReportingServerName/reportserver'
|
Update Server details in CRM DB
UPDATE
|
[Server]
|
SET
|
[Name] = 'YourServerName'
|
Common Issues Related to Environment
Registry values are corrupted. So take a look at MSCRM
registry if you face any kind installation issues
·
Error rsReportServerNotActivated while accessing report server
Solution: delete encryptionkey in ssrs configuration wizard
·
Reports are not published after CRM 4.0 deployment
or reports shows error.
Check
your event viewer for proper description of error
Solution :
<Program Files>\Microsoft Dynamics CRM\Tools\publishreports.exe
·
Error: Port 80 is available to configure report server or
reports [This is not mandatory, you can configure report server in any port but
if you want to release use below command
netsh
http delete urlacl http://+:80/ReportServer/
·
Error: Microsoft CRM
Setup.common.analyzer+CollectAction for failure of Installation
Solution:
Mostly it is related to wrong registry settings of installed components
No comments:
Post a Comment