Read time 4 minutes
Joint Engine Technology (Jet) error in Exchange is familiar to businesses relying on the Exchange database. As per user reports from several Microsoft forums, the error is seen when you try to mount an EDB file to an Exchange Server. The occurrence of errors such as “0xFFFFFC01 JET_errInvalidPath” brings an unwanted pause to your workflow. While you can fix it with a simple correction in EDB file path, sometimes the issue requires repairing the database (when the header is corrupt).
Additionally, the most crucial task in fixing this error is analyzing its nature and the message it is throwing. Properly identifying the reason will help you simplify the recovery. We will discuss valuable ways to fix this error without encountering any data loss.
Understanding the “0xFFFFFC01 JET_errInvalidPath” error
The error code 0xFFFFFC01 is telling you that there is an issue with the EDB file path (that the Exchange Server is trying to access). In such a situation, the Extensible Storage Engine (ESE) service fails to access the directory where your EDB file is. As a result, the Exchange Server cannot complete the database mounting process.
You may not get a pop-up regarding the issue. To verify its existence, you must check the Event Viewer and look for the following entry:
| Log Name | Event Source |
|---|---|
| Event Source | MSExchangeIS (or ESE) |
| Event ID | 9518 |
| Task Category | General |
| Error Code | 0xFFFFFC01 |
| Symbolic Name | JET_errInvalidPath |
After confirming the error, let’s look at the reasons why you are getting it.
Reasons behind 0xFFFFFC01 JET_errInvalidPath error
Primary reasons behind the occurrence of jet invalid path error are:
- The database file path was changed due to a server reboot or abrupt shutdown. A single letter change, even an extra white space, in the directory path can make the path completely inaccessible by any Exchange service, especially the one responsible for mounting the database.
- You can also get the error message when an antivirus program has blocked read/write access to the drive where database file is stored.
- Another common reason for the error is a corrupt EDB file. A virus attack or human error can damage the Exchange database header, which makes it impossible to read the correct EDB file path, thus leading to the error 0xFFFFFC01. In such a case, you must repair EDB files to save the data.
Reliable solutions to fix the 0xFFFFFC01 error
To resolve the specified error message and mount the database in Exchange Server, try the following solutions:
Method 1. Disable or Update the Antivirus
The simplest method to try is confirming whether the problem has occurred due to an antivirus program. To verify it, follow these steps:
- Disable the antivirus program for a while.
- After that, again try mounting the database file in MS Exchange Server.
If the mounting process is completed successfully, then it means the problem was due to the antivirus. In that case, you must make changes to the antivirus settings and make it skip accessing the Exchange database files. Otherwise, you may face the same issue again in the future
Method 2. Verify Locations of the Database Files
If the previous solutions didn’t work, you must verify the location of the database in the Exchange Server. Use the following steps to access and correct the locations:
If you have Exchange Server 2010 and later versions currently running in your system:
When you are currently making use of the Exchange Server version 2010 and later, you have the option to use the Exchange Management Shell (EMS). EMS allows you to obtain information about the EDB file using the help of Get-MailboxDatabase cmdlet. With that information, you can verify if the path is correct. After that, verify if it matches the directory from where you are trying to mount the database and if there is any mismatch, correct it to resolve unable to mount database error.
For Exchange Server 2007 and earlier:
- Click Start > All Programs > Microsoft Exchange > System Manager.
- Expand Administrative Groups and right-click the storage group that contains the mailbox store. Click on Properties.
- Select the General tab and examine the path in the Transaction log location box and in the System path location box.
- If you found the path wrong, then click Browse and specify the correct path. Then, click OK to save.
- Repeat steps 3 to 7 for each storage group in the Server to verify the file location and fix any issue (if present)
However, if all the storage group locations are accurate, then you need to verify the database location for each store in each storage group with these steps:
- Select and expand a storage group. Right-click the StoreName (ServerName) and click Properties.
- Select the Database tab. Verify the path in the Exchange database box and the Exchange streaming database box.
- If any one or both of the paths are found incorrect, then click Browse to locate the correct database file.
After correcting the paths, mount the database. If you still get the JET_errInvalidPath error, then your EDB file is corrupt. Try the next method to fix it.
Method 3. Fix EDB file corruption to resolve 0xFFFFFC01 JET_errInvalidPath error
If the path of your database files is correct, then the issue is in the header of the EDB file. When the header part is damaged, the Exchange Server mounting services fail to read the path where the database file is present.
A malware attack, human error, or improper server handling can cause it. To fix it, you can use eseutil to fix the Exchange database file. It’s a native, free utility that comes preinstalled with Exchange Server. However, this free tool requires log files for recovery. In case log files are missing, you have to perform a hard recovery that basically deletes every corrupt page from the database, leading to permanent data loss.
When you cannot afford to lose your users’ mailboxes, you must use a professional Exchange recovery tool to remove corruption without data loss. I recommend using Kernel for Exchange Server. The tool can read and repair severely corrupt databases and provides multiple options to save the recovered data, either locally (PST file) or online (Exchange Server).
Conclusion
Be cautious when handling your Exchange Server. Improper handling or a virus attack can lead to unexpected problems like 0xFFFFFC01 JET_errInvalidPath. Fix the problem with the methods discussed above. However, if corruption is the culprit, don’t risk your data with the free method, let the professionals handle the recovery.
Frequently Asked Questions
Ans.
1. Exclude the Exchange folders from antivirus scanning.
2. Avoid abrupt system shutdown & other irregularities.
3. Make sure there is at least 20% free space available at all times on the drive hosting the server.
4. Monitor server health and disk health periodically.
Ans. You can reduce the size of your EDB file with these methods:
1. Extract user mailboxes locally. For this, use Exchange Admin Center (EAC) or an EDB to PST converter tool.
2. Delete obsolete data items and perform offline defragmentation with eseutil /d
3. Set up rules to automatically delete emails with large attachments.
Ans. Directly mounting the EDB (if orphaned) is not possible. So, you must use a professional tool that supports direct offline EDB to Live Exchange migration. However, before migration, kindly check if it is not corrupt.
