A Custom Script agent has quit gathering data with FMS errors "Failed to create a topology object" (4324738)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

A Custom Script agent has quit gathering data with FMS errors "Failed to create a topology object"
Description

A custom agent that ran for several weeks has quit gather data. It shows as active.
I have tried restarting everything I could and the custom agent script output looks good when executed from the cmd prompt.
Errors seen in FMS log:
2014-11-14 15:18:19.055 ERROR [Data-3-thread-21108] com.quest.nitro.service.topology.TopologyService - Failed to create a topology object with name Sbc2CatTlk_Agent_Table_Sbc2CatTlk: {unit=all-hk, agent=aea2cd9f-1b62-455e-98df-ebbce6291b57, name=Sbc2CatTlk}: com.quest.nitro.service.sl.interfaces.topology.IncompleteIdentityException: Sbc2CatTlk_Agent_Table_Sbc2CatTlk.it
Cause

Customer had made modification to the script but did not reload the script in Administration | Tools | Script Builder.
Resolution

Whenever a script is modified, one must always reload it in the Administration | Tooling | Script Agent Builder to increase the version and redploy the package to the FglAM client.
1) Load the script via Administration | Tooling | Script Agent Builder increasing the version from 1.0.0 to 1.0.1.
2) Push out the cartridge package update to the FglAM.
3) Restart the agent and did not observe the FMS error messages.
4) Viewed the Data Browser and saw current data.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title