When starting HyDraw CAD, an error message appears stating that the username is not a valid short file path name
When installing HyDraw CAD on an Active Directory, there can be some permissions issues that do not allow the correct files to be configured in the proper location on the system when HyDraw runs for the first time. To resolve this, registry edits are required. More information regarding which registry edits are required can be found here:
.net framework - error 1325 <username> is not a valid short File Name - Super User
Related Articles
When browsing the file path, unable to see folder other than Desktop
While browsing the path for library or Templates in both MDTools and HyDraw CAD, user unable to see any folder other then Desktop To resolve the issue stop syncing your Desktop folder with OneDrive. Important: Before proceeding, copy the files in ...
When running the exe file from a network location I am receiving an error stating the file is untrustworthy
When running the .exe file from a network location, this error message appears stating the file is untrustworthy: This is not because the file is untrustworthy, but rather because the network location is not listed as a trusted location. All VEST ...
HyDraw CAD 2022 License won't apply and throws an Object Reference error
When applying the HyDraw CAD 2022 CLS ID for Single-user License, the program gives the following error: Follow the instructions below to set an exclusion for the HyDraw CAD executable: Go to Start > Settings > Update & Security > Windows Security > ...
When opening HLM, an error message appears mentioning a missing dll in MS Office 2016
Problem When opening HLM, the following error message appears and forces the application to close: Additionally, when opening HyDraw CAD, the following error appears: Solution: This error appears on users with Office 2016 or Office 365 and is due to ...
When running HyDraw CAD, a message appears alerting me that the 32-bit Microsoft Office is installed
When opening HyDraw CAD, the following message appears, and the library pane does not load symbols within it correctly: This is due to conflicting versions of the Microsoft Access Database Engine To resolve this issue, navigate to the control panel ...