Although my keep steep drop in amount of K2 posts from my side with more than high probability in the future, I’m keep jotting little things for now. The other day I was a bit perplexed by K2 Platform Classic setup manager which blocked me from adjusting K2 service account like that:
What it actually does is forcing you to use currently logged in user. And addressing why part it happens when you have developer license – in that case setup manager forces you to use currently logged in user as a “service” account (remember that Developer license requires you to run your K2 service in a window within interactive user session). Just though it may be useful to write this down and share.
Recently I was cleaning up some malware from Asus Windows 10 laptop. It took using AV software boot disk to remove malicious software and after that I upgraded Windows 10 to the latest feature update/build (2004). Windows Update was working pulling some more update but finally stuck with 0x80240023 (WE_E_EULAS_DECLINED) error and it took a bit too long for me to solve this problem, so taking a note of resolution here.
As machine has been infected I was suspecting that I might not had cleaned up it completely but in the end it was a problem of rare combination of Windows 10 2004 with Office 2007. There was basically one specific update for Office 2007 which was failing to be installed without being able to properly say so (it was Microsoft Office File Validation Add-in update). I went for using “Show or hide updates” troubleshooter package which allows you to hide/prevent specific update from installing. Once I launched it I saw this one pending update and hide it which cleared up the error. It seems that as an alternative solution you may try to install it manually locating OFV.cab in C:\Windows\SoftwareDistribution\Download, extracting it and running OFV.msi. As I understand there is some unexpected request for user input on installation of this thing, but I end up just hiding this update, although not without trying bunch of other solution like rebuilding Software Distribution directory and so on.
Another issue with this laptop was random waking up from sleep state, which user saw as random power on, that was resolved through disabling wake up timers on all Windows power plans as well as ensuring machine being shut down instead of put to sleep (hiding Sleep option from power off menu etc.).
I’ve recently run into issue on my Windows 10 machine with WhatsApp Desktop app – it was keep running in maximized window mode without possibility to resize window/make it smaller. I was ignoring/tolerating that for quite some time, next looked for a setting in app GUI which could have trigger this (there is none) and checked if my app is of the latest version (it is). So it was time to google a bit to find a solution which I’ll just share below.
In case you cannot minimize your WhatsApp Windows app window and it keep running in maximized mode, you should do the following to get back an ability to perform window resize:
Navigate to %appdata%\WhatsApp folder and open settings.json file located here in text editor.
Change “isFullScreen” setting value from true to false and restart WhatsApp app.
Just writing this down to have a record of the fix 🙂
In some scenarios you may have empty K2 roles with no users added, and in the past it was possible to create new role in K2 Management without adding any users into it or delete all users from the role (this is not the case in current versions of K2). When you have K2 role with no users K2 will be logging error shown below on each attempt to resolve this role (look at Interval configured for this role in DestQueue table to get an idea about error frequency, and the same will be logged every time when role used as a destination etc.):
“1 The K2.net 2003 Destination Queue SecurityLabel provider ” does not exist at K2DestQueue.RunDestQueue(Object obj)”
To address/remove that error you need to identify empty role first which can be done with help of the following SQL query run against K2 DB:
Once empty role identified you either delete it or add some user into it to get rid of error message, or as a third option you can increase its refresh interval in DestQueue table to decrease frequency with which this error will be logged in K2 host server logs.
When you run current versions of K2 Setup Manager it saves trace file in %temp%\K2 Setup Log directory and you may also find trace files in your K2 installation directory in Setup\Log subfolder. Trace files which you can find there named InstallerTraceDDMMYYY_N.log. Quite often it is necessary to confirm what mode (Install, Upgrade, Configure, Repair) was selected during last run of K2 Setup Manager. To do that based on installer trace you need to search trace files entries containing this string:
Last entry will tell you selected mode – Configure, Install etc.
Hopefully this tip can save you some time or clarify doubts on what action was selected during last run of K2 Setup Manager.