SQL Server Express 2008 error -2146893007, service won't start for Microsoft Office Accounting 2009

Just discovered the old accounts package, Microsoft Office Accounting 2009 won't load. It reports ExecuteRestricted.exe crashed, then tries to load MS Office Accounts again and prompts to start a new company. After a bit of digging through Event Viewer for useful error codes we found that trying to start the SQL Server (SQLEXPRESS) service failed, reporting error -2146893007.

Event Viewer indicates that this is an SSL related error. So, we realised that TLS 1.0 had recently been disabled on this PC in line with PCI recommendations. We use the excellent IISCrypto utility to achieve this quickly and simply. Reinstating TLS 1.0 (no reboot required) allowed the SQLEXPRESS service to start up again.

123-reg auto renew SSL .crt certificate won't load in ISA Server, no key, can't export .pfx

We've got an Exchange Server 2003 as part of an SBS 2003 setup, just hanging in on its last couple of months before it gets upgraded - just before the July 2015 sunset on security updates. You best contact redleg.net if you haven't planned upgrading from Server 2003 yet.

The replacement Alpha SSL certificate came as a plain text email, to save as a .crt file and import. Loaded the MMC, added the Certificates option to manage the Local Computer certificate store, and easily imported into the Personal section. From there, head to IIS Manager > Default Website > Properties > Directory Security > Server Certificate and change to the updated certificate.

Easy enough, however on the SBS 2003 Premium, running ISA server as the firewall, you also need to update the certificate in the ISA Outlook web publishing rule too. Right-lick on the rule > Properties > Listener > Properties > Preferences > SSL > Select

But the new certificate doesn't appear on the list. Thats because it needs to be in PFX format, which also includes the private key. This comes from the original certificate request. If you try and export that certificate in PFX format its greyed out, because the private key is missing. There's a quick and easy way to fix the certificate, which doesn't involve exporting or trying to recombine the certificate and key with openssl (yes tried all that!)

Look at the new certificate details and find the serial number - should eb something like a 36 character hex number. Now start a CMD prompt and use the command
   certutil -repairstore my "serialno"

Then go back to ISA to change the certificate attached to the web publishing rule listener and your new certificate should be on the list.

(I also did a restart of IIS Admin service - not sure whether that was required or not - let me know in the comments below)