Sitebeam unavailable to some users

The database is back online and all users should be able to log in and run reports as expected.  Have a Happy Thanksgiving!

 

We understand that this is the day before Thanksgiving and how important uptime is to our users at this moment, and we are doing everything we can to restore access as quickly as possible.

We are aware of an issue with Sitebeam affecting a number of our users.  We are looking into it now and will update this page as soon as we have more information.  Thanks for bearing with us.

There seems to be an issue with one of the RDS databases.  We understand that some users are able to log in but are unable to use the tool.  More information will be provided as soon as we have it.

Sitebeam and WebScan not available to some users

We are aware of an issue preventing some users from logging into Sitebeam and WebScan.  Amazon is upgrading some databases we use, and that is causing the interruption in service.  We will be monitoring the situation and will update this page as we know more.

Sitebeam is now back up and running, we are waiting on the DB upgrade for WebScan to finish.

WebScan came back up last night, all users should be able to log in and run reports as usual.

Excel export issues in Sitebeam

A new security update to Microsoft Office has caused a problem for our Excel export.  Sitebeam exports as HTML and that can be understood by Excel, but the latest security update is preventing Windows users from opening the exported files.

More information here:

https://social.technet.microsoft.com/Forums/en-US/d2d84793-9920-45e3-baef-5027a4ac1ae0/kb3170008-for-office-2016-breaks-functionality-ms16088

The Excel team has made a change in the behavior of certain file types to increase security. This change came in the security updates KB3115262, KB3170008, and KB3115322. Previously, when you tried to open an HTML or XLA file with an .XLS file extension from an untrusted location, Excel would warn about the mismatch between the file extension and content, but would still open the workbook without Protected View security. After the security updates Excel no longer will open the workbook because these files are not compatible with Protected View and there is no warning or other indication it was not opened. We apologize that Excel is showing a blank screen instead of a more helpful error message with information about what to do next.

We have a few options for workarounds. These are in order from safest to riskiest. While some people in the forums have suggested rolling back the security patch, we do not recommend that option as it can leave you open to other current and future threats.

  1. The best option is to move away from using HTML wrapped as .xls. If you use native formats (e.g. xls, xlsx, xlsb) which will open in protected view when untrusted, this will provide some level of protection from the documents being opened.
  2. You can unblock access for individual files you know are safe. To do this:
    1. Right click on the file and choose Properties
    2. On the General tab, click Unblock
    3. Click OK
  3. You can make use of existing Trusted Locations capabilities in Excel 2010, 2013, and 2016 via File -> options -> Trust Center -> Trust Center Settings -> Trusted Locations.
    1. You can save the web html file to a trusted location on the local machine (Excel comes with a set of default trust locations). If you do not see the local folder location you trust for these files, then press “Add new location…” button and add it in the Trusted Location dialog. If the HTML document is in a trusted location the KB fix is not applied (e.g. the unsafe HTML file is not blocked).
    2. This approach may unblock you, but it carries some risk as files of any file type in Trusted Locations are fully trusted. If an attacker can drop files into the trusted location they can easily exploit users who open such documents. Be especially cautious when specifying a custom folder as a trusted location.

We are also investigating a more permanent solution that allows our users to remain secure as well as minimize disruption to existing user experience. We’ll provide updates on this in the coming days. Thank you for your patience.

Freya

Office Newsroom

 

This is affecting a number of companies around the word.  We are looking into solutions for our users, but currently the best recommendation we can make is to export into another format (HTML) and cut and paste it into Excel, or use the suggestions from Microsoft to let Office know the file isn’t malicious.

http://www.infoworld.com/article/3098898/microsoft-windows/excel-refusing-to-open-files-blame-the-kb-3115322-3115262-security-updates.html

W3C validator updated August 2

The local copy of the validator was updated on August 2nd.  We are keeping an eye out for updates to the public validator, which you can see for yourself here:

https://github.com/validator/validator/releases

W3C validator updated on June 28

The local copy of the validator was updated on June 28th.  We are keeping an eye out for updates to the public validator, which you can see for yourself here:

https://github.com/validator/validator/releases