Question
Kainos
CA
Last activity: 19 Feb 2021 10:56 EST
Excel 'Save As' issue in Virtual Machine
Hi,
Not sure if anyone experienced this but we are having issues saving an excel file in our production virtual machine (see below error snippet). Our code is working fine from Dev and UAT region and able to save the excel report with no issues.
We already checked the office license, versions and also try to manually save it and no issues with these things.
Office Version: Office (2016)
Pega Version: 19.1.49
Excel Method Used: C# Script
'System.Runtime.InteropServices.COMException (0x800A03EC): Exception from HRESULT: 0x800A03EC
at Microsoft.Office.Interop.Excel.WorkbookClass.SaveAs(Object Filename, Object FileFormat, Object Password, Object WriteResPassword, Object ReadOnlyRecommended, Object CreateBackup, XlSaveAsAccessMode AccessMode, Object ConflictResolution, Object AddToMru, Object TextCodepage, Object TextVisualLayout, Object Local)
at Dynamic.Script_8D70AC9F674F417.Script.CreateEODReport(String strTemplatePath, String strNewFilePath, Int32 sheetIndex, DataTable dt, Int32 startIndex, String& exceptionMsg)'
Pegasystems Inc.
US
Updated: 19 Feb 2021 4:22 EST
Kainos
CA
@KONSTANTIN Serditov Yes, all Virtual machines and access has the same set up with dev and UAT region as we validate.
Also the issue happens everytime the bot is creating/opening then saving an excel file.
Updated: 19 Feb 2021 10:56 EST
Pegasystems Inc.
US
In this case, unless someone has a better idea, please try to google the error code and see if one of the solutions works for you.
This is Office.Interop.Excel error and there are a lot of topics reporting similar issue. I would start with these two:
https://stackoverflow.com/questions/1981395/windows-7-net-excel-saveas-error-exception-from-hresult-0x800a03ec
Digital Fast Forward
US
@Rose030494 I would also recommend re-adding the Microsoft.Office.Interop reference file and also even the Microsoft Excel tool item.
Hi @Rose030494
Do you have any difference in Windows version and bitness between Dev/UAT and PROD machines?
Does the error occur on first save attempt after startup or only on next attempts?
Does Windows user (that Runtime process uses) have same access rights to target folder on Dev/UAT machine vs PROD machine?