All im saying is this is from Epicor, it is recommended, but not required and a graceful fallback will happen.
If the .NET 6 SDK is not installed on the client, the BPM designer will gracefully fall back to using .NET Framework 4.8 after giving the warning.
Which doesnt seem to be true 
Hi Scott, I have exactly the same error, Epicor recommend the following steps, didnt work for me but maybe for you.
OK - In that case, I think I found a case for another customer that had a similar issue. It appears this may be workstation related. Can you please go try logging into another workstation and performing the same test there? Try a couple other workstations if possible. This may be a localized .NET issue. My guess is, if you went into a BPM Method Directive and tried using the Directive Design window, you’d get similar errors. We’ve had a few other reports of this and although we don’t know what is causing it because we’ve been unable to duplicate it, the thought is there is a .NET conflict with another application on your server. So far, only advanced developer type users have reported this issue. So it may be a conflict with another development related tool. Dev has stated that they have seen cases where .net has to be uninstall and reinstalled multiple times and then it started working. Can you uninstall .net and reinstall .net48 and .net6.0.403 SDK. One developer mentioned to make sure its the SDK, not runtime. If this does not help, they suggested to delete the client folder from the problem workstation and copy the client folder from a working computer and put there. Scott
Hi
I have gone down the .Net rabbit hole, and I don’t see any more light.
This is mostly over my head, and the multiple iterations of .Net Framework, .Net SDKs, .Net Runtimes have left me behind.
I have burnt more vacation time than I should have.
I think this is headed to “another Epicor problem that cannot be duplicated by Epicor – do another update and do the Epicor prayer.”
I can uninstall and reinstall the sdk and runtime. Nothing changes here.
I don’t see how to uninstall the actual .net framework.
I agree that it is definitely an individual computer problem.
Two App servers do not have a problem.
An old laptop without any dotnet directory does not have a problem.
An old desktop with runtime v5 does not have a problem.
Some computers with the problem do not see the “dotnet” command unless you drill down into the actual directory.
In the registry, I do see Version=v4.8 on every computer in this mess.
Time to move on to the deleting the client when I go back into the office.
Thank you
Scott
What about if you just ignore it and save code anyway, Will it build on server after that on directive save?
Good Morning,
Has this issue been solved?
I am having the same issue. I have a very simple UBAQ. The UBAQ will work on another workstation with no errors, but on my workstation I get a long list of errors. Just like the above posts, I have similar error messages:
Second error message for UBAQ.docx (24.1 KB)
Epicor has told me almost the exact same advise as Raul Dominguez received in December 2022. I have copied the Epicor client from the no error workstation and installed it on my computer. No solution. I have installed .NET SDK 6.0.405. No solution. I have not been able to reinstall .NET 4.8. The installation was blocked. Is it safe to remove .NET 4.8 and then re-install? .NET 4.8 is also not showing up as an un-install option.
Any recommendations?
I see you have the .Net 6 sdk, so we can omit that.
Uninstall your client completely.
DELETE the folder.
Reinstall.
I have been getting the “System.Void” errors when checking syntax on a simple custom code box and when trying to Validate a BPM (on my main machine). On my old PC I do not get these errors.
I Uninstalled the SmartClient, Deleted the Epicor folder, reinstalled the SmartClient, and I continue to see the errors.
What has worked for others to get rid of this annoyance?
Have you installed the .NET 6 SDK?
yes,
Well dang. We’ve all tried to get a definitive answer on this, but what has worked for some has not
always worked for others.
At this point, I would go (near) nuclear.
Uninstall Epicor, Delete Folder. Delete All Epicor Data From Program Data, and Local AppData.
Remove the .NET SDK.
Reboot and Reinstall all of them.
If that doesn’t work, I’m out of ideas.
I uninstalled Epicor, Deleted the Epicor folder, Deleted the Epicor folder in Program Data, a search of the Program Files and Program Files (x86) yielded no results for Epicor. I uninstalled the .NET SDK. Rebooted, installed .NET SDK:
Rebooted again. Then installed the Epicor Smart Client but still getting the errors.
I think Epicor is out of ideas too.
so did you try just ignore it and continue? Build on save happens on server and should not have this problem.
That of course works, if his programming is correct, but makes it very difficult to develop/debug, especially for beginners.
i agree, but i don’t know how to repro it to be more specific.
Technically speaking, what else can be reviewed:
We know this is machine-specific, so probably it could be connected with client folder itself.But people say reinstall does not help.
What else can be involved? .Net version? Same versions work for some and not for others. What else? Some registry for .NET? .Nuget folder?
idk. Maybe, people can run Process Monitor for Epicor.exe to compare with working machine, but there will be ton of entries.
Yeah we’re lost too. Mine was fixed with a simple install of the .NET 6 SDK.
It seems this symptom can manifest many ways.
Hello,
I wanted to provide an update. I have un-installed and re-installed Epicor a third time. I have not found a fix for my problem yet.
My problem keeps getting worse. Epicor Pilot had an update over the weekend. We are a multi-tenant customer and receive all updates.
Now I am not able to get into the Part, Part Tracker, and Part Transaction History Tracker. Each screen errors out with the following message:
==================
AppServer Connection: https://ausmtsPilot102.epicorsaas.com/SaaS201Pilot
Form Name: ShellMenuForm
Customization Name:
Menu ID:
Software Version: 4.2.200.11
============
Application Error
Exception caught in: Erp.UI.PartEntry
============
##!Message:##! Could not load file or assembly ‘Erp.Contracts.BO.Part, Version=11.2.200.0, Culture=neutral, PublicKeyToken=5d3fa3c7105d7992’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
##!Program:##! Erp.UI.PartEntry.dll
##!Method:##! TransactionLoad
==================
at Erp.UI.App.PartEntry.PartTransaction.TransactionLoad()
at Ice.Lib.Framework.EpiTransaction.createTransaction()
This problem is with my workstation. I can go to another workstation and login using my credentials and have no errors. I am also a system administrator and there was mention that it is affecting system admins.
I am at a lose on how to fix this issue and advice would be helpful.
At this point I would cut my losses and reinstall Windows, just to be honest.
reinstall cient, you have obsolete Erp.Contracts.BO.Part, probably you did not logoff before upgrade?
Hi Olga,
Can you please give me step by step directions for the re-install of the client? I believe that I logged off of Epicor Live and Epicor Pilot. We still use Epicor classic display and I just closed the window with the X in the upper right corner. I know of no way to “log off” on the classic display, other than the red X.
When I did the re-install of Epicor Live and Pilot, in Epicor Live I can open the Part, Part Tracker, and Part Transaction History screen but in Epicor Pilot I have the errors. I completed the re-install all at the same time.
Thank you for the quick response,
Heide
I don’t have the steps. In your case, you should start from empty client folder - delete it or rename for reference. Probably copy from the working machine and check if that will resolve the issue with BPM references you have.
