Debug & Troubleshooting
For the smooth operation of a integration many factors need to come together, this section contains important debug and troubleshooting tips.
inRiver has two windows services, one has display name "inRiver Server" and the other "inRiver Connect". (If you are using inRiver 6, the service names are "inRiver Server 6.0" and "inRiver Connect 6.0").
If these two services fail to start, or gets stuck in the middle, try following troubleshooting steps.
While you test the integration it is frequently required to clean-up the whole Litium Studio product catalog from its test data, including removing fields and field templates. A helper method is implemented with inRiver connector, which can only be accessed by visiting this Url and when the System user is logged in.
If the generated field name in Litium Studio does not contain the value set by FieldDefinitionName setting in inRiver check the following.
1. Is connector restarted?
2. Are there any other fields with the same name or renamed to this? Perhaps the field attributes are contradictory.
3. Is the FieldDefinitionName attribute name is correct? check for spellings and remove any spaces at the end.
When you add a entity in InRiver, if the Entity is not visible after some time in Litium Studio product catalog, follow these troubleshooting tips.