Overview
We have received some reports where users have encountered an “Unspecified error” in certain situations when accessing or using M Files.
Here's an example of the error message that may appear for a user:
CoShellView.cpp, 6451, Unspecified error. (Unspecified error) (0x80004005)
These reports have been observed with M‑Files Desktop versions 26.3.15818.7 and 26.3.15818.13.
Some reported scenarios in which the error occurred include:
- Connecting to a vault with the M-Files Desktop client.
- Attaching a document from an M‑Files vault to an email using Classic Outlook.
- Saving an Office file (e.g., Excel) to the vault using File -> Save As via the M-Files virtual drive (by default M:).
Solution
We have made a fix for this issue (ID CE-3335), and the fix is included in M-Files Online 26.3 SR4 (26.3.15818.16) and later versions. This fix is implemented on the M-Files Desktop client, so upgrading M-Files Desktop is required to receive it. The information is also documented on our release notes page.
M‑Files Desktop can be updated either via automatic updates or by using the installation package and selecting the Simple upgrade option (see Manually updating M-Files). The latest installation packages are available on our downloads page.
If you still encounter "CoShellView.cpp, 6451, Unspecified error (0x80004005)" type of error in some situations with the 26.3.15818.16 version (or newer), please report it to us by submitting a support case via our Support Portal.
Workarounds
The following workarounds can help with the issue before updating M-Files Desktop to a newer version with the fix.
If a user encounters the error when connecting to a vault using the M-Files Desktop client
- Restart your computer
- Access the vault with New Desktop or M‑Files Web if these are valid and available options in your organization, in case the issue occurs with Classic Desktop.
If the issue is encountered with Classic Outlook
- Restart your computer
- Drag and drop the file directly from the M‑Files Desktop client into the Outlook email
- Use New Outlook if it is an option in your organization, as switching to it may prevent this error.
If the error occurs in other situations
- Restart your computer
