Entities are not exported
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.
- Check whether any error file is generated in <integrationfolder>\InriverStudioIntegration\SyncCommands\ImportErrors folder, or any error logged to inRiver connect log file.
- Check whether channel is published.
- Check whether inRiver integration service is running and the Litium Studio connector is started in inRiver admin backoffice.
- Check the Program Files\inRiver AB\inRiver Connect\Log\inRiver.Connect.log and makesure the line which says "Connector started successfully" is there.
- Makesure Connector is receiving events from the Windows message queue.
- In certain scenarios, the windows message queue does not send messages from inRiver Connect framework. To detect this, do some modification in the rich client, like editing a published entity, which is supposed to change the data .xml file of that entity. Open the Program Files\inRiver AB\inRiver Connect\Log\inRiver.Connect.log and see whether you have any new messages logged there. If the connector is getting the message queue events, new log lines will appear.
- If you suspect the connector is not getting the messages, shut down both inRiver connect and inRiver server services, and restart the whole machine. Then start the services again and try.
- If still not working, install inRiver standard output connector and see whether it generates output, and makesure the standard connector is working, and events are getting fired. You should contact inRiver if the message queue service cannot be made to work in your server configuration.
- Makesure channle is published and then Re-start the connector, and check <integrationfolder>\InriverStudioIntegration\Model\ChannelStructure.xml file, and check whether the entity is there.
- If entity is not there but file contain values, check your channel filters in inRiver
- If the file is entirely empty, check the ChannelID connector setting for LitiumStudio inriver connector
- Makesure item is there in the command file in <integrationfolder>\InriverStudioIntegration\SyncCommands folder or in <integrationfolder>\InriverStudioIntegration\SyncCommands\Archive folder.
- if there are files remaining in the <integrationfolder>\InriverStudioIntegration\SyncCommands folder, then the LitiumStudio startup task to import is not running. Check the web.config file and its settings. Log the inriver events to a seperate log file and check whether import messages are logged.
- if the files are in the <integrationfolder>\InriverStudioIntegration\SyncCommands\Archive folder and it contains the command to import the item, Rebuild Litium Studio search indexes and check.
Updated
2020-06-10
|