Building Automation Knowledge Base

Issue PCT 2.0 shows "503 Service Temporarily Unavailable" error when trying to reach to PCT server. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The PCT 2 disk has a fixed size limit of 200GB and cannot be expanded by users. Once the disk reaches full capacity, access to PCT 2 becomes unavailable. Resolution Check the size of the "data.vhdx" file: The file resides in the "Virtual Hard Disks" folder. This folder can be found in the path selected during the installation. Folder location: Navigate to the installation path to locate the "Virtual Hard Disks" folder. File location: Inside the "Virtual Hard Disks" folder, locate the "data.vhdx" file. Check the size of the "data.vhdx" file.   If the disk size is over 200GB, contact local support and attach the information.   

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 The added to parent column shows incorrect information. PCT 1.X  PCT 2.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause PCT doesn't detect detachment in WorkStation. Resolution Do not detach the child server from its parent in PCT 1.x and 2.x. Webhelp information: Adding a Virtual EcoStruxure BMS Child Server to a Parent Server.

Issue How to collect log files from the Project Configuration tool 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the PCT, log files should be provided. Resolution Collect log files through the Web interface on both Windows and Ubuntu installations: Logon to PCT server, Click Diagnostic  Click Collect logs Log starts collecting. After the log collection process is complete, the file will either be saved to the browser's default download location or a window will pop up asking where to save the ZIP file. Select the desired location then click Save   Log collector tool for PCT for Ubuntu: If the PCT web interface is unavailable, you can use the Log Collector tool to gather log files. This tool is included with the PCT installation on Ubuntu, eg. pct-2.1.1.8-log-collector-ubuntu. Give the file proper permission to be able to run as an executable either using chmod command:  chmod +x pct-2.1.1.8-log-collector-ubuntu​ or via file properties, as shown in below screenshot: Run the log collector tool. ./pct-2.1.1.8-log-collector-ubuntu​ A zip file containing the required log files will be saved in the same folder where the log collector tool is located.

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 move PCT storage file to another location Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The hard drive where the storage file resides may be full, or the space may be allocated for another purpose Resolution It's suggested to create a backup before proceeding, follow How to backup PCT 2.0 data to create a backup.   Open Hyper-V Manager Select "pct" under Virtual Machines then click "Move..." from the right-hand side menu Move "pct" Wizard Window will pop-out, click Next Select "Move all of the virtual machine's data to a single location" then click Next Select the NEW location for PCT then click Next. Check if the location is correct, then click Finish. Hyper-V will initial the process Once the Status shows the progress finishes. Click "Shut Down" from the right-hand side menu for "pct" image   Click "Stop Service" from the right hand side menu to stop Hyper-V as we need to modify the file location for PCT settings file   Open Windows Explorer and go to C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool Open the "settings" file Replace the old folder location with the new one then Save the file (I changed the folder from 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool' folder to 'D:\PSS\PCT 2 storage' Before modification After modification Go back to Hyper-V then click Start Service   Select "pct" then Click Start   Wait for a couple of minutes for the VM to start Go to https://192.168.10.2/ in a browser and PCT will start with all the existing projects

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 create PCT backup Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause Users need to backup all PCT data to prevent data loss or corruption. Resolution Since PCT 2.0 virtual machine resides in Hyper-V., the process is the same as backup any VM in Hyper-V Manager. Open Hyper-V Manager: Launch the Hyper-V Manager application on your server. Select the VM: Navigate to the virtual machine you want to back up in the left pane. Right-click and choose "Export": Right-click on the VM and select "Export" from the context menu. Choose a destination: Select the folder where you want to save the exported VM files. Start the export process: Click "Export" to begin the backup process. The "Export" process will create a "pct" folder from the folder in step 4. The 3 folders under "pct" folder are the backup for PCT 2.0 with projects and server packages installed.      

Issue Getting error "Failed to run: import-VM" when trying to install PCTv2 Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Could install PCTv2 fine but the issue started when going back and forward between PCTv1 and PCTv2 so that might have caused the issue. Resolution Uninstall Hyper V in Windows Programs and Features and restart computer Delete everything in ProgramData\Microsoft\Windows\HyperV Install PCTv2 version 2.0.2.13 or later

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 Project Configuration Tool generates a 'failed get matching version' error when attempting to start an existing server Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) Cause The associated PCT server package files are not installed, cannot be accessed or are corrupt Resolution The "get matching version error" can occur when the associated server package files are not installed, cannot be accessed or are corrupt.  Try the following steps:   Check the associated PCT server package is installed, click manage packages (1) and check the Manage packages window (2)   Install the package if it is missing and then attempt to start the server If still unsuccessful, reinstall the server package and then attempt to start the server When installing the package if the error below occurs navigate to 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\logs' and open the ConfigurePCT.log file to try and identify the problem                                                                                                  In the case the server package config file is corrupt navigate to the server packages folder at 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\cfg' and delete the associated *.cfg file.      Reinstall the server package and then attempt to start the server Additionally consult PCT error installing EBO package for further suggestions

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 How to uninstall PCT 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause The uninstalling instruction isn't documented. Resolution Launch Hyper-V. Shut Down PCT VM. After the VM is shut down, select Delete from the bottom right window. Select Delete if the confirmation window prompts. It may take some time depending on the VM size.   Go to the VM location selected during the PCT installation The default installation path is  "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool 2.0"     Right-click on the pct folder then select Delete (This action will delete all the data in PCT including projects and servers created)    

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 PCT 2 and 'Starting VM pct' step, one encounters the error: "Error: System.InvalidOperationException: Failed to run: Start-Vm -Name pct". Open Hyper-V Manager and confirm the 'pct' VM was created. Manually trying to start produces this error: Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Hyper-V is not set to start on boot automatically. Resolution DO NOT perform these instructions if PCT 1 is installed on the same OS. Contact Product Support for assistance. Launch Command Prompt as Administrator. Type: bcdedit /enum​  Ensure 'Hypervisorlaunchtype' is not 'Off' and set to 'Auto' by running the following command: bcdedit /set hypervisorlaunchtype auto​ Reboot the PC Rerun PCT 2 installer

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.