Solution Import Error without message

All replies

• 

  

  0

  Sign in to vote

  I tried to make a solution only with sitemap-clientextention. The import succeed if you import the unmanaged solution on the target system

  Wednesday, April 29, 2015 8:09 AM
• 

  

  0

  Sign in to vote

  Hi,

       Check the timeout settings for the SQL and CRM. If the solution is very big or bulky, this could happen.

  Hope this helps.
    
  -----------------------------------------------------------------------
  Minal Dahiya
  blog : http://minaldahiya.blogspot.com.au/

  If this post answers your question, please click "Mark As Answer" on the post and "Vote as Helpful"

   

  Wednesday, April 29, 2015 8:23 AM
• 

  

  0

  Sign in to vote

  I increased the values in the web.config located in C:\Program Files\Microsoft Dynamics CRM\CRMWeb to:

  <httpRuntime executionTimeout="3600" maxRequestLength="32768" requestValidationMode="3.0" encoderType="Microsoft.Crm.CrmHttpEncoder, Microsoft.Crm" />
  	
  ...
  
  <location path="MSCRMServices">
      <system.web>
  	  <httpRuntime maxRequestLength="20000" />

  The import fails again.

  I tried some furhter imports. If I import my solution to a new, blank organisation it will succeed. It seems to fail only on the my exitsting organisation, which i want to update with new functioniality.

  Are there any other timeouts, beside the web.conifg-settings I already did?

  Wednesday, April 29, 2015 9:33 AM
• 

  

  0

  Sign in to vote

  Hi,

      There are few things to check and fine tune. Here is the blog article for this:

  http://blogs.msdn.com/b/darrenliu/archive/2011/10/27/lesson-learned-import-failed-and-publish-failed.aspx

  Hope this helps.
    
  -----------------------------------------------------------------------
  Minal Dahiya
  blog : http://minaldahiya.blogspot.com.au/

  If this post answers your question, please click "Mark As Answer" on the post and "Vote as Helpful"

   

  Wednesday, April 29, 2015 10:30 AM
• 

  

  0

  Sign in to vote

  Hi,

  I already applied all these settings, but again no success.

  Wednesday, April 29, 2015 10:59 AM
• 

  

  0

  Sign in to vote

  If the import works on a blank, have you changed a field's type (delete and re-create as a different type like Two Options changed to Option Set)?

  I would make a new solution and try adding component by component (or small groups of components) until the import fails.

  • Marked as answer by k.duschlbauer Monday, May 4, 2015 5:56 AM

  Wednesday, April 29, 2015 1:39 PM
• 

  

  0

  Sign in to vote

  You can check if event log has any error.

  Or open CRM server trace to have a look.

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

  • Edited by Wilson Lou[MSFT] Thursday, April 30, 2015 7:33 AM

  Thursday, April 30, 2015 7:31 AM
• 

  

  0

  Sign in to vote

  Finally i solved the problem. It was similar to your assumption:

  We have the same field on both systems (created manually). The only difference was the the field-name on the source system was defined in lowercase and the one on the targt system in camel-case.

  • Marked as answer by k.duschlbauer Monday, May 4, 2015 6:00 AM

  Monday, May 4, 2015 6:00 AM