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

[BUG]Xrm toolbox for MS dataverse and MS dynamics 365 unhandled exception #1374

Open
Sarahhiggins1 opened this issue Dec 17, 2024 · 4 comments
Labels

Comments

@Sarahhiggins1
Copy link

Describe the bug
I updated to the latest version of the xrm toolkit (i had to do an uninstall and start over), I'm able to download some of the tools from the library but when I try to download the Bulk Data Updater, I get thr following error.

Xrm ToolBox for Microsoft Dataverse and Microsoft Dynamics 365 (v1.202...

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

An error occured while copying files: The process cannot access the file C:\Users\higgis\AppData\Roaming\Mscrm Tools\Xrm ToolBox\Plugins\R appen.XTB.BDU\System.Collections.Immutable.dll' because it is being used by another process.

Trying to install the Bulk Data Updater from.the Tools Library.

Expected behavior
Successful install

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • XrmToolbox Version - 1.2024.9.69
  • Tool version

Additional context
Add any other context about the problem here.

@erikhagby-ae
Copy link

Same problem here. No issue before update to latest version.
I'm trying to use the Easy Translator plugin

@MscrmTools
Copy link
Owner

@rappen Can you check if it's possible to install a new tool of yours when another one has been already used?

@MscrmTools
Copy link
Owner

@erikhagby-ae Can you provide steps repro + screenshot?

@erikhagby-ae
Copy link

@erikhagby-ae Can you provide steps repro + screenshot?

Issue was "resolved" by deleting connection and creating a new connection. As I don't have the old connection it is hard to reproduce, but I assume the issue was related to upgrade of version. It worked fine in the old version 1.2023.xxxx something, then after upgrade to 1.2024.9.69 this became an issue.

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