Wednesday, 26 October 2011

Crm 2011 installation issues and solutions

After Setup is complete, you cannot change the database collation, base ISO currency code, or the organization unique name. However, you can change the base currency name and base currency symbol.

Issue: What Org Unit should I use to setup Crm 2011?
Solution: Just use the top Unit.

Issue: I can ping the sql server but can not connect to it using Sql Management Studio.
Solution: Turn off the firewall on the sql server.

Issue: Error "The instance name must be the same as computer name."

sp_dropserver 'old server name'

sp_addserver 'new server name', local

Issue: The reporting server doesn't exist
Solution: Enable the service on Services.msc
Then Start the reporting service via Reporting Services configuration Manager

Issue: "The report server has encountered a configuration error. (rsServerConfigurationError)" And then when you look into the log at C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles. Under the latest ReportServerService*.log, there was the following error: "Message: No DSN present in configuration file".
Solution: Basically you need to setup the sql reporting service database using Reporting Services configuration Manager.

Issue: Immediately after the Crm installation, I was not be able to login to Crm with an error says cannot login with my current login.
Solution: Wait. It may take a moment for the changes in AD to take place.

Issue: SSRS errors: (rsReportServerDatabaseUnavailable) The report server cannot open a connection to the report server database.

Reporting Services requires two databases to run:

To solve the error mentioned above you need the following information:
What is the SQL Server Reporting Services instance you are trying to reach?
Where are the SQL Server Reporting Services databases hosted?

Once you located the SQL Server database instance where the ReportServer and ReportServerTempDB database are hosted you need to follow this checklist:
* Is the SQL Server database instance running? Is the SQL Server service started?
* Can you verify connectivity to the SQL Server database instance?
* Are the ReportServer and ReportServerTempDB databases attached and online?
* Does the Reporting Services service account have read/write access to the ReportServer and ReportServerTempDB databases?

Once all of this is verified to be true and issues have been fixed, than the last step would be to restart the Reporting Services instance. If everything is right you should be able to access your reports.

No comments:

Post a Comment