Share
Report
190Workflow is installed on the same host as SQL, when configuring the Workflow Setup with SMTP and email address, the test email failed with the message to enable CLR which I have with:
EXEC sp_configure 'clr enabled', 1; RECONFIGURE WITH OVERRIDE
The next message from the email test was an error loading the assembly id 65565.
An error occurred in the Microsoft .NET Framework while trying to load assembly id 65565. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: System.IO.FileLoadException: Could not load file or assembly 'microsoft.dynamics.gp.workflowgp.workflowengine, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A) System.IO.FileLoadException: at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString)
I enabled Trustworthy on the DYNAMICS and company databases with:
ALTER DATABASE TWO SET trustworthy ON
After making DYNSA a member of the sysadmin SQL role the test email would send successfully.
I do not believe I should have to enable the trustworthy option on the GP databases and have DYNSA as sysadmin for this to work.
Some background: These database were initially built and some initial setup done on another database server before being transferred to the final SQL server. Web Services was initially configured on another virtual server before being installed on the same host as SQL to consolidate servers.
I do not believe DYNSA needs to be sysadmin, how can I remove this work around?
Rich
*This post is locked for comments
All responses (
Answers (
