# Troubleshoot an Adapter blade

If your new Integration Adapter blade won’t start properly, or misbehaves when running, have a look at this checklist of commonly occurring faults:

* Have you forgotten to create a _var_ directory in the blade?

  Its path in the Deployment Framework is:

  _<Framework-root>/kits/<blade-name>/DataSource/var/_
* Have you set up the server hostnames for the blade?

  See [Change server hostnames](cdf-change-server-specific-configuration.md#change-server-hostnames) in How Can I... [Change server-specific configuration](cdf-change-server-specific-configuration.md).
* Is there erroneously more than one instance of the Integration Adapter running? 
  * For Integration Adapters that connect to the Liberator, you can easily check this by looking at the [Liberator’s status page](../liberator/liberator-liberator-status-web-page.md), where you’ll find that the DataSources section shows the Adapter as a flashing entry.
  * For Integration Adapters that connect only to the Transformer, look in the _servers/Transformer/var/transformer.*_ files on the server under which the Transformer is running, and check for multiple peer connection and disconnection messages.
* Are there any errors shown in the log files in the blade’s _var_ directory?
* On the server where the Liberator is running, check the _servers/Liberator/var/event-rttpd.*_ files for errors. Look out especially for field-related errors (reused field names or numbers).
* If you’re using a Transformer, check on the server where the Transformer is running the _servers/Transformer/var/*_ files for errors. Look out especially for field-related errors (reused field names or numbers).