Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Service Graph Connector for Tenable - Error: "Zero or More than One File Attached" during test load

PrasadShelar
Tera Contributor

Hi Community!👋

 

We’ve installed the Service Graph Connector for Tenable(x_tsirm_tio_now) to bring assets into the CMDB from Tenable. The connector setup was successful, and we received a 200 OK(success) response when testing the connection.


The connector includes multiple data sources mapped to scheduled import jobs. One of the data sources, 'SG-Tenable TVM - 1', uses the "Attachment" method to retrieve files.


However, when we attempt a test load of 20 records from the related list of this data source, we receive the following error:

com.glide.db.impex.datasource.DataSourceException: Zero or More than one file Attached

I’ve attached screenshots of:

  • Import Status
  • Application Logs
  • Data Source

Has anyone encountered this issue before? What could be causing it, and how can we resolve it?

Any guidance would be appreciated!

https: // store. servicenow. com  /store/ app/ d102bfea1ba46a50a85b16db234bcbf7

https:// docs.tenable .com /integrations/ServiceNow /Content/Welcome.htm

 

Thanks in advance for your help!🙏

 

Tags - Service Graph Connector, Tenable, CMDB, Import Jobs, DataSourceException, ServiceNow Integration, Test Load Error, Import Status, Application Logs, SG-Tenable TVM - 1, File Attachment Issue, Scheduled Import Jobs, Import Set API, ServiceNow CMDB, Troubleshooting, com.glide.db.impex.datasource.DataSourceException: Zero or More than one file Attached

10 REPLIES 10

PrasadShelar
Tera Contributor

Hey @donhall ,

 

 

After some time, one of my friends took this implementation further. He informed that 2 modifications helped him resolve this error. Please try and confirm if this works for you as well.

 

1. Disable MID Server: The error occurs because ServiceNow cannot locate exactly one file during the attachment-based import.

2. Switch Endpoint URL: (Try this only if 1st option didn't work.) Disable the "Use MID Server" option in your web connection settings to allow direct cloud communication, and change your API endpoint from https:// cloud.tenable.com to https:// tenable.io to route through the correct regional cloud infrastructure. [Please remove space " " in the URLs].


Please hit Like if this helps you in any way. And let me know if this resolves your issue so that we can mark this as a Solution.

Thanks in advance!