轉到esim並連上網路了,開啟網頁卻又顯示無網路時,要去設定裡把這個esim的漫遊開啟才會開始連線。
如果切到esim後,網路一直不穩,可把手機重開試試。
環境:
windows
異常狀況:
有些檔案的路徑,連同檔名,非常的長,要複製/移至 其他資料夾,就會跳出錯誤,要重新命名,讓長度縮短,才能複製/移至 其他資料夾
解決過程:
如果檔案很多,改名稱太麻煩了,可用free file sync,這是檔案同步軟體,用它來把要移動的檔案同步到其他位置,就可以完成,不會因為路徑名稱太長而無法移動。
Environment:
Windows
Issue:
Some files have very long file paths, including the file names. When trying to copy or move these files to another folder, an error occurs.
The file or folder names must be renamed to shorten the overall path length before the files can be copied or moved successfully.
Troubleshooting and Resolution:
If there are many files, renaming them one by one can be time-consuming.
In this case, FreeFileSync can be used. It is a file synchronization tool that can synchronize the files to another location.
By using FreeFileSync to synchronize the files to the target location, the files can be transferred successfully without being blocked by the long file path issue.
環境:
fortigate 防火牆
異常狀況:
有用戶認證的設定中,要指派token時,會跳出 forticare無法訪問的錯誤訊息。
已經指派過的用戶,要改其他token也是一樣錯誤。
解決過程:
原廠有說明 https://community.fortinet.com/fortigate-3/technical-tip-fortigate-unable-to-access-several-fortiguard-services-due-to-crl-scope-errors-september-2026-229879
執行下列指令清除快取就可以排除問題,不會影響防火牆原本的服務
Environment:
FortiGate Firewall
Issue:
When assigning a token in the user authentication settings, an error message appears indicating that FortiCare cannot be accessed.
The same error occurs when changing the token for users who have already been assigned a token.
Troubleshooting and Resolution:
Fortinet has provided a technical tip regarding this issue:
The issue can be resolved by clearing the FortiGuard cache using the following commands.
This procedure does not affect the existing firewall services.
FortiGate # config system fortiguard
FortiGate (fortiguard) # set fortiguard-anycast disable
FortiGate (fortiguard) # end
FortiGate # config system fortiguard
FortiGate (fortiguard) # set fortiguard-anycast enable
FortiGate (fortiguard) # end環境:
2007,2010,2013,2016,m365 excel
異常狀況:
同一個xlsx檔:
透過m365 excel 開啟後,存檔正常。
透過2007,2010,2013,2016 excel 開啟後正常,存檔的話excel程式就會當掉。
解決過程:
該檔案中,有附上幾個貼圖。
在m365 excel裡可正常看見圖,但在2007,2010,2013,2016 excel 中,看不到圖,只會看到#VALUE!
因為該圖是用m365裡的「圖片置於儲存格內」功能放入,這功能只有在 Microsoft 365 Office 2024,但在其他較舊的excel則不支援。
所以不但看不到圖,就算只是在其他欄位修改資料存檔,都會直接當掉。
Microsoft Excel 2007
Microsoft Excel 2010
Microsoft Excel 2013
Microsoft Excel 2016
Microsoft 365 Excel
Opening the same .xlsx file shows different behavior depending on the Excel version.
Microsoft 365 Excel: Opens and saves normally.
Excel 2007/2010/2013/2016: Opens the file successfully, but Excel crashes when saving.
The workbook contained several images.
In Microsoft 365 Excel, the images displayed correctly.
In Excel 2007/2010/2013/2016, the images did not appear and were shown as #VALUE! instead.
The cause was that the images had been inserted using the "Place in Cell" feature, which is only supported in Microsoft 365 and Office 2024.
Because older Excel versions do not support this feature, the workbook becomes incompatible. As a result, not only are the images displayed incorrectly, but even saving changes made in unrelated cells causes Excel to crash.
The issue is caused by using the "Place in Cell" image feature, which is not compatible with Excel 2007/2010/2013/2016.
To make the workbook compatible with older versions, replace the "Place in Cell" images with standard inserted pictures before distributing the file. After removing or converting those images, the workbook can be opened and saved normally in older versions of Excel.
環境:
Dell server idrc
raid 5
設定過程:
為了增加容量,新增了硬碟。
插入硬碟後,在idrac內,要去"維護"--> "作業隊列"裡面,會出現待執行的工作,就可以看到插入的硬碟,要做何種設定,這邊就可以選擇要擴充到原本的raid中,設定好,這個作業不到幾分鐘就會完成了。。
Environment:
Dell Server
iDRAC
RAID 5
Procedure: Expanding a RAID 5 Virtual Disk
To increase the storage capacity of an existing RAID 5 array, install the new hard drive into the server.
After the drive is installed:
The configuration job itself typically completes within a few minutes.
Monitoring the Expansion Progress:
After the job has been applied:
You can monitor the RAID expansion (reconfiguration) progress from this page until the operation is complete.
Note: Although the configuration job completes quickly, the actual RAID expansion and background initialization may take several hours depending on the RAID controller, disk capacity, and system workload. During this time, the virtual disk remains available, but performance may be reduced until the expansion is finished.
環境:
synology Active Backup for Business
透過"即時還原"功能 ,快速還原整台虛擬機
設定過程:
在Active Backup for Business備份的虛擬機,可以全部完整還原到esxi/hyperv主機上,因為要將所有資料還原回去,時間需要比較久。
但今天只要想要測試一下,可以在還原時,選擇"即時還原"。
這樣的話,還原是將synology掛載到esxi上變成一個datastore,所以還原過程不到幾分鐘就完成了。
可以馬上開始使用,但任何資料異動,會另外儲存,不會寫入虛擬機的vmdk中。
測試ok沒問題,就先關機,回到synology Active Backup for Business中,在還原工作裡找到剛剛的那個工作,選擇"取消",這台虛擬機就會從esxi/hyperv上刪除,datastore也會被卸載,都不需要在esxi/hyperv上做刪除。
Environment:
Synology Active Backup for Business
Instant Restore of a Virtual Machine
Overview:
Active Backup for Business can fully restore a virtual machine to an ESXi or Hyper-V host. Since the entire VM and all of its data must be copied back, a full restore can take a considerable amount of time.
If you only need to quickly test or verify a backup, you can use the Instant Restore feature instead.
How Instant Restore Works:
Any changes made while the VM is running are stored separately and are not written back to the original VMDK files.
Cleanup After Testing:
Once testing is complete:
Active Backup for Business will automatically:
No manual cleanup is required on the ESXi or Hyper-V host.
環境:
synology Active Backup for Business
備份整台虛擬機
異常狀況:
解決過程:
在Active Backup for Business的確是只有整台虛擬機還原的選項。
但可以到Active Backup for Business Portal 裡面,在左上角可以選擇你備份的其中一台虛擬機。
畫面下方就會有時間軸讓你選擇備份的時間點,畫面中間就是每個磁區,你就可以點進去查看裡面所有的檔案,針對需要還原的檔案直接下載到本機中就行了。
Environment:
Issue:
You need to restore specific files from a virtual machine backup, but you do not want to spend the time restoring the entire virtual machine first.
Resolution:
Although Active Backup for Business only provides an option to restore the entire virtual machine, you can restore individual files through Active Backup for Business Portal.
This method allows you to restore individual files without having to restore the entire virtual machine first, saving both time and storage space.
AD裡GPO有些設定不在內建的選單中,但可以透過下載admx檔,增加要透過GPO派送的設定。
以m365 office為例,可以先去下載它的admx檔(https://www.microsoft.com/en-us/download/details.aspx?id=49030)。
下載的時後雖然只有英文版,但下載完,執行後,會將相關的檔案解壓縮在一個資料夾中。
裡面會有admx跟adml檔。
https://www.wisecleaner.com/think-tank/764-How-to-Install-ADMX-and-ADML-for-Microsoft-Edge-Group-Policy-Management.html
admx放在 C:\Windows\PolicyDefinitions\
adml放在 C:\Windows\PolicyDefinitions\zh-TW
環境:
win11
windbg
異常狀況:
解決過程:
點選 command browser。
執行 !analyze -v ,就會出現記錄,可以查看是什麼原因造成系統異常。
環境:
solidworks
異常狀況:
解決過程:
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:
After reassigning the shortcut, the Del key will function normally and can be used to delete objects again.
環境:
commvault
異常狀況:
在開始發出警告信後的備份,還原時都會出現錯誤: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.
環境:
acer主機
Intel 13代 cpu
pcie ssd
異常狀況:
安裝win11,一直抓不到ssd硬碟。
上acer官網找到了irst的驅動,安裝時這個驅動也不支援,還是找不到硬碟。
上intel官網抓到最新一代的irst驅動,卻是exe檔,在win11安裝過程,也沒辦法安裝
解決過程:
intel官網抓到最新一代的irst驅動是exe檔,需在其他台電腦,用powershell指令,去解壓縮,裡面就會有driver這個資料夾。
安裝win11時就可以透過裡面的檔案,載入pcie ssd。
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.
.\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:
After loading the extracted driver, the PCIe SSD will be detected and Windows 11 installation can proceed normally.
環境:
AD
NAS
MS SQL
異常狀況:
MS SQL 維護計劃 在設定DB備份的路徑,不能指定到NAS上的共用資料夾。
解決過程:
維護計劃在備份時,執行的身份通常是預設的一個系統服務帳號,可以到"服務"去查。
因為沒辦法在NAS上的共用資料夾上指派存取權限給這個帳號。
所以要換個方法
1.先在AD建立一個群組,然後把MS SQL這台主機的電腦帳號,加到這個群組。
2.接著在NAS上的共用資料夾,指派AD群組有修改權限。
這樣就完成了,備份時,這台主機就直接有權限讀寫,不會被SQL服務執行的身份給影響。
Environment:
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:
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.
環境:
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:
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:
to:
環境:
m365 office
異常狀況:
比對後發現,因為m365 office會自動更新,有些更新到最新的outlook,才會有這種問題。
然後在去檢查,才發現是圖片如果有設定成"文繞圖",這個圖變成附件。
只要把"文繞圖"改成"與文字排列"就沒問題了。
後來m365 office自己也把那個問題處理掉了。
版本 2605 (建置 20026.20140)
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.
環境:
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:
Backup Exec displays an error on startup and must be closed immediately.
Resolution:
The issue is caused by Windows Update installing .NET Framework 4.8, which is incompatible with Backup Exec 2014.
Removing .NET Framework 4.8 and rebooting the server allows Backup Exec to function normally again.
Reference:
https://www.veritas.com/support/en_US/article.100055701?utm_source=chatgpt.com
The .NET Framework 4.8 update may appear in Installed Updates as:
環境:
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",裡面可以變更網路資料夾的帳號與密碼,修改正確後就可以正常備份。
環境:
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.
環境:
M365 office
異常狀況:
Environment:
Microsoft 365 Office / Outlook
Issue:
When opening Outlook, an error message appears and Outlook cannot be used normally.
Resolution:
After removing the unused accounts, Outlook should log in and function normally again.
1. CZ-T007 先安裝到冷氣機上,安裝時,冷氣機無需斷電。
2. 搖控器拔掉電池,然後按住"溫度上跟下鍵",裝上電池,看到搖控器顯示 "31 bu"的畫面時,放掉上下鍵。
3. 按下"下鍵",畫面會顯示 "31SA"
4. 開啟手機中安裝的Panasonic IOT app。
5. 選擇"新增裝置",選擇無線模組。
6. 照app上的操作,先開啟手機的wifi功能,連上這個無線模組的WIFI,然後再輸入家中的wifi帳號/密碼。
7. 這樣就新增成功了,但要記住,搖控器不能改回原本的樣子了,就保持在"31SA"這個模式下,這時搖控器畫面雖然不會顯示其他的東西,但開關機的功能還是可以用,其他的就在手機上操作。
如果搖控器改回原本的操作模組,無線模組就會無法使用。
環境:
esxi
異常狀況:
在系統裡的進階設定,裡面有一個Security.PasswordQualityControl 參數。
在裡面加入 similar-permit ,存檔後馬上生效,就可以變更密碼了。
環境:
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:
This setting must be applied to all domain controllers.
After applying the change, the issue is resolved.
環境:
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.
環境:
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.
環境:
ESXI 6.7
異常狀況:
底層硬碟RAID擴充完一顆新硬碟後,要在ESXI上也對儲存區進行擴充。
在web console上操作,對著要擴充的datastore ,選擇"增加容量"。
再來選擇"擴充現有..........."。
第三步,要先在分割之前的圖,點選vmfs區塊,然後就會出現一個調整新增容量的設定,選擇要把新增的硬碟,擴充多少容量到vmfs中。
按下完成後,就會出現錯誤,試了很多次,擴充不同的容量,都一樣錯誤:
說明:延伸 VMFS 資料存放區範圍的容量
狀態:失敗 - 無法變更主機組態。
解決過程:
用指令的方式擴充,就成功了。
Environment:
ESXi 6.7
Issue:
After expanding the underlying RAID by adding a new disk, the datastore also needs to be extended in ESXi.
When performing the operation via the web console:
However, after clicking Finish, the following error occurs regardless of the size selected:
Resolution:
Expanding the datastore using the command line (CLI) was successful.