How can I fix Allplan program data?
You can fix Allplan program data by renaming the program folders and installing an update.
Due to the new names, Allplan cannot find the resources during the update. Consequently, it creates new resources.
To fix Allplan program data, do the following:
You need the latest installation package for your version.
You can download this package from Allplan Connect (www.connect.allplan.com)
Copy the zip file to the local computer and unzip the file.
- Open the Services application of the Allplan version you want to fix.
- Select Service -> Windows Explorer -> CAD program folder.
- Rename the "PRG" folder "PRG_OLD". If Windows Explorer tells you that a file is still in use, restart the computer and try again.
- Start the *.exe file of the installation package you just unzipped.
- Select "Update installation".
- When Setup prompts you for the license, select "Current license file" or "Use active license".
- Select "Minimum" for the Setup type.
Allplan gets new program resources during installation.
As soon as the installation is complete, you can test how Allplan behaves.
If you are not sure, give these instructions to your system administrator.
Keep in mind that you install the version of the installation package you downloaded. This means that you may have to reinstall any subsequent hotfixes.
Does Allplan create backup files (*.bak)?
How can I use these files?
Allplan creates backup files when you do the following:
- Copy, Move Elements between Documents …
Allplan creates a backup file of the destination drawing file or layout.
- Deleting drawing files and layoutsin the "Open on a project-specific basis" dialog box
If you have selected "Create backup copies of drawing files", Allplan creates a backup file of the drawing file or layout.
- Importing data to drawing files
If you have selected "Create backup copies of drawing files", Allplan creates a backup file of the drawing file.
Note on points 2 and 3:
To select the "Create backup copies of drawing files" option, click
Tools -> Options -> Desktop environment -> Save/load area (until V2009 Global Options -> Miscellaneous -> Autosave, Backup)->Create backup copies of drawing files.
If need be, you can restore the original drawing file or layout.
Make a note of the drawing file number or layout number and determine the corresponding project folder as follows:
Services application -> Service -> Hotline Tools -> wopro
Open this folder in Windows Explorer.
Rename the corresponding drawing file "tb000001.ndw" "tb000001.ndw.old" or the corresponding layout "pb000001.000" "pb000001.000.old.", for example.
Delete the bak extension from the corresponding bak file.
You have inadvertently copied the wrong elements to drawing file 4711.
1st step: exit the project in Allplan.
2nd step: delete file tb004711.ndw or rename it tb004711.ndw.old.
3rd step: find file tb004711.ndw.bak and rename it tb004711.ndw.
You have inadvertently copied the wrong elements to layout 815.
1st step: exit the project in Allplan.
2nd step: delete file pb000815.000 or rename it pb000815.000.old.
3rd step: find file pb000815.000.bak and rename it pb000815.000.
These backup files can considerably increase the volume of data to be backed up. So it is a good idea to delete the .bak files you no longer require before you start backing up data. To delete the .bak files, you can select the Services application and click Utilities -> Delete temporary files.
You can also find this information in the help for Allplan. Please refer to the topic "Using bak files".
You have installed Allplan on several workstations in the network with a shared data storage and now additionally you want to work on this shared network drive with Workgroupmanager.
Before making this change, it is essential to perform a complete data backup on the server and on all workstations.
We recommend to have this work done by an experienced technician!
The conversion may only be carried out within one version, i.e. if necessary, then the upgrade to the same version should be carried out first and only after the upgrade has been completed should the conversion described here be carried out.
For the network installation, the data is on the server.
However, the configuration files for the workgroup manager are missing. These are only installed during a new installation.
The new installation can be done - if the following steps are followed - in the existing 'central file storage folder'.
Open the Allmenu/Services at all workstations and note the following paths, which are displayed in the Allmenu window:
Central file storage folder (this should be the same on all workstations)
First update your license on all workstations.
In order to be able to use the Workgroupmanager function, you must have purchased it additionally. You will then receive an update for your license(s).
Perform the update as follows: https://connect.allplan.com/de/faqid/20150618142528.html.
1. Uninstall Allplan
Uninstall (only) Allplan on one workstation.
2. New installation
Now perform a new installation of the same version on this workstation again.
Since your license now includes the Workgroupmanager option, this option should also be displayed in the setup.
During the installation, enter the following installation paths:
local (e.g. C:\Programs\Nemetschek\Allplan)
Central file storage folder:
Browse -> Network... select
Enter here again the central file storage folder which you have determined before in the Allmenu.
Afterwards the installation can take place.
3. Test start, create new users and restore backup
After successful installation, test the Allplan start once.´and close Allplan again.
Then, as administrator, create the new users who will work with Allplan via:
Allmenu -> Workgroupmanager -> Manage users -> Right click -> Create user.
Under "User name", a freely selectable Allplan user name with up to 8 characters in length can be assigned.
Under "Windows user name", the user name that the user uses when logging on to the computer must be specified.
Important: If the user logs on to the computer via a domain, this must also be specified under "Windows user name", e.g.: DOMAIN\User
Under "User group" the administration right can be granted:
Administrator" must be selected in the drop-down menu. Existing users can thus also be granted administration rights at a later date.
When setting up the user folder, always select the server here.
Then copy the contents of the previous local user folder (...\usr\local) from the local computer to the new user folder of the newly created user via the Explorer. The user folder is located on the server under ...\Nemdata\usr\<username>.
4. Update project management file
Rename the project.dat file in the server folder...\Nemdaten\Allplan\Net to project.alt. Then perform the following steps:
Allmenu -> Service -> Hotline Tools -> reorg -> Restore project administration file.
5. Set up user rights for the projects
Start Allplan as Allplan administrator and assign the access rights for the projects to the newly created users via
Allplan -> File -> ProjectPilot / Administration
Select the Projects node and mark the desired projects in the right-hand window, to which authorized users are to be added or removed (CTRL or Shift key).
Right-click on one of the selected projects and then click Add / Remove Authorized Persons... in the context menu.
The Add / Remove Authorized Users dialog box appears.
In the list, check all the users you want to add or remove as permissions to the selected projects.
The displayed user list is for selection purposes only; it does not represent an overview of the permissions currently assigned to the projects.
Click Add or Remove.
The selected users are added to or removed from the project as authorized persons. It does not matter whether already assigned permissions are added again or unassigned users are removed.
Setting project owners for multiple projects
In the ProjectPilot, in the right window, select the desired projects for which you want to set the owner (CTRL or Shift key).
Right-click on one of the selected projects and then click Change Project Owner... in the context menu.
The Set owner dialog box appears.
In the list, select the user you want to set as the owner of the selected projects.
Note: The displayed list of users is for selection purposes; only one user can be set as the owner.
7. Add the remaining workstations to the workgroup
You can subsequently switch on the workgroup manager on the remaining workstations and do not have to reinstall Allplan on these computers.
Open the following key in the registry editor
Change the value NETMANAGER from off to on.
Restart the allmenu. If the user has been set up as described above, the allmenu now opens with the note Workgroupmanager: YES and the user path on the server.
This completes the changeover.
What can I do if Allplan no longer starts after I have upgraded and the following messages appear?
After this, Quality Reporter displays an error report.
Exit Allplan on all workstations and do the following:
Open the Services application and make a note of the path to the 'central file storage folder', which is displayed in the Services application window.
In addition, check whether the workgroup manager line is followed by 'Yes' or 'No'.
Open the central file storage folder in Windows Explorer.
If the workgroup manager line is followed by
'Yes', open the NET subfolder.
'No', open the PRJ subfolder.
Find the 'project.dat' or 'project.Dat.xm' file in the NET or PRJ folder and rename it 'project-old.dat'.
After this, do the following:
Services application -> Service -> Hotline Tools -> reorg -> OK -> Restore project management file -> OK
The program creates a new, correct project management file and you can start Allplan again.
If you come across error messages while doing this, please email the following information to firstname.lastname@example.org:
- Describe exactly what you did before the error or crash occurred.
- The error message itself (as a screenshot).
- The log file (trace).
- A Hotinfo support request with question 01.
You have installed Allplan on several local workstations. Now you want to change the installation so that you can access a common network drive.
Before you switch to a network installation, it is essential that you back up all the data of all the workstations.
We strongly recommend that you take advantage of the expertise of Nemetschek’s technical support staff. We are happy to help you!
The following description shows how to change several workstations where Allplan is installed locally and the project data is also stored locally on each computer to workstations with a common network drive without Workgroup Manager.
1st - getting ready
Choose one of the workstations where you will install all the projects and the office standard (hereinafter referred to as the main workstation).
First, move all the projects to the main workstation.
1.a: copying resources into projects
To make sure that the projects in your office have a uniform appearance, change the path settings for the projects' resources to 'Project'.
Make the following setting for each project:
Allplan -> File menu -> ProjectPilot - Admin -> select the individual projects one after the other -> right mouse button -> Properties -> Settings tab
Set the path settings for 'Pen and line definitions', 'Fonts', 'Patterns, hatching styles, area styles', 'Bar and mesh cross-section catalogs', 'Layer structures, line styles, drawing types' and 'Attributes proposed' from 'Office' to 'Project', if necessary.
The corresponding elements are copied from the office standard directly to the project. This ensures that the project settings stay the same even when you copy the project to the new server with the new office standard.
1.b: same folder name as project name
Open the 'General' tab and select the 'Same folder name as project name' setting if you want to proceed as described in 2b.
1.c: pen color ("Color stands for pen")
The pen color for the "Color stands for pen" setting is a user-specific setting that is not saved in the project but in the user folder (...\Usr).
2.a: backing up projects of the individual workstations and importing them to the main workstation (recommended method):
Back up the individual projects. To do this, open the Services application and select Data Backup -> Create -> Entire folders -> Projects.
You can back up several projects in a single operation.
Before you start, specify the backup folder on the network or on the local hard disk: Services application -> Configuration -> Backup path ->Browse for Folder.
The next step is to import the saved projects to the main workstation.To do this, open theServices application -> Data Backup -> Import -> Projects Before you import the individual projects, you can create new Allplan projects at the main computer. As an alternative, you can also create a new project during the import.
2.b: backing up projects of the individual workstations and importing them to the main workstation (special approach):
This approach should only be used with good reason for exceptional cases as it requires in-depth knowledge of Windows.
With this method, Windows Explorer is used to import the projects to the main workstation.
If some project names exist twice, you need to rename these projects before you back them up.
You can then rename the existing 'project.dat' file in the Prj folder of the main workstation.
Next, select the Services application -> Service -> Hotline Tools -> reorg -> Restore project management file.
The system creates a new project administration file (project.dat), which should list all projects with names.
Now the main workstation contains the latest version of all the projects of the office.
3rd - merging project defaults
Open ProjectPilot at the individual workstations and copy the elements you want to transfer (symbols, smart symbols, lists, schedules, and so on) to the external path. Of course, you can set the external path to a common network folder that can be accessed by all workstations.
Next, open ProjectPilot at the main workstation and copy the contents of the external path to the office standard.
4th - data backup
- Back up the projects, office standard and user settings at the main workstation:
You can also copy the ..\prj (projects), ..\std (office standard) and ..\usr (user folder) paths to a backup folder (Nemsic, for example) on the hard disk.
- In addition, you need to back up the ..\usr\local folder at every stand-alone computer.
- Export the user interface setting of each user to a file: Allplan -> Tools - > Customize .... -> Export...
5th - uninstalling
Remove Allplan from all workstations.
6th - reinstalling
Before you install the same version again, create and share a folder (Nemdata, for example) on the future data server. Create a subfolder - Allplan - in this folder.
The next step is to reinstall the same version on all the workstations.
Specify the following installation paths:
local (C:\Programs\Nemetschek\Allplan, for example)
Central file storage folder:
Browse -> Network...
Find the sharedNemdata folder and select the Allplan folder.
After this, start installing.
7th - testing the start and restoring the backup
After the installation (check whether Allplan starts), copy the ..\prj and ..\std folders you backed up from the main workstation to the new ...\Nemdata\Allplan server folder.
Next, use Windows Explorer to copy the contents of the former user folder (…\usr\local) of the stand-alone workstation to the new user folder of the computer you just installed.
8th - updating the project administration file
Go to the project.datfile in the ...\Nemdata\Allplan\Prjfolder and rename itproject.alt.After this, do the following:
Services application -> Service -> Hotline Tools -> reorg -> Restore project management file.
9th - summary
Now all the workstations access a common network drive with the same project pool and office standard.
With this type of installation, only one user can access a project at any one time. If several users are to work on a project at the same time, you need to install Workgroup Manager.
Why does ProjectPilot open with the following error message:
"Unable to create ProjectPilot control. Is the registry correct?"
The reason for this is usually an "external path" that no longer exists. When you start ProjectPilot,
the program tries to access the "external path", which is stored in the Windows Registry.
If this path no longer exists, you will see the above error message.
To correct this error, please do the following:
- Services application
- Service menu
- Windows Explorer - CAD program folder
- The path to the "User folder" is displayed in the window of the Services application. Open it in Windows Explorer.
- Find the "extern.cfg"file in this user folder and delete this file.
Now try to start ProjectPilotagain. If the problem still occurs, please do the following:
Start the services application -> Service -> Windows Explorer -> CAD program folder.
Open the "PRG" folder.
Find the following file: "NemProjectPilot10.exe"
Right-click this file -> select "Run as administrator" on the shortcut menu.
ProjectPilot should now start.
Try to start ProjectPilotstraight from Allplan. If the problem is still not solved, please do the following:
- Services application
- Service menu
- Windows Explorer - CAD program folder
- The Allplan program folder opens.
- Rename the "PRG" subfolder "PRG_OLD".
- Start installing the program from the current Allplan DVD.
- Select "Update installation".
- Select "Current license file".
- Set the setup type to "Minimum".
After installation try to start ProjectPilotagain.
How can I restore a lost building structure or layout structure?
To restore a lost or corrupt building structure or layout structure, you can do the following:
- Close Allplan.
- Open Windows Explorer, go to the central file storage folder of Allplan and open the "Prj"folder. Open the corresponding project folder and the "BIM" subfolder.
If the "Same folder name as project name" option is not selected for the project, a number is used for the folder name in the "Prj"folder. In this case, open the Services applicationand select the woprohotline tool (Services application -> Service -> Hotline Tools -> wopro). Select the corresponding project by double-clicking its name. An information dialog box shows the folder and file name of the project.
- You can find an XML file for each structure in the BIM subfolder.
Objects derived from building structure:
Allplan_BIM_LevMo_"name of model".xml
- To restore the building structure from a backup, rename the existing file "Allplan_BIM_BuildingStructure.xml" "Allplan_BIM_BuildingStructure.xml.old", for example.
- Switch to the "Backup"folder, which you can also find in the"BIM"folder.
- Select the most recent file that had been created beforethe building structure was deleted, for example, "Allplan_BIM_BuildingStructure.xml.27.5.2008--10-32-21.bak". The characters in bold indicate the date and time of the backup. Copy this file to the "BIM"folder.
- Rename this file by deleting the characters after ".xml". Now the file name is "Allplan_BIM_BuildingStructure.xml".
- Restart Allplan. The last version of the building structure is displayed in the "Open on a project-specific basis"dialog box again.
Using Allplan 2009-2 and later, you can restore the layout structure from a *.bak file straight from the "Open on a project-specific basis: layouts"dialog box.
- Right-click the topmost structural level in the layout structure (project name) and select Load layout structure favoriteon the shortcut menu.
- Open the last version of the Allplan_BIM_LayoutStructure.xml file in the backup folder mentioned above.
If the *.bak files are not displayed, please follow the steps described above.
How to install and run NemSLock Server?
Before installing, check whether the package you received includes the following items:
- Temporary licenses for NemSLock Server, e.g. 1234567a_001_psd.nslsrv
- Temporary licenses for clients, e.g. 1234567a_001_psd_client.nslock
How to install NemSLock Server
- Start the Setup program for NemSLock Server. You can find the latest Setup program on our FTP server:
- Select one of the temporary license files for NemSLock Server. These licenses are valid for 30 days. However, each license includes only one seat of each configuration purchased. The full number of seats purchased will be available to you as soon as you have installed the registered licenses (see below). If you purchased a configuration for one seat only, you will, of course, receive only one temporary license.
- When you opt for the “Custom” setup type, you can choose between the following program features:
You can use this program to administer NemSLock Server. You can also install the console on more workstations so that you can administer the server from a number of different locations. However, you can only connect one console to the server at any one time.
The actual license server.
This tool analyzes the log files of NemSLock Server.
By default, Setup installs all these features.
If you have several temporary licenses for NemSLock Server, use the server console to install the remaining licenses after the installation. The procedure is described in the section "How to install licenses".
How to register licenses
- Open NemSLock 2006 Server Console by clicking the corresponding icon on the desktop or by selecting Start -> All Programs -> NemSLock 2006 Server -> NemSLock 2006 Server Console.
- Click "Modules" on the left.
- Select the seat you want to register. If your license includes configurations for several seats, you must send a separate registration request for each seat. You will then receive a registered license file for each seat. You must install each file.
- Click the "Registration request (register.txt)" button.
- Click "Edit".
- You must fill out all fields marked with an asterisk (*). Make sure you enter your email address correctly, because the registered license file will be sent to this address (and not to the address of the person who sent the registration request!). Click OK to confirm.
- Click "Create registration request". Windows Explorer opens and shows the register.txt file. If this window is closed, you can find this file in the program folder of NemSLock Server. If you installed the program to the path proposed, the path is:
C:\Program Files (x86)\Nemetschek\NemSLock Server 2006\Programs\License
- Now you can use all the options provided by Windows Explorer to copy the registration file to a computer with Internet access on the network. Alternatively, you can also use an USB stick. You can then email this file to us.
- Send the email with the registration request to email@example.com
How to install licenses
- Open NemSLock 2006 Server Console.
- Click "Stop server" on the left.
- Click "Modules" on the left.
- Click "Browse" to navigate to the registered license file.
- Click "Install license file".
- After this, you can start the server again by clicking "Start server".
How to set up users (optional)
- predefined user ALLis created automatically. If there is no other user, each user is given the privileges of the user ALL. By default, this user can use all licenses but cannot check out any licenses. By double-clicking the user, you can change the user's privileges.
- predefined user ALLallows all users to use licenses. In order to do this, the users must be able to access the server. You do not need to create individual user profiles until you want to assign specific rights to individual users or limit access to selected users. predefined user ALL. If you want to work only with individual users, you should deactivate the predefined user ALL by revoking the user's right to use licenses.
- predefined user ALL has administrator privileges unless another user is created and appointed as the administrator. As soon as you have appointed an administrator, ALL no longer has administrator privileges.
- You can enter users in the “Users.mcf” file. predefined user ALL has administrator privileges again. In addition, each user can once again administer the license server using the console.
- The administrator user is not a special user. If there are several administrator users, only one administrator user can start the console for this license server at any one time.
- If you are setting up users without giving administrator privileges to anyone, the program will ask you whether you want to appoint yourself as the administrator.
You can also specify a domain (user authentication for Windows server). However, this is not mandatory. If you do not specify a domain, the program uses the Windows user name for each user.
The program writes the user accounts and the associated access rights as ASCII text to the users.mcf file.
You can find this file in the \Programs folder of the NemSLock Server installation. You cannot rename, delete or move this file. If the program can no longer connect to this file, you must exit NemSLock Server, restart it and enter all users again from scratch. predefined user ALLis retained.
Experienced administrators can use the PowerShell script NemGenUsers.ps1. This file is in the \Programs folder of the NemSLock Server installation or you can find it as an FAQ in Allplan Connect:
How to install and configure clients
- Use one of the nslock license files you received to install the clients. Do not use the trial license or the license server license. It is irrelevant which of the client licenses you use, as the actual license will come from the license server later.
- You do not need to register the clients.
- When switching from Hardlock to NemSLock (server), you need to update the client using a nslock license file.
After having installed the client, you need to switch to the license server:
- Start -> (All) Programs -> Nemetschek -> Nemetschek SoftLock 2006 -> License Manager
- If the license server window is not visible, select "Configure NemSLock Server" at the bottom. Lock this window. All you need to do is click the drawing pin icon.
- Enter the computer name or IP address of the license server in the empty box. Then click the "Update” icon to the right.
- Now the user can select one of the seats provided.
- After having successfully connected to the license server, clear the check boxes for the trial licenses in the area at the top.
- Click "Close" to complete the configuration. Now you can start Allplan.
- If a user selects several configurations for a seat and starts Allplan, the license server will provide the required licenses; in other words, starting Allplan once might require two licenses. Consequently, fewer licenses are available to other users.
- 2014-1 and later: If the latest version of License Manager is installed (file version 1. 0. 26. 153 or later, see License Manager- Options- System), you can also select several licenses. If one of the selected licenses is currently being used by someone else, the program will automatically select the next available license.
- Clients communicate with the server by TCP/IP via port 10977. So you need to configure the firewall accordingly.
- The license server and the licenses are downward compatible; they can be used in conjunction with older Allplan versions.