From c9a47a4ded6f74cc71fd6bba905fbb5b903fc44d Mon Sep 17 00:00:00 2001 From: Howard Enos Date: Tue, 5 May 2026 18:57:20 -0700 Subject: [PATCH] sync: auto-sync from HOWARD-HOME at 2026-05-05 18:57:19 Author: Howard Enos Machine: HOWARD-HOME Timestamp: 2026-05-05 18:57:19 --- ...ard-aim-connection-broken-investigation.md | 25 +++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/clients/instrumental-music-center/session-logs/2026-05-05-howard-aim-connection-broken-investigation.md b/clients/instrumental-music-center/session-logs/2026-05-05-howard-aim-connection-broken-investigation.md index 55e90f8..c6e589e 100644 --- a/clients/instrumental-music-center/session-logs/2026-05-05-howard-aim-connection-broken-investigation.md +++ b/clients/instrumental-music-center/session-logs/2026-05-05-howard-aim-connection-broken-investigation.md @@ -53,9 +53,30 @@ AIM uses Telerik OpenAccess connection pooling. Pool slots hold idle TCP connect ## Plan -### Tonight — scheduled service restart (low risk) +### Tonight — scheduled service restart (REGISTERED) -Restart `MSSQL$AIMSQL` at **02:30 AM MST on 2026-05-06** via a one-shot scheduled task on IMC1. Releases the paged-out working set, clears stale pool state, ~30 seconds of unavailability. RDP users with AIM open will need to relaunch in the morning. Expected to clear the immediate symptom for at least a week or two. +| Field | Value | +|---|---| +| Task name | `AIMSQL_Restart_20260506_0230` | +| Trigger | 2026-05-06 **02:30 AM MST** (one-shot) | +| Runs as | SYSTEM | +| Action | `powershell.exe -NoProfile -ExecutionPolicy Bypass -File "C:\Windows\Temp\aimsql-restart.ps1"` | +| Restart script path | `C:\Windows\Temp\aimsql-restart.ps1` (984 bytes) | +| Run log | `C:\Windows\Temp\aimsql-restart.log` (created on first run) | +| Auto-delete | none — manually remove after verifying clean run | + +Script does: log pre-state → `Restart-Service "MSSQL$AIMSQL" -Force` → 15s sleep → log post-state → `SELECT 1, GETDATE()` via sqlcmd to confirm responsiveness → log result. + +Quirks worth noting for future scheduled-task work on this server: +- `Register-ScheduledTask` rejected `-DeleteExpiredTaskAfter` on its own; it requires a trigger `EndBoundary`. Setting `EndBoundary` after the fact also returned "parameter is incorrect" on this Server 2016 box. Workaround: register without `DeleteExpiredTaskAfter` and clean up by hand. Worth saving as a recipe for future jobs. +- `schtasks.exe /Create` failed with "parameter is incorrect" — possibly the colon in the original task name (`... 02:30`) hit a path-vs-name validation. Switched to underscore-only name (`AIMSQL_Restart_20260506_0230`), which Register-ScheduledTask accepted cleanly. + +### Morning verification (Howard, 2026-05-06 first thing) + +1. Check `C:\Windows\Temp\aimsql-restart.log` via GuruRMM +2. Confirm SELECT 1 succeeded and AIMSQL post-state is Running +3. Sample-test AIM from a workstation if possible +4. Delete the scheduled task: `Unregister-ScheduledTask -TaskName AIMSQL_Restart_20260506_0230 -Confirm:$false` ### Note for Mike