"Export Data Failure, Sorry, the data could not be exported at the moment due to some internal error", exporting inventory data fails on vCenter Server after upgrading to 7.0 Update 3i (7.0.3.01100)
Article ID: 318142
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
- Exporting Inventory Data using the "Export" feature in vCenter Server UI Client fails with "Export Data Failure" Error message after upgrading vCenter Server to 7.0 Update 3i (7.0.3.01100)
UI will show following error message:
- UI Client log file (/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log) will show following error snippets:
[2022-12-15T16:34:45.460Z] [ERROR] http-nio-5090-exec-10 70000196 100016 200003 net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper Error loading font family net.sf.jasperreports.engine.fonts.InvalidFontException: Error loading font "net/sf/jasperreports/fonts/icons/icons.ttf".
at net.sf.jasperreports.engine.fonts.SimpleFontFace.loadFont(SimpleFontFace.java:206)
at net.sf.jasperreports.engine.fonts.SimpleFontFace.setTtf(SimpleFontFace.java:167)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.parseFontFace(SimpleFontExtensionHelper.java:390)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.parseFontFamily(SimpleFontExtensionHelper.java:311)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.parseFontExtensions(SimpleFontExtensionHelper.java:259)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.loadFontExtensions(SimpleFontExtensionHelper.java:230)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.loadFontExtensions(SimpleFontExtensionHelper.java:187)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.io.IOException: Problem reading font data.
at java.awt.Font.createFont0(Font.java:1000)
at java.awt.Font.createFont(Font.java:877)
at net.sf.jasperreports.engine.fonts.SimpleFontFace.loadFont(SimpleFontFace.java:198)
[2022-12-15T16:34:45.465Z] [ERROR] http-nio-5090-exec-10 70000196 100016 200003 net.sf.jasperreports.engine.util.JRStyledTextParser Error while loading available fonts java.lang.NullPointerException: null
at sun.awt.FcFontManager.getDefaultPlatformFont(FcFontManager.java:76)
at sun.font.SunFontManager$2.run(SunFontManager.java:443)
at java.security.AccessController.doPrivileged(Native Method)
at sun.font.SunFontManager.<init>(SunFontManager.java:386)
[2022-12-15T16:34:45.467Z] [ERROR] http-nio-5090-exec-10 70000196 100016 200003 com.vmware.vise.data.mutation.impl.MutationServiceImpl MutationServiceImpl.add failed: java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.ExceptionInInitializerError: null
at net.sf.jasperreports.engine.fill.JRBaseFiller.<init>(JRBaseFiller.java:116)
at com.vmware.vsphere.client.export.ExportFileMutationProvider.generateFile(ExportFileMutationProvider.java:129)
at com.vmware.vsphere.client.export.ExportFileMutationProvider.add(ExportFileMutationProvider.java:79)
... 238 common frames omitted
Caused by: java.lang.NullPointerException: null
at sun.awt.FcFontManager.getDefaultPlatformFont(FcFontManager.java:76)
at sun.font.SunFontManager$2.run(SunFontManager.java:443)
at net.sf.jasperreports.engine.fonts.SimpleFontFace.loadFont(SimpleFontFace.java:206)
at net.sf.jasperreports.engine.fonts.SimpleFontFace.setTtf(SimpleFontFace.java:167)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.parseFontFace(SimpleFontExtensionHelper.java:390)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.parseFontFamily(SimpleFontExtensionHelper.java:311)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.parseFontExtensions(SimpleFontExtensionHelper.java:259)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.loadFontExtensions(SimpleFontExtensionHelper.java:230)
at net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.loadFontExtensions(SimpleFontExtensionHelper.java:187)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.io.IOException: Problem reading font data.
at java.awt.Font.createFont0(Font.java:1000)
at java.awt.Font.createFont(Font.java:877)
at net.sf.jasperreports.engine.fonts.SimpleFontFace.loadFont(SimpleFontFace.java:198)
[2022-12-15T16:34:45.465Z] [ERROR] http-nio-5090-exec-10 70000196 100016 200003 net.sf.jasperreports.engine.util.JRStyledTextParser Error while loading available fonts java.lang.NullPointerException: null
at sun.awt.FcFontManager.getDefaultPlatformFont(FcFontManager.java:76)
at sun.font.SunFontManager$2.run(SunFontManager.java:443)
at java.security.AccessController.doPrivileged(Native Method)
at sun.font.SunFontManager.<init>(SunFontManager.java:386)
[2022-12-15T16:34:45.467Z] [ERROR] http-nio-5090-exec-10 70000196 100016 200003 com.vmware.vise.data.mutation.impl.MutationServiceImpl MutationServiceImpl.add failed: java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.ExceptionInInitializerError: null
at net.sf.jasperreports.engine.fill.JRBaseFiller.<init>(JRBaseFiller.java:116)
at com.vmware.vsphere.client.export.ExportFileMutationProvider.generateFile(ExportFileMutationProvider.java:129)
at com.vmware.vsphere.client.export.ExportFileMutationProvider.add(ExportFileMutationProvider.java:79)
... 238 common frames omitted
Caused by: java.lang.NullPointerException: null
at sun.awt.FcFontManager.getDefaultPlatformFont(FcFontManager.java:76)
at sun.font.SunFontManager$2.run(SunFontManager.java:443)
Environment
VMware vCenter Server 7.0.3
Cause
This issue is caused due to some missing Fonts on the vCenter Server Appliance 7.0 U3i (7.0.3.01100) build number 20845200.
Resolution
This issue is resolved in vCenter Server 7.0 U3j, available at VMware Downloads.
Workaround:
As a workaround, inventory objects can be exported to CSV using PowerCLI CmdLets.
Below are some examples:
File paths and inventory object names should be updated to match your environment.
Export all VMs in vCenter
Get-VM | Select Name, NumCpu, MemoryGB, VMHost, PowerState, ProvisionedSpaceGB, UsedSpaceGB | Export-Csv -Path C:\export\VM_Inventory.csv -NoTypeInformation
Export all ESXi hosts in vCenter
Get-VMHost | Select Name, ConnectionState, PowerState, NumCpu, Version | Export-Csv C:\export\Host_Inventory.csv -NoTypeInformation
Export all Datastores in vCenter
Get-Datastore | Select Name, State, FreeSpaceGB, CapacityGB | Export-Csv C:\export\Dastore_Inventory.csv -NoTypeInformation
Export all VMs in a specific cluster
Get-Cluster -Name "CLUSTER_NAME" | Get-VM | Select Name, NumCpu, MemoryGB, VMHost, PowerState, ProvisionedSpaceGB, UsedSpaceGB | Export-Csv -Path C:\export\VM_Cluster_Inventory.csv -NoTypeInformation
Export all ESXi hosts in a specific cluster
Get-Cluster -Name "CLUSTER_NAME" | Get-VMHost | Select Name, ConnectionState, PowerState, NumCpu, Version | Export-Csv -Path C:\export\Host_Cluster_Inventory.csv -NoTypeInformation
Export all Datastores on a specific host
Get-VMHost -Name "ESXI_HOST_NAME" | Get-Datastore | Select Name, State, FreeSpaceGB, CapacityGB | Export-Csv -Path C:\export\Datastore_Host_Inventory.csv -NoTypeInformation
Workaround:
As a workaround, inventory objects can be exported to CSV using PowerCLI CmdLets.
Below are some examples:
File paths and inventory object names should be updated to match your environment.
Export all VMs in vCenter
Get-VM | Select Name, NumCpu, MemoryGB, VMHost, PowerState, ProvisionedSpaceGB, UsedSpaceGB | Export-Csv -Path C:\export\VM_Inventory.csv -NoTypeInformation
Export all ESXi hosts in vCenter
Get-VMHost | Select Name, ConnectionState, PowerState, NumCpu, Version | Export-Csv C:\export\Host_Inventory.csv -NoTypeInformation
Export all Datastores in vCenter
Get-Datastore | Select Name, State, FreeSpaceGB, CapacityGB | Export-Csv C:\export\Dastore_Inventory.csv -NoTypeInformation
Export all VMs in a specific cluster
Get-Cluster -Name "CLUSTER_NAME" | Get-VM | Select Name, NumCpu, MemoryGB, VMHost, PowerState, ProvisionedSpaceGB, UsedSpaceGB | Export-Csv -Path C:\export\VM_Cluster_Inventory.csv -NoTypeInformation
Export all ESXi hosts in a specific cluster
Get-Cluster -Name "CLUSTER_NAME" | Get-VMHost | Select Name, ConnectionState, PowerState, NumCpu, Version | Export-Csv -Path C:\export\Host_Cluster_Inventory.csv -NoTypeInformation
Export all Datastores on a specific host
Get-VMHost -Name "ESXI_HOST_NAME" | Get-Datastore | Select Name, State, FreeSpaceGB, CapacityGB | Export-Csv -Path C:\export\Datastore_Host_Inventory.csv -NoTypeInformation
Additional Information
Information on installing PowerCLI can be found in: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-F02D0C2D-B226-4908-9E5C-2E783D41FE2D.html
Information on using PowerCLI for vSphere can be found in: https://developer.vmware.com/docs/powercli/latest/products/vmwarevsphereandvsan/
Information on using PowerCLI for vSphere can be found in: https://developer.vmware.com/docs/powercli/latest/products/vmwarevsphereandvsan/
Feedback
Yes
No
Powered by
