Building Automation Knowledge Base

Issue Open Tgml Graphics Not enough storage is available to process this command. Environment Vista Workstation TGML graphic Cause This is a Windows error having to do with how many applications are running simultaneously/how much memory is available. Resolution A reboot of the PC should free up allocated memory that is no longer needed.

Issue BCX not showing up on infinity side but shows up on the Bacnet side. Environment Continuum Cyberstation Explorer Cause View options in the Continuum Explorer were set to view the Continuum Bacnet device as Bacnet Only. Resolution In Continuum Explorer, select the menu item View Select Show Continuum Bacnet Device As Select Infinity Controller and Bacnet Device

Issue When using the above sensors in conjunction with a BAS or Sigma building management system, out of range values can occur. Environment BAS 2800+ Outstation Sigma Controller 0-10 volts Cause If is possible for the sensor to provide greater than the specified 10 Volts DC output, and this causes the Outstation / Controller to display a default value. Resolution To resolve this issue carry out the following; 1 - Connect a 10K ohm 0.1% resistor in series with the 0 – 10 volt signal as shown in the drawing below. 2 - Create a lookup table in Sigma or BAS 2800+ with the following values. Input                        Output 0                    –        0 83.335           –        100.000 100.000         –        100.000 3 - Allocate this table to the analogue input object, and download the (Point / Object) and table, to the (Outstation / Controller). The above configuration will allow the DC voltage to rise to 11.335 Volts before an out of range alarm would be generated.

Issue Cannot see any licenses when I log in to schneider-electric.flexnetoperations.com using an Activation Id Environment Vista 5.1.5 Vista licensing website (schneider-electric.flexnetoperations.com) Cause Once the license has been activated the Activation Id is no longer valid. Invalid Activation IDs are not shown in the user interface. Resolution After the initial activation of the license, use the Entitlement Id to login to schneider-electric.flexnetoperations.com instead of the Activation Id. The Entitlement Id will remain valid each time you log on to the licensing website.  

Issue Trend log creation is successful, but no values are recorded in the Vista SQL database. Error message “Failed to write values to log database” is visible in Vista Workstation alarm window and review of the b0warlog.txt in the $log folder of the Vista database reports errors: TLogHandler :: ObjectInitEnd: Failed to setup event log queue directory (hr=-2147024773) TLogXenta :: ServiceExecuted: Log (Path to Trend Log) not successfully read. Error: -2147024893 Environment Vista 4.3.0 - 4.5.0, 5.x.x Cause Corruption in the Vista database directory $queues folder causes disruption in recording of trend log values. A file with the name of insertlogvalues exists in the $queues directory when Vista Server is expecting a directory to exist with that name. Attempts to write queue files to the \$queues\insertlogvalues\ directory fails with a ERROR_PATH_NOT_FOUND error ( -2147024893). When Vista Server starts it tries to create the directory, but due to the presence of the file with the same name the process fails with a ERROR_INVALID_NAME error (-2147024773). Resolution Shut down Vista Workstation and Vista Server. Start Vista Server Setup from Start Menu\All Programs\Schneider Electric\TAC Vista Server 5.1.x\Server  Setup. For Vista version lower then Vista 5.1.4: Start Menu\All Programs\TAC\TAC Vista Server x.x.x\Server Setup. Click the Vista Database tab to view the Vista database directory: Open a Windows Explorer and browse to the Vista database directory. Open the $queues directory. Delete the contents of directory. Start Vista Server. Trend Log operation should now be restored.

Issue History Extensions in History Service show a “Fault” Status.  The Fault cause displays: "Duplicate history id:" followed by the name of the object. Environment I/A Series G3, version 3.3.22 and later Cause  By default, history extensions inherit the name of the objects they’re attached to (e.g. CFM).  If CFM is to be trended on multiple VAV units (VAV1, VAV2, etc.), this can cause issues when enabling history collection in the History Service; one or more histories will be in a “Fault” state, with the error message: “Duplicate history id:” for the Fault Cause. Resolution To resolve the issue, the history names can be configured to include the parent folder names:     1.  Open the Program Service in the station’s Services container, and click on the “Find Objects” button at the bottom of the Batch Editor view 2.  In the Bql Query Builder window, select (Custom Type) in the “Of type:” drop-down menu.  Two more drop-down menus will appear.  In the middle drop-down, select “history”.  In the last drop-down, select the appropriate history extension (e.g. NumericIntervalHistoryExt).  Then, click OK.  The Batch Editor view will populate with all of the history extensions in the station for the extension type selected     3.  In the Batch Editor view, highlight all of the history objects, then click the “Edit Slot” button at the bottom of the view 4.  In the Edit Slot window, select “historyName” in the Property drop-down menu.  In the New Value field, type the following:      %parent.parent.name%_%parent.name%     NOTE:  Depending on the tree structure, the filter may need to be modified in order to create a unique history name.  For example, if the network is structured in the following format:   In this example, the object nviSatSwitch1_value is a child of the Points container, which is a child of the device MnlRs3_10. In order to create a unique name for the history extension, the correct filter would need to be:         %parent.parent.parent.name%_%parent.name%.   5.  Click OK.  After a few seconds, the BatchEditor Results window will appear, displaying the objects that were changed.  The history extensions now have unique names, and can be enabled in the History Service

Issue It is not possible to communicate with Sigma controllers from the Sigma laptop or PC when using a Windows 7 operating system. Attempting to communicate with Sigma controllers will cause an error, the exact error will depend on the user action at this time. Environment Windows 7 Operating system. Cause The Windows 7 operating system network configuration is set to "Public" instead of "Work". Resolution From the Windows "Start" carry out the following; Select "Control Panel". Select "Network and Sharing Centre" Under "View your Active Networks" select your network and its existing network type, for instance "Public Networks". Choose "Work Network" and then "Close". The computer will now accept messages from other devices on the network.

Issue How to view user login/logout information in TAC Vista Workstation Environment TAC Vista Workstation Cause User login/logout information is captured in the events log. Event viewer can be filtered for displaying just the login information. Resolution Sign in TAC Vista Workstation as an administrator. Open the Event Viewer.   Use event filter to filter out unnecessary information Open Event Filter window, and select “General” tab. Under “Type”, leave “Commands” to be checked and uncheck everything else. Under “Object type”, Type “Vista Server” After the filtering, the event viewer will only display user login, user logout, server start up information. Additional Information: Viewing only the login/logout information: In the Event Filter window, select “Event Specific” tab Under “Command”, type “LOGIN” or “LOGOUT   Viewing specific user login/logout information In the Event Filter window, select “General” tab Under “User”, type the user name NOTE: if the user is in a user group, need to include the user group name also. For example, user SYSTEM is also in the SYSTEM MANAGER group, need to type “SYSTEM (User Profile SYSTEM)” in "User" textbox.

Issue Double clicking a .tgmlcomponentarchive file should automatically add the Component Archive to the Editor's component libraries. Sometimes it does not work and instead shows the following windows: TAC Vista Server Please wait while Windows configures TAC Vista Server Gathering required information... TAC Vista Server The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'TAC Vista Server.msi' in the box below. TAC Vista Server Error 1706.No valid source could be found for product TAC Vista Server. The Windows Installer cannot continue. Product Line TAC Vista Environment TGML Graphics Editor Cause There are five libraries that are included by default with every installation of the editor. They are: TAC Vista Symbols (EN) ISO Symbols DIN Symbols (EN) My Components Basic Controls If any of these libraries are removed by navigating to C:\Documents and Settings\All Users\Application Data\TAC Graphics Editor\Components and deleting the folder, attempts to add new libraries will fail. Resolution Navigate to the Buildings Business Extranet Go to Products > TAC Vista > Vista Software Click on the correct version of TAC Vista in the left-hand column. Choose Downloads Download the TAC Graphic Editor 1.1.X. Double click to install The directories are restored. Do not delete them.

Issue ETHERNET Cable Requirements. Environment Sigma 4.05 and earlier versions. V53 and ARM7 Processor Boards. Cause ETHERNET Network cabling advice. Resolution The Sigma Cabling Guide should be followed when installing an ETHERNET network: Sigma Cabling Guide 2.2 Further information about cabling can be found in the following guides: For V53 Processor Boards (UNC496, 596, UNC532, DNN and IC integration controllers): Cguide26.pdf For ARM7 Processor Boards (UNC696, 796 & UNC632): Cguide31.pdf Cguide32.pdf For ARM7 Processor Boards (DNN3 Decentralised Network Node): Cguide33.pdf For ARM7 Processor Boards (IC3 Integration Controller): Cguide34.pdf RJ45 Plug connections are:

Issue Configuration instructions for setting up a communications VX Log in the Xenta 5/7/9xx for communications troubleshooting. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 VXI Cause Configuration instructions for setting up a communications log in the Xenta 5/7/9xx for communications troubleshooting. Obtaining the communications log for a Modbus or BACnet network is crucial in finding communications errors, or other unforeseen problems with integrating to third party devices. Resolution Step by step instructions for creating the communication log for troubleshooting or for data analysis: Log In to the Xenta 5/7/9xx controller and navigate to the Utilities Folder:   Click on the Target System Folder and choose VXI Web Shell Commands:   The command line should appear with VX populated in the command line:   Logging to file in the Xenta controller will first need to be enabled to by typing VX L 1 and press submit:   VXI Web Shell Commands should return a messing indicating logging has been enabled for 1 hour:   After logging has been enabled, the verbosity will need to be set in order to capture each layer of communications on the wire. In the command line type VX V 9 and press submit:   VXI Web Shell Commands should return a messing indicating the verbosity has been set to 9 and what messages you will see with this verbosity level :   Let the communications log run for 5-10 minutes. Create as many changes on the 3rd party wire as possible to get various data changes to and from the Xenta Server.   In the command line type VX O and press submit:   This command will output the communications log the Xenta Server has collected. Highlight this entire output log and copy, then paste it into notepad for archiving or emailing:   To set the communication logging back to default type "vx V 1" or power cycle the Xenta Controller. To stop the logging to file, type "vx L".   For TCP/IP logging you can only monitor one client at a time: Complete Steps 1- 8 above Enter "vx d" This will display a list of the TCP available devices Enter vx d # where # is the number corresponding to the deice you wish to monitor To view the log, follow steps 9 and 10 above

Issue The nvoEffectSetPt is different than the nviSetPoint The nvoEffectSetPt is different than the cooling or heating setpoint (SCPTsetPnts) Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The nvoEffectSetPt is calculated according to nviSetPoint, cooling or heating setpoints (SCPTsetPnts), nviStPointOffset, and thermostat offset. Resolution The nvoEffectSetPt is a SNVT network output in Xenta 102-AX and represents the current effective setpoint that the controller is utilizing in its control loop. nvoEffectSetPt can be configured to display in two different manners: Actual and Normalized. (As defined bynciVAVselctcCntl.oP.ESS (UCPTvavSelection)) Actual nvoEffectSetPt displays the setpoint that corresponds to the currently active application mode of the controller (occupied cooling, unoccupied cooling, standby cooling, occupied heating, unoccupied heating, and standby heating). Normalized nvoEffectSetPt displays the average of the cooling and heating setpoints for the currently active occupancy mode (occupied, unoccupied, standby). NOTE: Whether nvoEffectSetPt is set to Actual or Normalized only affects how the effective setpoint is displayed and does not affect how the application operates. The 102-AX application utilizes the setpoint that corresponds to the currently active mode (occupied cooling setpoint, etc.). In addition, the thermostat adjustment of the setpoint will not appear in any SNVT in Xenta 102-AX controller. This offset is captured in the Xenta 102-AX's memory, and although it is not displayed, it is utilized into the nvoEffectSetPt calculation. Also note that the below scenarios only apply to the occupied and standby modes since the unoccupied setpoints are unaffected by nviStPointOffset, nviSetPoint or by the thermostat offset. Scenario 1: nviSetpoint is unused 1.1 Actual nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the sum of one(1) of the four setpoints (occupied cooling, standby cooling, occupied heating and standby heating) plus the offsets (nviStPointOffset and thermostat offset). 1.2 Normalized nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the average of heating and cooling setpoints ( 1/2(Occupied Cooling Setpoint + Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint + Standby Heating Setpoint) ) plus the offsets (nviStPointOffset and thermostat offset).   Scenario 2: nviSetpoint is used 2.1 Actual nvoEffectSetPt calculation: In cooling mode, the nvoEffectSetPt is the nviSetPoint plus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint -Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ),  plus the offsets (nviStPointOffset and thermostat offset). In heating mode, the nvoEffectSetPt is the nviSetPoint minus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint - Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ), then plus the offsets (nviStPointOffset and thermostat offset). 2.2 Normalized nvoEffectSetPt calculation In this scenario, whether the application is in the cooling mode or the heating mode, the nvoEffectiveSetPt is the sum of the nviSetPoint and the offsets (nviStPointOffset and thermostat Offset). Therefore, when nviSetPoint is used and nvoEffectSetPt is to Normalized, the actual heating and cooling SCPT setpoints do not matter; only the difference between them is significant. For example, setting occupied cooling and heating setpoints to be 75°F (24°C) and 65 °F (18°C) will give the same resulting nvoEffectiveSetPt as setting occupied cooling and heating to be 45°F (7°C) and 35°F (1°C).   Example Occupied Cooling = 72°F (22°C), Occupied Heating = 68°F (20°C), nviSetPoint = 75°F (24°C), assuming the nviStPointOffset and thermostat offset are zero. nvoEffectSetPt in Occupied Cooling or Heating Mode   Scenario 1.1 Scenario 1.2 Scenario 2.1 Scenario 2.2 Cooling Mode 72°F (22°C) 70°F (21°C) 77°F (25°C) 75°F (24°C) Heating Mode 68°F (20°C) 70°F (21°C) 73°F (23°C) 75°F (24°C)

Issue Xenta group bindings are used for group communication between Xenta group masters and members.  They also transmit TAC Network Variables between two programmable controllers.  Redoing group bindings is a common troubleshooting technique to address issues with these functions.  However, it can often be time consuming, especially if using LonMaker which requires the Visio drawing to be resynchronized.  Verifying that the Xenta group bindings in the device's address table are correct prior to redoing them can save time on an unnecessary troubleshooting step. Product Line TAC Vista Environment Vista programmable controllers LonMaker, NL220 Cause Checking to see if the group bindings need to be redone instead of always using it as a standard troubleshooting technique can save time. Resolution To access the Device Address Table of an application device in LonMaker: Right-click on the controller in LonMaker and go to Properties. Go to the Address table tab. Look at the first two entries (0 and 1) and note the value in the ID column. Go to another controller in the same group and compare the values in the ID column. Every controller on a network should share the same ID in row 0. Every controller in a group should share the same ID in row 1. If the group bindings are correct, there is no need to redo group bindings.   To access the Device Address Table of an application device in NL220: Select the application device in the tree Press Ctrl+A keys or right click on it and select the option Network\Network tables ... in its context menu Select the tab Addresses    The grid contains one line for each entry in the address table. Index = The index of the address entry MT = Yes if the entry is reserved for message tags connection Type = Type of the entry, Unbound (Not used or "free"), Turnaround, Subnet/Node, Broadcast, Group Size = Size of the group (zero for a large group) and Used only if Type is Group Domain = Domain index (0/1) Mb/Node = Member if Type is Group (not used for a huge group), Node id if Type is Subnet/Node or Unused Repeat timer = Value of the repeat timer  Retries = Retries count Rcv timer = Value of the receive timer  Tx timer = Value of the transmit timer  Gp/Subnet  = Group id if Type is Group, Subnet id if Type is Subnet/Node or Unused   Refresh will refresh the table.

Issue In order to make the correct determination when selecting an actuator, it is important to first understand the difference between sourcing and sinking triacs.  A triac will act as a switch. By triggering its gate electrode, it will either conduct alternating current or impede it. While it can be thought of as contacts on a relay, it is important to note that it is decidedly different. Environment Xenta 121-FC, 121-HP Xenta 101-VF, 102-VF, 102-ES, 100-D (legacy) Cause A digital output on a Xenta 121 (labeled V1 through V4) utilizes a ground sourcing triode for alternating current (TRIAC). In general, a TRIAC will either be voltage sourcing or ground sourcing (also referred to as voltage sinking). The Xenta 121 using ground sourcing TRIACs will be a determining factor when selecting actuators to be driven by digital outputs. Resolution A TRIAC output is similar to a hardware switch in that it will either open or close a circuit, allowing or stopping the flow of current.  Whether the internal side of the triac is connected to power or ground will determine whether it is a sourcing or sinking TRIAC. If the internal side of the TRIAC is connected to power, as shown in Figure 1, it will be considered a voltage sourcing TRIAC.  When the output is activated, current will flow from the output, through the actuator, to ground.  Most actuators are designed to accept voltage sourcing outputs from controllers. Figure 1. Voltage Sourcing Triac Configuration If the internal side of the TRIAC is connected to ground, as shown in Figure 2, it will be considered a ground sourcing (or voltage sinking) TRIAC.  When the output is activated, current will flow from a power source, through the actuator, and into the output.  Some actuators are designed to accept both voltage sourcing and voltage sinking outputs from controllers.  Figure 2. Voltage Sinking Triac Configuration The digital outputs on terminals V1 through V4 of a Xenta 121 utilize ground sourcing triacs.  The G terminal between each pair of triac outputs sources 24 Vac.  It has direct continuity with the G power terminal.  When the output is active, the triac will conduct current to ground completing the circuit. Said another way, if the output is inactive, there will be a 24V potential between V1 and G0 (ground), but a 0V potential between V1 and G.  When the output is active, there will be a 0V potential between V1 and G0, but a 24V potential between V1 and G.  An actuator is wired between V1 and G, so the potential across these two terminals will dictate whether the actuator is on or off. In one example, a 3-wire floating actuator is wired with OPEN, COM, CLOSE connected to V1, G, V2 respectively.  There shouldn’t be a problem if the actuator is using the 24Vac signal to drive an AC motor.  When the open command is active, the actuator will see a 24V potential across its contacts and drive the motor. In another example, a 4-wire floating actuator is wired in the same manner, but now also requires its own 24Vac power signal to run some on-board logic.  This example will not work because that actuator is expecting to see COM wired to ground, but it is in fact wired to the same 24Vac, resulting in 0V potential between power and ground of the actuator. One solution is to use caution when selecting actuators to be driven by the Xenta 121.  Avoid actuators designed to be controlled with voltage sourcing outputs.  Another option is to use the triac outputs to close contacts on external relays that will source the necessary 24V as needed. Another application of the digital outputs is to control the coil of a relay in order to open or close the circuit of another device, such as a low voltage terminal strip, fan motor contactor, etc. While some low voltage applications may function without the use of the relay between the 121 outputs and the device being controlled, this is generally not recommended and may negatively impact the reliability of the triac outputs. Because the triacs are ground sourcing and G provides 24V power to the circuit, they can be wired directly to the 2 legs of the relay coil, as shown in Figure 3 below. Using this configuration, the triac is isolated from any harmful current that may travel through the external relay contacts. Figure 3. Wiring Configuration for Relay Control with Triac

Issue When right click on the user account, the Delete choice is grayed out and all Properties textboxes are grayed out. Or, the error message “Access is denied” is displayed when trying to delete or edit the account. Product Line TAC Vista Environment TAC Vista Workstation 5 Cause The account was locked for database protection. The access rights were removed. Resolution Log in Workstation as the administrator Right click on the user account, and select “Authority” Uncheck “Require signature on database object change” and “Protected database object”. NOTE: need to uncheck twice to release those two requests. If the $Administrators is missing or does not have “Full Control (All)” right under "Access Control list", do the following: Under Groups/Users, expend the list,  until find $AdministratorsSelect $Administrator, then click Add. $Administrators should appear under the "Access control list" now with "Read (R)" permission. Select $Administrators under "Access control list". Expend the "Access level" drop down list, and choose Full Control (All). Click Apply, and then click OK. Refresh the window (F5) Now the user account can be deleted or edited.

Issue TGML Graphic Alert: TypeError: Cannot call method "getAttribute" of null (cmd#52) TGML Graphic Alert: TypeError: Cannot call method "setAttribute" of null (cmd#52) Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML file has attempted to perform an action on a null pointer.  Oftentimes this is due to a component being deleted or renamed without realizing that a script elsewhere in the graphic was pointing to it. Resolution Determine which script tag is generating the error. When did the error occur?  When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 52 of the code. The text in quotes tells which method was being used.  In this example "getAttribute."  Investigate what is in the parameters of the getAttribute() function.  Verify that object exists as defined. Edit the script to point to a valid object, rename or restore any deleted object.

Issue Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), while Reports from within Workstation work fine.  Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), and get no Reports folder within Workstation. Login Screen appears as expected, but when attempting to log in with the user name/password; It times out and comes with the message 'Failed to establish connection with server.' Product Line EcoStruxure Building Operation Environment Building Operation WebReports 1.1 / 1.2 Cause The error is most likely due to ports been blocked and/or the incorrect port settings entered during the WebReports installation process. When installing (or upgrading) WebReports, you must enter this information on each occasion as this information is not retained from previous installations. If you need to change these settings, then you should follow the procedure detailed below. Resolution If installed on separate machines, then check the firewall settings and ensure the ports used for the Enterprise Server and the Report Server are not blocked.  If this does not resolve the issue or if you are running both the Enterprise Server and Report Server on the same PC, then the Enterprise Server port configuration during the WebReports installation may need to be changed.  This is achieved as follows: this, and follow these key steps: Run the WebReports Installation setup program, and at the Setup Type prompt, select Upgrade from... Proceed through the other options as normal. Once you reach the Reporting Agent setup, make sure you enter the correct URL (path and port number - this is unique for each installation) used during the Enterprise Server setup. Continue through the other settings as required - Ensure that any Path and URL ports are set correctly.  Once you complete these settings, the WebReports Installer package then goes through the following checks and installation: Checking Installation Requirements Pre-upgrade Configuration Installation of Reporting Agent, WebReports, and WebReports Service Post-Installation Configuration Installation PublishedReports After the above steps, the upgrade is completed. This will now allow login to the WebReports URL using your web browser. For additional assistance in installing/upgrading WebReports, refer to the online help website. 

Issue TGML Graphic Alert:  Unable to cast object of type 'org.mozilla.javascript.UniqueTag' to type 'org.mozilla.javascript.Function'. Product Line TAC Vista Environment Vista Workstation 5 TGML Graphic Cause A script tag somewhere in the TGML graphic file has a function defined in the Behavior attributes that does not have a corresponding function in the script Content or is misspelled in the script. Resolution This error tells you that a script tag in the file has a function defined but not used.  It does not tell you which script tag it is.  The first step is to identify which script tag has the extra function defined.   Click on the script tag.  Look at the Behavior attributes.  Compare the function names defined next to the events with the content of the script.  Click the "..." button next to the Content attribute to open the script editor.       In this example, the event OnDocumentLoad has a function named "load" defined.  But in the content of the script there is no function load defined.   Identify the unused event and delete the function name assigned to that event. If this is not the issue, verify that the function names defined next to the events with the function names declared in the script editor for spelling errors. 

Issue Trying to create a new Filter in I/NET AMT but the icon is grayed out. Trying to create a new Filter in I/NET AMT but Edit>Filters is missing from the menu bar. Environment I/NET Seven Windows XP, Windows Vista, Windows 7 AMT Cause I/NET will not allow you to modify, or apply filters when any of its preset filters are active. This includes Alarm Windows, All Messages, or All Transactions. The Filter Edit icon can only be used when there is an Event Window selected, or there is no window open. Resolution Click on the blue icon to create a New Event  Either add a new event or click on the OK button Once the editor closes, the Filter icon becomes available and it is now possible to create or modify accordingly.

Issue webClient browser will not log on to Single User system, shows "Waiting for ServerName/WebClient/LogOn.aspx" in Internet Root\ " ". Then check out the Workstation (Single User) screen, this will show error message: "The root path name could not be read, the root path name will be set to "Root\ " " See Screenshot: Environment Continuum webClient Single User V1.81 running on Windows XP SP2 Note: This scenario could also occur if a LAN Cyberstation were to be run up on the webClient IIS Server, but this is not a valid installation. Check out the webClient Installation guide on the software CD for valid LAN webClient configurations. Cause As the webClient IIS connections use the Cyberstation software to access the system SQL database, limiting the Cyberstation functionality will stop the additional webClient users from accessing the system. Resolution Ensure any users logged on to a Single user system have full system access or are logged off when connecting using the webClient Browser. Also use the inactivity timer in the User configuration to automatically log off users not active on the system. This issue does not apply to LAN systems where the webClient server is not used as a regular workstation.