Share
ReportHello:
At the end of this posting is an error that I was getting here on my laptop with installs of both GP 2013 R2 and GP 2015. As I mentioned to Steve Erbach, in a posting from back in December, I resolved this error when I conducted a variation of steps listed in the following article that Steve attached, as follows:
support.microsoft.com/.../918040.
I had to conduct a variation of this article's steps, because I would only want DYNSA to be the database owner of the DYNAMICS database where this assembly lives.
First, I changed the DYNAMICS database's Trustworthy property to be "on". Secondly, I accessed the "Securables" section of the DYNSA login's properties and checked the boxes for "External access assembly" and "Unsafe assembly".
Afterward, I was able to send the test e-mail successfully!
The assembly that this error refers to is the Microsoft.Dynamics.GP.WorkflowGP.WorkflowEngine assembly.
Now, the only remaining question that I have refers to the steps that this article outlines and the steps that I took.
Does anyone know if setting the Trustworthy property of the DYNAMICS database causes issues and, likewise, does granting rights for DYNSA to "External access assembly" and "Unsafe assembly" cause any issues?
If I have to put this in place in production, this is a question that I need to know about. I will test in a separate test environment, of course. :)
Thank you, so much, everyone!
John
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
