I am submitting this help request on behalf of our Network team. One of our users who is on Windows 10 just recently had his Solid Works app updated and since then whenever he tries to open an Epicor application that has a customization tied to it he gets a message that he needs to open it in developer mode.
If he logs into my Windows 10 box with his profile and logs into Epicor with his profile everything is fine.
If I go to his desktop and login with my Windows profile and Epicor login I get the same error message that he is getting.
My thought is it has to be a Windows setting, but nothing has changed with his Windows other than the Solid Works update.
Any ideas or suggestions from anyone on what they can try?
All the engineers have Solid Works installed and they all had the same upgrade done to their systems and they have no issues.
Yesterday, they took one the workstation (which was currently not being used) and set this particular user on this workstation.
We also created a new Epicor User ID for this engineer and the same error message came up that the engineer needed to log in as Developer because there was
a compile issue.
My thought had been that perhaps a personalization done on the Windows display itself was creating the issue because in the past we had a few users that had
changed their windows font size and after they had done this they would get an application error on modules that had customizations tied to them.
But, when they set up this users on a different workstation and he is having the same issue that ruled out that theory.
Below is another application error that had popped up … I think it is related (perhaps that is why it will not compile)… so now investigating outlook.
Does anyone know if there are different MicrosoftOffice.Interop.Outlook.dll’s for Outlook2010 VS Outlook2007?
I’d bet that there is some shared DLL between Solid Works and Epicor, and Soild Works updated/tweaked it.
It’s rather time consuming but do a file compare between E10 client folder on an unaffected machine and the affected one.
The following in a batch file compares the DLLs on the local machine (L:) to those in a directory on a remote system (R:)
net use L: C:\Epicor\ERP10.2Client_PRD\Client
net use R: \\usdcaaps00371\c$\Epicor\ERP10\LocalClients\PRD_102300
for %%f in (L:\Astria.Framework.*.dll) do @fc %%f R:\%%~nxf >> fc.log
Someone has a Customization Layer that uses the Office Interop which is used to interact with Outlook, its not standard Epicor and usually ships with Office.
It says access denied, so looks like a permissions issue loading the dll. If you have them on a UNC Path it might be blocked by GPO, I cant remember now but there was something we had to enable for Assemblies to be loaded from UNC.
Find the dll you find the problem. Perhaps you were loading the dll from the SolidWorks folder and you need to change the permissions - or - the Interop is being denied by Outlook from reading Distribution Groups. Either way, a permissions issue somewhere.
