10-31-2013 01:55 PM
10-31-2013 02:28 PM
I've seen this error before when publishing a script that uses an imported assembly. The only workaround I have found so far is to publish my script from the same PC where I originally imported the DLL. If anyone has a better solution, I'd love to hear it, as this is something of a nuisance.
11-21-2013 08:15 AM
Hey Scott,
Were you ever able to fix this by using the suggestion? That error is pretty strange and I haven't seen it before.
11-21-2013 10:07 AM
I am not receiving this error anymore. I performed a reset of the appserver and it seemed to fix itself. Thanks!
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.