Plaxis 3D file opening issue - issue with shared drive or file location?

Hi there,

We use a shared drive (N:) at our company to save working files on to

To date, saving, saving over, moving etc. Plaxis 3D project files and data file folder (.p3dat) has normally been OK.

However when I try to re-open this project, the following appears? The projects open with "Not for commercial use", titled COMBIN~N.p3d. Note that this only occurs for this particular project today (i.e. after closing last night, I reopened this morning with no problems) and not for other Plaxis 3D projects saved on the /N: drive server.

For your information please find a snip from the licensing tool - Commercial license allowed.

Note I managed to open the project from "Recent" and save it locally (i.e. on my PC C: drive), and that after "Reading project" loading time the project opens fine as expected.

Any idea on why this project (only) seems to have this issue when saved on :N drive? Potential issue with file location? Thanks in advance

  • Hi James,

    It looks like the folder containing the project files has a different name or is at a different location than the one expected.

    Typically, your folder should contain the PLAXIS file (e.g. “Project.p3d”), and a sub-folder containing the project files with the same name (e.g. “Project.p3dat”). If that sub-folder is not present or has a different name than the PLAXIS file, the project will not be recognized, and you will get the “Not for commercial use” watermark.

    My initial guess is that the file path may be too long, which could cause this issue. Can you copy your project file and folder to a different folder with a shorter path (e.g. N:\PLAXIS\)

    It is also possible that you may have copied only the .p3d file to a different location but forgot to do the same with the sub-folder, or your access to the sub-folder is blocked for some reason.

    Answer Verified By: James Lee 

  • Hi Vasileios,

    Thanks for the help, seems to be a problem with the file path length. Saving to a location with shorter file path sorts the problem out - thanks again.