Callwrapper Help

From GAB Help
Jump to: navigation, search

This page exists to help troubleshooting issues with implementing callwrappers.

Typical Errors

Generally, the implementation callwrapper goes through various checks and tests to verify its proper functionality, so it's very rare that is issue is coming from the callwrapper itself.
Here are some common errors you might run into and how to resolve them:

GAB Execution Error

GabError.png
This is because the GSSEO.Callwrappers.dll you are using is not up-to-date and the callwrapper you are trying to use is not referenced in the dll you are using.

Fix: Update the GSSEO.Callwrappers.dll

TargetInvocationException

When receiving and error similar to:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. 
---> GSSEO.Callwrappers.CallwrapperException: Error launching Fujitsu task.  Exception has been thrown by the target of an invocation. 
---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. 
---> System.NullReferenceException: Object reference not set to an instance of an object.

This is most likely due to the GSSEO.Callwrappers.dll not existing where it is trying to be called. Or the references are out of date

Fix: Update/get the GSSEO.Callwrappers.dll and/or references. Also make sure you have the dlls of the core programs you are trying to use with the callwrapper.

Fix: Also, make sure you have a STDCONFI.txt file at X:\Testing\STDCONFI.txt. It can be a blank file.

Any kind of NullException

Most common reason for this error is due to the GSSEO.Callwrappers.dll is NOT in the PLUGINS folder of the Clinic's directory that is being tested on.

Fix: Ensure that the GSSEO.Callwrappers.dll is inside the PLUGINS inside the clinic's directory you are using


Other errors

Other things to check if the error persists:

  • Make sure the GSSEO.Callwrappers.dll is the correct version
  • Make sure the Clinic's file structure has all the needed dlls in the BIN folder
  • Make sure the callwrapper's property values conform to their types and requirements according to their documentation. Specific callwrapper documentation may have special requirements you need to adhere to for proper functionality.
  • Ensure that references are up to date in the BIN folder; if you build to LocalGlobal\BIN, you can delete everything there. Sometimes, the callwrapper will execute here in certain cases.