locked
SQL Server error occurred in CRM 4.0 RRS feed

  • Question

  • Hi,

    I was trying to import my customized entity from one organization to another organization.
    While importing, an error is showing: A SQL Server error occurred. Either the file could not be uploaded or import failed.
    Can you please help to resolve this.
    Thanks.

    • Edited by rittu123 Wednesday, December 30, 2009 8:14 AM
    Wednesday, December 30, 2009 8:07 AM

Answers

  • Has the production system been upgraded from CRM 3.0 to CRM 4 in the past?

    There was a hotfix issued to address the SQL error that occurs during importing certain types of customizations.
    • Marked as answer by Jim Glass Jr Wednesday, December 30, 2009 5:37 PM
    Wednesday, December 30, 2009 2:01 PM
    Moderator

All replies

  • Hi,

    You can try to reset IIS and then try to import again.
    And if possible try to import your customizations in small chunks.

    Hope it will help you !!


    Mahain
    Wednesday, December 30, 2009 8:13 AM
    Moderator
  • I have reset IIS. It is not importing again.
    Thanks.
    Wednesday, December 30, 2009 8:19 AM
  • Ok,

    Just check Is there any mismatch of datatype for field in any entity between these organization ???

    Mahain
    • Proposed as answer by HIMBAPModerator Wednesday, December 30, 2009 9:56 AM
    Wednesday, December 30, 2009 8:22 AM
    Moderator
  • The easiest solution is to take a trace using CrmDiagTool during importation...

    You will then find the real SQL error message and not that inunderstandable generic message 

    My blog : http://mscrmtools.blogspot.com
    You will find:
    Form Javascript Manager (export/import javascript from forms)
    ISV.Config Manager (graphical ISV.config edition - export/import)
    View Layout replicator (customize one view and replicate to others)
    And others (use tool tag on my blog)
    Wednesday, December 30, 2009 8:25 AM
    Moderator
  • i have added a new field in the organization from where i am importing.
    Wednesday, December 30, 2009 8:29 AM
  • whether CrmDiagTool4.zip is enough?
    Wednesday, December 30, 2009 8:38 AM
  • Hi Rittu123,

    Adding new field won't create this problem but if datatype of the same field differs in these organizations, this could be the reason.

    Also Agreed with Tanguy,it's better to trace to get real culprit you can use CrmDiagTool or enable default tracing

    Check this link to enable tracing

    http://support.microsoft.com/kb/907490


    Hope it will help you !!!
    Mahain
    • Proposed as answer by HIMBAPModerator Wednesday, December 30, 2009 9:58 AM
    Wednesday, December 30, 2009 8:40 AM
    Moderator
  • i have enabled tracing. there is a datatype mismatch for a field in the entity.
    thanks.

    Wednesday, December 30, 2009 9:31 AM
  • Make sure that you have unique attribute name.
    My Dynamics CRM Blog: http://bovoweb.blogspot.com
    Wednesday, December 30, 2009 12:18 PM
  • Has the production system been upgraded from CRM 3.0 to CRM 4 in the past?

    There was a hotfix issued to address the SQL error that occurs during importing certain types of customizations.
    • Marked as answer by Jim Glass Jr Wednesday, December 30, 2009 5:37 PM
    Wednesday, December 30, 2009 2:01 PM
    Moderator