Chrome: Aw, Snap – Windows 10

Microsoft has released a new update. This update causes Google Chrome to produce an Aw, Snap error whenever opening Chrome. Even if you click on the settings page.

There have been fixes, such as the –no-sandbox command line. However, this isn’t a nice solution.

The best way (for now), is to set compatibility mode on all users to Windows 7.

To do this, navigate to:

  1. C:\Program Files (x86)\Google\Chrome\Application
  2. Right click on Chrome.exe and select properties.
  3. Click Compatibility
  4. Select Change Settings for All Users
    dllhost_2016-09-20_15-01-09
  5. Select Run this in compatibility mode for Windows 7
    dllhost_2016-09-20_15-02-27
  6. Click Ok

This will change the compatibility mode for all users. If you do not select all users, the setting will revert after the first time it’s run.

PHP Fatal error: Uncaught Error: Call to undefined function xml_parser_create()

I’ve recently upgraded this WordPress site to PHP7, along with Ubuntu 16. When logging in today, I received an error 500.

Looking through the /var/log/apache2/error.log I found

[Wed Sep 07 21:25:43.730755 2016] [:error] [pid 710] [client 84.247.81.102:43280] PHP Fatal error:  Uncaught Error: Call to undefined function xml_parser_create() in /var/www/tecfused.com/public_html/w               p-includes/class-IXR.php:264\nStack trace:\n#0 /var/www/tecfused.com/public_html/wp-includes/class-IXR.php(464): IXR_Message->parse()\n#1 /var/www/tecfused.com/public_html/wp-includes/class-IXR.php(432               ): IXR_Server->serve('<?xml version="...')\n#2 /var/www/tecfused.com/public_html/wp-includes/class-IXR.php(440): IXR_Server->__construct(Array, false, false)\n#3 /var/www/tecfused.com/public_html/wp-in               cludes/class-wp-xmlrpc-server.php(197): IXR_Server->IXR_Server(Array)\n#4 /var/www/tecfused.com/public_html/xmlrpc.php(84): wp_xmlrpc_server->serve_request()\n#5 {main}\n  thrown in /var/www/tecfused.c               om/public_html/wp-includes/class-IXR.php on line 264

This is because the XML module is missing. you can check this by typing php -m from the command line:

root@tecfused:~# php -m
[PHP Modules]
calendar
Core
ctype
date
exif
fileinfo
filter
ftp
gettext
hash
iconv
json
libxml
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
Phar
posix
readline
Reflection
session
shmop
sockets
SPL
standard
sysvmsg
sysvsem
sysvshm
tokenizer
Zend OPcache
zlib

To fix this, type the following:

apt-get install php7.0-xml

Then

service apache2 restart

Your WordPress site should now be working. You can check your modules to make sure.

root@tecfused:~# php -m
[PHP Modules]
calendar
Core
ctype
date
dom
exif
fileinfo
filter
ftp
gettext
hash
iconv
json
libxml
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
Phar
posix
readline
Reflection
session
shmop
SimpleXML
sockets
SPL
standard
sysvmsg
sysvsem
sysvshm
tokenizer
wddx
xml
xmlreader
xmlwriter
xsl
Zend OPcache
zlib

Veeam Backup Fails: VSS Writer Errror 0x800423f4 (Azure AD Connect)

An updated post is here 31/10/2017

Hi Guys.

An interesting issue over the last few days. Our backup logs have had the following failures in Veeam.

Unable to release guest. Error: Unfreeze error (over VIX): [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{6323fe10-0205-47df-b015-4a5ff60c31e2}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]
Error: Unfreeze error (over VIX): [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{6323fe10-0205-47df-b015-4a5ff60c31e2}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Digging through the event logs, you will see errors like the following:

  1. Inital backup
    SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=19908. Thread=18488. Client. Instance=LOCALDB#SH7A2278. VD=Global\{C7140958-2759-4979-BA55-0E3F258064ED}1_SQLVDIMemoryName_0.

    vpxclient_2016-09-08_13-09-55

  2. Followed by
    A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
    the error is likely to reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    
    Operation:
     PrepareForSnapshot Event
    
    Context:
     Execution Context: Writer
     Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
     Writer Name: SqlServerWriter
     Writer Instance Name: SQL Server Code-Named 'Denali' CTP2:SQLWriter
     Writer Instance ID: {2f97c809-8eb4-431c-93ac-b0f81e610013}
     Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
     Process ID: 19908

    mstsc_2016-09-08_13-17-47

    mstsc_2016-09-08_13-18-02

We have found this issue is related to an update of the Microsoft Azure AD Connect client.

On all servers that were affected by this, we had just upgraded to the latest Azure AD Connect client. This seems to corrupt the SQL writer somehow.

We haven’t seen many reports of this. There are various fixes for the 0x800423f4 error, but the easiest fix is to repair the LocalDB SQL instance.

To do this:

  1. Go to Add/Remove Programs
  2. Select Microsoft SQL Server 2012 Express LocalDB
  3. Select Repair
    vpxclient_2016-09-08_13-11-17

Once this is finished, you will need to reboot.

We had this issue with many servers. This process fixed it on everyone.