From 265fa0edd8d6c9699ed5cfff8e2c53a05242c0e6 Mon Sep 17 00:00:00 2001 From: Howard Enos Date: Wed, 17 Jun 2026 09:53:09 -0700 Subject: [PATCH] sync: auto-sync from HOWARD-HOME at 2026-06-17 09:52:59 Author: Howard Enos Machine: HOWARD-HOME Timestamp: 2026-06-17 09:52:59 --- .../lens-auto-brokerage/docs/issues/log.md | 9 +++ .../2026-06-17-howard-deskman-crash.md | 62 +++++++++++++++++++ 2 files changed, 71 insertions(+) create mode 100644 clients/lens-auto-brokerage/session-logs/2026-06/2026-06-17-howard-deskman-crash.md diff --git a/clients/lens-auto-brokerage/docs/issues/log.md b/clients/lens-auto-brokerage/docs/issues/log.md index 134dba70..e5e63b64 100644 --- a/clients/lens-auto-brokerage/docs/issues/log.md +++ b/clients/lens-auto-brokerage/docs/issues/log.md @@ -1,5 +1,14 @@ # Issue Log — Len's Auto Brokerage +## 2026-06-17 — Deskman crash on login (RESOLVED, transient) +- **Reported by:** Becky — Deskman not opening on the server. +- **Box:** LAB-SERVER (192.168.1.241), Windows Server 2008 SP2 (OS 6.0.6002) — the OLD/EOL server, NOT the new 2019 box. +- **Crash signature seen in Windows error report:** CLR20r3, gui.exe (Deskman .NET front-end) v4.4.2248, fault module mscorlib, exception `System.UnauthorizedAccessException`. +- **What happened:** On login + opening Deskman it showed "the program is updating." Waited ~30 sec; clicked again and Deskman opened normally. +- **Root cause:** Transient — Deskman was mid-update and the access-denied crash was the GUI hitting files locked/being-written by its own updater. Cleared once the update finished. Not a corrupt install. +- **Action:** None required; self-resolved. No fix applied. +- **Note for tracking:** Deskman still runs on the EOL 2008 server and is slated to migrate to LAB-SVR / LENS-SV (Server 2019, 192.168.1.81). If this recurs and does NOT clear, it's a permissions/ACL issue (grant the user Modify on the Deskman program/data folder, or relocate data to ProgramData) — but priority is the migration off 2008. + ## 2026-04-13 — RDP Enable - Enabled Remote Desktop via registry on Server 2008 SP2 machine - `fDenyTSConnections` set to 0 diff --git a/clients/lens-auto-brokerage/session-logs/2026-06/2026-06-17-howard-deskman-crash.md b/clients/lens-auto-brokerage/session-logs/2026-06/2026-06-17-howard-deskman-crash.md new file mode 100644 index 00000000..604509b9 --- /dev/null +++ b/clients/lens-auto-brokerage/session-logs/2026-06/2026-06-17-howard-deskman-crash.md @@ -0,0 +1,62 @@ +# Len's Auto Brokerage — Deskman Crash Triage (2026-06-17) + +## User +- **User:** Howard Enos (howard) +- **Machine:** Howard-Home +- **Role:** tech + +## Session Summary +Becky at Len's Auto reported Deskman would not open on the server. The Windows error report +showed a CLR20r3 crash in `gui.exe` (Deskman's .NET front-end, v4.4.2248) with fault module +`mscorlib` and exception `System.UnauthorizedAccessException`, on OS version 6.0.6002. + +Decoded the signature: the box is LAB-SERVER (192.168.1.241), the OLD Windows Server 2008 SP2 +machine (EOL), not the new Server 2019 box (LAB-SVR / LENS-SV, 192.168.1.81). The crash was an +access-denied condition, initially diagnosed as a likely permissions/ACL problem on Deskman's +program or data folder. + +On the user logging into the server and opening Deskman directly, it displayed "the program is +updating." After ~30 seconds, reopening it launched normally. Root cause was therefore transient: +the GUI hit files locked/being-written by Deskman's own updater, producing the +UnauthorizedAccessException; it cleared once the update finished. No corrupt install, no fix +required. + +Logged the event to the client issue log as a tracking note (explicitly not a ticket). + +## Key Decisions +- Treated the crash as transient (updater file lock) rather than a corrupt install, based on the + observed self-resolution after the update completed. +- Did not apply any ACL/permissions fix since the symptom cleared on its own. +- Reinforced that the durable priority is migrating Deskman off the EOL 2008 server to the 2019 + box, rather than investing remediation effort in the dying server. + +## Problems Encountered +- Deskman `System.UnauthorizedAccessException` crash on launch — resolved itself after the + in-progress Deskman update finished; reopening worked normally. + +## Configuration Changes +- Modified: `clients/lens-auto-brokerage/docs/issues/log.md` — added a 2026-06-17 entry + documenting the Deskman crash, root cause (transient updater lock), and resolution. +- Created: this session log. + +## Credentials & Secrets +- None discovered, created, or rotated. + +## Infrastructure & Servers +- LAB-SERVER (192.168.1.241) — Windows Server 2008 SP2 (OS 6.0.6002), EOL, WORKGROUP. Currently + runs Deskman. To be decommissioned. +- LAB-SVR / LENS-SV (192.168.1.81) — Windows Server 2019, current/new server. Deskman migration target. +- Deskman GUI: `gui.exe` v4.4.2248, .NET (mscorlib 4.0.0.0). + +## Commands & Outputs +- Crash signature (Windows error report): CLR20r3 / gui.exe 4.4.2248 / mscorlib / + `System.UnauthorizedAccess[Exception]` / OS 6.0.6002. + +## Pending / Incomplete Tasks +- Migrate Deskman from LAB-SERVER (2008) to LAB-SVR / LENS-SV (2019) — open migration item. +- If the crash recurs and does NOT self-clear, fix as permissions: grant the user Modify on the + Deskman program/data folder, or relocate its data to ProgramData. + +## Reference Information +- Issue log: `clients/lens-auto-brokerage/docs/issues/log.md` +- Overview: `clients/lens-auto-brokerage/docs/overview.md`