IT Log & 期權賠錢全記錄
IT 經驗與期權交易紀錄分享
2026/05/11
HUKE HK100藍牙折疊鍵盤
2026/04/29
COMMCAULT DR備份 Error Code [34:53] [34:53]
環境:
COMMCAULT
異常狀況:
存放DR備份的網路資料夾密碼有變更,之後DR備份就會有錯誤訊息
Error Code [34:53] [34:53]
Failure Reason CommServeDR: Destination Directory [\\sharefolder\commvault\CVDRBackup] does not exist or is inaccessible
CommServeDR: Destination Directory [\\sharefolder\commvault\CVDRBackup] does not exist or is inaccessible
解決過程:
到commvault console裡的"控制台",找到"DR Backup",裡面可以變更網路資料夾的帳號與密碼,修改正確後就可以正常備份。
2026/04/27
環境:
WIN11 25h2
Logitech meet up視訊設備
異常狀況:
查看event log,會看到錯誤訊息
失敗的應用程式名稱: AUDIODG.EXE,
版本: 10.0.26100.8246,
時間戳記: 0x923cfbc9
錯誤模組名稱: igo_src.dll,
版本: 3.0.0.0,時間戳記: 0x642f89de
例外狀況代碼: 0xc0000005
錯誤位移: 0x000000000001d019
錯誤處理常式識別碼: 0x788
失敗的應用程式開始時間: 0x1DCD6189BA1A78A
Faulting 應用程式路徑: C:\WINDOWS\system32\AUDIODG.EXE Faulting
模組路徑: C:\WINDOWS\System32\DriverStore\FileRepository\igoapo.inf_amd64_50fe8789ddef31f8\igo_src.dll
這個錯誤關鍵是明顯音效處理模組故障,不是羅技設備本身壞掉。
最快的方式就是把內建的喇叭/麥克風的驅動程式移除,改裝舊一點的驅動,就正常了。
Environment:
Windows 11 25H2
Logitech Meetup video conferencing device
Issue:
When using Teams or web applications with the built-in speaker/microphone, everything works normally.
However, when switching to the Logitech Meetup speaker/microphone, the audio devices fail, and Teams shows an error message.
Investigation:
In Event Viewer, the following error can be found:
Faulting Application Name: AUDIODG.EXE
Faulting Module Name: igo_src.dll
Exception Code: 0xc0000005
Module Path: C:\Windows\System32\DriverStore\FileRepository\igoapo.inf...\igo_src.dll
This indicates a failure in the audio processing module (APO) rather than a hardware issue with the Logitech device itself.
Resolution:
The root cause is related to the built-in audio driver.
By:
Uninstalling the current built-in speaker/microphone driver
Installing an older (stable) version of the audio driver
The issue is resolved, and the Logitech Meetup device functions normally again.
2026/04/22
M365 office 的出現錯誤 : Symmetric Key Derivation Function version 'KDFV1' is invalid
環境:
M365 office
異常狀況:
2026/04/21
國際牌冷氣 無線控制模組 CZ-T007 設定
1. CZ-T007 先安裝到冷氣機上,安裝時,冷氣機無斷電。
2. 搖控器拔掉電池,然後按住"溫度上跟下鍵",裝上電池,看到搖控器顯示 "31 bu"的畫面時,放掉上下鍵。
3. 按下"下鍵",畫面會顯示 "31SA"
4. 開啟手機中安裝的Panasonic IOT app。
5. 選擇"新增裝置",選擇無線模組。
6. 照app上的操作,先開啟手機的wifi功能,連上這個無線模組的WIFI,然後再輸入家中的wifi帳號/密碼。
7. 這樣就新增成功了,但要記住,搖控器不能改回原本的樣子了,就保持在"31SA"這個模式下,這時搖控器畫面雖然不會顯示其他的東西,但開關機的功能還是可以用,其他的就在手機上操作。
如果搖控器改回原本的操作模組,無線模組就會無法使用。
2026/04/08
ESXI 變更密碼 失敗 - 發生一般系統錯誤: Weak password: is based on the old one. *** passwd: Authentication token manipulation error
環境:
esxi
異常狀況:
在系統裡的進階設定,裡面有一個Security.PasswordQualityControl 參數。
在裡面加入 similar-permit ,存檔後馬上生效,就可以變更密碼了。
2026/03/27
使用LDAP與AD連線出現異常
環境:
win2025 AD
異常狀況:
PHP程式要用LDAP協定,透過domain name抓ad使用者資料,時好時壞,改用IP連線也是。
連到不用的DC主機都會有狀況。
解決過程:
DC主機上的本機安全性原則中,在"電腦設定->windows設定->安全性設定->網域控制站:LDAP伺服器簽署要求強制執行",要設定成停用,每台DC都要設定成停用,就可以排除問題。
Environment:
Windows Server 2025 Active Directory
Issue:
A PHP application uses the LDAP protocol to query AD user information via the domain name, but the connection is unstable (intermittently works and fails).
Using the DC’s IP address shows the same issue.
The problem occurs when connecting to certain domain controllers.
Resolution:
On the domain controllers, modify the Local Security Policy:
-
Go to:
Computer Configuration → Windows Settings → Security Settings → Domain Controller: LDAP server signing requirements - Set it to Disabled
This setting must be applied to all domain controllers.
After applying the change, the issue is resolved.
2026/03/26
Commvault 備份虛擬機 突然變的很慢
環境:
Commvault 備份虛擬機
異常狀況:
對新的虛擬機做第一次備份,可能容量比較大,過程中又有其他的備份,造成效能問題,最後就停住多個小時後,手動取消。
但後來要重新備份時,傳輸速度變超級慢,速度大概只剩之前的1/7~8,重開機也一樣。
解決過程:
後來發現之前備份失敗後,虛擬機上有一份snapshot沒被移除,先在esxi上,把那份snapshot刪除後,重新備份,就正常了。
Environment:
Commvault (VM Backup)
Issue:
When performing the first backup of a new virtual machine, the data size was relatively large. During the process, other backup jobs were also running, causing performance issues. Eventually, the job became unresponsive and was manually canceled after several hours.
After that, when attempting to run the backup again, the transfer speed became extremely slow, dropping to about 1/7–1/8 of the original speed. Restarting the system did not resolve the issue.
Resolution:
It was later discovered that after the failed backup, a snapshot remained on the virtual machine and was not removed.
By logging into ESXi and deleting the leftover snapshot, then running the backup again, the performance returned to normal.
2026/03/25
ESXI 無法開啟虛擬機器 xxx的電源。開啟模組 monitorloop 的電源失敗
環境:
ESXI
Synology active backup business
異常狀況:
解決過程:
原機配置了較高的CPU與RAM,還原後,目的esxi上資源不足,無法開機,把虛擬機的CPU與RAM調低後,就可以正常開機
Environment:
ESXi
Synology Active Backup for Business
Issue:
After restoring a virtual machine using Synology Active Backup for Business to another ESXi host, the VM fails to power on and shows an error.
Resolution:
The original VM was configured with relatively high CPU and RAM.
After restoration, the target ESXi host did not have sufficient resources to support that configuration.
By reducing the VM’s CPU and RAM allocation, the virtual machine was able to power on normally.