1
I think its the way the third party dll is created, and there is nothing you can do to fix it
you can contact the product support and they may be able to help
0
you have to dig into further to findout that on the machine where error occurs
check the system event log if you can find any details or look on the third party documentation for this error.
0
But why it is working above .NET framework 3.5?