IT Log & 期權賠錢全記錄

2026/06/17

windbg 查看 memory dmp檔

環境:

win11

windbg

異常狀況:

用windbg 開啟dmp檔，看不到裡面的log分析。

解決過程:

點選 command browser。

執行 !analyze -v ，就會出現記錄，可以查看是什麼原因造成系統異常。

2026/06/10

solidworks 按 del 鍵沒反應

環境:

solidworks

異常狀況:

del 鍵失效，在圖中對任何東西按下del鍵，都無法刪除，沒任何反應

解決過程:

solidworks內對刪除的快速鍵設定不見造成此問題。

從"工具" ->"自定"->"鍵盤"，裡面會有"刪除"的快速鍵可以設定，這邊選擇del鍵，就可以恢復del鍵的刪除功能。

Environment:

SolidWorks

Issue:

The Delete (Del) key stops working.
Pressing the Del key on any object within a drawing or model has no effect, and nothing is deleted.

Resolution:

The issue is caused by the Delete keyboard shortcut assignment being removed or changed within SolidWorks.

To restore the Delete key function:

Go to Tools → Customize.
Select the Keyboard tab.
Locate the command Delete.
Assign the Del key as its keyboard shortcut.
Apply the changes.

After reassigning the shortcut, the Del key will function normally and can be used to delete objects again.

2026/06/09

commvault Alert: Index State Type: Custom Rules - Index State

環境:

commvault

異常狀況:

突然每天都會收到這個警告信，但備份工作都正常，不知是哪邊有問題。

後來發現這個backupset底下的所有虛擬機備份，在這警告信出現前的備份都可以正常還原。

在開始發出警告信後的備份，還原時都會出現錯誤:Could not perform the operation as Log restore failed for Job 161471. Please check Index Server log for more details。

解決過程:

參考ai上的作法，在commvault主機上的C:\Program Files\Commvault\ContentStore\IndexCache，底下有CvIdxDB跟CvIdxLogs資料夾

在裡面找到跟上面DbName相同名稱的資料夾，把他們改名。

重新建立還原工作，系統就會重建裡面的內容，恢復正常~~但試過沒用。

後來重新啟動完整備份，還是一樣的錯誤。

最後解法就是，建一個新的backupset，在裡面對虛擬機建立新的備份工作，備份完測試，可正常還原。

Environment:

Commvault

Issue:

An alert email suddenly started appearing every day, although all backup jobs were completing successfully and no obvious issues were found.

Further investigation showed that:

Backups of all virtual machines under this Backupset that were created before the alert emails started could be restored normally.
Backups created after the alerts began failed during restore with the following error:

Error:
Could not perform the operation as Log restore failed for Job 161471. Please check Index Server log for more details.

Troubleshooting Process:

Based on suggestions found online, the following method was attempted:

On the Commvault server, navigate to:
C:\Program Files\Commvault\ContentStore\IndexCache
Locate the folders under CvIdxDB and CvIdxLogs that have the same name as the DbName shown in the error.
Rename those folders.
Create a new restore job so the system can rebuild the index data.

However, this method did not resolve the issue.

A Full Backup was then executed again, but the restore error still occurred.

Final Resolution:

The issue was resolved by:

Creating a new Backupset.
Creating a new backup job for the virtual machines within that Backupset.
Running the backup again.

After the new backup completed, restore tests were performed and the restore worked normally.

2026/06/03

安裝win11 抓不到pcie ssd硬碟。

環境:

acer主機

Intel 13代 cpu

pcie ssd

異常狀況:

安裝win11，一直抓不到ssd硬碟。

上acer官網找到了irst的驅動，安裝時這個驅動也不支援，還是找不到硬碟。

上intel官網抓到最新一代的irst驅動，卻是exe檔，在win11安裝過程，也沒辦法安裝

解決過程:

intel官網抓到最新一代的irst驅動是exe檔，需在其他台電腦，用powershell指令，去解壓縮，裡面就會有driver這個資料夾。

安裝win11時就可以透過裡面的檔案，載入pcie ssd。

在包含SetupRST.exe檔的目錄中打開終端，方法是右鍵按兩下目錄並在此處選擇「在終端中打開」或「打開 PowerShell」。您可能必須在目錄上按 SHIFT 鍵，才能看到要選擇的正確選項。
透過執行命令 ./SetupRST.exe -extractdrivers SetupRST_extracted 來解壓縮預安裝驅動程式

Environment:

Acer desktop/laptop
Intel 13th Gen CPU
PCIe SSD

Issue:

During Windows 11 installation, the SSD drive is not detected.

The Intel Rapid Storage Technology (IRST) driver downloaded from the Acer support website was loaded during setup, but the SSD still could not be detected.

A newer IRST driver was found on Intel's website, but it was provided as an .exe installer, which cannot be installed directly during the Windows 11 installation process.

Resolution:

The latest Intel IRST package downloaded from Intel's website must first be extracted on another computer.

Download the latest SetupRST.exe from Intel.
Open a terminal (PowerShell or Command Prompt) in the folder containing SetupRST.exe.
Run the following command:


.\SetupRST.exe -extractdrivers SetupRST_extracted

This will extract the pre-installation drivers into a folder named SetupRST_extracted.

To open a terminal in the correct folder:

Right-click within the folder and select "Open in Terminal" or "Open PowerShell window here".
On some Windows versions, you may need to hold the SHIFT key while right-clicking to see the appropriate option.

Copy the extracted driver files to the Windows 11 installation USB drive.
During Windows 11 setup, select Load Driver when choosing the installation disk.
Browse to the extracted driver folder and load the IRST driver.

After loading the extracted driver, the PCIe SSD will be detected and Windows 11 installation can proceed normally.

2026/06/01

MS SQL 維護計劃備份到NAS共用資料夾

環境:

NAS

MS SQL

異常狀況:

MS SQL 維護計劃在設定DB備份的路徑，不能指定到NAS上的共用資料夾。

解決過程:

維護計劃在備份時，執行的身份通常是預設的一個系統服務帳號，可以到"服務"去查。

因為沒辦法在NAS上的共用資料夾上指派存取權限給這個帳號。

所以要換個方法

1.先在AD建立一個群組，然後把MS SQL這台主機的電腦帳號，加到這個群組。

2.接著在NAS上的共用資料夾，指派AD群組有修改權限。

這樣就完成了，備份時，這台主機就直接有權限讀寫，不會被SQL服務執行的身份給影響。

Environment:

Active Directory (AD)

NAS

Microsoft SQL Server

Issue:

When configuring a database backup destination in an MS SQL Server Maintenance Plan, the backup cannot be written directly to a shared folder on a NAS.

Resolution:

When a Maintenance Plan runs, it typically executes under the security context of a SQL Server service account (which can be identified in Services).

Since it is often not possible to assign permissions on the NAS shared folder directly to this service account, the following approach can be used:

Create a new Active Directory security group.
Add the computer account of the SQL Server to this AD group.
On the NAS shared folder, grant the AD group Modify permissions.

With this configuration, the SQL Server host can access the shared folder using its computer account permissions, allowing the Maintenance Plan to read from and write to the NAS share without being affected by the specific SQL Server service account being used.

2026/05/26

Backup exec 備份MS SQL時只能完整備份

環境:

Backup exec

Commvault

MS SQL

異常狀況:

Backup exec 備份MS SQL時，，設定差異備份，還是只會執行完整備份

解決過程:

Commvault 虛擬機備份設定中，如果選擇了File System and Application Consistent，就會把之前Backup exec 對MS SQL備份的備份鏈資訊重置，造成Backup exec之後備份必須做完整備份。

所以要把Commvault 虛擬機備份設定改成下面的Crash Consisten。

Environment:

Backup Exec

Commvault

Microsoft SQL Server

Issue:

When using Backup Exec to back up MS SQL Server, the job is configured for Differential Backup, but it always performs a Full Backup instead.

Resolution:

In the Commvault virtual machine backup settings, if “File System and Application Consistent” is enabled, it resets the SQL backup chain information previously created by Backup Exec.

As a result, Backup Exec is forced to perform a new Full Backup before Differential Backups can continue.

To avoid this issue, change the Commvault VM backup setting from:

File System and Application Consistent

to:

Crash Consistent

2026/05/18

M365 Outlook 寄信時簽名檔內的圖檔變成附件

環境:

m365 office

異常狀況:

突然有愈來愈多使用者寄出的信件，在收件人的outlook，簽名檔內的圖檔會破圖，如下圖，裡面會寫"無法顯示連結的影像。檔案可能已移動............."，然後那個圖會變成附件

解決過程:

比對後發現，因為m365 office會自動更新，有些更新到最新的outlook，才會有這種問題。

然後在去檢查，才發現是圖片如果有設定成"文繞圖"，這個圖變成附件。

只要把"文繞圖"改成"與文字排列"就沒問題了。

後來m365 office自己也把那個問題處理掉了。

版本 2605 (建置 20026.20140)

解決的問題

Word

修正了在經典 Outlook 中使用上下文字換行時圖片無法顯示的問題。

Environment:

Microsoft 365 Office / Outlook

Issue:

An increasing number of users suddenly found that images in their email signatures were broken when viewed by recipients in Outlook.

The image area displayed the message:

“The linked image cannot be displayed. The file may have been moved…”

The image would also appear as an attachment in the email.

Resolution:

After comparison and testing, it was found that the issue only occurred on systems updated to the newer versions of Outlook through Microsoft 365 automatic updates.

Further investigation showed that the problem occurs when the signature image is configured with a text wrapping option.

If the image wrapping style is changed from “Wrap Text” to “In Line with Text”, the issue is resolved and the image displays normally in the email signature.

2026/05/14

Backup exec 2014 無法正常啟動

環境:

windows 2012

backup exec 2014

異常狀況:

windows 2012 做完windows update，安裝完backup exec 2014，執行都會出現錯誤訊息，無法使用

Backup exec 啟動時跳出錯誤，必須直接關閉

問題事件名稱: CLR20r3

問題簽章 01: BackupExec.exe

問題簽章 02: 14.1.1786.0

問題簽章 03: 5371d883

問題簽章 04: mscorlib

問題簽章 05: 4.8.4110.0

問題簽章 06: 5de6dafa

問題簽章 07: 113a

解決過程:

因為windows 系統在做更新時，裝了frameworks4.8，需要把它移除後，backup exec才能運作。

可參考官網說明

https://www.veritas.com/support/en_US/article.100055701

卸载 .NET Framework 4.8 并重新启动服务器。此更新将在已安装的更新列表中显示为 KB4486105 （Windows 2012 R2）、KB4486081 （Windows 2012）、KB4486129 （Windows 2016）、KB4486153 （Windows 2019）。

Environment:

Windows Server 2012
Backup Exec 2014

Issue:

After installing Windows Updates on Windows Server 2012 and then installing Backup Exec 2014, Backup Exec fails to start and immediately crashes with an error message.

Error details: