Applies to: Plex-Earth 2027, 2026, 2025 Audience: End users
📌 Using an older version of Plex-Earth? Some error messages may differ in older versions. Contact us at support@plexscape.com for assistance.
This article lists common error messages you may encounter in Plex-Earth. Some of these messages have dedicated support articles — if so, you’ll find a link to those. For the rest, we provide quick fixes and explanations here.
Use the search function (Ctrl+F / Cmd+F) to find your error message quickly.
Object reference not set to an instance of an object
Cause: There are several reasons this message might appear, such as connectivity issues, imagery/terrain issues, etc., which may or may not hinder the user’s workflow.
Solution: Make sure you have the latest Plex-Earth build installed: Plex-Earth download. This might be a one-time or temporary message. If the issue happens repeatedly, please submit your log files following this guide to investigate further: Submit your Plex-Earth files for Troubleshooting.
Activation Code from Another Version
Cause: This happens when you try to use an activation code from a different version of Plex-Earth with version 2027 or 2026.
Solution: Uninstall the current version of Plex-Earth, then follow the steps in this guide to download and install the correct one: Installed the wrong version of Plex-Earth – Activation Code from Another Version.
Activation Limit Reached
Cause: Plex-Earth subscription has already been activated on the maximum number of computers or Windows profiles allowed. Even if Plex-Earth was uninstalled from your old computer, the activation is still registered with us.
Solution: If you have access to the Plex-Earth Console, you can release the old workstation and then activate Plex-Earth on the new computer. If you don’t have Console access, please contact our Support team, and we will release the workstation for you. More info can be found here.
Oops! Something went wrong! You may try to sign in again.
This is a generic error message that may appear alongside one of the following messages:
10000: A server error (10000) has occurred!
Code = InternalServiceError Message = Start Service Failed
Code = ydg Message = Start Service Failed
Code = 10021 Message (10021) -> No more concurrent checkouts allowed
Code=InternalClientError Message=Start Service Failed. (20001): Initialization error! System.AggregateException: Failed to compute 'Part1' (WMI)!...
👉 To see possible causes and solutions for this message, visit: Oops! Something went wrong! You may try to sign in again.
Connectivity problem: We are sorry, but it was not possible to contact the web server. Please check your connectivity to the internet and try again.
Cause: This error points to a connectivity issue. It usually means Plex-Earth was unable to reach the web server due to internet problems, proxy restrictions, or firewall interference.
Solution: Follow the steps in this guide: Connectivity Issues with Plex-Earth Service.
Not Initialized: Plex-Earth service configuration could not be initialized
Cause: This might be a one-time message or temporary message due to a server outage. Otherwise, the user may have a connectivity issue.
Solution: Restart your AutoCAD session and/or restart your PC. If the issue continues, there could be an ongoing temporary server outage. Otherwise, to confirm if it is a connectivity issue, please submit your log files following this guide to investigate further: Submit your Plex-Earth files for Troubleshooting.
EarthExtension not initialized
Cause: This can be a temporary issue where the Plex-Earth service fails to load. If it persists, it might be due to a connectivity problem.
Solution: Restart your AutoCAD session or restart your PC. If the issue continues, it may be a connectivity issue. Follow the steps in this guide: Connectivity Issues with Plex-Earth Service.
Command unavailable / Unknown Command
Cause: This can occur due to an incompatibility, if Plex-Earth is not loaded properly, or due to a connectivity issue.
Solution: Make sure Plex-Earth is properly installed and loaded in CAD. Ensure your AutoCAD version is supported and your internet connection is stable. Restart AutoCAD and, if needed, your PC. If it is not any of the above, it might be a connectivity issue: Connectivity Issues with Plex-Earth Service.
eOutofRange
Cause: This error occurs when there are too many breaklines or each one contains an enormous number of points. The number of triangles required for the mesh becomes too high, making the operation inefficient — AutoCAD throws this error to avoid crashing.
Solution: If you have Civil 3D or Map 3D, try weeding the polylines several times using the steps here: Simplify Polylines and Create a Terrain Mesh from Existing Contours. Otherwise, or if the issue persists, break the area down into smaller sections and try again.
Sorry, we have no imagery here
Cause: This can be seen when importing Google Maps imagery and is most often caused by an incorrect georeference applied to the drawing.
Solution: Make sure the correct georeference is applied and the units in CAD and Plex-Earth match. You can follow this tutorial on georeferencing: Georeference Introduction. If the issue persists, please send your drawing to support@plexscape.com for further investigation.
Images Limit: You've reached the maximum number of consumable images allowed for this period
Cause: This is usually a temporary issue due to inactivity and is a bug in older Plex-Earth 2026 builds. Otherwise, you might have reached the image limit for your account, which will reset upon renewal.
Solution: Try to import again, and if that does not work, restart your session, which generally solves the issue. Please install the latest Plex-Earth build here to avoid getting it in the future. Otherwise, please send this error to support@plexscape.com for further investigation.
Out of bounds
Cause: The area of interest is being detected as outside the bounds of the applied coordinate system.
Solution: Check if the applied georeference is correct. If the georeference applied is correct, check if you have a custom UCS applied and reset to the default WCS, then reimport. If the issue persists, please send us your drawing for further investigation.
'gx' is an undeclared prefix / 'xsi' is an undeclared prefix
Cause: Malformed or non-standard KML/XML file structure, often caused by manual editing or using an unsupported format.
Solution: Follow this guide: Not Well Formatted KML – xsi Undeclared Prefix Errors During Import.
Value cannot be null
Cause: This message can have several different causes.
Solution: This might be a one-time or temporary message. If the issue persists, please submit your log files following this guide to investigate further: Submit your Plex-Earth files for Troubleshooting.
The calling thread cannot access this object because a different thread owns it.
Cause: This may be caused by a conflict in CAD and Plex-Earth thread handling or by third-party AutoCAD add-ons interfering with Plex-Earth’s behavior.
Solution: Try uninstalling any third-party CAD add-ons. If the issue continues, please submit your log files following this guide: Submit your Plex-Earth files for Troubleshooting.
Array dimensions exceed the supported range
Cause: This error typically occurs when attempting to import a very large area. For such large extents, georeferencing becomes inaccurate due to the curvature of the Earth. It may also happen if you've selected a coordinate system that does not support your area.
Solution: Try reducing the size of the area you're working with. If needed, switch to a more suitable coordinate system for your region. Breaking the area down into smaller sections may also help avoid this error.
Initialization Error: Version '2X.X.XXXX' not supported
Cause: This can be a temporary issue or most likely due to a connectivity problem.
Solution: Uninstall Plex-Earth first and install the latest build, which can be downloaded here. If the issue continues, restart your PC; otherwise, it is a connectivity-related issue. For connectivity issues, please refer here: Connectivity Issues with Plex-Earth Service. For further assistance, please submit your log files to our Support Team: Submit your Plex-Earth files for Troubleshooting.
Variations: Version '26.0.9159' not supported, Version '26.1.9228" not supported, Version '26.3.9428' not supported, Version '27.0.9608' not supported, Version '27.0.9649' not supported
Unable to Connect to Plex-Earth Services
Cause: This can be a temporary issue or most likely due to a connectivity problem.
Solution: Restart your PC or connect to a different network if it is a connectivity-related issue. For full troubleshooting for connectivity issues, please refer here: Connectivity Issues with Plex-Earth Service. For further assistance, please submit your log files to our Support Team: Submit your Plex-Earth files for Troubleshooting.
No Internet Connection: We couldn't establish an internet connection. Please check your connection and try again.
Cause: This can be a temporary issue or most likely due to a connectivity problem.
Solution: Restart your PC or connect to a different network if it is a connectivity-related issue. For full troubleshooting for connectivity issues, please refer here: Connectivity Issues with Plex-Earth Service. For further assistance, please submit your log files to our Support Team: Submit your Plex-Earth files for Troubleshooting.
bff at ResumeActivationFlow()
This only appears in 26.0 versions.
Cause: This message can have several different causes and is only present in older 2026 builds.
Solution: Uninstall Plex-Earth first and install the latest 2026/2027 build, which can be downloaded here. If you are still encountering issues, please submit your log files following this guide to investigate further: Submit your Plex-Earth files for Troubleshooting.
Still Having Issues?
If your error message is not listed here, or if the suggested solution did not resolve your issue, please contact our support team with the exact error message, and/or a screenshot, and a description of when it appears.
FAQ
How do I know which version of Plex-Earth I have installed?
Open CAD and click My Account on the Plex-Earth ribbon. The version number is displayed there. You can also check via Control Panel → Programs → Uninstall a Program and search for "Plex".
I keep getting random one-time errors that don't repeat. Should I be worried?
Not necessarily. Some errors, such as "Object reference not set" or "Value cannot be null", can appear as one-time occurrences due to temporary server or connectivity hiccups. If the error does not affect your workflow and does not repeat, it is generally safe to ignore. If it recurs, submit your log files.
How do I get the latest Plex-Earth build?
Download it directly from plexearth.com/download. Always uninstall your current version before installing a new one for a clean update.
Several of these errors mention connectivity as a possible cause. How do I know if I have a connectivity issue?
A quick way to check is to open a browser and navigate to
https://apisrv-v2-winuser.plexearth360.com. If the page
loads, your connection to Plex-Earth services is open. If it fails.
times out or you still encounter the same issue, follow the full guide:
Plex-Earth Won't Connect to the Internet – Connectivity Troubleshooting.
My error message is not listed here. What should I do?
Contact us at support@plexscape.com with the exact error message, a screenshot if possible, and a description of when it appears. We will investigate and update this article if needed.
How do I submit my log files?
Navigate to %appdata%\Plexscape, compress the folder into
a ZIP file, and send it to
support@plexscape.com. Full
step-by-step instructions are available in
How to Submit Your Plex-Earth Files for Troubleshooting.
I get the "Activation Limit Reached" error but I only have one computer. Why?
This can happen if Plex-Earth was previously installed on a different computer or Windows user profile, or if the activation was not properly released before reinstalling. Contact our support team, and we will release the old activation for you.
The "Images Limit" error appeared, but I haven't imported many images. Is this a bug?
Yes, in older Plex-Earth 2026 builds, this could appear incorrectly due to a known bug. Updating to the latest build resolves it. If you are already on the latest build and still see this error, contact us at support@plexscape.com.