Plugin encountered an exception when compiling during logon
Hi,
I'm getting these errors on my Production API server, it seems to happen within a few hours to a day of when these plugins are modified. It's not specific to any one plugin. I've seen at least three give this error.
Plugin 'plugin name' encountered an exception when compiling or loading during logon. Exception Message: 'System.IO.IOException: The process cannot access the file 'pluginname.dll' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveFile(CopyOrMove operation, String sourceFileName, String destinationFileName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyFile(String sourceFileName, String destinationFileName, Boolean overwrite)
at JiwaFinancials.Jiwa.JiwaApplication.Plugin.Plugin.LoadAssembly()
at JiwaFinancials.Jiwa.JiwaApplication.Plugin.Plugin.Load()
at JiwaFinancials.Jiwa.JiwaApplication.Plugin.PluginCollection.()
at JiwaFinancials.Jiwa.JiwaApplication.StartupLog.Add(String Description, Action CallbackMethod)
at JiwaFinancials.Jiwa.JiwaApplication.Plugin.PluginCollection.Compile()
It's causing errors like "Custom field with Setting Name 'OpportunityID' not found" when making requests to our API, i'm guessing, because the plugin containing that custom field isn't compiling.
But it could be session based, because I made a request from a different device (with different user & token, and a SalesQuoteGETRequest instead of SalesQuotePOSTRequest) and it returned the Quote entity including the OpportunityID custom field. Therefore the custom field plugin was working for that session.
If i restart the API service the problem goes away.
This reminds me of https://service.jiwa.com.au/servicedesk ... /JIWA-9388 that we've reported, but have been unable to reliably reproduce. In that issue, the problem was always fixed by restarting the API, was difficult to reproduce, and behaviour could vary based on user/token.
Do you have any ideas what I could do to troubleshoot?
We're running JIWA SR12 7.2.1
REST API 7.2.1.23
API Server is using the self hosted service behind reverse proxy.