Building Automation Knowledge Base

Issue Will the Multi-Purpose Manager (MPM) act as a BACnet IP BBMD?   Product Line EcoStruxure Building Expert Environment Site using BACnet and one or more  SmartStruxe Lite Multi-Purpose Manager (SSL MPM)  Cause Can the MPM act as a BBMD Resolution The MPM cannot act as a BACnet Broadcast Management Device (BBMD), but it can be a foreign device to another BBMD BACnet protocol includes broadcast traffic which does not pass through on-site routers. For BACnet devices to network across a wide area or across multiple separate sites connected by the Internet, it is necessary to register the BACnet devices with a Schneider BBMD using the Foreign Device Registration function in Building Expert. For a Multi-Purpose Manager (MPM) running Building Expert to function as a BACnet device, when being managed remotely over a standard TCP/IP network, it must be configured as a Foreign Device. It must also be registered on an Automation Server (AS) on the remote network that acts as a BBMD. Once done, BACnet devices can send messages to the BBMD, which are translated by the BBMD so they can pass over a standard on-site router. Then BBMD forwards the messages to the appropriate destination MPM controlling the Devices for which the BACnet messages were originally intended. Then the MPM translates the messages received over the network from the BBMD into standard BACnet messages and passes them on to the intended Devices as if they were direct BACnet messages. This Foreign Device Registration feature allows a single user with a StruxureWare Building Operations (StruxureWare Building Operation) terminal to remotely oversee multiple disparate sites simultaneously using BACnet, without having to install expensive direct connections to each site. You must have Firmware release version 2.9 or higher installed on your Manager to use Foreign Device Registration function. Here is the BACnet-Specifications-PIC-Statement.pdf And the  explanation on how to setup the DR-ForeignDeviceRegistration.pdf

Issue Why does the PID example function in the Script editor library not operate like the bPID? Product Line Andover Continuum, EcoStruxure Building Operation Environment Script/ Plain English differences Cause PID example does not operate as expected with regard to the integral action. Resolution The Script Program editor contains various library functions that can be selected from the "Library" tab at the lower right of the editor screen. Plain English program/ function examples were available and used in Continuum and known as the "Andover Controls Standard Modules" ACSM, they are available in Where can I obtain standard Plain English example functions? This document also contains further information about the PID use and application. In both the script PIDLoop (Long version) library function and the bPID function as used in Andover Continuum the Proportional component is the same, they both use Proportional Gain which is defined as 1 / Proportional Band. In the Script Editor Library PID function this requires the Integral Gain constant, this is defined as 1 / Integral Action Time as used in the Continuum bPID function. In the Script Editor Library PID function this requires the Derivative Gain constant, this is defined as 1 / Derivative Action Time as used in the Continuum bPID function. Either of the functions may be used in the SmartStruxure Script editor, but you need to ensure your calling program is passing the correct arguments for the PID function used.

Issue Help with Creating Custom Reports for EcoStruxure Reports Server Product Line EcoStruxure Building Operation Environment SQL Report Builder 3.0 Cause In order to create a custom report for EcoStruxure, the user must have a basic knowledge of SQL and writing SQL SELECT Statements.  Report Builder 3.0 can walk a user through most of the process but there is a bit of a learning curve. Resolution If you are attempting to create a custom report the most difficult piece of information is determining what Tables store which information.  To get definitions of Table Rows, run the provided Database Schema report in the Web Reports browser.  This will show primary/foreign key relationships as well as give you information on what is stored in each column. Information on Extended Trend Logs is stored in the tbLoggedEntities table and the tbLogTimeValues Tables.   Additional Metering information can be found in tbMeter, tbMeteringLogFilter, tbEntityData and tbEntityRelation

Issue Receive alarm messages as "Server does not exist or access denied", "08001: [FreeTDS][SQL Server]Unable to connect to data source" or "08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" when using SQL Server Express for External Log Storage even though login credentials are correct. 08001: [FreeTDS][SQL Server]Unable to connect to data source 08S01: [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist" Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation External Log Storage SQL Server Cause SQL Server Express is using Windows Authentication and/or the TCP/IP network protocol is disabled. Resolution To use external log storage with SQL Server Express the User must be able to login with SQL Server Authentication (e.g. a username and password) and the TCP/IP Network protocol must be enabled.  Consult Setup External Log Storage using MSSQL for additional details.   Check SQL external log storage host address: In the host address type the IP address or DNS name of your external log storage, without the SQL instance name. Having the SQL instance name in the host address can cause communication failure if EBO server is connecting to remote SQL server, refer to: Microsoft SQL Server - Basic Tab. To check the User login credentials: Open SQL Server Management Studio and enter the details from EcoStruxure Building Operation into the SQL Server connection window.  Choose SQL Server Authentication (A), enter the server details (1), user name and password (2) and attempt to login. If an error message appears indicating cannot connect and the credentials are correct it is possibly SQL Server Authentication is not enabled. Login to the SQL Server using Windows Authentication and follow the Microsoft article Change server authentication mode to set to 'SQL Server and Windows Authentication mode'. Attempt to login to SQL Server and the specific database should be visible. To enable the TCP/IP Network protocol:  Open SQL Server Configuration Manager (1) In the SQL Server Network Configuration menu, select Protocols for SQLExpress (2) Right-click TCP/IP (3) and select Properties (4) In the window that opens, click the IP Addresses tab (5) Either set a different port number for each one of the IP addresses or simply set one for all (6).  The default is 1433 but will need to be a port that is free.   Click OK. Back in the SQL Server Management Studio ensure the SQLExpress service is restarted. For additional information please consult Default SQL Server Network Protocol Configuration and Enable or disable a server network protocol            

Issue When a value in one Automation Server is transferred to a value in another Automation Server what port is used? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Automation Server (ASP/ASB) Cause Documentation required on ports being used Resolution EcoStruxure Automation servers can use one of three different communication protocols: Transport Control Protocol - TCP Hypertext Transfer Protocol - HTTP Hypertext Transfer Protocol Secure- HTTPS   The communication protocol and ports are configured in the Server wizard when you add an EcoStruxure BMS server via the Enterprise Server   EcoStruxure Automation servers can listen on one of the three communication protocols from Version 1.3 upwards. The TCP port is fixed but please refer to Changing the Automation Server HTTP/HTTPS ports TCP on port 4444 (fixed) HTTP on port 80 (default) HTTPS on port 443 (default)   Each EcoStruxure Automation server maintains a list of all the other EcoStruxure servers in the system and the communication parameters of those EcoStruxure BMS servers. To see the list and which protocol/port is being used select the server (1), select the Communications tab (2) and view the list (3) or individual server settings (4). Note when selecting an Automation Server the individual server settings (4) of other Automation Servers will be greyed out.   When an automation server is added, its communication parameters are distributed by the Enterprise Server to all other EcoStruxure BMS servers in the system. For additional information please refer to EcoStruxure BMS Server Communication   If the IP address or protocol port number in an already commissioned EcoStruxure Automations server is changed, this information must be manually updated in the Enterprise Server Communication view. The Enterprise Server then distributes the new parameters to the other EcoStruxure Automation servers. Select the Enterprise Server (1), select the Communication tab (2), select the server to be changed (3), update the settings (4):   If there are problems with the communication parameters please refer to Inconsistent Communication Parameters

Issue When using an Echelon U10/U20 USB or other Lon network adaptor for communication with a laptop and standalone WorkPlace Tech, not WorkPlace Tech Editor, you must change the default configuration settings.  The default Lon Network Domain ID length (1 byte), Domain ID (18 decimal) and Subnet (254) in the AS-P conflicts with the defaults used by WorkPlace Tech. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech (Lon Network communication settings) Building Operation Automation Server Premium Building Operation Enterprise Server Cause Lon Network configuration Resolution Look at the LonWorks Network "Advanced" tab in the AS-P to determine the addressing information. Open the WorkPlace Tech WorkStation Communication Settings and select LonWorks.  Open the Change Address window Select the "Manual Setup" radio Button Modify to match the AS-P Lon Works Network configuration.  If a different Domain ID or subnet has been assigned in the AS-P, it will need to be assigned the same in WorkPlace Tech You can now browse the LonNetwork from the laptop.  If the MNL devices are assigned applications from the AS-P, do not modify the programs from the WorkPlace Tech Tool  

Issue What are the steps to reload a controller Environment CX controllers BCX controllers ACX controllers NCII NC2 CX9680 I2 controllers B3 controllers Cause Point or program not available, receiving 5121 error Resolution To reload a controller follow the steps below: In continuum explorer select Options/Send to controller options and either the middle choice or bottom choice depending how which and how many controllers to be reloaded The most common and the default is to set to the middle setting to reload only the controller selected. Now select the controller to reload and right click and select send to controller The distribution located in the icon tray can be launched from a double-click to watch the progress of the reload.

Issue Temperature Sensor Location Valve Location Actuator Location Product Line Field Devices Environment Actuator Sensor Valve Cause Where to fit and locate field devices. Resolution Valves: If the valve is lift and lay type and the application is diverting, then the valve must be fitted in the return. If the valve is lift and lay type and the application is mixing, then the valve must be fitted in the flow. The rule of thumb for lift and lay valves is "2 ins and 1 out" Rotary (shoe) valves can be fitted in either the flow or return for either mixing or diverting applications. Use pipe unions, so that the valve can easily be removed. Actuators on Valves: If the heating medium is steam then the actuator/valve arrangement is not fitted vertically, tilt the valve/actuator to an angle so that heat can convect away vertically and the actuator is not subjected to as much heat. In all cases, do not fit the actuator/valve arrangement so that the actuator is vertically under the valve. If the valve leaks, it will damage the actuator. Temperature Sensor location, in both wet and air applications the sensor need to sense correctly the medium it is in. Where possible install in a location for easier maintenance e.g. at a height reachable from a fixed floor level. Pipe Temperature Sensors: The tip of the sensor needs to be in the core of the medium i.e. the centre. The sensor needs to be fitted where stratification does not take place or is reduced. This can be achieved by fitting after a pump or after a bend where turbulence provides a good mix. If the sensor is fitted on a bend, then the probe faces the flow of/oncoming water. In CHW applications, fit the pocket just off horizontal, so that any condensation forming in the pocket can drain away. Adequate insulation will prevent condensation forming in the pocket. If fitting vertically in the top of the pipe is unavoidable see Oil for the DWT0001 (or STP660) pocket sensor to prevent problems with condensation. Duct Temperature Sensor: Supply Air - If a probe type sensor is fitted, it needs to be ideally 3 meters downstream and in the centre of the duct from the supply fan and preferably after a bend fitted with turning vanes. Return Air - The temperature sensor needs to be fitted before/upstream of the extract fan. Frost Coils - Temperature sensor, due to the short distance available, probe sensors are difficult to locate, but try to be as far away from the coil e.g. on the other side of the pre-filter bank and in the centre of the duct/AHU. Even better is to use an averaging type temperature sensor. Frost Coils - Fan Hold Off thermostat. Allow sufficient capillary to cover the battery surface. Lace the capillary across the frost battery on the downstream side using the correct clips. If the thermostat body needs to be fitted on the external side of the AHU, then fit with the minimum of capillary on the external of the AHU. Use a grommet or stuffing gland to protect the capillary as it goes through the AHU skin. If the AHU is fitted outside or is in an unheated space then the thermostat needs to fitted internal to the AHU. Do not cut the capillary if it is too long. Tidy capillary ends so they do not flap in the airstream. Outside Temperature Sensor: Outside temperature sensors should be located correctly to the local region you are in and the application they are serving i.e. compensated outside sensor in the UK are fitted on a wall facing north. The sensor should not be fitted on flues, chimneys, near opening windows. They should not be fitted near to compounds containing plant expelling heat e.g. chiller compounds. The sensor should be fitted at a height that does not require the use of steps or ladders for maintenance. Room Temperature Sensor: Sensors should be fitted at an agreed height and not fitted on external walls, near opening windows and doors or above radiators. They need to be exposed to the area they are controlling and not be directly influenced by heat sources e.g. computers. Sensors with exposed setpoint adjust or controls need to be fitted at a lower height so that people with disabilities can adjust them. Sensors that are fitted onto partitioned walls or have a conduit need the hole plugging so that there are no draughts. Sensors that are fitted directly to concrete or steel beams should be packed out with a thermal insulating material. Valves and Sensor Wiring: Allow sufficient cable to allow removal of actuator or sensor without having to disconnect the device. See the full Building Controls Group - Control Sensor Installation guide.

Issue Quick Knowledgebase access to Continuum 2.0X information Product Line Andover Continuum Environment Continuum Cause A Knowledgebase article for Continuum 2.0X information in case a product announcement wasn't received. Resolution The initial release of Continuum v2.0 software was announced by Schneider Electric in PA-00353 CyberStation & web.Client v2.0. Version 2.0 includes a Software licensing option, SMTP email, support for Internet Explorer 10 & 11, and access control enhancements. Version 2.0 is a paid upgrade for all prior Andover Continuum versions (i.e. v1.9x and below). Release Documents: Feature Blast Compatibility Matrix Cyberstation Installation Guide Webclient Installation Guide Download Links: Continuum Cyberstation 2.0 Download Webclient 2.0 Download Software license and Ordering and activation process  

Issue Is it possible to setup more than one custom card format in Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Custom Card Formats Cause Have a requirement for two or more custom card formats. Resolution Currently, only one Custom Format can be configured.   It is possible to add a Secondary Format to a Reader port in Reader Expanders, but only one port can be setup with a Custom Format.    However, Credential Types have now been introduced with the release of Security Expert 4.3, which largely supersedes Custom Formats going forward and allows multiple custom card formats and even QR codes where required.  Please see AN 276 Security Expert - Configuring Credential Types - Integration Guide for more information on setting up Credential Types and Maximum number of Credential Types for more info on how many can be used.

Issue When logging into Xenta server using Internet Explorer 8 a certificate error is displayed as displayed below: When logging into the web server of a Xenta controller using Internet Explorer 8 an error message is shown stating that there is a problem with the website's security certificate. The error reads: There is a problem with this website's security certificate. The security certificate presented by this website was issued for a different website's address. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. We recommend that you close this webpage and do not continue to this website. Click here to close this webpage. Continue to this website (not recommended). More information How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Internet Explorer 8 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Internet Explorer 😎 cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution Click "Continue to Website" to continue to the screen shown below. Click on "Certificate Error" which is found on the right side of the address bar at the top. A dialog similar to the one below will open. Click "View certificates". The certificate dialog will appear. Click "Install Certificate." The Certificate Import Wizard will open. Click Next. Allow Windows to automatically select where to store the certificate. Proceed to Finish the Certificate Import Wizard. A notification appears indicating that the certificate was imported successfully. Restart Internet Explorer for the change to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Internet Explorer is uninstalled then reinstalled. The alternative is that a certificate issued by a Certificate Authority (CA) may be purchased. These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. See "This Connection is Untrusted" certificate error when logging in to a Xenta Server using Firefox for information on installing certificates into Firefox. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Need to replace an AVUE, AVUX or AVUM Mark 5 Actuator Product Line Field Devices Environment AVUE5305 AVUE5355 AVUE5304 AVUE5354 AVUX5202 AVUM5601 Cause Need to find a replacement for the obsolete AVUE, AVUX or AVUM Mark 5 actuator, that will allow the valve to be retained. Resolution The AVU* Mark 5 range of actuators can be replaced from the MZ300S range. AVUE5305 replace with MZ300S-24M AVUE5355 replace with MZ300S-24M AVUE5304 replace with MZ300S-24M AVUE5354 replace with MZ300S-24M AVUX5202 replace with MZ300S-24F AVUM5601 replace with MZ300S-230F The AVUE, AVUX, AVUM Mk 5 Datasheet is attached   MZ300S Specification sheet   MZ300S-24M Installation Instructions MZ300S-24F Installation Instructions   MZ300S-230F Installation Instructions

Issue Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause When configuring extended logging in the BACnet application folder, these objects are not available when performing a device discovery from the AS or ES. Prepare one AS with a BACnet point Create a trend log on the BACnet point Create an Extended log for that BACnet trend log From a second AS, the BACnet objects are available after a Device Discovery except for the Extended log object. StruxureWare Building Operation online help for “Configuring Extended Logging for a BACnet Trend Log” states:    ***Key Concept: Extended trend logs are not BACnet objects. These are StruxureWare Building Operation exclusive. The term "BACnet Extended Trend Log" does not exist and is a misnomer. Resolution The main reason is that extended logs are not defined in the BACnet standard; they are proprietary to EcoStruxure.  Everything that is proprietary to EcoStruxure Building Operation is not exposed to BACnet including graphics, script & function block programs and central IO points are not directly exposed, but have to be bound to BACnet I/O objects. The extended log serves the purpose of expanding a log on a larger capacity server.  A trend log on an AS would be more appropriate to extend on an ES. If you have a trend log in an external BACnet device (like a b3 or a 3rd party device/system) then you would want an extended log in the AS, to collect from that device (and then maybe a larger extended trend on a parent ES). If there is a local BACnet trend log in an AS (in the BACnet interface application folder) that is required to be larger, consider increasing the buffer size property of the one log that is needed (the default size of 10 may be too small, and increasing to 1000 up to 5000 (extended log size) may be an option). That would be most interoperable with other (3rd party) BACnet clients that need access to the trend log data.

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue The enhanced logging module in the 50 series does not continue logging once full if not configured to do so. Product Line Satchwell MicroNet Environment MicroNet VisiSat Logging Object Cascade Logs Cause The old logging object when the logs were full over wrote the oldest values automatically. The current 50 series logging object requires additional linked for the logging object to function the same way. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- The logging object has been enhanced. An example of the 100 series and IAC logging object is shown here. An example of the 50 series logging object is shown here. The original logging object defaulted to log and overwrite the older values and when configured looked like this. To achieve the same result with the 50 series type logging object, a couple of the logging object external nodes need configuring. and when configured looked like this. Further information regarding this object can be found in the VisiSat help file and engineering guide. VisiSat V1.2 Engineering Guide This document provides details for IAC 400, IAC 420, IAC 600 and IAC Touchscreen configuration. VisiSat V2.1 Engineering Guide (This document contains details for configuring the MicroNet range of controllers. MN300, MN440, MN500, MN 620, MN350, MN450, MN550, MN 650, MNLCD and MN Touchscreens). VisiSat V2.1 Installation and User's Guide VisiSat V2.1 data sheet  See MicroNet 100 series controller MLi's and Data sheets See MicroNet 50 series controller MLi's and Data sheets See Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue Every time an alarm comes in to Workstation, the Alarm View pop up window opens up. Product Line EcoStruxure Building Operation Environment Workstation Alarm View Window Cause This is a setting that can be turned off and on as desired. Resolution Right click anywhere inside of the alarm queue (either on an actual alarm or in the white space below the alarms). Go to "Alarm view settings." Check or uncheck "Display alarm view" to turn on or off the pop-up feature.

Issue At times numbered errors pop up in Cyberstation or you may see a numbered error in the Error Listview Product Line Andover Continuum Environment Continuum Cyberstation Windows Cause Numbered errors appear in Cyberstation or in an Error Listview and an explanation is needed for troubleshooting Resolution With Continuum running and with the focus on the main Continuum screen or Continuum Explorer, press F1 to bring up the help menu Select index Type in ‘error’ Select Error Messages, Cyberstation This displays a list of some of the error messages that may come up in Cyberstation. This is not a comprehensive list and it doesn’t provide solutions, but gives an initial idea of what is happening for troubleshooting.   Below is the error list that you will find in the Help   OS Error Messages Error Hex Code Error text 1 0x0001 No message block available 2 0x0002 No message queue available 3 0x0003 Invalid message block 4 0x0004 Invalid message size 5 0x0005 Message is blocked 6 0x0006 Can't deallocate message, it is on a queue 7 0x0008 Invalid message queue 8 0x0008 Invalid message blocking order 9 0x0009 Invalid process ID 10 0x000A Duplicate queue ID 11 0x000B Timed out waiting for message CPL Error Messages Error Hex Code Error text 1024 0x0400 Name has more than 16 characters 1025 0x0401 Comment has more than 132 characters 1026 0x0402 Comment has more than 132 characters 1027 0x0403 Symbol(s) are not from the correct set 1028 0x0404 Field is too long to display 1029 0x0405 Statement or expression is not correct 1030 0x0406 Array is longer than 32,767 entries 1031 0x0407 FOR and NEXT use different index var names 1032 0x0408 GOTO is not allowed inside a loop 1033 0x0409 Fatal, not enough free memory 1034 0x040A Same line name given to more than one line 1035 0x040B No line has this line name 1036 0x040C Same name for more than one local variable 1037 0x040D No item with that name exists 1038 0x040E Cannot define any more local variables 1039 0x040F BREAK or CONTINUE is outside a loop or block 1040 0x0410 Same name or number for more than 1 argument 1041 0x0411 Operation is not available 1042 0x0412 Number is not valid 1043 0x0413 Number cannot be longer than 132 digits 1044 0x0414 Fatal, bad stack address 1045 0x0415 Fatal, illegal stack operation 1046 0x0416 No function with that name exists 1047 0x0417 Attributes do not apply to local variables 1048 0x0418 No quotation marks at end of string 1049 0x0419 Data type is not same as field type 1050 0x041A Data has more chars than field allows 1051 0x041B Record has too many or too few fields 1052 0x041C More records than RECORD statement allows 1053 0x041D Date or time is not valid 1054 0x041E Path name has too many names 1055 0x041F Attribute does not apply to the item type 1056 0x0420 Local variable name cannot be an argument 1057 0x0421 Incorrect array entry type 1058 0x0422 Alarm expression is too long 1059 0x0423 You cannot set that item value 1060 0x0424 You cannot change that attribute value 1061 0x0425 Name is not a program or function name 1062 0x0426 Cannot enable/disable all of one type 1063 0x0427 You must give a name of a local data file 1064 0x0428 Parser stack overflow 1065 0x0429 Cannot use that var as FOR...NEXT index var 1066 0x042A Data file is too long 1067 0x042B You cannot change value of system variable 1068 0x042C Statement is too long 1069 0x042D 0, C or E is a reserved line name 1070 0x042E Feature not available on this controller 1071 0x042F Number must be an integer 1072 0x0430 Passed too many arguments to a function 1073 0x0431 An argument index must be from 1 to 15 1074 0x0432 No chars allowed after continuation symbol 1075 0x0433 Cannot run or stop program from command line 1076 0x0434 Report files are not supported yet 1077 0x0435 Unknown command option 1078 0x0436 Name given is not a controller name 1079 0x0437 Command is valid only from the command line 1080 0x0438 Command is valid only in a program or function ITP Messages Error Hex Code Error text 2048 0x0800 Tried to set item you cannot set 2049 0x0801 Set point or var to value of wrong type 2050 0x0802 Tried to use local var that does not exist 2051 0x0803 An expression uses an operand incorrectly 2052 0x0804 Must set HOUR to value from 0 to 23 2053 0x0805 String is too long 2054 0x0806 Operation is not available 2055 0x0807 Scanner runtime stack overflow 2056 0x0808 Used an incorrect function argument 2057 0x0809 Tried to print to a non-string item 2058 0x080A Tried to rotate prog to nonexistent line 2059 0x080B Used an item type when it is not allowed 2060 0x080C Tried to divide a value by zero 2061 0x080D Gave an array entry that does not exist 2062 0x080E Gave non-numeric var as array index 2063 0x080F Gave more or less arguments than allowed 2064 0x0810 Date or time is not valid 2065 0x0811 Executed too many statements on one line 2066 0x0812 Function did not give the expected result 2067 0x0813 FOR...NEXT loop index variable not numeric 2069 0x0815 Invalid import point address 2070 0x0816 Used name that is not a data file name 2071 0x0817 Used rec or field data file does not have 2072 0x0818 Cannot read data file 2073 0x0819 Cannot write to data file 2074 0x081A Path name is not an actual path 2075 0x081B Attribute does not apply to the item type 2077 0x081D Tried to set attribute to an invalid value DCP Error Messages Error Hex Code Error text 3072 0x0C00 Operation is not available 3073 0x0C01 String is too long 3074 0x0C02 Fatal, not enough free memory 3075 0x0C03 Exceeded number of displayable lines 3076 0x0C04 Invalid import point address 3077 0x0C05 Statement is too long 3078 0x0C06 Controller cannot find an item 3079 0x0C07 Controller cannot open a file of this type 3080 0x0C08 Date or time is not valid OMS Error Messages Error Hex Code Error text 5121 0x01401 Cannot find the item 5122 0x01402 Reached end of the list 5123 0x01403 Attribute does not apply to the item 5124 0x01404 Name is too long 5125 0x01405 Attribute is inappropriate 5126 0x01406 Cannot access file on other controller 5127 0x01407 FatalErr__ Gave invalid hash table size 5128 0x01408 Not enough memory 5129 0x01409 SysErr__ Passed invalid info to database 5130 0x0140A Item is being used and not available now 5131 0x0140B Access to the item denied 5132 0x0140C Array index too large or too small 5133 0x0140D SysErr__ Invalid format for retrieving data 5134 0x0140E Cannot associate these items 5135 0x0140F No relationship of the type defined for item 5136 0x01410 SysErr__ Passed invalid setup to database 5137 0x01411 Reached end of the list of related items 5138 0x01412 Line is too long 5139 0x01413 Value does not apply to the attribute 5140 0x01414 File read error 5141 0x01415 Duplicate item name 5142 0x01416 SysErr__ Cannot set/get attribute 5143 0x01417 SysErr__ Terminal communication error 5144 0x01418 Lbus creation failed 5145 0x01419 String display failed 5146 0x0141A SysErr__ Cannot access the item in database 5147 0x0141B Incorrect path name 5148 0x0141C Incompatible value 5149 0x0141D SysErr__ Invalid message queue Id 5150 0x0141E SysErr__ Session not found 5151 0x0141F Attribute not defined yet 5152 0x01420 Invalid auto-conversion 5153 0x01421 Zero string size 5154 0x01422 Not allowed to delete a system variable 5155 0x01423 SysErr__ System hash tables locked 5156 0x01424 The class object list locked 5157 0x01425 Duplicate handle Id 5158 0x01426 Not enough memory - reset log array size 5159 0x01427 HardwareErr__ Bad RTC chip 5160 0x01428 Duplicate serial number 5161 0x01429 Duplicate Infinet Id number 5162 0x0142A Infinet learn mode is in process 5163 0x0142B Line name is undefined 5164 0x0142C SysErr__ Reserved line label 5165 0x0142D Unable to send the message 5166 0x0142E Dump process stopped 5167 0x0142F Controller not found 5168 0x01430 Invalid handle Id 5169 0x01431 Incorrect line or statement 5170 0x01432 Missing end of controller statement 5171 0x01433 Does not know the type 5172 0x01434 Not allowed to set the attribute 5173 0x01435 Not allowed to set the description 5174 0x01436 Not allowed to set the format 5175 0x01437 Not allowed to set the engineering unit 5176 0x01438 Item already exists 5177 0x01439 Not allowed to set the attribute 5178 0x0143A SysErr__ Invalid controller path 5179 0x0143B SysErr__ Invalid current controller message 5180 0x0143C Invalid response from other controller 5181 0x0143D Item is already being used 5182 0x0143E File is being saved by another operator 5183 0x0143F File is too long 5184 0x01440 Cannot access the item on other controller 5185 0x01441 SysErr__ Passed invalid indicator to database 5186 0x01442 Invalid Energynet ID 5187 0x01443 Invalid Infinet ID 5188 0x01444 Invalid Infinet port 5189 0x01445 Missing end of dictionary statement 5190 0x01446 Missing end of import/export statement 5191 0x01447 Unable to compile the file 5192 0x01448 Invalid dump file statement 5193 0x01449 Missing end of block statement 5194 0x0144A Missing end of code statement 5195 0x0144B Missing end of object statement 5196 0x0144C Unable to rename the controller 5197 0x0144D Unable to rename the comm port 5198 0x0144E Item has no type 5199 0x0144F Undefined alarm 5200 0x01450 Attribute can only be retrieved, not set 5201 0x01451 Conversion too long 5202 0x01452 Not allowed to retrieve the attribute value 5203 0x01453 No default format defined 5204 0x01454 SysErr__ Passed invalid indicator to database 5205 0x01455 Invalid schedule type 5206 0x01456 Missing colon in the statement 5207 0x01457 Incorrect name 5208 0x01458 Incorrect header for the code block 5209 0x01459 Incorrect header for a sub block 5210 0x0145A Incorrect header for the object block 5211 0x0145B Undefined system variable 5212 0x0145C Undefined comm port 5213 0x0145D Not allowed to create an alarm 5214 0x0145E Inappropriate request for the comm port 5215 0x0145F Invalid mode for the comm port 5216 0x01460 LBus is already set up 5217 0x01461 Invalid program file 5218 0x01462 Program is already in the firing order 5219 0x01463 Unable to access the item 5220 0x01464 No response to the Infinet token pass 5221 0x01465 NetworkErr__ Received incorrect CRC on Infinet 5222 0x01466 SysErr__ Invalid error value from Infinet 5223 0x01467 Attribute does not apply to the point type 5224 0x01468 Attribute does not apply to the port type 5225 0x01469 Item must be a program 5226 0x0146A File must be open 5227 0x0146B File took too long to open 5228 0x0146C Cannot alter the file 5229 0x0146D Cannot add or remove records 5230 0x0146E The relationship is already set up 5231 0x0146F CAnnot dump dictionary block of controller 5232 0x01470 Cannot dump the controller 5233 0x01471 Cannot dump associated items 5234 0x01472 Undefined IOU number 5235 0x01473 Invalid channel number 5236 0x01474 No free alarm links 5237 0x01475 Cannot access next Enet controller in list 5238 0x01476 Cannot access next Infinet controller in list 5239 0x01477 Incorrect header for the log array block 5240 0x01478 Invalid log array index 5241 0x01479 Cannot modify the file 5242 0x0147A Unable to create the Infinet controller 5243 0x0147B Zero is not a valid serial number 5244 0x0147C Invalid baud rate 5245 0x0147D Comm port is not set up for Infinet 5246 0x0147E Controller is not online 5247 0x0147F Not allowed to delete a comm port 5248 0x01480 Cannot define any more handle IDs 5249 0x01481 Invalid controller name 5250 0x01482 Invalid Infinet controller name 5251 0x01483 Invalid Energynet controller network ID 5252 0x01484 Controller doesn't know Infinet ID 5253 0x01485 Invalid electrical type 5254 0x01486 Invalid DateTime value 5255 0x01487 Invalid log type 5256 0x01488 Invalid floating point number 5257 0x01489 Attribute doesn't exist for the item 5258 0x0148A Access to the conversion denied 5259 0x0148B Number of array entries is too  arge 5260 0x0148C Invalid program status 5261 0x0148D Unable to access the comm port 5262 0x0148E Cannot overwrite the item 5263 0x0148F New default mode is current mode 5264 0x01490 Cannot set export flag for Enet controller 5265 0x01491 Operation is not supported 5266 0x01492 SysErr__ Unused sched events are inaccessible 5267 0x01493 Sched occup/unoccup variable not DateTime 5268 0x01494 Holiday schedule doesn't exist 5269 0x01495 Import/Export item must be a point 5270 0x01496 Point must export to controller/alarm 5271 0x01497 Sched occupancy flag not output/numeric point 5272 0x01498 Item is not a holiday schedule 5273 0x01499 Cannot dump the import/export block 5274 0x0149A Cannot set up the port 5275 0x0149B Index number for the alarm is too large 5276 0x0149C Invalid state 5277 0x0149D Comm port is busy 5278 0x0149E Reference array is full 5279 0x0149F Undefined alarm type 5280 0x014A0 Item is not local controller 5281 0x014A1 HardwreErr__ Bad EEPROM chip 5282 0x014A2 Cannot retrieve controller model number 5283 0x014A3 Cannot retrieve controller serial number 5284 0x014A4 Unspecified Enet ID 5285 0x014A5 Undefined controller model number 5286 0x014A6 Controller has no assigned Infinet port 5287 0x014A7 Cannot find controller in the Infinet list 5288 0x014A8 Invalid password 5289 0x014A9 Cannot retrieve controller version number 5290 0x014AA Handle ID is out of range 5291 0x014AB Not allowed to delete user ACC 5292 0x014AC Not allowed to use this many Infinet devices 5293 0x014AD Not allowed to change user ACC's security level 5294 0x014AE Full path is not set 5295 0x014AF Access denied 5296 0x014B0 User passwords are mismatched 5297 0x014B1 User doesn't exist on remote controller 5298 0x014B2 Invalid stop bits 5299 0x014B3 Invalid data length 5300 0x014B4 The user is logged in 5301 0x014B5 Not allowed to change user name 5302 0x014B6 Not allowed to delete this controller 5303 0x014B7 No TankProbe extension block installed 5304 0x014B8 No TankNet exists 5305 0x014B9 TankNet is already set up 5306 0x014BA Can't change a TankProbe to another electrical type 5307 0x014BB Duplicate PIN 5308 0x014BC There is no card information available for this person 5309 0x014BD Invalid card entry 5310 0x014BE Duplicate card 5311 0x014BF Invalid schedule 5312 0x014C0 Attribute does not apply to object type 5313 0x014C1 Undefined card type 5314 0x014C2 Invalid PIN value 5315 0x014C3 Same area on both sides of a door is not allowed 5316 0x014C4 The maximum number of doors allowed has been reached 5317 0x014C5 Personnel cleanup in progress.  Please try again. 5318 0x014C6 Unable to delete one or more personnel objects on rip 5319 0x014C7 Personnel distribution in process.  Please try again. 5320 0x014C8 Not allowed to set an area in a DefaultDoor 5321 0x014C9 Unable to set remote sync bit for one or more personnel objects 5322 0x014CA Could not synchronize CX and SX databases 5327 0x014CF Event log size has been automatically adjusted 5328 0x014D0 No XDriver code module installed 5329 0x014D1 XDriver code module installed 5330 0x014D2 XDriver code module incomplete 5331 0x014D3 Checksum error detected in S-record 5334 0x014D6 Duplicate XDriver parameter 5338 0x014DA Invalid IP parameter 5339 0x014DB Invalid Subnet Mask for the IP class 5340 0x014DC IP network number should not equal 0 5341 0x014DD IP host number should not be all 1s 5342 0x014DE Possible Infinet bus short detected 5345 0x014E1 Update operation still in progress 5348 0x014E4 Invalid NetWare frame type 5349 0x014E5 UTC Offset is out of range 5350 0x014E6 No personnel cache entries available 5351 0x014E7 Memory expansion board not installed 5352 0x014E8 Flash memory operation failure 5353 0x014E9 Too many IOUs 5354 0x014EA The maximum number of areas allowed has been reached 5355 0x014EB Attempt to lock door has failed 5356 0x014EC Attempt to unlock door has failed 5357 0x014ED OMS database has become corrupt 5358 0x014EE OMS internal error 5359 0x014EF Buffer too small for data requested 5360 0x014F0 OMS database not currently available (backing up) 5361 0x014F1 String size exceeds implementation limit 5362 0x014F2 Backup disabled due to excessive use (requires manual enable) 5363 0x014F3 Schedule events are out of order 5364 0x014F4 Invalid bookmark for error log 5365 0x014F5 Duplicate SmartSensor control point 5366 0x014F6 Inappropriate value for current restart mode 5367 0x014F7 Copy protection violation has occurred —  please contact your ACC dealer 5368 0x014F8 Error sending CustomABAFormat string to IOU module 5369 0x014F9 OBJ_ERR_BACnet_ERROR  - A BACnet error occurred. 5370 0x014FA OBJ_ERR_DABL_OVERFLOW - The controller has reached its BACnet device binding limit. LAN Error Messages Error Hex Code Error text 6144 0x1800 Comm user return 6145 0x1801 Comm invalid message length 6146 0x1802 Comm invalid destination address 6147 0x1803 Comm invalid source address 6148 0x1804 Comm invalid QID 6149 0x1805 The port is not an Infinet 6150 0x1806 The controller is not responding 6151 0x1807 Comm LAN reconfig in progress 6152 0x1808 The controller is offline 6153 0x1809 The EnergyNet is not configured 6154 0x180A Comm destination node paused 6155 0x180B Send request timeout 6156 0x180C Send error 6157 0x180D NULL message received 6158 0x180E Unable to send message 6159 0x180F Invalid EnergyNet node ID 6160 0x1810 Duplicate Ethernet ID 6161 0x1811 Duplicate EnergyNet ID 6162 0x1812 Out of memory 6163 0x1813 Ethernet RAM test faillure 6164 0x1814 Undefined EnergyNet ID 6165 0x1815 Undefined Ethernet ID GLB Error Messages Error Hex Code Error text 7169 0x1C01 Symbol name too long 7170 0x1C02 Invalid characters in symbol 7171 0x1C03 Symbol cannot be a system variable 7172 0x1C04 No items 7173 0x1C05 Too many items 7174 0x1C06 First character must be alpha 7175 0x1C07 System internal error 7176 0x1C08 System clock was changed IES Error Messages Error Hex Code Error text 8192 0x2000 Cannot build IE API request 8193 0x2001 Cannot send IE API request 8194 0x2002 IES has bad OMS pointer 8195 0x2003 IE handle points to wrong network address 8196 0x2004 IE handle is invalid 8197 0x2005 IE bad data in ObjKey 8198 0x2006 IE API response not received 8199 0x2007 IE no Infinet 8200 0x2008 Could not establish import 8201 0x2009 IE database locked LBS Error Messages Error Hex Code Error text 9217 0x2401 LBus not ready 9218 0x2402 wait_collect or wait_update timeout 9219 0x2403 Invalid IOU number 9220 0x2404 LBus database is locked 9221 0x2405 An active IOU exists 9222 0x2406 LBus error no memory 9223 0x2407 Comm channel specified is invalid 9224 0x2408 Sensor's channel is invalid 9225 0x2409 LBus does not exist 9226 0x240A The IOU number has not been defined yet 9227 0x240B Bad electrical type 9228 0x240C Value is too large or too small 9229 0x240D IOU communication status = online 9230 0x240E IOU communication status = offline 9231 0x240F IOU number is not between 1 and 16 IOS Error Messages Error Hex Code Error text 10240 0x2800 NULL 10241 0x2801 Type not valid for this IO channel 10242 0x2802 IO channel number out of range 10243 0x2803 IO channel already assigned 10244 0x2804 Vref out of tolerance 10245 0x2805 IO channel is unassigned 10246 0x2806 Tri-state partner is already assigned 10247 0x2807 AD converter trashed 10248 0x2808 AD converter timed out 10249 0x2809 Reference channels not initialized 10250 0x280A Adjacent channel is already in use 10251 0x280B Invalid channel for RTD use 10252 0x280C Cannot delete IOU module until all associated objects are moved to other IOU modules or deleted 10253 0x280D Duplicate module ID 10254 0x280E Insufficient memory for IO operation 10255 0x280F IO module is not commissioned 10256 0x2810 Incorrect channel type 10257 0x2811 Channel doesn't exist 10258 0x2812 Error installing IO system 10259 0x2813 Error in IO database 10260 0x2814 Module is not saved 10261 0x2815 Attribute does not exist 10262 0x2816 IO message queue does not exist 10263 0x2817 Illegal IO queue designator 10264 0x2818 IO module number is too large 10265 0x2819 IO queue is full 10266 0x281A No IO message buffers available 10267 0x281B Unknown IO message buffer size 10268 0x281C IO routing table section doesn't exist 10269 0x281D IO routing table entry not saved 10270 0x281E IO module response was lost 10271 0x281F IO MIP interface initialization error 10272 0x2820 No response from IO module 10273 0x2821 Illegal message received from IO module 10274 0x2822 IO module message data error 10275 0x2823 IO module message is not a service pin message 10276 0x2824 No IDs available for IO module commissioning 10277 0x2825 Too many IO modules for the controller 10278 0x2826 IO module domain update error 10279 0x2827 IO module read memory command failed 10280 0x2828 IO module update address command failed 10281 0x2829 IO module update NV cnfg table failed 10282 0x282A No message tags available for IO message 10283 0x282B Not a suitable replacement IO module 10284 0x282C Error in routing IO module response 10285 0x282D Incorrect response from IO module INF Error Messages Error Hex Code Error text 11264 0x2C00 NULL 11265 0x2C01 Comm port cannot connect an Infinet 11266 0x2C02 Comm port already set up for another purpose 11267 0x2C03 Comm port has not been assigned a purpose 11268 0x2C04 No Infinet controller with that serial number 11269 0x2C05 Infinet is not set up 11270 0x2C06 Infinet ID is already in use 11271 0x2C07 ID is not valid for Infinet 11272 0x2C08 Message received is not for an Infinet controller 11273 0x2C09 Controller received message from an unknown source 11274 0x2C0A Learn mode currently in use 11277 0x2C0D Learn already in process on this port 11280 0x2C10 Infinet controller is not responding 11281 0x2C11 NULL buffer passed to Infinet server 11282 0x2C12 Message type is not supported by Infinet server I2LD Error Messages Error Hex Code Error text 202752 0x31800 No model matching download header exists on this CX 202753 0x31801 Error found in I2 download header 202754 0x31802 Error found in I2 model information 202755 0x31803 Models in I2 download exceeds maximum 202756 0x31804 Received download message type out-of-service 202757 0x31805 Begin I2 download header not received 202758 0x31806 Comm Error - socket receive 202759 0x31807 Comm Error - socket send 202760 0x31808 No comm buffers available 202761 0x31809 Download state machine error 202762 0x3180A Illegal message type response from Infinet controller 202763 0x3180B Listen call failed 202764 0x3180C Bind call failed 202765 0x3180D Socket call failed 202766 0x3180E Received short packet - not enough data 202767 0x3180F Application type unknown by I2 202768 0x31810 Download model does not match I2 model 202769 0x31811 Unknown/unsupported message type 202770 0x31812 I2 download out-of-sync 202771 0x31813 I2 received unknown/unsupported packet type 202772 0x31814 I2 received segment that exceeds block storage 202773 0x31815 I2 received block address out-of-range for flash 202774 0x31816 I2 detected end of download CRC error 202775 0x31817 I2 does not support download revision 202776 0x31818 I2 is running in boot loader mode 202777 0x31819 I2 total received block count does not match 202778 0x381A I2 detected external RAM failure 202779 0x3181B I2 malloc failure during boot-up 202780 0x3181C I2 detected unknown flash device

Issue The re-install of the Continuum system and security key is not being recognized. Product Line  Andover Continuum  Environment Continuum Cyberstation Sentinel Security Key Cause Driver not loaded Resolution Make sure the antivirus is not running on installation. If so, disable and re-install Continuum, or try to reinstall the Sentinel Key driver. The Sentinel Key driver is located in "\Continuum\ISSetupPrerequisites\{1F0227D8-C348-45F0-9789-1DEE3E8C5889}" directory and is an executable that can be run to install the driver. Sentinel Key drivers can be located on their website: http://www.safenet-inc.com/support-downloads/sentinel-drivers/ At times, the removal and reinstall of the driver still don't recognize the key even when it can be seen in another PC. If that is the case then do the following: Go to http://www.safenet-inc.com/support-downloads/sentinel-drivers/ and download SSDCleanup and run it. This will do a clean removal of sentinel drivers on the PC. Reboot and then reinstall the Sentinel driver from \Continuum\Install\Sentinel directory (SSDv7_xx.exe) Test multiple Windows accounts. There can be restrictions placed even on local admin accounts that interfere with reading the key.

Issue There are 31 different Parser Errors that can result from a Menta direct download to a programmable controller. Product Line TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Causes vary by error code.  See details below and any links to additional information. Resolution No. Name Comment 0 PARSER_OK   1 PARSER_CREATE_OBJ_ERROR Seen immediately on an attempt to download directly.  Subsequent attempts result in "Download Failed."  Resetting the device caused the error to come back.  See in the error in COD window that its showing 0,0 coordinate pairs and underlying information.  The error's not in the Menta code itself.  No spaces allowed in the Program Specification -- a change from earlier versions.  May render your device unusable after attempting to download -- correct files won't download either. 2 PARSER_ALLOCATE_FLASH_ERROR   3 PARSER_IOMOD_SAVE_ERROR   4 PARSER_VERSION_ERROR   5 PARSER_APPNAME_ERROR   6 PARSER_ABBREV_ERROR   7 PARSER_TYPE_ERROR   8 PARSER_SOURCEFILE_ERROR   9 PARSER_SIGNAL_ERROR Error 9 has to do with the signal list (ESP-file) there all the public signals are transferred from Menta into the GraphOP tool by a sort of a long list. Normally, if you just make the application in Menta, this should not be any problem, however search and replace on signal names could give you headache. 10 PARSER_ALARMTEXT_ERROR Seems to download and fails on resetting device.  Had a case where this occurred when the application was too large due to generation of an OP tree where there wasn't one before.  Check memory. 11 PARSER_TIMESCHEDULE_ERROR   12 PARSER_IOMOD_ERROR   13 PARSER_IO_ERROR The terminal may not exist in this unit type.  Could also include situations where the same terminal reference is used in multiple references (this could be on the Xenta or the IO module). Typically caused by copy/paste. Reference to unsupported I/O Error in COD file - Error:13 for more information. 14 PARSER_CYCLETIME_ERROR   15 PARSER_CODE_ERROR Constants table has scientific notation, PVR blocks have scientific notation, Expression block attempting to use scientific notation, application size too large PARSER_CODE_ERROR Error in COD file - Error:15 for more information. 16 PARSER_DST_ERROR   17 PARSER_CHECKSUM_ERROR   18 PARSER_EOF_ERROR   19 PARSER_SNVT_ERROR   20 PARSER_SNVT_CRC_ERROR   21 PARSER_AUTHOR_ERROR   22 PARSER_BLUEPRINT_ERROR   23 PARSER_NO_BPR_FILE   24 PARSER_TLOG_RAM_ERROR   25 PARSER_TLOG_FLASH_ERROR   26 PARSER_TLOG_TO_MANY   27 PARSER_TLOG_ERROR_IN_DEF   28 PARSER_TOLG_PARSE_ERROR   29 PARSER_IMAGE_TOO_BIG   30 PARSER_RESET_BEFORE_PARSED   31 PARSER_SELF_DESTRUCTION_PERFORMED  

Issue When attempting to log in the below network errors, or similar, are displayed. Connect: The server was unable to process the request due to an internal error. Could not log on to Server. Please check your remote connection setup Further checking the Windows Application Event logs on the Server you may also find error messages similar to the below being logged against the Security Expert services. CDTNames::GetTagName : Cannot open database "SecurityExpert" requested by the login. The login failed. Product Line EcoStruxure Security Expert Environment Security Expert MS SQL Cause The Security Expert services do not have the correct credentials to access the SecurityExpert database. Resolution Confirm the user account that the Security Expert services are using in Windows. Go to Start > Run > and type "Services.msc". Confirm the account that those services are being run under. By default, and in the example, this is the Local System account. Run Microsoft SQL Server Management Studio and under your server browse to Security > Logins. Find the user account that your services were used in step 1 In the Server Roles page of this user account. Enable the "sysadmin" server role Save changes and restart the Security Expert services.