Error com.glide.db.impex.datasource.DataSourceException: org.apache.poi.poifs.filesystem.OfficeXmlFileException: The supplied data appears to be in the Office 2007+ XML. You are calling the part of POI that deals with OLE2 Office Documents. You need
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2019 11:46 PM
Hello
we are currently in london patch 6
i get the error
com.glide.db.impex.datasource.DataSourceException: org.apache.poi.poifs.filesystem.OfficeXmlFileException: The supplied data appears to be in the Office 2007+ XML. You are calling the part of POI that deals with OLE2 Office Documents. You need to call a different part of POI to process this data (eg XSSF instead of HSSF)
while importing data into servicenow table with help of excel in a datasource??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2019 12:03 AM
I have had this message before when the XLSX file I was using as a datasource was password protected.
To solve my situation I saved a copy with password protection removed and used that.
As far as I know ServiceNow can't handle password protected imports. If you need to secure the data you are importing use SFTP or something similar to get you files rather than adding a password to the data itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2020 04:35 AM
I'm getting the same error in Madrid when receiving an Excel file generated externally. My Excel file is not password protected however. Any insight into why this is happening and how to correct it? I'm receiving this error from a Data Source process within ServiceNow that is running an HTTP request to an external REST service that generated the Excel file.
thanks,
-vince

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2020 04:17 AM
We were importing ".xls" files and it stopped working with the same error message. Changing the extension on the file name from ".xls" to '.xlsx" resolved our issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2025 09:02 AM
Hello Everyone,
I also encountered the same error; however, upon reevaluating the data that I had entered into the Excel, I discovered that it was not in the correct format. If Excel contains any incorrectly formatted data, then it generates such an error.
Solution :
- Maintain limited data during the creation of a new staging table.
- Ensure that all data is entered in the correct format, particularly for date and time.