Increase the Maximum Number of Records Exported from Excel

Microsoft Dynamics CRM by default will allow an export from CRM to Microsoft Excel of up to 10,000 records. If you are trying to export more than 10,000 records, CRM will allow the export, however there is no warning that only 10,000 of your 10,000+ records just exported. The solution for this is to increase the size of your export by changing a database value.

To do this, perform the following steps (applies to CRM 4.0, 2011, 2013, 2015):

1. Open SQL Management Studio
2. Use the _MSCRM database
3. Open the OrganizationBase table
4. Locate the column - MaxRecordsForExportToExcel
5. Change the value to the new value

For a link to Microsoft's KB Article supporting this, please visit

Dynamics GP Excel Drillback. A connection Microsoft Dynamics GP could not be established. Be sure you are logged on to the appr

According to the following link :

If you're moving your Microsoft Dynamics GP databases and you use the drilldown functionality in the SQL Server Reporting Services or Excel integrated reports, you need to follow the steps below in order to update your server links so the drilldowns will continue to work after the server move:

1. Ensure that everyone has logged out of Microsoft Dynamics GP and close all instances of SQL Server Management Studio.

2. On a machine where Dynamics GP is installed click on Start, then point to All Programs. Then click to expand Microsoft Dynamics, then GP and click on Database Maintenance.

3. When the utility opens select or enter the SQL Server instance name where the Dynamics GP databases are stored. If you are logged in as a domain account with rights to this SQL Server instance you can select the Windows Trusted Authentication method. Otherwise select SQL Authentication and enter an appropriate user name and password. Click Next.

4. Select Mark All to choose each of the Dynamics GP databases. Click Next.

5. Select the Microsoft Dynamics GP product. Click Next.

6. Select Functions and Stored Procedures. Click Next.

7. Review the confirmation window. Click Next to begin the process.

Note: This process can take some time to run. It will depend on the number of products installed along with the number of databases that need to be addressed. Once this process has completed, your external report drilldowns will work in the new S

GP 2013 and 2015 GP Web Services "Exception message: The security object does not exist"

After moving the GPWEBSECURITY database for GP Web Services and running a repair we received the following error opening the Security Console:

"Exception message: The security object does not exist. Missing Key: 25cc1a21-2cc4-4b13-a1c8-eea186fb688a"

Turns out we ran the wrong repair.  DO NOT run the repair from the GP Web Services Configuration Console.  Instead, launch the GP Setup.exe from the GP installation media.  This will detect the existing install and give you the option to repair.I used information from the following link and updated it for the new web services that does not run in IIS:

To determine the scopes in the ADAM database, use the Authorization Manager (Azman.msc) Microsoft Management Console (MMC) snap-in to browse the database. To do this, follow these steps:

  1. Click Start, click Run, type azman.msc, and then click OK.
  2. On the Action menu, click Open Authorization Store.
  3. Click Active Directory.
  4. In Windows Explorer, open the following folder:
    C:\Program Files\Microsoft Dynamics\GPWebServices\WebServices
  5. Use Notepad to open the DynamicsSecurity.config file.
  6. Copy the following value for the AzManConnectionString setting:
    mssql://Driver={SQL Server};Server={MySqlServer\MyInstance};/GPWEBSECURITY/DynamicsGPWebServices
  7. Paste the value into the Store Name field in the Open Authorization Store window, and then click OK.
  8. Expand the DynamicsSecurityService store.
  9. Expand 25cc1a21-2cc4-4b13-a1c8-eea186fb688a to view the scopes. A folder graphic designates the scopes that are installed and that have an assigned integer value.

I was able to verify that the database in the new GPWEBSECURITY database did not contain the data from the original database.  I restored from backup.  Reran the repair.

NOTE: I also had to search all .config files in the install folders for the original MyOldSqlServer\MyOldInstance and replace it with the MyNewSqlServer\MyNewInstance.

I used FNR.exe from codeplex.

SSRS Report Builder "Application cannot be started, contact application vendor."

When trying to launch Report Builder you receive the error "Application cannot be started, contact application vendor."

I did two things that seemed to of helpled.

1. Open SSMS and connect Server type "Reporting Services", Server name. Right Click the Server Name in Object Explorer and pick Properties. Under Advanced setting in the Reports section set the ReportBuilderLaunchURL to https://serverurl/ReportServer/Report/BuilderReportBuilder_3_0_0_0.appli....

2. Create a Web.config file in the C:\Program Files\Microsoft SQL Server\MSRS11.instancename\Reporting Services\ReportServer\ReportBuilder folder containing the following

<?xml version="1.0" encoding="utf-8"?>
<compilation tempDirectory="C:\Program Files\Microsoft SQL Server\MSRS11.instancename\Reporting Services\RSTempFiles\"/>

Management Reporter 2012 on GP 2015 Couldn't retrieve the list of available databases: The connection attempt failed.

While trying to configure Management Reporter 2012 on a brand new install of GP 2015 I received the following error:

"Couldn't retrieve the list of available databases: The connection attempt failed."

Configuration is SQL 2012 on Server 2012 R2, GP 2015 on Server 2012 R2.

Solution: Install Dexterity Shared Components 12 from the install disc for GP2013 R2.

I found the answer here:

Thank you to Richard Markham.

Syndicate content