Hi,
We use Aspose Cells product in our application to generate worksheets. After generating work sheet, we use a proprietary firm specific method to transfer large files from application server to UI server. A Metascan software is used to scan the xlsx generated before its stored by the proprietary system. Any XSLX generated by Aspose is being treated as an archive file by Metascan and it is not able to identify it as XSLX and hence take over 40 seconds to scan,
When we created an XLS using ASPOSE, the Metascan works faster and is able to scan within 4 seconds.
Attached is a sample code which shows how we use Aspose to generate excel
Please look into issue and advise if this is a known issue and any fix available.
We currently use Aspose Cells 8.4.2.0
MetaScan version used is
MetaScan 3.13.1.29739
Yes, when we tried with a regular XSLX created using MS office Excel product, the scan completed within 3 seconds.
Hi,
SampleInvestmentList.xslx is the one created using ASPOSE Cells,
Test.xslx is one created directly using MS Excel.
We observed that the content type was missing in the one generated by Aspose.
Attached are header screenshots of both File generated by Aspose cell and MS Excel
Hi,
- Metascan 3.8.2 Now Available!
Hi
I will get the information requested.
In meanwhile, is there any possibility one of your team members or yourself can join a conference call if we arrange for one along with a webex so you can observe what happens within our side with scan taking longer?
Hi,
- CELLSNET-45390 - Incompatibility of Aspose generated XLSX with MetaScan software
They have re-branded their product suite as Metadefender. The underlying product we use is Metascan.
I am also re attaching the file creating using Aspose which takes longer time to scan
Steps to reproduce:
• Download trial version of Metascan 3.13.1 and install on their machine
• Run command “D:\apps\OPSWATMetascan\omsCmdLineUtil.exe” config eod=0
• Run command “D:\apps\OPSWATMetascan\omsCmdLineUtil.exe” getinfo
to check if scan property Extract Microsoft Office documents is set to FALSE
• Run command “D:\apps\OPSWATMetascan\omsCmdLineUtil.exe” scan
for files (Aspose generated xlsx, Excel generated xlsx)
• Time taken for Aspose generated xlsx has been observed to be much higher than excel generated xlsx
Regarding you question about Scan Engine.
We utilize McAfee Engine licensed by Enterprise. We can probably provide our current engine details in production, but cannot provide them the engine itself.
find attached the version screen shot.
Hi,
Hi,
Bot the files took more time to scan (>40 seconds) than any other which is created directly from Office EXCEL product as Meta scan is treating both as archives.
Please advise if a call and webex session can help take this forward?
Hi,
we are evaluating your request for test page. In meanwhile wanted to check if you were able to try out what was mentioned in reply # 843955 on setting up and testing metascan?