Home › Forums › Model Expert queries › LogicNP.CryptoLicensing Could not load file
Home › Forums › Model Expert queries › LogicNP.CryptoLicensing Could not load file
- This topic has 6 replies, 2 voices, and was last updated 7 years, 9 months ago by Barrie Treloar.
-
AuthorPosts
-
6 February 2017 at 10:08 pm #9479Barrie TreloarParticipant
When I click the “Start Analysis” button I get the following error:
[code]See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly ‘LogicNP.CryptoLicensing, Version=6.0.0.0, Culture=neutral, PublicKeyToken=4a3c0a4c668b48b4’ or one of its dependencies. The system cannot find the file specified.
File name: ‘LogicNP.CryptoLicensing, Version=6.0.0.0, Culture=neutral, PublicKeyToken=4a3c0a4c668b48b4’
at Model_Expert.frmMXAnalyse.btStart_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLMSoftwareMicrosoftFusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLMSoftwareMicrosoftFusion!EnableLog].************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
—————————————-
Model_Expert
Assembly Version: 1.0.0.3
Win32 Version: 1.0.0.3
CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Model_Expert.DLL
—————————————-
Interop.EA
Assembly Version: 2.10.238.1
Win32 Version: 2.10.238.1
CodeBase: file:///C:/Program%20Files%20(x86)/Sparx%20Systems/EA/Interop.EA.DLL
—————————————-
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
—————————————-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8750 (QFE.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
—————————————-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
—————————————-
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
—————————————-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
—————————————-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
—————————————-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
—————————————-
System.Xml.Linq
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8763 built by: WinRel
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll
—————————————-************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.[/code]
7 February 2017 at 3:44 pm #9480eadocX SupportParticipantThis means that the installation didn’t work, because Model Expert can’t find the Crypto sub-system. This should have been installed when you installed Model Expert.
I suggest you de-install MX, clean-up your registry if you are will & able, and re-install MX.8 February 2017 at 11:14 pm #9481Barrie TreloarParticipantI’ve uninstalled, and re-installed.
But I get the same error.If you tell me which reg keys to fiddle with I can try that too.
23 February 2017 at 10:42 pm #9482Barrie TreloarParticipantIs there something else you would like me to try to get this to work?
Cheers
16 March 2017 at 4:51 pm #9483eadocX SupportParticipantI think I may have an answer for this.
It looks like in the last build of Model Expert I forgot to include that Crypto DLL in the installer: the reason we didn’t see it before is maybe because most other customers already use eaDocX: do you have eaDocX?
If not, then please download and install the eaDocX Trial – this will install the relevant Crypto bits on your machine, until I can get out a new installer.
Sorry for the bother.
Ian16 March 2017 at 7:40 pm #9484Barrie TreloarParticipantNo, I don’t have eaDocX.
I’ll try installing that as well and let you know.16 March 2017 at 7:45 pm #9485Barrie TreloarParticipantYes, Model Expert now runs without the crypto error.
-
AuthorPosts
- You must be logged in to reply to this topic.
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download