v2013.3.1316 over VS2013 Community Edition

Thread is closed for posting
3 posts, 0 answers
  1. TonyG
    TonyG avatar
    239 posts
    Member since:
    Feb 2006

    Posted 22 Feb 2015 Link to this post

    Per the subject, I'm trying to install an older version of JustCode into the current Visual Studio freeware. Unlike Express Editions, Community _does_ support extensions. The errors logged are below. I've rebooted and retried a few times. I confess that I am no longer under support and cannot yet load the latest version. If a later version overcomes this issue, so be it.


    Action start 9:15:00: PublishProduct.
    MSI (s) (B4:F8) [09:15:00:281]: Resolving source.
    MSI (s) (B4:F8) [09:15:00:281]: Resolving source to launched-from source.
    MSI (s) (B4:F8) [09:15:00:281]: Setting launched-from source as last-used.
    MSI (s) (B4:F8) [09:15:00:282]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\ProgramData\Telerik\Installer\Downloads\'.
    MSI (s) (B4:F8) [09:15:00:282]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\ProgramData\Telerik\Installer\Downloads\'.
    MSI (s) (B4:F8) [09:15:00:282]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{7F81EFE9-BF5B-4F9E-B72D-A8D75AC99E07}'.
    MSI (s) (B4:F8) [09:15:00:282]: SOURCEDIR ==> C:\ProgramData\Telerik\Installer\Downloads\
    MSI (s) (B4:F8) [09:15:00:282]: SOURCEDIR product ==> {7F81EFE9-BF5B-4F9E-B72D-A8D75AC99E07}
    MSI (s) (B4:F8) [09:15:00:282]: SECREPAIR: CryptAcquireContext succeeded
    MSI (s) (B4:F8) [09:15:00:283]: Determining source type
    MSI (s) (B4:F8) [09:15:00:283]: Note: 1: 2203 2: C:\ProgramData\Telerik\Installer\Downloads\JustCode_2013.3.1316.1_Dev.msi 3: -2147287038
    MSI (s) (B4:F8) [09:15:00:283]: Note: 1: 1316 2: C:\ProgramData\Telerik\Installer\Downloads\JustCode_2013.3.1316.1_Dev.msi
    MSI (s) (B4:F8) [09:15:00:283]: SECREPAIR: Error determining package source type
    MSI (s) (B4:F8) [09:15:00:283]: SECUREREPAIR: SecureRepair Failed. Error code: 524DD9357D8
    MSI (s) (B4:F8) [10:21:59:503]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (B4:F8) [10:21:59:503]: Product: Telerik JustCode Q3 2013 SP2 -- Error 1316. The specified account already exists.
  2. Steliyan
    Steliyan avatar
    45 posts

    Posted 23 Feb 2015 Link to this post

    Hi Tony,

    Thank you for contacting us.

    We have analyzed your reports and it seems that a Microsoft update is causing this issue. Here is more information: LINK
    To resolve this issue, I would suggest you to update your Windows to the latest version or apply the fix recommended by Microsoft. After applying the fix launch the installer and give it another try.

    Please let us know if the issue still exists.


    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. TonyG
    TonyG avatar
    239 posts
    Member since:
    Feb 2006

    Posted 23 Feb 2015 in reply to Steliyan Link to this post

    This system is fully patched to-date. But I did check the recommended KB. From there, I tried to load the KB hotfix, but it turns out the file is bad. (Yay Microsoft!) I spent the morning with Microsoft looking at my system. We tried a clean reboot and some other checks with no resolution. This was going down a rabbit hole that I needed to exit.

    I suspected the issue was that I loaded JustCode last year with one MSI to VS2010, and now I'm trying to install to VS2013 on this same system, perhaps with a different MSI. To test this and otherwise just try to "shake this loose", I removed JustCode from VS2010 and the completely uninstalled it. Then I reinstalled it for both VS2010 and 2013.


    Now, this should be of interest to anyone attempting to load a Telerik product into multiple VS environments on the same system, but over a period of time. For example, someone might logically try to install a new VS2015 side by side with their existing VS2013, and I'm guessing they could see the same issue. Telerik, please be aware of this so that someone can find this report if they have a similar problem - and avoid a call with Microsoft, to your Support, or endless Googling through random internet forums that don't have solutions. I'll ask Microsoft to update my trouble ticket and perhaps their KBs with a scaled down version of this info as well.

Back to Top