One or more of the recent updates for Windows 10 rendered my laptop incapable of communicating with the outside world. The Windows Firewall failed to run due to Base Filtering Engine not being able to run either. It’s the dreaded “Error 5: Access denied” error message all over again. Windows 10 also thought it was not activated, which is plain wrong. And no, I haven’t changed any hardware, save upgrading the wireless NIC in May last year. Running
sfc /scannow with elevated privileges found nothing wrong. Restoring the system to the state prior to the latest updates made the network and firewall subsystems running again. All is well. What a mess.
The Office 365 instance installed on a student’s laptop showed signs of not being activated and in need of an update. Clicking on any of the small buttons below the ribbon made no difference. Running Office updates manually from “File → Account → Update” gave us an error message: 30125-28 (404).
sfc /scannow with elevated rights managed to repair enough of the corruption to allow Office 365 to continue working.
Why are modern “cloud” software so fragile? Why are Dropbox and Google Drive far superior to the equivalent of Microsoft? Why is OneDrive for Business more on the order of OneDrive from Hell?
A student experienced Revit 2018.1 giving him this rather useless error message:
Licensing System Error 1
After Googling for a solution, we installed/repaired all the Visual C++ runtimes we could find in
3rdParty\x64\VCRedist and in
3rdParty\x86\VCRedist from the Revit 2018 distribution.
Shame on lazy developers not willing to code reasonable error messages explaning what the program attemped to do with what.
GNU style error messages is a lot better than nonsense words. E.g.:
sourcefile.c: lineno: open("/some/file") = -1, errno = 2 (No such file or directory)
Today I had the opportunity to examine another case of “Licensing System Error 1”. This time I installed
3rdParty\x86\VCRedist\2005\vcredist_x86.exe only. As far as I can tell, Visual C++ 2005 Runtime x86 wasn’t installed at all prior to my actions.
Yesterday, a student installed Autodesk Revit 2018 on his Windows 10 x64 laptop. He then upgraded to Revit 2018.1. After entering the licensing details, Revit crashed. Installing the latest drivers from nVidia, currently at version 385.41, and rebooting the laptop saved us from any more grief.
I’ve been exploring Pässler PRTG on Microsoft Windows Server 2016 (Microsoft Imagine Premium) for the past couple of days. While the system is impressive and on the border of being overwhelming, it lacks complete IPv6 support.
The web interface is IPv4 only, and the NetFlow v9 collector only understands IPv4. PRTG can do PING, SNMP, etc, over IPv6, but you can only specify whether PRTG should contact a device using IPv4 or IPv6, not both. For as long as our networks remain dual-stack it makes sense to explore both network protocols simultaneously, in the same manner we can do with Icinga and Nagios, i.e. specify IPv4 and IPv6 addresses where applicable. A workaround is to register a device twice, once for IPv4 and again for IPv6. Be careful not to create too many duplicate sensors.
I wish PRTG would ask me if I wanted to run autodiscovery after installing it. PRTG detected our core switch as the DHCP (relay) service, duplicating all the sensors it could find.
Neither SNMP nor PRTG are ZFS aware, and in many cases it’s utterly pointless to monitor a lot of ZFS filesystems. Instead we should monitor ZFS pools, if only that were possible.
SNMP doesn’t convey whether a filesystem is diskbased or not, so I had to remove sensors for mountpoints such as
Updates to Trend Micro OfficeScan last week resulted in four cases of
Reboot to safe mode, uninstall Trend Micro OfficeScan, reboot, and reinstall Trend Micro OfficeScan.
One additional positive outcome was the firmware update we conducted simultaneously.
If you run into error 30174-4 while installing MS Office and related software, try running a full repair of the product from the Control Panel.
After installing Autodesk Revit 2017 on a student’s laptop, the software started whining about missing
msvcr100.dll. This was solved by repairing Microsoft Visual C++ Redistributable for Visual Studio 2012 Update 4, both x86 and x64.
C♯ and mono are both a blessing and a curse. Most documentation, FreeBSD-specific or not, on the internet are more or less outdated. Maybe I was looking in the wrong places. It was really frustrating. Soon this will be outdated too.
Start by adding
lang/mono. Then add
x11-toolkits/libgdiplus. Continue reading FreeBSD has mono
… Windows machines try to request two URLs (www.msftncsi.com/ncsi.txt and ipv6.msftncsi.com/ncsi.txt, the former over IPv4, the latter over IPv6) to ascertain whether a given network is routed to the Internet and if there is a captive portal in the way (NCSI stands for “Network Connection Status Indicator”).
See also: https://blogs.technet.microsoft.com/networking/2012/12/20/the-network-connection-status-icon/.