Skip to content

[BUG] Unable to install any tools due to SQL 4 CDS #1452

Description

@Russtagrammaton

I had an already reported issue on SQL 4 CDS where trying to export data or copy it was throwing an error after updating my tools. I saw that going back to 10.3.0 gets around the issue. After uninstalling the latest version the older version wouldn't install and keeps throwing DLL errors related to the sub folder. It just picks a random DLL in \AppData\Roaming\MscrmTools\XrmToolBox\Plugins\MarkMpn.Sql4Cds\ and tells me it can't install because one is running. I'm unable to install ANY tool now, no matter which one I pick, for this same issue. It's no longer exclusive to SQL 4 CDS.

I am on the latest version of XRMToolbox 1.2025.10.74 and I've even tried running off a "fresh install" though I accept that's unlikely to do anything due to the nature of it running through roaming.

Activity

  1. RaduChiran commented on Jun 3, 2026

    @RaduChiran

    I had the same issue and i manage to solve it in the following way:

    1. backup from xrm toolbix plugins golder, both the .dll AND the folder of SQL4CDS plugin as in images below:
    Image Image
    1. uninstall from xrm toolbox the sql 4 cds plugin. close xrm toolbox.
    2. come back in plugins folder, and now delete the folder "MarkMpn.Sql4Cds".
    3. open xrm toolbox and do a fresh installation of the plugin, BUT version 10.3.0. the latest version 10.4.3 would lead back to issues.
    4. you should hane no more errors, at least related to sql 4 CDS plugin
  2. Russtagrammaton commented on Jun 3, 2026

    @Russtagrammaton
    Author

    Ironically, I have just done this myself and was about to come back and post this solution!

    I'll add as well that I lost none of my many unsaved SQL queries should anyone come across this and fear that.

  3. BluFinSolutions commented on Jun 9, 2026

    @BluFinSolutions

    is this project still alive? since Nov 2025 no updates even with many open issues...

  4. MscrmTools commented on Jun 10, 2026

    @MscrmTools
    Owner

    Yes the project is still alive, but I'm on my own and cannot reproduce all errors/issues.

    This is why it's an open source project. People can help to reproduce errors and provide fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions