Building Automation Knowledge Base

Issue After updating FireFox to version 34 and later, you get the message "Unable to Connect Securely" when accessing a Xenta Server using HTTPS   After updating Chrome to version 40 and later, you get the message "This webpage is not available" when accessing a Xenta Server using HTTPS   In Internet Explorer, you get the message "This page can't be displayed" when accessing a Xenta Server using HTTPS Product Line TAC Vista Environment Xenta Server FireFox Chrome Internet Explorer Cause From version 34 of FireFox and version 40 of Chrome, SSLv3 is disabled by default for security reasons as SSLv3 is no longer considered secure enough. As per Vista Server Cryptographic Protocols TAC Vista, TAC Xenta Server and TAC Xenta 911 is using SSLv3 and is therefore blocked when using SSL (HTTPS). In the newest versions of Chrome and FireFox, not even the work around described below works, so you need to set the Xenta Server to low security through the XBuilder project. Resolution In Internet Explorer, FireFox and Chrome you can manually reenable SSLv3.   Solution 1: Set the Xenta server to only use HTTP and not HTTPS This is done in TAC XBuilder   Solution 2: Allow SSLv3 in FireFox 1: In the FireFox address bar, write about:config 2: Accept the warning 3: Write security.tls.version.min in the search field - below you can see the default setting 4: Double click the line, and change the number to 0 5: Try logging into the Xenta Server again. If it doesn't work the first time, restart the browser and try again   Solution 3: Allow SSLv3 in Internet Explorer Check the advanced settings in Internet Explorer. SSL 3.0 must be enabled. If it's not, then enable it. If you can't, it's because it's disabled by a policy, and you need to get the IT department to enable it.   Solution 4: Allow SSLv3 in Chrome 1: In the Chrome address bar, write chrome://flags/#ssl-version-min and select SSLv3 in the drop down box. Solution 2: Allow SSLv3 in FireFox 1: In the F

Issue During Energy Expert installation an error is shown, and the floating license manager is never installed Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert (formerly Power Manager) Installation Cause "Error 1722" occurs due to a conflict between the version of Java installed on the PC and the version included in the EE installation package Resolution Uninstall all versions of Java from the PC Install the JavaRuntime manually from the install media "..\setup\SetupSupport\Licensing\JavaRuntime\x86\jre1.7.0_02.msi" Run the complete installation again

Issue What is the difference between a Numeric Input, Numeric Output and Numeric Public within a script program. Is using a Numeric Public a less efficient choice (as opposed to using a Numeric Input or Numeric Output) that will generate negative overhead in the AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Workstation b3 and Infinet controllers Cause Want to determine best practices when choosing numeric types during script programming. Resolution Numeric Input is a read only numeric (from the point of view of the script program) that accepts a binding. Numeric Output is a write only numeric (from the point of view of the script program) that accepts a binding. Numeric Public is both read and write (from the point of view of the script program). Numeric Public also accepts a binding. (A Numeric Public can be bound to both a Graphic and a Value Object to allow overriding of values from a Graphic. See SBO Script Public.zip for an example) When choosing the numeric type in a script program there is no overhead cost difference between using one of these numeric types vs the others. Also check out the Script Programming - Writing the Script Program Quick-Help video on the Exchange. NOTE b3 and Infinet Controller scripts do not support "Numeric Public", but "Numeric Output", in these controller scripts, can be used in a similar way to "Numeric Public" The Bound value is read by the script as well as being written to.

Issue Performing Load Sources in the EcoStruxure ETL tool causes errors with the following headers:   There was no endpoint listening at http://localhost:8080/EcoStruxure/DataExchange that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. The HTTP request is unauthorized with client authentication scheme 'Digest'. The authentication header received from the server was 'Digest realm="ews@SxWBM",qop="auth",nonce="AEEE5A9347E49ECADC753B5AA17EECE0",OPAQUE="5B4718"'. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Enterprise Server Automation Server Cause The EBO EWS Extract Task settings are incorrect in regards to the EcoStruxure ES or AS that it is trying to access.    There was no endpoint listening at... This error is due to the use of the incorrect port numbers in the EWS Web Service URL.   The HTTP request is unauthorized with client authentication scheme 'Digest'... This error is due to the use of the incorrect admin Username and/or Password.  Resolution The settings of EBO EWS Extract Task need to be verified and corrected.    Click on the Tasks tab in the ETL tool and select the "EWS Extract Task". The extract task settings will be displayed on the right side of the screen.                                                                               Verify that the port number in Web Service URL address corresponds to the port number being used by the ES or AS  Verify that a valid Username and Password has been entered into the EWS Web Service User Name and Web Service Password fields. 

Issue Unable to log in to Web Client. After filling in the username and password and clicking "Sign In" the Sign In box disappears and the Username, Password, and Language Box are shown. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client Security Expert SOAP Cause Configuration issues are usually related to a mismatch between SOAP and Web Client security settings. Resolution Commonly this problem is resolved after re-installing SOAP and Web Client then rebooting the machine. If this does not resolve the problem then continue to check the below troubleshooting steps and gather information for support if those steps do not resolve the problem.   Is everything on one machine or are the various components spread across a number of machines? If so, where is SQL, Security Expert Server, SOAP, Web Client, and Security Expert Client installed? If different machines, provide these details to support, which components are on each and what Operating System (OS) is installed. Are you using the HTTP connection for SOAP or HTTPS? If HTTPS and SOAP are on the same machine as Web Client then try using the HTTP port. Either re-install SOAP and Web Client using the HTTP option instead of or: Browse to the soap.connect.php located at C:\inetpub\wwwroot\SecurityExpertWebClient\include.  Edit it using e.g. Notepad and change HTTPS to HTTP and change the port to 8030 so the Web Client uses HTTP to communicate with the SOAP service. Then in IIS Manager restart the SecurityExpert and SecurityExpertWeb services. If a hardware or software firewall is being used, test the connection without these enabled. If Chrome is the browser being used then test with another browser such as Internet Explorer, Microsoft Edge, or Firefox. Confirm that all Security Expert services are running and started. Confirm the SOAP prerequisites have been installed for your Operating System (OS). See the Enabling the Required Windows Features section in the SX-SOAP Security Expert - SOAP Service - Installation Guide. In this document, there is a heading with instructions for each supported OS. Confirm that a Windows local admin user has been used to install all components. If in doubt, re-install Security Expert, then SOAP, then Web Client. Confirm if Security Expert was installed with Windows Authentication selected, if so then SOAP will need to have this option enabled as well during its installation.  Determining Security Expert authentication settings after installation  Confirm that you have adequate concurrent client licenses available on your Security Expert license. SOAP uses one of these when connecting to the Data service and if none are available the SOAP connection will fail.  See Unable to log in to Security Expert Web Client - 'Too Many Connections' The Microsoft Visual C++ 2015-2019 Redistributable Package is a requisite install for Web Client. Web Client installs this as part of the setup, confirm that this was installed. Check the Windows Event Logs for Security Expert errors. Open Windows Event Viewer: browse to Windows Logs > Application. Review logs and save all events to file. Provide this to Product Support if raising a support case. browse to Applications and Services Logs > Schneider Electric Security Expert. Review logs and save all events to file. Provide this to Product Support if raising a support case. Reboot machine after re-installation of SOAP or Web Client. If SOAP was re-installed then also re-install Web Client. Please provide findings and responses to the above steps through to your local support channel for additional assistance should the problem continue.  

Issue The Automatic Logoff feature is available in version 1.4 and higher. Starting in version 1.5, there is a default automatic logoff time of 10 minutes in both Workstation and WebStation for the Administrators user group. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation WebStation Cause To prevent unauthorized users access to the system the automatic logoff feature has been added to SBO/EBO. The default Administrators group is set to automatically log off of both Workstation and Webstation after 10 minutes of being idle. This setting cannot be changed for the Administrators group. Resolution The automatic logoff function makes it possible to decide when a user is automatically logged off after a specified time of inactivity. Inactivity means that no user initiated activity is ongoing, that is, no action has been made using the mouse or the keyboard. However, if a user has initiated a big operation in Workstation, for example an import or a large copy and paste, the user is still considered to be active as long as the process is ongoing in Workstation. This is to prevent loss of data. The automatic logoff function is used for security reasons and it also prevents that a Workstation user occupies a license when inactive. The automatic logoff time is set at User Group level and is always defined by the group that has the longest automatic logoff time. For example, if a user belongs to two groups, one group has an automatic logoff time of 5 minutes and the other group has an automatic logoff time of 15 minutes, the user is automatically logged off after 15 minutes. If a user belongs to a group that does not have the automatic logoff function enabled the user will never be logged off. Note: When a user is logged off by the automatic logoff function all settings that are not saved are lost.   Creating a new user group so the Automatic logoff time can be adjusted Starting in version 1.5, in order to change the duration of time before the automatic logoff occurs or turn it off a new User Account Group must be created. Follow the steps below. Go to the Control Panel in Workstation. Click on Account management. Click Add under the User Account Groups section. Name the new User Account Group. Click Next. Select the Users to add to the new group and then click the right arrow to move them to the "Selected User Accounts" window. Click Next. In the same method as step 4, select the Workspace to add to the new group and move it over to the "Available Workspaces" window. Click Next Set the group policies for the new group taking note of the Automatic logoff time which can be set to "Never" if desired. Click Create.   Changing the Automatic logoff time of an existing user group In the System Tree under System > Domains > Local > Groups, select the user group and click on the "Policies" tab. Here the Automatic logoff time can be changed and then click the save button on the tab at the top of the window.

Issue Understand methods for integrating Security Expert with Active Directory for creation and management of Operators and Users. Product Line EcoStruxure Security Expert Environment Security Expert Active Directory SX-AD-OPR SX-AD-USR SX-DB-SYNC Cause Security Expert Active Directory Integration provides synchronization and authentication for Active Directory users enabling organizations to leverage on the user management and security policies that Active Directory provides. This article looks at the details between each integration option. Resolution There are four options for Active Directory Integration. 1. Default Windows Authentication option. This allows for logging in to Security Expert with the Windows User account credentials which could include AD users if on a Domain. Operator object must be created in Security Expert and configuration of windows authentication option has some specific steps to be followed for it to work. Unable to login to Security Expert using Windows Authentication Remember to use syntax "<domain>\<username>" for the username when configuring the Operator for a Windows user ON a  Domain. Remember to use syntax "<computername>\<username>" for the username when configuring the Operator for a Windows user that is NOT on a Domain. No extra license is required for this. 2. SX-AD-OPR : License for adding Security Expert Operators from AD. Security Expert Operators will need to be added manually using the following steps: Navigate to Operators and click Add. Check the Windows Authentication box. Click the ellipsis adjacent to the User Name. Use the Active Directory Users window to search for the AD credentials you wish to use. Once the Operator has been added, you may check the Windows Authentication option when logging in. 3. SX-AD-USR : License for adding Security Expert Users from AD. This will allow an active directory domain windows group to be periodically polled for updates that will in turn update the Users in Security Expert. Individual options for importing users, disabling user if AD user is disabled, disabling user if AD user is deleted. Only user names are imported, other than this only action can be disabling of users in Security Expert. No other details can be updated or added. See application note AN-141 Security Expert LDAP User Import Configuration. 4. SX-DB-SYNC : Data Sync Service with Powershell script. Powershell script pulls user details out of AD and writes to a CSV file that the Data Sync Service then imports into Security Expert. Can perform more functions than SX-AD-USR as any attribute from AD users can be mapped to any attribute in Security Expert users. Will require use of powershell experience as the sample script will likely need to be tweaked. Here is a really good video Using Data Sync to Transfer Information from Active Directory to ProtegeGX on using Windows Active Directory as a source of Users/Operators for the Data Sync Service. It provides a good overview of how this is accomplished and how easy it can be to setup. See Security Expert Data Sync Service and sample Powershell script SXFetchADUsers.zip attached  

Issue How do I time sync my controllers to my workstations? Product Line Andover Continuum Environment Continuum site Cause The workstation will only synchronize its time to the controllers automatically when the controller is reloaded. It is common practice though to have the controller synchronize its time with the workstation on a periodic basis, commonly once a day. Resolution The only way to synchronize time between the Controller and the Workstation is through a Plain English program running the Workstation. This Program only needs to be created in one Workstation. Below is an example of the program as well as how to trigger the program to run. If Minute = 3 then Goto SetTime Else Stop SETTIME: Set NetworkName\LowestNodeCXName\Date to Date Stop E: Stop Note: This program needs to be triggered off the minute system variable. The program is a Fallthru program which resides in the CyberStation. You only need to do the lowest ACCNet Id controller in each Continuum network. Also ensure that the UTC offset has been correctly entered in every Workstation and BACnet device, and that each Network has the correct Time Zone setting.

Issue What is the BACnet attribute COV Increment and how to use it Product Line Andover Continuum Environment BACnet Cause The COV Increment attribute on a BACnet point is equivalent to the Threshold attribute of standard Continuum Infinity inputs. When a Continuum BACnet point is subscribed to by other BACnet devices using COV (Change of Value), its value must change by at least that COV Increment value before a new Value Notification will be sent out. Using this attribute will decrease network traffic especially on the MSTP network when subscribing to frequently changing values.  Resolution This CovIncrement attribute can be set in the BACnet point's Editor on the Basic Alarms Tab.   If you have a CyberStation prior to Version 1.8, setting this value from the point editor will not stay persistent in the controller after the controller is reloaded, it will default to 0. In order to keep the value after a reload, you will need to write a PE program to set the desired value after a reload. The program should be Autostart and Fallthru. A sample of the program is below: Line SetCov Writeproperty("Full Bacnet Path to Point", CovIncrement, "Desired Value") Stop If you have several points that need the CovIncrement set, you would just add the additional lines into this program.   In 1.8 or greater, this program is not needed as these attributes get sent to controller on a reload. Suitable initial CovIncrements still need to be added to each BACnet point however as they default to 0.

Issue How can the true/false output from a Boolean object (i.e. Tstat) be changed to a numeric 0 or 100 in Niagara G3? Environment Niagara G3 Cause Represent a boolean on/off value with a numeric that can be used to drive other logic. Resolution Open the kitControl palette under the Util folder Use an object called NumericSwitch Link the output of the Boolean object into the InSwitch property of the NumericSwitch In the properties of the NumericSwitch object, set the "in true" value to 100 and "in false" value to 0 (or vice versa if reverse acting). The output of the NumericSwitch will be a numeric type.

Issue Modbus slaves are programmed according to device documentation, but either the wrong values are returned or error codes complaining about invalid address. Product Line TAC Vista Environment Xenta 913 Xenta 731 Xenta 511:B Cause The XBuilder Device Editor has two ways to address modbus registers. The improper usage of these methods can cause communication problems because the wrong register is polled. 1. Fixed Address Blocks This method combines the function code and register address to produce a single number format that serves multiple function codes. This is sometimes referred to as numerical notation. A poll of a holding register uses function 03 and an address from 00 00 to FF FF. When using Fixed Address Blocks a message of function code 03 and address 00 00 is displayed as 40001. Due to this combination it is limited to 9,999 addresses per function code. Type Function Code  Address  Coil Status  01  00001-9999  Input Status  02  10001-19999  Holding Register  03  40001-49999  Input Register  04  30001-39999 When the device editor is using Fixed Address Blocks then the numerical number is parsed from the Register in the following way. Register Function Code Address 1-9999 01 Register - 1 10001-19999 02 Register - 10001 30001-39999 04 Register - 30001 40001-49999 03 Register - 40001 2. Function Code Tables (Discrete Input, Coil, Input Register, Holding Register) This addressing format is closer to the actual protocol and keeps the function code separate from the register address. It also provides full use of the addresses from 0 to 65535. Table Function Code Discrete Input 02 Coil 01 Input Register 04 Holding Register 03   If the wrong format is used it can result in failure to communicate because the wrong register is used. For example polling register address 40010 on function code 03 when it should have been address 9 on function code 03. Resolution The documentation of the product being interfaced with is the best guide on the register addressing and the format they use. If the documentation does not directly specify the information then use the follow hints to guide your selection: Hints to use Function Code Tables Addresses that fall on zero (0, 10000, 30000, or 40001) Non binary data that is less then 30001 or greater then 40001. Devices states it is J-Bus. Register address is displayed in Hexadecimal format. Hints to use Fixed Address Blocks Any address register above 30000 or 40000, unless it claims to be a JBus device. If it is still unclear which addressing format to use then experiment with read only data and value pages in the Xenta Servers. Pick a point that you can easily confirm the value, add both address formats to a device template, and then confirm the proper format with a values page. Once you know how to read one point the rest of the product documentation is easier to work with.

Issue Microsoft Visual C++ Runtime Library Error After you install I/NET on a computer containing Microsoft Office XP or one of the Office XP programs, you may receive one of the following error messages: Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSDMN.EXE abnormal program termination Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSEARCH.EXE abnormal program termination Environment XP computers containing Microsoft Office or other loaded programs, one of which may be I/NET  Cause This behavior occurs if a program (not necessarily I/NET) conflicts with the Mosdmn.exe and Mosearch.exe files or with video settings, antivirus or 3rd party programs conflicting with your operating system. Resolution The Mosdmn.exe and Mosearch.exe files are part of the "Support for fast searching" feature in Office XP. This feature is similar to the Find Fast feature in Microsoft Office 2000. Fast searching uses the Indexing Service in Office XP to create a catalog of Office files on your computer's hard disk. To resolve this issue, use the following methods, as needed, in the order presented. Method 1: Clean Boot with Only MoSearch The Mosearch.exe (Microsoft Office Search Service) and Mosdmn.exe (Microsoft Office 10 Search Filter Daemon) Startup items may be conflicting with some other program (or programs) running in the background. Therefore, clean boot your computer with only MoSearch selected on the Startup menu to determine whether this program is the source of the conflict. To do this, follow these steps:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the General tab, click Selective startup. 4. On the Startup tab, click to clear all check boxes except for MoSearch. 5. Click OK, and then click Yes when you are prompted to restart the computer. 6. If the error message can be reproduced, repeat the preceding steps. In step 3, also click to clear the Process System.ini file and Process Win.ini file check boxes.   If the error message cannot be reproduced, this indicates that MoSearch is conflicting with some other program or programs running in the background. Follow these steps to locate the conflicting program:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the Startup tab, click to select one of the check boxes. 4. Click OK, and then click Yes when you are prompted to restart the computer. 5. If the preceding steps reproduce the error message, the last item added to the Startup menu is causing the conflict. If the error message is not reproduced, repeat these steps until all Startup menu check boxes are selected. 6. If all the Startup menu check boxes are selected and the error message is still not reproduced, start Msconfig again, and then click to select the Process System.ini file and Process Win.ini file check boxes.   Restart the computer. You may need to install a clean version of I/NET depending on your computer setup.   This is the solution for the Microsoft Visual C++ Runtime Library error with XP Office. Other solutions may entail removal or reconfigure of video drivers, antivirus programs, or other 3rd party programs conflicting with your operating system.

Issue Reference of I/NET Guide Product Line TAC INET Environment I/NET Seven Cause Combination of various TCON documents showing most common used functions for easy reference.  Note that this document is not maintained.  Please refer to documentation available on Exchange Resolution Download the INET Pocket Reference Guide PDF

Issue Where to go to download the Access Expert Device Administrator application. Product Line Access Expert Environment Server 2012 SQL 2012 and above Premise Install V2 Hosted V2 Applet V3 Cause There is no documentation on where to go to download the Device Administrator and how to program the SSC to communicate with the selected application. Resolution The following steps describe where to go and download the software and how to use it to program an SSC: Go to the EcoBuilding Exchange In the search field type Device Administrator Select the Access Expert Device Administrator and download to any location Browse to location and double click execute to run and install the program Accept Agreement and click next to continue installation Click Next to start installing the software Select the location where the file will be installed Successfully loaded software To complete installation, click on Finish Connect the device to a network switch that is open to the internet and launch the application by opening Access Expert device Administrator from the Schneider Electric group in All Programs Launch the application  Right click on the usb line or click on the green arrow to the top left to upgrade the software Once upgraded successfully, Right click again on the line and select properties then select the Ethernet 1 ConfigurationTab Select applicable choice whether it is DHCP or Static addressing being used and click on OK. Once the device comes back Online, select the DIP Switches Tab and check the box for Default User Using the IP address given from step number 13, open up IE and browse to that address Once opened, configure the SSC per Setting up an SSC (System Security Controller), EP1501 and EP1502 Mercury Controllers.

Issue There are a number of reasons that RPC error occur on Cyberstation and troubleshooting steps are needed Product Line Andover Continuum Environment Continuum Webclient Windows XP Window Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause RPC (Remote Procedure Call) errors happen on Cyberstation when the connection to the SQL database is not available Resolution There are many reasons that RPC errors can occur. A Google search of RPC errors will indicate that many applications have similar issues with these errors. An RPC error on a Cyberstation means that it has lost connection to the database for some reason and you will need to restart Cyberstation in order to recover. Below is a list of things to check when dealing with RPC errors on CyberStation.   Multiple Cybers Does the issue occur on multiple Cyberstations? Database Does the issue follow the database? i.e. load the database onto a test server or try a test blank database. Were some new objects recently added to the database when this started happening? Does reverting to a backup stop the errors? Increase Virtual Memory Right Click on My Computer> Properties> Advanced System Settings> Under Performance select the Settings button> Advanced tab> Under Virtual Memory click the Change button Recommended is 4096 Network disruption or slowness Networking  -  Verify all aspects of your networked environment.  This includes, but not limited to, slow networks, possible problems with your network interface card (NIC), cabling issues, switch/router issues, busy networks.  As you can see from the above definition of what RPC is it can be heavily reliant on the stability of the network and all it’s interfaces. Continuum does not support DHCP Multiple NIC cards – ensure there is only 1 NIC card enabled. No all NIC cards are created equal. Connections issue can be caused by an integrated NIC card of low quality. There can be settings within the NIC card itself that could affect consistent communication. Check the manufacturers website for details. Verify that there is no duplication of IP addresses on the network. Pull a cable and ping the address, if you still get a response there are 2 devices with the same IP address. WINS -  Verify your WINS settings and make sure there are no issues with the WINS Server.  This is known by Microsoft to cause RPC errors. DNS - Verify your DNS settings and make surer there are no issues with the DNS server.  This also is known by Microsoft to cause RPC errors. Verify that  the "TCP/IP NetBIOS Helper" service is running. Check and see if “File and Print Sharing” is enabled.  There are references in a lot of online articles, on RPC, problems that turning on “File and Print sharing” resolves RPC errors. Ping and SQL Is the SQL database still available to Cyberstation? From a DOS prompt> Ping IP (SQL Server) –t (continuous) Ex. c:\> ping 192.168.1.5 –t Note the number of responses as well as the time in milliseconds to respond. A local SQL server would usually be under 100ms. Check resources on the SQL Server (CPU, I/O Read/Write, memory usage, etc.) Windows Server 2003 Network card setting (This setting isn’t available in Windows Server 2008) Shut Continuum down on the machine having the problem. Start>Settings>Network Connections>Local Area Connections>Right Click and select Properties> Click on File and Printer Sharing for Microsoft Networks>Click Properties button> Select 'Maximize data throughput for network applications'. (Default is Maximize data throughput for File Sharing) Ok through all the screens and start Continuum and see if this makes a difference. XP/Vista/Windows 7 Start> Settings> Network Connections> Local Area Connection> Properties> Advanced tab> Windows Firewall - Click the Setting button> Click the exceptions tab Verify that File and Print Sharing is selected. File and printer sharing are disabled by default with XP SP2. There is no network throughput option in XP, Vista or Windows 7 like there is on Windows Server 2003. Windows Event Viewer Take a look at the Windows Event Viewer Application Log (Start> Run type ‘eventvwr’ or Launch Windows Control Panel> Administrative Tools> Event Viewer Examine the events and look for RPC error indications in the details. There may be a pattern of which executable is causing the errors. You may also see informational events that indicated momentary disconnects. A large number of these can indicate an issue with the Cyberstation being able to connect to the database consistently in a timely manner. Monitoring tools Run an acctrace.exe (C:\Program Files\Continuum) and a wireshark capture at the time of the RPC error to see the Continuum and network processing going on at the Cyberstation. Windows Process Monitor may also be helpful in seeing which process is having trouble. http://technet.microsoft.com/en-us/sysinternals/bb896645 Check the system for SpyWare and/or Viruses. Workgroup versus Domain connection An excerpt from the Continuum System Admin manual In a LAN Configuration, the Continuum CyberStation must be in a “Microsoft Domain “ type installation. This is because the Continuum CyberStation will use Named Pipes Interprocess Communication System (IPC). This is accomplished with Windows remote procedure call (RPC). In a Microsoft Domain model installation, once the session is established between the Continuum Cyberstations Client(s) and the SQL server it is a persistent connection once authentication is established.   In a Workgroup installation, the database connectivity session is re-authenticated and re-established for each database transaction. This results in much slower performance and an inconsistent connection. If you are running a LAN system using Windows 2003 server SP2/R2 and SQL 2005 try disabling the TCP Chimney Offload feature by following the below. Disable the TCPchimney setting on the SQL server and application server Windows 2003 SP2 comes inbuilt with a new network scalability pack which is supposed to accelerate the Windows networking stack. But this setting may not be compatible with all the network cards and it could pose connectivity issues as well. For more information you can refer to http://support.microsoft.com/kb/912222 http://support.microsoft.com/kb/942861   To disable this feature please take the following steps on both the SQL Server and application server.   Open up a command prompt on the machine. Run the following command: "Netsh int ip set chimney DISABLED" Change the values of the following registry keys to 0 a. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ EnableRSS   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ EnableTCPA Reboot the machine after the above changes. ==========================================================   Disable SynAttackProtect on SQL server: Windows 2003 Sp1 and Sp2 introduces this new feature which monitors processes getting high number of connections and if it detects that too many connections are being made, the connections will be rejected. Click Start, click Run, type regedit , and then click OK. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters On the Edit menu, point to New, and then click DWORD Value. Type SynAttackProtect , and then press ENTER. On the Edit menu, click Modify. In the Value data box, type 00000000 . Click OK. Quit Registry Editor. Sound Card In some cases it was found that the built in sound card is causing the problem. If your not using WAV files for alarms then try disabling the integrated sound card in the BIOS.  If WAV files are being played then try disabling the integrated sound card and put in a PCI sound card. There have also been problems with OEM versions of the Operating system of the client machines.  A lot of vendors, like Dell, add additional applications to the systems they ship to assist them if they need to remote into the computer for troubleshooting purposes.  It is strongly recommended that these OEM versions of the Operating System is removed and install the system from a genuine Microsoft installation CD. Go to Control Panel-> Administrative Tools -> services, click with right mouse button Remote Procedure Call -> click properties. remote procedure call properties window is now open, go to recovery and you´ll see: First failure, second failure, subsequent failures -> choose : restart the service. In this setup the system will automaticaly restart RPC when something shuts it down. Check all your Firewall settings.  If possible turn off the firewall for testing and see if the problem goes away. Check to make sure there are no ports being blocked that the RPC Server uses.  See KB 908472 (http://support.microsoft.com/kb/908472) details the steps for specifying the RPC port range.  Also, be aware of the consequences of reserving the RPC ports. This has the potential to break other applications that assign ports in this range. KB 812873 discusses this, too. http://support.microsoft.com/kb/812873 Make sure all Peripheral devices like Network cards, Video cards, Sound Cards, etc. have the latest drivers for them installed. http://support.microsoft.com/kb/913384 Control Panel > AdminTools >Services and selected the Properties for Remote Procedure Call (RPC)  In the Log On tab, they changed the Log on as: to the Local System Account. It had been "This Account" NT Authority\Network Service. Is an EventNotification configured to send a page on alarm? If a PC running Continuum did not have a modem but on startup Continuum was trying to send an alarm with a page then accdataservice was crashing causing an RPC. Microsoft KB177446 article that describes in depth RPC troubleshooting procedures http://support.microsoft.com/kb/177446

Issue Replacing a DC3000 controller. Environment Drayton DC3000 Cause The DC3000 is now obsolete. Resolution The DC3000 controller is obsolete, and there is no direct replacement available. Our current range of discrete controllers cannot provide the same functionality as the DC3000, assuming that functionality has been used. To provide the same controller functionality a programmable controller such as the Micronet or Xenta ranges will be required To upload an overview of the Micronet range, please click HERE. The Xenta controller range is listed as part of the TAC Vista Product Catalogue which can be downloaded from Schneider Electric but a table of the controllers and their I/O are shown below.

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 

Issue What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF  

Issue When swiping a card in front of the reader, there should be a beep indicating that the reader has read the card. There is no beep. Product Line EcoStruxure Security Expert, Andover Continuum, TAC I/NET Environment Access Control HID Reader Cause There are 3 possible reasons for this issue: The beeper is disabled through a default configuration when the card is shipped The beeper has failed The Reader and Card represent incompatible technologies such as an 125Khz Prox Reader trying to read a 13.56MHz IClass Card Resolution Ensure Reader and Card both support a common technology (125Khz/13.56Mhz etc..) Short the Beeper wire (yellow) and the GND wire (Black) with the reader powered On If there is a beep, that indicates that the beeper can work but is disabled. Ask the manufacturer to send a configuration card to enable the beeper (use 3 seconds after reader power is on) If shorting the beeper produces no sound, the beeper has failed. Send the reader to repair and replace it with a new one.

Issue In a Niagara G3 station with a BACnet MSTP integration, the following error appears in the application director output: Transaction Timed out! invokeId 223 TransactionException in poll() for BacnetDevice {Kens_RM106}:pl=PollList [Kens_RM106 device:7219 3000:13] 196608025 {160} 10 PLEs) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) .... Hundreds & hundreds more Environment Niagara G3 Cause MSTP trunk / traffic issues Resolution See the discussion about an identical issue at Niagara-Central.com.  Here is a link:  https://community.niagara-central.com/ord?portal:/discussion/DiscussionThread/11258