Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Import limits on number of records RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I seem to be limited to importing 15 records at a time. Since I have about 500 records for accounts and about 3000 records for Contacts. This really is time consuming, when it should be a piece of cake. What am I missing?
    Sunday, July 12, 2009 11:05 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi
    like donna said "ther is no limit"

    this might be a sql timoe out condition.

    add the sql timeouts in your registry and see if this sorts out your problem.
    Also create a excel export form CRM and then add your data in that file and then import the file again.

    Method 1: Add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values

    Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
    3. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
    4. Rename the DWORD value to the following value:
      OLEDBTimeout
    5. Right-click the DWORD value, and then click Modify.
    6. In the Edit DWORD Value dialog box, type 86400 in the Value data box, click Decimal in the Base option, and then click OK.

      Note According to the requirement of the computer that is running SQL server and the number of customization files, the value can be larger than 86400. The value of 86400 is equivalent to 24 hours.
    7. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
    8. Rename the DWORD value to the following value:
      ExtendedTimeout
    9. Right-click the DWORD value, and then click Modify.
    10. In the Edit DWORD Value dialog box, type 1000000 in the Value data box, and then click OK.

      Notes
      • In the Value data box, you can type a value that is larger than 1,000,000. However, do not type a value that is larger than 2,147,483,647. This is hexadecimal 0x7FFFFFFF.
      • If this key already exists, notice the current value. After you have completed the import or the upgrade for Microsoft Dynamics CRM, set the value of this key back to the original value or delete the key if it did not previously exist. The default OLEDB timeout value is 30 seconds.
    Method 2: Modify a parameter in two different Web.config files
    1. Click Start, click All Programs, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
    2. Expand the server name, and then expand Web Sites.
    3. Right-click the Microsoft CRM v3.0 Web site or the Microsoft CRM v4.0 Web site, and then click Open.
    4. Right-click the Web.config file, click Open With, and then click Notepad.
    5. In Notepad, locate the following line. 
      <httpRuntime executionTimeout="300" maxRequestLength="8192"/>
    6. Increase the "8192" value to a value that is large enough to handle the Customization.xml file.
    7. Save and then close the Web.config file.
    8. In the directory in which you opened the Web.config file, open the MSCRMServices folder.
    9. Right-click the Web.config file, click Open With, and then click Notepad.
    10. In Notepad, locate the following line. 
      <httpRuntime maxRequestLength="8192"/>
    11. Change the "8192" value to the value that you specified in step 6.
    12. Save and then close the Web.config file.
    Tiaan van Niekerk http://crmdelacreme.blogspot.com Skype:tiaan.van.niekerk1
    Tuesday, July 14, 2009 5:15 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Could you let us know of the following:
    1# Are you using the Data Migration Manager or CRM Import Tool?
    2# CRM 3.0 or CRM 4.0?

    Best Regards,
    Gagandeep Singh
    http://mscrmnovice.blogspot.com
    Sunday, July 12, 2009 11:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    CRM does not have a 15 record import restriction for a 'standard' or 'default' installation.  What is the behavior you are seeing?
    Best Regards, Donna
    Monday, July 13, 2009 7:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi
    like donna said "ther is no limit"

    this might be a sql timoe out condition.

    add the sql timeouts in your registry and see if this sorts out your problem.
    Also create a excel export form CRM and then add your data in that file and then import the file again.

    Method 1: Add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values

    Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
    3. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
    4. Rename the DWORD value to the following value:
      OLEDBTimeout
    5. Right-click the DWORD value, and then click Modify.
    6. In the Edit DWORD Value dialog box, type 86400 in the Value data box, click Decimal in the Base option, and then click OK.

      Note According to the requirement of the computer that is running SQL server and the number of customization files, the value can be larger than 86400. The value of 86400 is equivalent to 24 hours.
    7. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.
    8. Rename the DWORD value to the following value:
      ExtendedTimeout
    9. Right-click the DWORD value, and then click Modify.
    10. In the Edit DWORD Value dialog box, type 1000000 in the Value data box, and then click OK.

      Notes
      • In the Value data box, you can type a value that is larger than 1,000,000. However, do not type a value that is larger than 2,147,483,647. This is hexadecimal 0x7FFFFFFF.
      • If this key already exists, notice the current value. After you have completed the import or the upgrade for Microsoft Dynamics CRM, set the value of this key back to the original value or delete the key if it did not previously exist. The default OLEDB timeout value is 30 seconds.
    Method 2: Modify a parameter in two different Web.config files
    1. Click Start, click All Programs, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
    2. Expand the server name, and then expand Web Sites.
    3. Right-click the Microsoft CRM v3.0 Web site or the Microsoft CRM v4.0 Web site, and then click Open.
    4. Right-click the Web.config file, click Open With, and then click Notepad.
    5. In Notepad, locate the following line. 
      <httpRuntime executionTimeout="300" maxRequestLength="8192"/>
    6. Increase the "8192" value to a value that is large enough to handle the Customization.xml file.
    7. Save and then close the Web.config file.
    8. In the directory in which you opened the Web.config file, open the MSCRMServices folder.
    9. Right-click the Web.config file, click Open With, and then click Notepad.
    10. In Notepad, locate the following line. 
      <httpRuntime maxRequestLength="8192"/>
    11. Change the "8192" value to the value that you specified in step 6.
    12. Save and then close the Web.config file.
    Tiaan van Niekerk http://crmdelacreme.blogspot.com Skype:tiaan.van.niekerk1
    Tuesday, July 14, 2009 5:15 AM