azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from HOWARD-HOME at 2026-05-06 13:50:24

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-05-06 13:50:24
This commit is contained in:
Howard Enos
2026-05-06 13:50:25 -07:00
parent f8c6b4b9ca
commit 4da4e5bac5
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.claude/scheduled_tasks.lock
View File

@@ -1 +1 @@
{"sessionId":"aebc81fa-2fbf-471d-abed-2f6338d36987","pid":77200,"acquiredAt":1777494782547}
{"sessionId":"8a956328-8afb-492a-a3d3-709f80396122","pid":14796,"acquiredAt":1778100485870}

2
clients/instrumental-music-center/PROJECT_STATE.md
View File

@@ -55,7 +55,7 @@ Music retail + repair shop running AIMsi POS on-prem. Primary server IMC1 (Dell
- C: drive at ~77% full — monitor
- SMB1 still enabled — disable when time permits
- `TestConv61223` DB (on orphan `IMC1\AIMSQL`, leftover from 2023 conversion test) safe to drop — verify first
- **AIM "connection broken" recurrence under host memory pressure.** SQLEXPRESS has no `max server memory` cap; under pressure Windows trims working sets and reaps idle Telerik pool slots, causing user-facing `Telerik.OpenAccess` connection-broken errors. First seen 2026-05-05 (Station 1), recurred 2026-05-06 ~12:14 PM (Station 1 again). Recommended fix: cap `max server memory` on SQLEXPRESS (~12-14 GB), WID (~512 MB), and AIMSQL (~256 MB). Long-term: dedicated DB host or Server 2019 migration. Note: misleading instance name burned ~1 day of triage — do NOT stop SQLEXPRESS thinking it's idle.
- **AIM "connection broken" recurrence under host memory pressure.** SQLEXPRESS has no `max server memory` cap; under pressure Windows trims working sets and reaps idle Telerik pool slots, causing user-facing `Telerik.OpenAccess` connection-broken errors. First seen 2026-05-05 (Station 1 = `IMC-STATION1`, **192.168.0.50**), recurred 2026-05-06 ~12:14 PM (same workstation). Recommended fix: cap `max server memory` on SQLEXPRESS (~12-14 GB), WID (~512 MB), and AIMSQL (~256 MB). Long-term: dedicated DB host or Server 2019 migration. Note: misleading instance name burned ~1 day of triage — do NOT stop SQLEXPRESS thinking it's idle.
---

2
clients/instrumental-music-center/session-logs/2026-05-06-howard-imc1-aim-instance-correction.md
View File

@@ -123,7 +123,7 @@ GuruRMM command_id for audit: `1889a150-b775-4fb2-9f4b-cd794d4e7d9f`, exit 0.
- WID: 512 MB
- AIMSQL: 256 MB (or just leave it; we want it stopped eventually anyway)
The cap stops the trim cycle even when global pressure rises, because SQL voluntarily stays under the ceiling instead of getting forcibly trimmed.
2. **Confirm Station 1's hostname / IP** with Leslie. None of the active SQLEXPRESS sessions matched `IMC-STATION1` exactly. Likely either `DESKTOP-44L80C0` / `DESKTOP-MR3ALTK` (un-renamed boxes) or a station that was disconnected at check time.
2. ~~**Confirm Station 1's hostname / IP** with Leslie. None of the active SQLEXPRESS sessions matched `IMC-STATION1` exactly. Likely either `DESKTOP-44L80C0` / `DESKTOP-MR3ALTK` (un-renamed boxes) or a station that was disconnected at check time.~~ **Resolved 2026-05-06 by Howard:** Station 1 = `IMC-STATION1`, IP **192.168.0.50**. It wasn't in the active connection list at enumeration time — consistent with it being disconnected after the user-facing error and not yet reconnected at our snapshot. For next recurrence, target diagnostics by `client_net_address = '192.168.0.50'` in `sys.dm_exec_sessions` and by remote IP in SQLEXPRESS connection events.
3. **Locate AIMSQL `.mdf` files** before any consolidation talk. They weren't where I expected. Worth a 5-minute filesystem search.
4. **Schedule SQLEXPRESS-targeted restart cadence** only if the memory cap doesn't hold — but it's after-hours-only because every register would briefly disconnect.