Building Automation Knowledge Base

Issue How to configure PCT memory in Hyper-V. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Hyper-V Cause There is more memory available but PCT 2.0 can't start more servers. Example: Users with over 8 GB of memory can't start more than 36 servers.  Resolution This is because the default memory is set to 8GB, approximately 36 servers. (8GB - 2GB)/.170 GB = 36 server. Open the Hyper-V Manager In the left panel, right-click on "pct" and select Settings. The Setting dialog box opens. In the left pane, under Hardware, select the Memory item. The memory settings open in the right panel. The RAM shows 8192 MB(8 GB * 1024 = 8192 MB), the "Enable Dynamic Memory box" is checked, the Minimum RAM is 8192 MB and the Maximum RAM is 262144 MB(256GB *1024 = 262144 MB).    Enter the amount of memory assigned to PCT, 10240 MB(10 GB) in the example. If the "Enable Dynamic Memory" box is unchecked, the memory assigned to PCT will be 10240 MB. If the "Enable Dynamic Memory" box is checked, the memory assigned to PCT will be between 8 GB and 10 GB(not 256 GB or other amount because the limitation is set at 10 GB from the RAM setting above). R&D recommends not using "Enable Dynamic Memory".   Helpful Link: PCT 2.0 memory usage calculation

Issue How to calculate memory needed for PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause Unclear memory usage in PCT. Resolution The specifications show that the PCT default memory is 8 GB in Hyper-V. Each running PCT server takes 2 GB and 170 MB per running server. A 4-core CPU can run up to approximately 100 servers and an 8-core CPU can run up to approximately 200 servers. Memory Usage calculation example: For 23 servers, i.e. 23*0.170 GB + 2 GB = 6 GB For 36 servers, i.e. 36*0.170 GB+ 2 GB = 8 GB (default) For 47 servers, i.e. 47*0.170 GB+ 2 GB = 10 GB To start 100 servers, 100*0.170 GB+ 2 GB = 19GB   Helpful Link: PCT 2.0 memory configuration in Hyper-V

  Issue Fail to login to the selected server when the User name and Password are correct. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause In the example, the Server is in EBO 3.2.1.630 and the Workstation is 3.2.3.59. The Workstation is at a higher version than the Server but it's not the latest version. PCT loads the incorrect IP(192.168.10.2) in the WS due to the version.     Resolution PCT requires to use of the latest version of WorkStation for all releases (3.2, 4.0, 5.0, 6.0).  For example: EBO 3.2.1.630, 3.2.2.61, 3.2.3.59 and 3.2.4.1009 use WorkStation 3.2.4.4007(CP2) or above. EBO 4.0.1.86, 4.0.2.559, 4.0.3.176, 4.0.4.45 and 4.0.5.7 use WorkStation 4.0.5.3004(CP2) or above.    

Issue When attempting to detach an AS, PCT continues to shown the server as being attached to the ES.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool 1.x (PCT) Cause In PCT, when an AS is detached from its parent ES, the ES name still appears in the Added to parent column of the Servers list. Resolution Once the AS has been detached from an ES it can be added to another ES though Workstation using the following steps even though the "Added to parents" column shows otherwise.   To create a SmartX server In WorkStation, in the System Tree panel, select the Servers folder. On the File menu, point to New and then click Server . In the Create Object wizard, in the Name box, type a name for the SmartX server. In the Description box, type descriptive information about the SmartX server. Click Next . In the Configure IP/DNS Address and Port page, in the Address box, type the IP address or fully qualified domain name of the SmartX server. Notice If the SmartX server has been assigned a dynamic IP address, use the fully qualified domain name of the SmartX server instead of the IP address. In the Protocol box, select a protocol for the SmartX server. For more information, see EcoStruxure BMS Server Communication . In the Port box, enter a port number. Click Create. In the Log on dialog box, in the Password box, type the custom password if required. Click OK.   For more information, see Creating a SmartX Server

Issue BACnet alarm state doesn't update when the monitored variable triggers the alarm in PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause BACnet alarms require a live device to send alarms to EBO. Since PCT doesn't have any live devices, BACnet alarms don't work in PCT. Resolution The BACnet alarm feature is not supported in PCT.

Issue When installing PCT 2 the following error is seen: Error: System.Management.Automation.CommandNotFoundException: The term 'Get-VM' is not recognized as a name of a cmdlet, function,script file, or executable program. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause The Hyper-V Module for Windows PowerShell is not installed. Resolution Follow these steps in Windows 10 to install the Hyper-V Module for Windows PowerShell: Right-click on the Start button and click Programs and Features. In the Programs and Features dialog, click Turn Windows features on or off In the Windows Features dialog, check the box for Hyper-V Module for Windows PowerShell and click OK. The dialog will signal completion and the module will be installed.

  Issue Unable to convert DMP file to SmartX servers with EBO 3.x, 4.x and 5.x using Continuum Conversion Tool(CCT) with PCT 2.0 Example: CCT3.2 is unable to connect to an AS-P in v3.2 created in PCT 2.0 It shows the "The user session is lost, no specific reason has been set" error when trying to connect. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Project Configuration Tool Cause PCT 2.0 is not compatible with earlier versions of CCT Resolution In PCT 2.0, create a version 6.0 ES. In PCT 2.0, create an older version of AS-P. In PCT 2.0, make the older version AS-P a child of version 6.0 ES. In WorkStation 6.0, log on to the ES, navigate to the AS-P, and create the desired MS/TP or Infinet networks. In CCT 6.0, log on to the ES and import and analyze the desired Continuum dump file. In CCT 6.0, click to select the target MS/TP or Infinet networks. When doing so, navigate into the older version of AS-P to select the desired networks. Convert the dump file.

Issue The toolbar icons in PCT 2.0 are jumbled. They seems to be stacked on top of each other, making it hard to use the toolbar. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Issue with the font used by PCT Resolution Follow these steps to resolve the problem: In Windows, navigate to Settings, then Font Settings, and search for "Material Icons". Select Material Icons, then choose Uninstall. Confirm by clicking Uninstall. Close all browser windows used to access PCT, then reopen and browse to PCT again. The toolbar icons should now display correctly.

Issue Need to bind program objects and as detailed in Deploying a Function Block Program to a Server it is not possible to interact (eg. bind its objects to the EcoStruxure BMS objects) with a saved program outside of Builder until it is deployed.  After creating a Builder for Function Block program it saves successfully but generates an "Undefined Problem" error when trying to deploy. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Project Configuration Tool (PCT) Building Operation Builder for Function Block Cause Program execution is not enabled on the specific server within PCT Resolution Follow the steps to enable program execution: In the PCT Client select the server containing the program Expand the Properties on the right hand side Check the "Enable Program Execution" box Save the changes Stop and Start the server as per the message to restart for the changes to apply Clear the message after restart Finally, back in Workstation observe when trying to deploy the program it is successful

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue When adding Server Packages to a new PCT install, the installation process does not complete.    Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Some security policy is interfering with the PCT installation process. The VirtualBoxDisclamer.log shows the following error     Could not add PCTService to BUILTIN\Administrators.   The lack of the PCTService could be responsible for a range of issues including the failure to install Server Packages. Resolution To learn what is preventing the creation of the PCTService, try manually adding the user to the Administrators group to see what errors might be presented.  Open Windows event log and look for errors that occurred during the same timeframe noted above. 

Issue PCT fails to open, presenting four 'could not connect' error messages.   Product Line EcoStruxure Building Operation Environment Project Configuration Tool Windows 10 version 1909 Windows 10 version 2004 Cause The cause maybe a firewall, scripts or group policy not allowing PCT to install correctly. Resolution First: check the VirtualBox Host-Only Network has the correct IP address. This can be found under: Control Panel\Network and Internet\Network Connections\VirtualBox Host-Only Network #?\Properties\Internet Protocol Version 4 (TCP/IPv4).   Raise a case with your region's IT2929 (UK = 020 7660 2747), requesting IT install the patch to correct the issue. IT2929 have a knowledge base article on the IT2929 system to help their representatives with this issue (KB0014074).   IT2929 will advise you to take a backup of your PCT projects, uninstall PCT and Oracle VM VirtualBox. IT2929 will then install the patch. Re-boot the laptop. Install PCT and Oracle VM VirtualBox (run as administrator). Restore your PCT projects. Re-boot the computer. If PCT still does not work after this, update the CCC case you have or create a new case with Product Support, providing your IT2929 KSR number is you do not have a case.

Issue The user installed the PCT on a machine and after running it, the following error pops up: “VM Module INITIALIZING_ Failed to refresh versions”     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause An installed and enabled antivirus may have corrupted the PCT installation. Resolution By verifying the PCT Virtual Box logs, we can see the folloiwng error:    ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={xxxx-xxxx-xxxxx-xxxx-xxxx} aComponent={MachineWrap} aText={The virtual machine 'Project Name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0   This indicates that the antivirus may have corrupted the PCT installation if it remained enabled during the installation. Now the PCT cannot communicate with the Virtual Machine. To resolve this, users will need to re-install the PCT while the antivirus has been disabled temporarily.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue During the installation of the EBO package, an error is displayed about PCT_temp.vbox already in existence.   ERROR_(3), UNABLE_TO_EXECUTE__COMMAND(99), reason=VBo xManage.exe: error: Machine settings file Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Leftover folder/file from previously failed installation Resolution Close PCT if running Take note of the folder/file that the error refers to, in this case "C:\Users\sesaxxxxxx\.VirtualBox\PCT_temp\PCT_temp.vbox Make a backup of the folder/file as a precaution (in case it has to be put back) Delete the folder or file, in this case, delete the PCT_temp folder Re-launch PCT and attempt to install the EBO package once again

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP server from the virtual machine. Resolution To change the Notification Address in the "Setup for use with remote server" to "localhost". 1. Select "Setup for use with remote server" after PCT start. 2. Update the "Notification address" to localhost  

Issue System memory usage stays high after exporting projects in PCT (Project configuration tool) Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The exporting process increases memory usage but is still withheld by the project after the process finishes.   Resolution Close the project exported.

Issue The port range used by the Project Configuration Tool is unclear Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The ports used by PCT are located in different documents Resolution • TCP on port 4444 (fixed) • HTTP on port 80 (default) • HTTPS on port 443 (default) • Server port 9091 (default) • Server port 9090 (default) • Engineering port 32768-61000

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.