Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not load file or assembly CINTEROS.XRM.FETCHXMLBUILDER.DLL #1318

Open
rvroemen opened this issue Feb 8, 2024 · 3 comments
Open

Could not load file or assembly CINTEROS.XRM.FETCHXMLBUILDER.DLL #1318

rvroemen opened this issue Feb 8, 2024 · 3 comments
Labels

Comments

@rvroemen
Copy link

rvroemen commented Feb 8, 2024

On a new computer I downloaded the latest version of XRM Toolbox.
After extracting the files and starting XRM Toolbox, I get the following message:

Could not load file or assembly CINTEROS.XRM.FETCHXMLBUILDER.DLL or any of its dependencies. Attempted to load a program with an incorrect format.

Exception: System.BadImageFormatException

@rvroemen rvroemen added the bug label Feb 8, 2024
@MscrmTools
Copy link
Owner

Hi,
FetchXmlBuilder is not part of a clean installation of XrmToolBox. Are you using a network roaming profile in your company so that your new computer got content from your older profile?

@astepforward
Copy link

astepforward commented Aug 12, 2024

I have the exact same scenario. I download the latest version from https://www.xrmtoolbox.com/ and get the same error.

Obviously, I don't have FetchXmlBuilder installed. Also, I'm using my personal computer and not connecting to any VPN's while opening the tool. At the same time, I have XrmToolBox v1.2021.9.52 on my work laptop and it works flawlessly.

I resolved the issue this way:
I removed my old config data here: %APPDATA%\MscrmTools\XrmToolBox.

It would be nice to not have to do all required steps by myself once I've downloaded the tool. Some prompt maybe, asking if I want it to clean/change all required things for me? And not blocking the loading process?

@MscrmTools
Copy link
Owner

MscrmTools commented Aug 23, 2024

The only way to handle that would be to search for a dummy file (like "initialized.txt") to detect if it's a new install. If so, I can look in the storage folder if files exist. If so, warn the user and allow to delete existing content.
Then create the file "initialized.txt" so that next run does not repeat the process.

Do you think it could be enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants