Issue After reinstalling Project Configuration Tool (PCT), the user is unable to log in using the "admin" account and receives an invalid login attempt. The issue may also be accompanied by installation-related errors such as: "The setup has detected no version of SBO Project Configuration Tool is installed" Error code 1603 Error code 1722 Product Line Project Configuration Tool Environment Project Configuration Tool (PCT) 2.x Cause The default password may not be used after reinstallation, or residual PCT installation files may remain on the system and prevent the login issue from being resolved.   Starting a new PCT installation before removing the existing PCT folder can leave residual files in place and may prevent the login issue from being resolved. Where project data must be retained, export projects and create any necessary server backups before removing the PCT virtual machine or performing cleanup activities required for reinstallation. Resolution Verify that you are using the correct default administrator password for PCT. If the issue persists, fully remove the existing PCT installation: Open Hyper-V Manager Shut down and delete the PCT virtual machine. Delete the PCT installation folder: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool If installation or uninstallation errors occur, back up the Windows Registry and remove the registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Reinstall PCT 2.3.1 and log in using the default password Admin-11. If the issue remains unresolved, contact local Schneider Electric support.    

Issue During installation or first‑run of Project Configuration Tool 2 (PCT 2), the setup stops at “Starting VM pct” and fails with: System.InvalidOperationException: Failed to run: Start-Vm -Name pct When starting the pct VM manually in Hyper‑V, one of the following errors appears: Error 1 – Hypervisor not running From the VM Connection window: Virtual machine 'pct' could not be started because the hypervisor is not running. Error 2 – Insufficient RAM From Hyper‑V Manager: 'pct' failed to start. Unable to allocate 8192 MB of RAM: Insufficient system resources exist to complete the requested service. (0x800705AA) These two errors represent distinct root causes. Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) 2.0 Windows 10 or Windows 11 Microsoft Hyper‑V Host PC running the PCT virtual machine 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. Cause Two independent conditions can trigger the Start‑VM failure: 1. Hyper‑V hypervisor not running The OS reports that the hypervisor is inactive. This is confirmed by the error: “Virtual machine 'pct' could not be started because the hypervisor is not running.” Common causes: hypervisorlaunchtype = Off Hyper‑V corrupted or disabled BIOS virtualization (VT‑x/AMD‑V) disabled 2. Insufficient host RAM to start the PCT VM The system cannot allocate the minimum required 8192 MB for the VM, showing: “Unable to allocate 8192 MB of RAM: Insufficient system resources (0x800705AA).” Causes may include: Too many applications consuming RAM Dynamic Memory conflicts Physical RAM below PCT requirements Resolution Scenario 1 – Hyper‑V hypervisor not running Do not use this procedure if PCT 1.x exists on the same OS. Contact Product Support if unsure. Open Command Prompt (Admin). Check hypervisor state: bcdedit /enum Ensure hypervisorlaunchtype is not Off . If needed, enable it: bcdedit /set hypervisorlaunchtype auto Reboot the PC. Relaunch the PCT 2 installer or start the pct VM again. Also verify in BIOS: Intel VT‑x or AMD‑V is Enabled Hyper‑V support is not blocked by firmware Scenario 2 – Insufficient RAM or system resources Verify the system meets the PCT minimum RAM specification (8 GB free for the VM). Close high‑memory applications (browsers, Teams, VMs). If using Dynamic Memory, temporarily disable it for testing. Increase physical RAM if below recommended levels. Retry starting the PCT VM in Hyper‑V Manager. Refer to PCT Specifications for full hardware requirements.  

Issue Installing or operating the Project Configuration Tool (PCT) on different host machines results in inconsistent behaviour, including failed installations, connectivity issues, and difficulty running server packages. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT v1) Building Operation WorkStation Host platforms (Server Mode or Client Mode) Cause PCT requires specific installation steps and host configurations to ensure reliable operation. Problems often arise due to: Incorrect installation mode (Server vs Client) Missing or incompatible WorkStation versions Windows firewall blocking PCT services Network adapter selection issues Ensuring a consistent installation workflow prevents connection failures, startup issues, and server package problems. Resolution PCT “Server Mode” Installation Sign in to Windows using an account with Administrator privileges. Join the computer to the domain if required for your environment. Download and install the PCT Server package. During setup, select Server as the installation type. Select the correct physical Ethernet adapter (not virtual or Wi‑Fi). Allow Oracle VirtualBox to complete its installation. Reboot the PC when prompted. Disable Windows Firewall or create PCT‑required firewall rules. If needed, install required versions of: EBO License Administrator EBO WorkStation (versions 1.9, 2.x, or 3.x.) EBO Server packages Individual User Laptop – Installation Install the EBO License Administrator. Install required EBO WorkStation versions. Install the PCT Client software. Individual User Laptop – Usage Open PCT Client and connect to the appropriate PCT Server. Enter the server’s IP address or use “Setup for use with remote server” to save it. Upon first connection, install all required Server Packages. Create a new PCT project or open an existing one. Start server instances if not already running. Open WorkStation to begin project engineering and testing.   Recommended PCT Workflow Summary Step Best Practice Notes 1 Install PCT Server or Client correctly Ensure the correct network adapter is selected 2 Install required WorkStation builds Use the latest available version for each EBO major/minor family 3 Configure firewall rules PCT may fail to connect if ports are blocked 4 Install server packages in PCT Server Install once; all users can then consume 5 Run project servers and connect with WorkStation Ensure all required packages are running  

  Issue Users are unable to log in to a server in Project Configuration Tool (PCT) 2.0, even though the username and password are correct. Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) 2.0 Building Operation WorkStation PCT Servers running various EBO base versions (3.2, 4.0, 5.0, 6.0) Cause The WorkStation version installed on the host machine is newer than the server version, but not the latest available build for that base release. Because PCT relies on the latest WorkStation build within a major/minor family, mismatched versions may cause: Incorrect IP addresses are being injected into WorkStation (e.g., 192.168.10.2 ) Authentication failure or inability to connect to simulated servers Example from the screenshot below shows: Server: EBO 3.2.1.630 WorkStation: 3.2.3.59 Latest required WS for that family: 3.2.4.4007 (CP2) This mismatch leads PCT to load incorrect connection parameters.     Resolution Always install and use the latest WorkStation build available for each EBO base release being used in PCT. Supported base versions and their minimum required WorkStation versions EBO Base Release Family Valid Server Versions Required Minimum WorkStation Version 3.2.x 3.2.1.630, 3.2.2.61, 3.2.3.59, 3.2.4.1009 EBO Hotfix 3.2.4.7003 (CP5) 4.0.x 4.0.1.86, 4.0.2.559, 4.0.3.176, 4.0.4.45, 4.0.5.7 EBO Hotfix 4.0.5.6000 (CP5) 5.0.x Any 5.0 build EBO Hotfix 5.0.3.18012 (CP17) 6.0.x Any 6.0 build See EBO Hotfix List for latest 7.0.x Any 7.0 build See EBO Hotfix List for latest   Installing the "latest within family" ensures: Compatible schemas Correct IP assignment inside PCT Successful authentication to hosted servers Stable simulation environments    

Issue When using Project Configuration Tool (PCT v1.x) installed as a server, a project can be created but fails to open or save. Error messages include: “Failed to open project” “Failed to start VM” Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT v1.x) PCT installed and operating in server mode Windows host with Hyper-V Cause In PCT v1 server mode, VM networking depends on obtaining IP configuration from a reachable DHCP server. If the host computer is disconnected from the network, cannot reach a DHCP server, or the Hyper-V external virtual switch is bound to a non-functional adapter, the PCT VM cannot start, which prevents projects from opening. Resolution Ensure the host machine running PCT v1 has an active and reliable connection to a network that provides DHCP services. If offline use is required, use Standalone mode instead of Server mode.   When PCT v1 is in server mode, it must contact a live DHCP server to assign network parameters to its virtual machines. Use the steps below to diagnose and resolve connectivity problems. 1. Verify Physical and Network Connectivity Confirm the PC network cable is connected or the Wi-Fi link is active. For wired Ethernet: check link lights on NIC and switch, try a different port or cable. For Wi-Fi: connect to a corporate or managed SSID that provides DHCP. Avoid guest or restricted networks. 2. Confirm DHCP Lease Assignment on the Host ipconfig /all Check for: Valid IPv4 address that is not 169.254.x.x DHCP Enabled = Yes DHCP Server shows an expected IP Lease Obtained and Lease Expires are present If a 169.254 address appears, DHCP is unreachable. Toggle the network adapter off and on. ipconfig /release ipconfig /renew Temporarily disconnect VPNs that may override local routing or DHCP. 3. Confirm Network Reachability Ping and trace to the DHCP server or gateway. ping <DHCP-server-IP> ping <Default-Gateway-IP> tracert <DHCP-server-IP> Interpretation: All pings fail: the host is not reaching the network. High latency or drops: instability can prevent VM startup. Trace stops immediately: firewall, VLAN, or NAC could be blocking traffic. 4. Validate Hyper-V External Virtual Switch Binding PCT v1 server mode relies on Hyper-V external switching. Steps: Open Hyper-V Manager. Open Virtual Switch Manager. Verify the External switch is bound to a working, DHCP-enabled physical adapter. Ensure the bound host NIC is enabled and not mis-bridged. Common pitfalls: Switch bound to Wi-Fi that lacks DHCP reachability. Docking changes result in binding to an inactive adapter. Corporate policies limiting bridge mode or VM MACs. 5. Check Firewall and Endpoint Security Confirm the DHCP Client service is running. Review Windows Defender Firewall and endpoint protection for blocked Hyper-V or DHCP traffic. Coordinate with IT to verify: DHCP scope availability and exhaustion status VLAN assignment and trunking MAC filtering or NAC policies affecting Hyper-V virtual NICs 6. Test PCT v1 VM Startup Independently Check PCT logs at: C:\ProgramData\Schneider Electric EcoStruxure\Project Configuration Tool\Logs\ Look for entries indicating DHCP lease failures, network timeouts, or Hyper-V switch binding issues. Attempt to start the relevant VM directly from Hyper-V Manager to surface more detailed errors. 7. Offline Use Case PCT Server mode requires an external DHCP server and is not suitable for offline use. If offline operation is required, install and use PCT v1 Standalone mode. If PCT was installed in the wrong mode, reinstall PCT and migrate the project repository as needed. 8. When to Escalate Escalate to network or IT teams when: Other machines obtain DHCP, but the host does not. Firewall, NAC, 802.1X, or VLAN policies may block VM traffic. DHCP scope exhaustion or MAC filtering is suspected. Rebinding the Hyper-V external switch does not restore VM networking. Quick Checklist Host has valid DHCP lease and can ping default gateway. Hyper-V External switch bound to an active, DHCP-enabled adapter. No VPN or security tool overriding DHCP or VM NICs. PCT logs show no VM network timeouts. Using Standalone mode when offline is required.

Issue There is uncertainty about how to change the external IP address in Project Configuration Tool (PCT) and whether the internal IP address can be modified Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause PCT uses two separate IP addresses: Internal PCT IP address (192.168.10.2) Used for logging in when PCT is installed locally. This IP is built‑in and cannot be changed. External PCT IP address Used when PCT is installed as a server. This IP is set in the Web interface and can be modified. It can be assigned automatically by DHCP or entered manually. Resolution Internal PCT IP Address (Not Changeable) The internal IP address is fixed and cannot be changed. To log on to a locally installed PCT: Open a web browser. Type 192.168.10.2 in the address bar. Enter Username  Enter Password  Click Log in External PCT IP Address (Changeable) The external IP address can be updated from the PCT Web interface: Log in to the PCT Web interface. Go to Settings → Network settings. Click the pen (edit) icon to open the Network panel. DHCP Select Dhcp to obtain the external IP address from the DHCP server. Static IP configuration (Dhcp unchecked) If Dhcp is not selected, manually configure: Static IP (cidr) – Type the static IP address using CIDR notation. Gateway – Type the gateway address. Click Save to apply the changes.  

Issue Webstation option is not available in some servers in Project Configuration Tool (PCT) 2.0. Product Line EcoStruxure Building Operation. Environment Project Configuration Tool (PCT) 2.0. Cause WebStation functionality was introduced in PCT 2.0 starting from EBO version 5.0.3 and later. Older versions do not support WebStation access within PCT. Resolution To use WebStation in PCT 2.0, ensure that the server package installed in PCT is EBO 5.0.3 or newer. For earlier versions (3.2 and 4.0), only WorkStation access is supported. Install the required WorkStation help file included in WorkStation 5.0.3.5001 or later to enable launching WorkStation from the browser. Verify the version of your EBO server in PCT before attempting to use WebStation. Reference: Project Configuration Tool – Version 2 - Support Tools Specification Sheet

Issue When planning an upgrade to EcoStruxure Building Operation (EBO) 7.x or the latest version for existing sites, users often want to complete engineering work before applying commercial licenses through Software Companion. Product Line EcoStruxture Building Operation Environment EcoStruxture Building Operation Project Configuration Tool 2.0 Cause Software Companion only provides Engineering licenses for new sites, but not existing sites. This limitation means that existing sites cannot be engineered without applying the commercial license first. Resolution To engineer or upgrade existing sites before applying commercial licenses, use Project Configuration Tool (PCT) v2: PCT is a standalone engineering platform, independent of the live system. It allows flexible design and upgrade workflows without impacting production. After engineering or upgrading: Deploy the EcoStruxure BMS server to the live site directly from PCT, or Use an XBK backup and import for deployment. Recommended Steps Download and Install PCT v2.x Windows Installer – v2.2.1.12 Ubuntu Installer – v2.2.1.12 Release Notes v2.2.1 Create or Import Existing Site in PCT Use the Import XBK backup feature for existing sites. Perform Engineering and Upgrade Tasks Configure controllers, graphics, and logic as needed. Validate compatibility with the target EBO version. Deploy to Live Site Either direct deployment from PCT or export XBK and restore on the live server. Additional Resources Project Configuration Tool – Support Tools Specification Sheet

Issue PCT does not run properly following installation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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. Cause Certain environmental settings may need to be adjusted in order to successfully install PCT. These settings are not described in the Project Configuration Reference Guide. Resolution If you have issues successfully running PCT after installation, check the following items: Enable Virtual Hardware Acceleration in BIOS Use this tool to check if virtual hardware acceleration is already enabled on your PC: Intel: https://www-ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-processor-identification-utility.html AMD: https://support.amd.com/en-us/search/utilities?k=virtualization Disable all Ethernet Adapters except the one in use (Only applies to Server Mode): It may be necessary to check Windows Device Manager for hidden network adapters Disable the Windows firewall Disable Anti-Virus Software A true local account may be needed to install and/or run PCT due to Group Policy or other factors. Use Run as Administrator for both installing and running PCT Note: You can right-click the PCT icon, open properties, select the “Compatibility” tab, and check the box “Run this program as an administrator” Test PCT by opening up the software application, creating a project, creating a server, and opening it up in WorkStation If PCT opens and works then enable Windows firewall and Anti-Virus program. - User may need to allow PCT in Windows firewall and PCT utilize port 9091 as default. - User may need to add exceptions within Anti-Virus software settings. We recommend installing Microsoft Fix 50410 to prefer IPv4 over IPv6. This software can be found here: - https://support.microsoft.com/en-us/kb/929852 - Choose the following download: Prefer IPv4 over IPv6 in prefix policies.

Issue PCT project folder size increases when an object is deleted. Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT 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. Cause Any change made in PCT increases the size of PCT project folder. This is by design and it is a normal behavior of PCT. The reason for this is that a project is a virtual machine using a dynamically allocated image that grows when memory is needed, but the image will not shrink when something is deleted.  Resolution The only way to reduce the folder size of a project is to backup all servers in the project, create a new project, restore the server backups to the new project and then delete the old project.

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) 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. 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 During certain situations, it may be required to remove and re-install PCT to address software conflicts with other software applications. While trying to remove/install PCT you may receive an error preventing you from completing the installation. The setup had detected that no version of SBO Project Configuration Tool is installed.  The specific command-line options require that the application be installed to continue. The setup will now terminate. Error: -1603 Fatal error during installation. Consult Windows Installer help(Msi.chm)or MSDN for more information. Error 1722. There is a problem with this Windows Installer... Product Line EcoStruxure Building Operation Environment Client versions (64 Bit Only): Editions: Pro, Home, Enterprise Windows 10 Windows 8.1 Windows 8 Windows 7       Server versions (64 Bit Only): Editions: Standard, Enterprise Server 2008 R2 Server 2012 Server 2012 R2  PCT versions (64 Bit OS Only): SBO Project Configuration Tool v 1.0.0.487 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.0.0.510 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.0.47 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.1.49 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.2.57 - SmartStruxure Solution - Software 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. Cause In order to get past a possible installation loop, you will need to locate and delete the following Windows registry key: [HKEY_CLASSES_ROOT\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B] Resolution Note: Always make a backup of your registry before making any modifications.   Run regedit.exe Locate/Search: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Delete Registry Key entry: B2A4F0AEC8BB0E2438706F07E2E2560B  

Issue Uninstall PCT doesn't uninstall Oracle VirtualBox Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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. Cause The uninstaller of PCT doesn't include VirtualBox as part of the uninstallation. Resolution 1. Uninstall PCT from “Control Panel\All Control Panel Items\Programs and Features”. 2. Uninstall PCT Client. 3. Uninstall Oracle VM VirtualBox.

Issue Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  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. 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.    

Issue PCT utilizes a large volume of hard drive space when the backup limit is not set. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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. Cause The virtual machine reserves additional hard drive volume each time a backup is created. Once this space has been allocated to the VM’s hard drive, it can not be reversed without deleting, recreating the project server then restoring the station from a backup.  (Once a VM grows, it cannot shrink.) Resolution The number of backups should be limited to a maximum of two (2).

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) 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. 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 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) 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. 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 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) 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. 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

Issue How to uninstall PCT 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. 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. 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)    

Issue Need to create PCT backup Product Line EcoStruxure Building Operation Environment Project Configuration Tool 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. 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.