Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Registration of Integration pack with Management server Failed

Answered Registration of Integration pack with Management server Failed

  • Wednesday, December 21, 2011 12:01 PM
     
     
    Sign In to Vote
    0

    While Modifying the Integration Pack for multiple times say more than 10*, then the registration of the Integration pack will get fail

    Please let me know the fix...

     

All Replies

  • Thursday, December 22, 2011 5:09 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Without knowing details I can only surmise that something is being corrupted along the way.  One quesiton would be why are you modifying the Integration Pack numerous times rather than testing your binaries using the "Invoke .Net" and "Monitor .Net" activities from the Integration Pack for .NET that comes included in the Toolkit?  The whole purpose of this IP is to allow you to test your binaries before packaging them up as distributable Integration Packs.

    Regards,

    Jeff.

     

     
  • Tuesday, January 24, 2012 1:11 PM
     
     
    Sign In to Vote
    0

    i also faced this problem, i think the following info may be helful.

    first of all make sure the previous version of IP is uninstalled through deployment manager or through control panel. This problem may also arise when you are upgrading an IP but you do not update the version number or keeping the version number same. Also make sure that "Upgrade from version:" checkbox is selected.

     

    Thanks,

    Vinay Ravish

     
  • Friday, August 17, 2012 7:13 PM
     
     Answered
    Sign In to Vote
    0

    We had the same problem and reported an incident with Microsoft. We're requesting a fix. Interestingly, Jeff Fanjoy responded with the following:

    

    I followed up with our Product Group and confirmed that we do in fact do a string compare rather than a numeric compare when checking if the Integration Pack represents an upgrade to a previous version. As a result “1.10” is considered a lower version than “1.9” since it does the comparison character by character “1” = “1” then “.” = “.” And finally “1” < “9” resulting in a determination that the new Integration Pack is actually an older version.

    So your options would be:

    1. Use the workaround that I provided in my previous email to artificially change the version of the Integration Pack as stored in the database.

    2. Re-package your Integration Pack setting the major version to “2” and the minor to “0” which should definitely be recognized as a newer version.

    My recommendation would be to pursue option #2 since that does not have you making changes directly to the database which is something that we discourage unless it is absolutely necessary.

    Regards, JEFF FANJOY

    Senior Support Escalation Engineer

    Glenn Puchtel