Building Automation Knowledge Base

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.    

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 PCT client can't start properly with "Hardware virtualization is not enabled" error. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) (All Versions) Cause Hardware Virtualization is Disabled or not available for PCT Resolution  Install "Intel® Processor Identification Utility" then verify the status of "Intel® Virtualization Technology" from the Utility. Using the table below, you can see if your processor supports Intel® Virtualization(provided by Intel).  The above information can also be found on Intel® Virtualization Technology web page If Virtualization is disabled in BIOS then enable it from BIOS else identify other software utilizing the Virtualization and stop the application.  Use Win key or press the Windows Start button Type: cmd Select Run as Administrator  Verify command prompt window title bar is Administrator: Command Prompt Type: shutdown /r /fw/ /f  Press enter and the computer will shut down immediately forcing all applications to close (/f) and restart (/r) into firmware interface (/fw)   If the issue persists, the following article may provide the answer Knowledge Base article - PCT error Hardware-virtualization is not enabled-Please-enable.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation, Project Configuration Tool Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a port group or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or port group you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode drop  down menu, click Accept. Note: The setting on the port group overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

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 Services for assistance. Issue V-Box fails to install network interface/Virtual Adapter during Project Configuration Tool Installation. Product Line EcoStruxure Building Operation Other Environment OracleVM VirtualBox (all versions) Project Configuration Tool (all versions) Cause Some security or anti-virus software prevents V-Box from installing virtual adapter during PCT/V-Box installation or prevent PCT from connecting to a virtual adapter.   Example: The anti-virus software can flag V-Box file as possible threat. Resolution Uninstall or Disable security and Anti-virus software. Install PCT. Install or Enable the software after PCT works properly.   NOTE:  You may have to disable and/or completely remove the security software even after PCT is installed and works properly.  Contact your IT group to get assistance with getting exceptions entered to have PCT work correctly in conjunction with your security software.

Issue The Project Configuration Tool is installed as a Server. A project can be created but when it should be saved, an error says, "Failed to open project," and "Failed to start VM." Product Line EcoStruxure Building Operation Environment PCT version 1.1.1 Cause When PCT is installed as a server PCT, and a project is opened, the computer running PCT must have a connection to the DHCP server in the network. Resolution Make sure that the computer running PCT has a good connection to the DHCP server in the network.

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. 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. Webhelp information: Adding a Virtual EcoStruxure BMS Child Server to a Parent Server.

Issue The port range used by the Project Configuration Tool is incorrectly documented. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause Documentation and web-help states the port range is 49152 to 65535, this is incorrect. Resolution The correct port range used, for the engineering ports, i.e. the ports that the EBO servers are listening too, so that it is possible to log on with WorkStation is 32768-61000.

Issue How to Identify a specific PCT (Project Configuration Tool) project. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause How to identify a specific PCT (Project Configuration Tool) project. Resolution In PCT check the project name for the project to be the backup. For this example, the project named “Test 5 Project” is used.   Go to the project storage folder. (The following is the default locations for PCT v1.2.7.223): C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects   Using a text editor (for example Notepad or Notepad++) open each folder then open the file “project.thrift.pctj”, Open each folder in turn until the correct project has been identified to backup. The stored project folder name can be seen:   Further on in the text editor, the PCT project name can be seen, in this example 'Test 5 Project'.   Alternatively click the “edit” menu item and select find (ctrl + F) from the options and search the text for the PCT project name. Making sure PCT is not running when copies of any of the projects are taken

Issue PCT workstation displays message “Server version not compatible with client", when restoring a server configuration with new IDs. Product Line EcoStruxure Building Operation Environment Buildings Operation Project Configuration Tool Cause When backing up and restoring an AS-P/AS-B with a new ID in PCT at EBO 3.2.2.61, when logging back on with PCT using the installed EBO workstation,  the message “Server version not compatible with client" is displayed Resolution PCT is the offline programming tool but, it launches the workstation installed on the computer. If the workstation version on the computer is EBO 3.2.2.61, Hotfix 3.2.2.4002 (CP3) is required to be installed on the computer running PCT, taking the computer’s installed workstation version to 3.2.2.4002.