Allplan installation stops and the "Bad configuration" message appears
When I try to upgrade Allplan, the installation stops after some time and the “Bad configuration” message appears:
What causes this problem and how can I solve it?
The following procedure is at your own risk.
We strongly recommend that you clarify all issues in advance.
Before you change registry entries, always copy the registry keys by exporting them in the Registry Editor. To do this, right-click the key that you want to export, for example, InstallRoot and select Export.
This problem is caused by an incorrect entry for the central file storage of Allplan in the Windows Registry.
You can find the central file storage of Allplan in the following path of the Windows Registry:
HKLM\Software\Nemetschek\Allplan\20xx.0\Installroot - in the "NetDrive" and "NetPath" key values.
In this example, you can find the central file storage of Allplan in the following UNC path: "\\C-C6615S2\Data\Allplan\Allplan 2021"
The name of the shared server folder for the central file storage of Allplan is ..\Data.
The complete UNC path for the central file storage of Allplan is stored in the “NetDrive” key.
When installing Allplan, Setup creates the STD, PRJ folders (plus the NET, USR folders for Workgroup Manager) in the folder under the shared ...Allplan\Allplan 2021 folder (see illustration 1).
For example, the following configurations
NetPath is empty
NetDrive contains not only the shared folder but also a subfolder in the shared folder
cause the problem when you upgrade Allplan.
To solve this problem, you need to adjust the entries in the Windows Registry before you start upgrading Allplan.
You can check the paths entered in the Windows Registry as follows: Open the Services application and select Service - File Explorer - My own CAD projects (PRJ). In the case of Workgroup Manager, select Common CAD projects (PRJ).
Afterward, File Explorer should open, and you should see the relevant folders.
If, however, File Explorer opens the “My Documents” folder under Windows, this indicates that the paths entered in the Windows Registry are not correct.