locked
Solution Import Error without message RRS feed

  • Question

  • Hey Guys,

    i have got troubles importing a default-solution (CRM 2013). The import procceds up to about 80% and fails. The strange thing is that the import diaolog does not contain any error-message-row as usual.

    If you look at the import-log you can not find any error message again. It seems that de import just stops. You can find the import log below.

    Does anybody know about this issue (it looks like there is something wrong with the sitemap-clientextention):

    <Row ss:AutoFitHeight="0" type="Bericht">
    				<Cell ss:StyleID="s137" name="Time">
    					<Data ss:Type="String">06:46:31.82</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="ItemType">
    					<Data ss:Type="String">Bericht</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Id">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Name">
    					<Data ss:Type="String">{744e3a45-f7fa-e011-b193-005056800000}</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="LocalizedName">
    					<Data ss:Type="String">Zielorientierter Status</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="OriginalName">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Description">
    					<Data ss:Type="String">Zielorientierten Status anzeigen</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Status">
    					<Data ss:Type="String">Verarbeitet</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="ErrorCode">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="ErrorText">
    					<Data ss:Type="String"/>
    				</Cell>
    			</Row>
    			<Row ss:AutoFitHeight="0" type="Clienterweiterungen">
    				<Cell ss:StyleID="s137" name="Time">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="ItemType">
    					<Data ss:Type="String">Clienterweiterungen</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Id">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Name">
    					<Data ss:Type="String">sitemap</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="LocalizedName">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="OriginalName">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Description">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="Status">
    					<Data ss:Type="String">Nicht verarbeitet</Data>
    				</Cell>
    				<Cell ss:StyleID="s137" name="ErrorCode">
    					<Data ss:Type="String"/>
    				</Cell>
    				<Cell ss:StyleID="s137" name="ErrorText">
    					<Data ss:Type="String"/>
    				</Cell>
    			</Row>



    Wednesday, April 29, 2015 7:50 AM

Answers

  • 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.

    Wednesday, April 29, 2015 1:39 PM
  • 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.

    Monday, May 4, 2015 6:00 AM

All replies

  • 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
  • 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
  • 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
  • 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
  • Hi,

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

    Wednesday, April 29, 2015 10:59 AM
  • 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.

    Wednesday, April 29, 2015 1:39 PM
  • You can check if event log has any error.

    Or open CRM server trace to have a look.

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

    Thursday, April 30, 2015 7:31 AM
  • 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.

    Monday, May 4, 2015 6:00 AM