Smart Service Upload and Reporting Macro - Errors (v3.6)

[Andrew Kirkby]

I am trying to generate the consolidated report using the Cisco supplied Smart Service Upload and Reporting macro. I can load the macro spreadsheet ok (Macros are enabled in Excel). The Inventory report import works OK, however, when doing the Product Alert import, after around 20 seconds it fails with 'Microsoft Visual Basic - Run-time error '9': - Subscript out of range'

Further investigation, by opening the individual files downloaded from the portal appears to point to an issue with the Alerts report. When opening in Excel it throws an error saying that the file may have errors, it then goes on to try and repair it with the following error log -

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

-<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">

<logFileName>error111280_01.xml</logFileName>

<summary>Errors were detected in file '\\****.local\****2$\*****5$\****.****\profile\Desktop\Report\2018-07-12_Alerts.xlsm'</summary>

-<removedParts summary="Following is a list of removed parts:">

<removedPart>Replaced Part: /xl/worksheets/sheet4.xml part with XML error. Illegal xml character. Line 7, column 281.</removedPart>

</removedParts>

</recoveryLog>

Can you please advise.

Andy

[Justin Sprake]

Hi Andy,

I'll work on reproducing the error and follow up once I learn more.

[Justin Sprake]

Hi Andy,

It appears as though you will need to repair the Product Alert file, then import the Customer Inventory followed by the repaired Product Alert.

I was able to reproduce the error you provided and these were the steps required to resolve.

[Andrew Kirkby]

Appreciate that running the repair allows you to use the file, however, I'd suggest that this was only a temporary workaround?
Is it possible to get this looked into? Something must have changed in a recent release to break the report output?

[Cheri Fairbrother]

Hi Andrew,

Thank you for bringing the issue to our attention.  We'll investigate further and get this fixed.

Cheers,
Cheri

[Justin Sprake]

Hi Andrew,

We've been able to identify the root cause of the issue. Specifically, All instances of Field Notice FN70223 appear to contain an invalid character within the generated report which causes the error in Microsoft Excel.

https://www.cisco.com/c/en/us/support/docs/field-notices/702/fn70223.html

We've created a CDET for this issue as well which should be visible shortly:

CSCvk39954