When attempting to run the Sony VAIO laptop BIOS update program you get the WBFLASH error “Cannot Read System Information”. This usually means you need to install the “Sony Shared Library” which should be a download under your laptop’s Sony support page. See Sony Knowledge Base article 36505 (Link). Once you download and install the Sony Shared Library files and restart your computer, try running the BIOS updater program again.
The first user account created in Web Help Desk is also the only user account that will remain active and useable if all of your technician licenses expire. So if you disabled the default admin user account in Web Help Desk when you purchased additional licenses and then you find yourself in the situation of your licenses expired you will be locked out of Web Help Desk since there are no active user accounts which can be used to log into it. If you are in this situation you will need to directly edit the Web Help Desk backend database to reset the default admin user account password and re-activate it. Here is the MySQL query for doing this. Execute it against your Web Help Desk database. You may need to adapt the query for your particular database backend server.
UPDATE TECH SET USER_NAME='admin', PASSWORD='password', use_ldap_authentication=0, INACTIVE=0, INCORRECT_AUTH_ATTEMPTS=0 where CLIENT_ID=1;
The above SQL query will set the username of the default user account in Web Help Desk to “admin”. The password will be set to “password”. At this point you should be able to log into Web Help Desk using those credentials. Of course you should immediately change the user account password to something more secure.
When trying to digitally sign an email message in Outlook 2016 for Windows running in Windows 10 you may get this error:
Encrypting emails works fine, it is only when you try to JUST sign an email you get this error. This error appears to only occur with Outlook x64 (64-bit). When you search the internet on the error “A required action was not successful because of an unspecified error” in relation to Outlook for Windows the most common solution you come across is to run the command “sfc /scannow” in an elevated command prompt. This didn’t work for me when I tried it on Windows 10 Enterprise (Current Branch) with Outlook 2016 for Windows. The solution that worked for me was in this forum post. The solution in that post was to enable the email security option “Request S/MIME receipt for all S/MIME signed messages”. Once I did that I was able to sign emails successfully without getting any errors. Sending emails to non-exchange email users with this option enabled doesn’t appear to have any adverse effects.