Building Automation Knowledge Base

Issue When restoring database, an error will show up, saying that version is incompatible with this server. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause This is usually caused by restoring new SQL database to older version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Microsoft doesn't like to do this. Resolution There is build number matrix for each SQL server version:     RTM (Gold, no SP) SP1 SP2 SP3 SP4 SQL Server 2012 11.00.2100.60 11.00.3000       SQL Server 2008 R2 10.50.1600.1 10.50.2500 10.50.4000     SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500   SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 So check the build number in the error message and download the corresponding version of SQL to restore and be used for I/NET.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Downloading a Xenta Programmable controller under a SmartStruxure Automation Server LON channel fails with message: "Application Download Failure." Viewing error details, the Progress view window shows "Wrong device version." Product Line EcoStruxure Building Operation Environment Automation Server LON channel Xenta Programmable Controllers Cause Right click on the Xenta controller in StruxureWare Building Operation Workstation. Go to the Xenta tab. Check the Software version. If this is below 3.6, then the controller's .MOT file is out of date and must be updated. Resolution The controller's software version must be at least 3.6 to be compatible with SmartStruxure. Use the Download Wizard to load an updated .MOT file into the controller. See Download an .MOT file into a Xenta Programmable controller for further instructions.

Issue When the EWS interface is created, the Status show "online". However, after clicking on the Hardware > EcoStruxure Web Service > SSLite, the Status will go offline. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause Make sure the SOAP Endpoint field says "ews" and not "EWS". Lua program is a case sensitive program. Resolution Change the SOAP Endpoint field to "ews". For firmware version support in EWS, see Firmware versions to support EcoStruxure Web Services (EWS) in SmartStruxure Lite MPM Controllers.

Issue Workstation Log on failure. Difficulties with Login, port settings, and Server localhost: 80 8080 443 444 and other ports Product Line EcoStruxure Building Operation Environment StruxureWare 1.2.x.xxx and higher StruxureWare Building Operation Device Administrator StruxureWare Building Operation License Administrator StruxureWare Building Operation Enterprise Server StruxureWare Building Operation Workstation Cause Logging into Workstation, since I have changed my HTTP and HTTPS port setting to avoid conflict, and error is produced when the login fails: Resolution Beginning with StruxureWare Building Operation 1.2 and forward, Workstation uses the HTTPS as the default protocol (to make communication safer).  Below is the Software Administrator screen capture. Notice HTTPS is using port 450 in this example rather than default 443 since that port is used by another program on the computer.    Now when logging into Workstation, change the Localhost to that HTTPS port number. In this case, it is Localhost:450 Note: Remember, Server field in the Login screen shot above is for the AS or ES you want to connect to. To connect to an AS, plug in directly with ethernet cable (see Ethernet port is AutoSensing (No Crossover Cable required)), and put in IP address of AS.

Issue There is a need for Xenta I/O modules to be added as standalone devices on a Lon network. Product Line EcoStruxure Building Operation Environment Xenta I/O modules Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Cause The Building Operation ES/AS structure allows I/O modules to operate without a Xenta programmable base unit. Resolution The following Xenta I/O modules can be added directly once the Lon interface and network have been created: I/O Module DI DI status DO DO override UI TI AO AO override Xenta 421A  - - 5 - 4* - - - Xenta 422A - 4** 5 5 4* - - - Xenta 451A - - - - 8* - 2 - Xenta 452A - 8** - - 8* - 2 2                   * - DI, 0–10 V DC or 0–20 mA, 1.8/10 kohm TI         ** - Status indication only when the corresponding universal inputs (UI) are being used as digital inputs. Once the I/O module is set up for SNVT communication the green LED will flash once every 10 seconds. For more information see Configuring Xenta I/O module inputs when used as stand-alone Lonworks devices.

Issue VisiSat 2.1 Build 196 Service Pack 1 provides the five following corrections: In the ARCnet debug Excel spreadsheet, the property editor can now be run. (Defect 1633) Exporting points to MNView or XBuilder, now allow up to 32 characters for the name and up to 50 characters for the description. (Defect 1706) In StruxureWare Building Operation WorkStation, MicroNet Interfaces can no longer be exported/imported. All MicroNet engineering should be done in VisiSat first and then imported into StruxureWare. (Defect 1765) Newly created blank points lists can now be saved without production an error message. (Defect 1784) Exports to StruxureWare no longer produce Memory leaks. (Defect 1808) Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment VisiSat 2.1 build 196 StruxureWare Building Operation Version 1.4 Onwards Cause Correction of five known defects. Resolution This Service Pack should only be added to VisiSat 2.1.196 Note: When installed, the VisiSat 2.1 Build version/build number increases to 2.1.200. (due to one of the files in 'Program Files'). VisiSat will still show as Build 2.1.196 in Control Panel - Programs - Programs and Features - Uninstall or change program. Installing VisiSat Service Pack 1 =============================== Shutdown VisiSat and the VisiSat-Server. Run "VisiSat 2.1.196 Service Pack 1.exe". Extract to VisiSat installation root drive. (or extract to another location and move the Satchwell folder, created when extracted to the root of the C: drive). To the question 'Would you like to replace the existing file', select 'Yes to All' Restart VisiSat. Download VisiSat 2.1 Build 196 Service Pack 1. See VisiSat version 2.1 Build 196 service pack 2 where information on VisiSat 2.1 Build 196 Service Pack 2 can be found and the service pack downloaded.

Issue When connecting to a Web Service, the connection is not established and the error "403 forbidden" is shown. A Web Service goes offline after having worked previously and the error "403 forbidden" is shown. Product Line EcoStruxure Building Operation Environment Web Service Generic Consume Cause The generic consume Web Service client in SmartStruxure doesn't have a user agent header defined. Some Web Service providers will not or no longer allow that, and denies the request when it comes from SmartStruxure. If the same URL is entered in a browser, the page is shown. The cause of this issue can also be that the Web Service is being polled too often. Resolution Until it is made possible to define a customer user-agent header, you need to use another application to relay the Web Service request. This can for instance be "SBO - Web Service through a Proxy and JSON conversion" from the Exchange Community.

Issue When adding a Simple XML Web Service interface in to SmartStruxure, the following error message is given.  Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation SmartStruxure Web Service Interface Enterprise Server  Automation Server Automation Server Premium  Cause The (403) Forbidden error means that the destination of the XML address being used is denying access.  Resolution Follow these steps:   Verify that the XML address can be reached in a normal web browser.  Contact the provider of the XML web service to gather more information on their requirements.    Note: Some providers require a username and password to acquire their information. In other cases they may require that the HTTP request contain an user-agent header. For example, weather.gov requires the HTTP header and will block any request without it. SmartStruxure does not currently support the HTTP user-agent header. You can check out the Community post SBO - Web Service through a Proxy, JSON and Image conversion as a possible workaround for these situations. 

Issue What is the firmware version that supports EcoStruxure Web Services in SmartStruxure Lite MPM Controllers? Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SmartStruxure 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause SmartStruxure Lite controllers have two variants of firmware depending on the sales channel: Schneider Electric Can2go Resolution EcoStruxure Web Services are only available in Schneider Electric firmware versions and full EWS support is planned for firmware version 2.7.0 SmartStruxure Lite shows offline in StruxureWare Building Operation

Issue Waveforms for PS, AS, and I/O modules Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Loss of power and UPS for the StruxureWare Building Operation and SmartStruxure product lines. Should you design a site with Stepped Approximation or Pure Sine Wave? Resolution Concerning the UPS, and in particular the APC UPS 650, this is a good UPS, but the problem is that it would still interrupt the power for enough time to reset the AS. The AS has a 100mS capacity. AS Power supply interruption or failure has a bit more information would be beneficial to read through. A good UPS would be one that is Online or sometimes referred to as Double Online. This means that the power is not interrupted. The APC UPS line that has this is the SmartUPS and the base model is the old 1000XLI. This model may or may not be available in every country, but there would be a comparable model available. APC has been replacing the 1000XLI with various models, but all have the capability to go directly to battery, then back to power once the power is restored (assuming that there is a backup generator or the main power is restored) before the battery is pulled down. The Automation Server is powered from one or several PS-24V units. They have and peak voltage rectification on the input and the voltage waveform should not be an issue as long as the peak voltage is similar to that of a sine wave. If the input voltage is increasing with a very high dV/dt there may be high input current peaks. Those peaks may but not necessarily be reduced by the 230/24V transformer.   Key Concept: Look for a model with the Topology of Line Interactive and the Waveform Type of Sine wave. Picture is simply for example but not required:

Issue Echelon Node Utility with Loytec NIC-USB Network Interface Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause There is a need to run Echelon Node Utility using Loytec network interfaces. Resolution The easiest way to accomplish this, is to use the NodeUtil Launcher. This program scans the registry for known interfaces. It was created by an active Community member. * Do take note Schneider Electric Product Support does not provide support for the NodeUtil Launcher - for support please write the developer of the tool. Below are two methods to manually achieve this if you don't want to use the tool. Here are 2 methods to run Node Utility using Loytec NIC-USB network interface. Method 1 involves accessing the Windows registry to check the path name of the Loytec network interface. We are not modifying any entries in the registry but as always, we should be careful when we access the Windows registry. Using Windows registry incorrectly can cause serious problems that may require you to reinstall Windows. Method 2 will configure the Loytec NIC-USB to use LON1. If you have used an Echelon LonWorks interface as LON1, you will need to detach it before you can use this method. Method 1 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity Run Windows registry editor (Start > Run > regedit). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers. The interfaces will be shown here. Look for the interface with '_LDV'. Run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil using the command nodeutil -D"". See example below. Method 2 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity. Click on the 'Advanced' button. Check the option 'LON1 Support for device' and select the appropriate device in the drop down list. You will need to reboot the computer for this to take effect. Once the computer has restarted, run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil. Node Utility should now run.

Issue How Permissions works in EBO Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Software Permissions are used to control user activities in a software application. For example, permissions can be setup to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Resolution EBO software permissions comprise path permissions and command permissions. Path Permission: Path permissions give a user or user account group basic permissions to the objects defined in a path. The permission level set on a path applies to all sub levels unless you set a new permission level for a sub level. Command Permission: To make the system even more flexible and useful, you can assign a user account group with special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands. Command permissions will not restrict a user from specific properties of a given window. They function to remove items from Action or Right Click menus. EBO uses the following basic rules to interpret software permission priorities: The path permission settings of lower branches overrule the settings of higher branches within a user account group For example, a user account group has the Read permission to the path /Trend_Logs and Full Access permission to the subbranch /Trend_Charts. Users in the user account group have permission to modify the objects in the /Trend_Charts but can only view the objects in the superior /Trend_Logs. If the path /System has the permission level Read, and the subbranch /Alarms has the permission level Full Access, the users in the group have full access to the objects in the /Alarms path. The highest permission rule wins between user account groups. For example, if a user has inherited the permission to accept an alarm from one group, this overrules settings from other groups that deny the user the permission to acknowledge alarms. The software permissions for a single user account overrule the permissions of any inherited user account group permissions. The path permission rules also apply to the basic commands Create, Copy, Paste, Cut, Move, Rename, and Delete. For example, you only need the Read path permission level to copy an object but you need the Full Access path permission level to paste an object. See the table for more details.       Download Software Permission.pdf, the detailed guide about how permission works in EcoStruxure Building Operation (Formerly known as SmartStruxure) and how to make it work.  Check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.

Issue The EcoStruxure Web Services Interface has been successfully setup in a Enterprise Server but cannot see the Vista objects / points in Workstation Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation 1.4.x TAC Vista SmartStruxure Interface TAC Vista 5 and above Cause The Web Services interface hosts the Vista objects in the System / Hardware / EcoStruxure Web Services / TAC Vista folder, these must be hosted to the Server to become visible within Workstation.  Resolution Once you have navigated to the System / Hardware / EcoStruxure Web Services / TAC Vista folder you will see the list of objects available associated with the TAC Vista user name setup in the TAC Vista SmartStruxure Interface. From the list of Vista objects select the required ones you wish to use within the Enterprise Server database. The right click on the selected folder and select the Host EWS Objects... option. The next option is to select the Vista EcoStruxure Web Service interface that will host these objects. The objects will now be visible within the Enterprise Server / Workstation.   For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure. For additional details see Creating an EcoStruxure Web Service Object on the SBO WebHelp site. 

Issue IP address using DHCP Product Line EcoStruxure Building Operation Environment IP network Cause Bacnet or Modbus IP loses communication Resolution The AS or ES may be configured using DHCP (Dynamic Host Configuration Protocol), this is usually set up using "Device Manager" See Troubleshooting AS configuration issues with IP address. However many other systems use fixed IP address and use the IP address to specify the controller or server. Thus it is usually best to use fixed IP addresses for the Automation Server and Enterprise Server, especially if using Bacnet or Modbus over IP NOTE When the IP address of an AS is manually changed, the IP address of the Bacnet or Modbus IP interface needs also to be manually changed

Issue The Automation Server is constantly using 100% CPU causing a slow operation Product Line EcoStruxure Building Operation Environment Automation Server Cause Check which process is taking the CPU. Cause 1: The cause was found to be a Function Block Program which was corrupt in some way. When trying to edit, open properties or do anything with this Function Block Program Workstation just hang. The root cause of the problem with the Function Block Program was never found. Cause 2: Some schedules have more than one entry for the same time stamp (likely if the process "CScanner" is taken the CPU) Resolution Solution 1: After deleting the particular Function Block Program (which took over 2 hours) the CPU usage was directly down to 20%. Another solution for an AS with the same symptoms: After downloading a new database to the automation server and then restoring a backup the CPU usage went down to normal levels.  Solution 2: Check all schedules for duplicate entries, especially around the time where the CPU goes to 100%. Also check out the SmartStruxure Quick Help - AS CPU and Memory Loading Quick-Help video on the Exchange.

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

Issue When trying to commission a controller into a LonWorks network in SmartStruxure you get a DST error. Product Line EcoStruxure Building Operation Environment WorkStation LonWorks Interface Cause The DST error occurs during the commissioning of the controller when the DST settings are attempted to be downloaded. Resolution TAC Xenta 280 and 300 series Controllers If the DST error occurs when commissioning a Xenta 280 or 300 series controller then check the label on the side of the controller. If there is no /N/P after the model number then it is not a network presentation controller and can not be commissioned in SmartStruxure. For more information see Xenta 280/300 without /N/P designation cannot communicate in a Network.

Issue It is not clear how to register a SmartStruxure system, and what information to write in case it's not a customer site (For example a test bench/controller or engineering PC). Product Line EcoStruxure Building Operation Environment S2Connect Workstation Cause Guidelines are needed regarding how to properly register a system. Resolution Starting in SmartStruxure 1.5, we have introduced a registration process to know more about SmartStruxure systems. In order to know our customer and/or partner better and provide better services we should register our SmartStruxure system with correct information. The SmartStruxure registration process requires a Buildings Exchange account. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Please make sure below points while registering SmartStruxure system. Test site: If you are registering a test site to test registration process, write "[Test]" keyword in Site note*. Demo site: If you are registering a site which is for demo, then write "[Demo]" keyword in Site note. Training site: If you are registering a site for training or you want to explore registration process, then write "[Training]" keyword in Site note Customer site: if you are installing an actual site for customer then DO NOT use above keywords in Site note field *Site note field can be found under Site Administrator tab (Shown below in screen shots) New system registration: If you are registering new system then you continue enter all information in Step 1 and continue to Step 2. In Step 2 you will find a Site note field. Fill the Site note field as explained above.  Already registered system: If you have registered your site without providing above explained details then you can browse to below website https://registration.smartstruxure.schneider-electric.com After successful login; Navigate to Systems -> Site Administrator and click on Edit button, now you can edit Site note field. Registration Process Does Not Complete In some cases after registering either the Enterprise or Automation server, it still prompts you to register when you log back in. There are two different procedures that can be taken to correct this issue. Procedure 1 - By editing the registration and clicking submit again, it can help the system complete the registration. Log into the sever again and either click Register now on the initial prompt or go to Help > Registration once you are in Workstation. Log into the Registration Portal. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Select the server that is experiencing the issue on the right side of the window. Click Edit. Click Submit. Procedure 2 - If procedure 1 still does not work, then the registration can be completed manually by entering the Registration code in the offline mode. Log in to the Registration portal directly through this link (registration.smartstruxure.schneider-electric.com). Select the server on the right hand side of the screen that has the registration issue. Take note of the Registration code. Insure that the Enterprise or Automation server does not have internet access and log into the server with Workstation (In the case of an Automation server you will need to connect directly to it via Ethernet). Click to Register now (Since the server does not have internet access, it will automatically launch the offline registration). Insert the Registration code the three fields provided and click Register now. Also check out the SmartStruxure Solution Connect (S2C) - SmartStruxure Product Registration Registration Quick-help video on the Exchange.