- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-04-2020 06:11 AM
Restarted MID server (due to it appearing hung thanks to a discovery job). Noticing the following error in agent.0.log: how do we determine what is causing that fatal? 11/04/20 05:07:41 (622) Worker-Standard:ServiceDiscoveryProbe-3286778d1b9ce0108ef69829bc4bcba5 SEVERE *** ERROR *** Can not parse content com.snc.sw.exception.FileParsingException: Failed to parse XML file. Error: Problem with File Structure, Invalid XPath expression: "": Unexpected ''
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2021 10:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2023 12:17 PM
Hello @Sandeep132 can you share your workaround? thank you!!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2023 12:29 PM
@FLP1 This issue is very old one and I do not think is happening anymore. As mentioned in the solution accepted, the issue is fixed in Paris release.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-08-2020 08:55 AM
Hi,
I suggest to debug the pattern and check the EVAL scripts which is causing this issue.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2020 02:07 PM
The biggest challenge is figuring out which pattern is causing the noise.
I'd love to debug it once I know what IT is.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-12-2020 01:22 PM
HI,
you can check that by doing a search in pattern log table and see which pattern has this error.
Thakns,
Ashutosh