Building Automation Knowledge Base

Issue Operating System Selection when using SQL Server Product Line TAC INET Environment I/NET Seven Site Cause Making decisions on operating system selection while using SQL Server 2000 Resolution If your site has grown beyond the capabilities of the Microsoft SQL Desktop Engine (MSDE) as discussed in Customer Advisory CA-2004-04 then you need to decide upon an operating system to use when you upgrade to SQL Server 2000. SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems: Windows Server 2003, Standard Edition Windows Server 2003, Enterprise Edition Windows Server 2003, Datacenter Edition Windows® 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server Source: http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.mspx An option to consider based on the needs of the customer is whether Windows Small Business Server 2003 Premium Edition can meet their needs. This version sells at almost the same cost as SQL Server 2000 (5 CALs), however it includes much more. Windows Small Business Server 2003, Premium Edition includes the following components: Microsoft Windows Server 2003 Microsoft Exchange Server 2003, Standard Edition Microsoft Shared Fax Services Microsoft Office Outlook 2003 Microsoft Windows SharePoint Services 2.0 Health Monitor 2.1 Remote Web Workplace Microsoft Internet Security and Acceleration Server 2000, Standard Edition with Service Pack 1 (SP1) Microsoft SQL Server 2000, Standard Edition with Service Pack 3a (SP3a) Microsoft Office FrontPage 2003 It is important to note that there are some restrictions built into this version of Windows Server 2003. These restrictions limit it to only a single domain solution and can only expand up to 75 users or device connections. Windows Small Business Server restrictions Windows Small Business Server provides a cost-effective suite of programs for small businesses that have 75 or fewer users or devices. To help you prevent unapproved network installations and to help you protect your networks against viruses and other attacks, Microsoft has placed the following restrictions on the use of Windows Small Business Server: You must install all the component server programs in Windows Small Business Server on a single computer. No component may be installed on a separate computer. If you want to run one or more of the component services on a computer other than the Windows Small Business Server-based computer, the other computer requires separate licenses. You can connect a maximum of 75 users or devices to a Windows Small Business Server-based network. This requirement limits the number of users or workstations that can access one or more of the component server programs. Windows Small Business Server is a single-domain solution that is not intended to be integrated with other Windows-based domains. You are not permitted to establish explicit trusts to other Microsoft Windows NT-based domains or to Active Directory directory service domains. Also, Windows Small Business Server does not let you create child domains. The computer that is running Windows Small Business Server must have all operations master roles and must be at the root of the Active Directory forest. The following features that are available in earlier versions of Small Business Server are not available in Windows Small Business Server: Microsoft Shared Modem Service Microsoft Terminal Server Windows Small Business Server supports up to two physical CPUs and up to four virtual CPUs with hyperthreading. Note: Earlier versions of Windows Small Business Server support up to four physical CPUs. You can have other domain controllers and member servers in your Windows Small Business Server-based network. However, the computer that is running Windows Small Business Server must be set up as the root domain controller of an Active Directory forest. This requirement may prevent the computer that is running Windows Small Business Server from serving as a corporate branch office server or as a department server of a large organization that is based on Active Directory or on Microsoft Windows NT 4.0. You cannot add Windows Small Business Server to an existing domain. You must install a Windows Small Business Server-based domain and then add additional domain controllers or member servers to the domain. When you run Exchange 2003 on a Windows Small Business Server-based network, Exchange 2003 cannot be part of a larger Exchange 2003 organization. Because Windows Small Business Server is installed at the root of the Active Directory forest, you cannot install Exchange 2003 components that belong to an existing Exchange 2003 organization. Source: http://support.microsoft.com/default.aspx?scid=kb;en-us;842690 Windows Small Business Server 2003 Premium Edition is a good solution for jobs where the controls contractor will be managing the server operating system that is the core of the BMS.  Many customers today will allow controls contractors to utilize their IP infrastructure but want the system managed and maintained by that same controls contractor.  This software allows that contractor to provide a turn key installation and include all PC hardware and software.  Windows Small Business Server 2003 Premium Edition is also a very cost effective solution for jobs where the specification requires a server operating system or a full version of SQL server that the contractor must provide.  It is recommended that if Windows Small Business Server 2003 Premium Edition is used, any software that is not needed on the server is disabled (i.e. Exchange Server, Fax Services, SharePoint Services).  In conclusion, Windows Small Business Server 2003 Premium Edition is a cost effective way to provide SQL Server at a site if all criteria are met.  Update: If using I/NET 2.40 and above, please check this compatibility matrix for Operating Systems when using SQL Server For other compatibility issues, see Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation.

Issue Can Sigma system controllers sit on multiple VLANs? Product Line Satchwell Sigma Environment Sigma all Ethernet controllers Link Addressing Cause Question by IT departments before upgrading BAS to Sigma systems Resolution You can put Sigma controllers onto different VLANs. But there are considerations: Sigma global data to be passed between controllers on different VLAN's will require Link Addresses to be configured. This is because Sigma globals are transmitted using the Ethernet broadcast address. Typically, most broadcast address messages are blocked by the routers used to link/connect the VLANs. Hence Link Addressing is used to 'tunnel' through the VLAN routers. A DNN will have to be added to each sub-LAN for Link Addressing configuration.  For configuration details click Link Addressing.pdf. All Sigma devices (controllers, Servers and DNN's) will have to be configured with default gateway IP Addresses. For controllers use pocket terminal command GW +  192.168.0.1  (where 192.168.0.1 is the default gateway for the local network) For DNN's set a Static Route as defined in Having set Link Addressing in a Sigma DNN3 can no longer communicate to the DNN3 and Link Addressing does not work. For Sigma servers set the PC default gateway IP address via network settings - Internet Protocol (TCP/IP) - properties. Therefore, although the answer is yes - Sigma controllers are supported on different VLANs, a 'flat' VLAN architecture is a simpler solution.

Issue How to use the Known Occupancy Count (KnownOccupCount) number of an Area in Plain English (PE) programming. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Access Control Cause Need to be able to retrieve the Known Occupancy Count number of an Area for use in Plain English programming for limiting access to an Area. The attribute does not show up in the list of attributes in  the Area Listview. Resolution Even though we can't see the attribute in an Area Listview, you can use the "KnownOccupCount" attribute at the command line or in Plain English programs. Example 1 - Print Known Occupancy Count to command line. print AreaFolder\Area1 KnownOccupCount Example 2 - In a Workstations Program, set a pre-defined AnalogValue to the Known Occupancy Count of an Area. Area1KnownCount = AreaFolder\Area1 KnownOccupCount Note: The Known Occupancy Count will not function with Entry only doors. Both Entry and Exit readers are required on the doors within the Area. See Known Occupancy Count number does not increase when Personnel enter the Area on this.

Issue Cannot get comms stats from the DNN or controllers below the DNN. Product Line Satchwell Sigma Environment Sigma Communication DNN RIP Listener Windows XP Persistent routes Cause The Sigma server 'learns' the network architecture by listening to RIP messages broadcast by the network DNN's.   This is performed by RIP Listener which by default is not enabled on Windows XP. Resolution Enable RIP Listener on the Sigma Windows XP server by; In Control Panel select 'Add or Remove Programs' From the left hand bar select 'Add/Remove Windows Components' Highlight 'Network services' and select 'Details' Enable 'RIP Listener'   Select 'Next' and then 'Finish' OR Add persistent routes as an addition to RIP Listener as a backup or if RIP v1 is not permitted on the system see Persistent routing on the Sigma server. Use the DOS Command ROUTE PRINT to list the dynamic and persistent routes, check that the gateway address and network addresses are correct.

Issue Ordering, installing, wiring of CLX LAN Expansion board. Product Line TAC INET Environment I/SITE 7798 CLX Cause There is not any CLX-specific installation guides or manuals. This article is intended to give some basic information about the expansion board and its use. Resolution Part number: CLX Part name: LAN Expansion Option for RS-485 Part description: I/SITE Expansion Board - adds controller LAN communications to network other controllers to 7728 & 7798 - RS-485 CE/EMC Compliant Comments: Plugs on to 7798 base unit, RS-485: 19,200 or 9600 baud, SDLC, token-passing. Wiring: Terminals 1 and 2 on the CLX are Controller LAN +,- respectively. For more information on installing the CLX expansion, see CLX Expansion Card for 7798B .

Issue Controllers IP address needs to be changed but any attempt to do so results in the IP address reverting back to what it was previously configured for. Product Line Andover Continuum Environment Continuum CX9702 BCX controllers NC2 controllers ACX57xx controllers Cause The Controller has hit the Flash writes circuit breaker and is no longer able to save any changes to Flash. This includes updating Device settings such as IP address and ACC Node ID. The controller error log may also contain an error similar to below when attempting to make any such changes.   10/08/2014 19:00:22.00 0x00004406         0x03b76100        0x0004cb68         0x003e2000        0x000007d1                                         DEVICE_ERR_ERASE_LIMIT      (Flash circuit breaker tripped. CX97XX code base) Resolution One of the two methods to reset the Flash circuit breaker listed below should then allow the controller to write to Flash again.   1. accstatusbackup = accbackupenable   For more information see Caution when using PE programs to perform an automatic flash backup on a controller.     2. INFFlashDisabled.   Create a numeric in the controller with the following name and alias:   INFFlashDisabled   A value  greater than 0 usually indicates that the flash circuit breaker had tripped, though in some cases you may find these errors occurring when INFFlashDisabled = 0. In either case, once the value of this numeric is set to 0 and applied,  the flash circuit breaker errors should stop.

Issue Where can I obtain the technical information, manuals, guides or other documents on Continuum? (or other product lines) Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Continuum Cause Manuals and documentation can be used for training or self-help troubleshooting for Continuum. (or other product lines) Resolution Review the course notes The notes and document gathered during training can be very useful and a great source of information. Technical Documentation is available on the EcoBuilding Download site at: https://ecobuilding.schneider-electric.com/ For technical data/PDFs installed with Continuum, Go to Start > All Programs > Continuum > Documentation The discs and downloaded zip files that are used to install Continuum also include technical PDFs. Some of these are installed when Continuum is installed. (CONTINUUM) Most of the online help is context based, thus if you click help within a InfinityNumeric, then InfinityNumeric help is given. This help file can also be searched in the normal way. It is an excellent source of information. (CONTINUUM) Bookmark this Knowledge Base:  https://community.se.com/t5/Knowledge-Base/tkb-p/knowledge-base_public New articles are added daily and should be used as a first stop for self help. The Exchange Community site has a community space just for Continuum, SmartStuxure, Sigma, Vista etc.  for posing questions, sharing solutions, https://community.se.com/ (CONTINUUM) The Continuum catalogue also provides a good overview of the product range Some documentation is freely accessible, see https://www.schneider-electric.com/en/work/products/building-automation-and-control.jsp If an end user has problems on site, they should first contact Schneider Electric local support or service department (In the UK contact Support Bureau 0870 606 2800, cs.bureau@uk.schneider-electric.com) SmartStruxure For Building Operation help can be found online at: http://help.sbo.schneider-electric.com/home/index.castle?locale=en-US&productversion=1.8   CONTINUUM ONLY Always ensure the site fits within the Continuum Compatibility Matrix, this includes:  For PC requirements see the relevant Installation Instructions included with the Continuum Software Controller firmware (Continuum, BACnet, Infinet), use the most up to date available (of the correct version) Workstation operating systems, service packs and .NET framework versions SQL versions See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for other system data The Continuum.chm file found in the Continuum directory include the "online help" It is usually worth ensuring the latest Continuum service pack is applied to ALL workstations on site (Cyberstation and WebClient) Click Here

Issue Steps in obtaining a Return Authorization (RA) number for a defective Niagara R2 UNC. Product Line TAC IA Series Environment Niagara R2 UNC Cause Failed unit requires repair or replacement. Resolution Before calling Customer Service for a Return Authorization, review the following steps to ensure the unit needs to be sent back to the factory. Symptom: Unit has a constant / steady heartbeat LED A UNC with a steady heartbeat LED indicates that the unit is not booting to the operating system. If a power cycle does not correct, there is not a way to recover without repairing with the factory fixtures. The only alternative is to provide a return authorization for repair or replacement. UPDATE: There are some issues that have been identified since this article was originally published that are field repairable.  To identify these field repairable issues, connect the serial console (see Need to correct invalid IP address or subnet mask entered into a UNC 520), power cycle the UNC and capture the console output.  Provide the console output information when you contact Product Support. Symptom:  Unit has a rapid heartbeat A rapid heartbeat typically indicates a memory issue.  During shipping the memory card has been known to have shifted in its socket. Power the unit down and remove then reseat the memory card in the UNC several times and then power up and monitor. Symptom: Unit is continuously rebooting In a new unit, this continuous rebooting could be a memory issue.  During shipping the memory card has been known to have shifted in its socket. Power the unit down and reseat the memory card in the UNC several times and then power up and monitor. Typically, if the fuse is bad you would see a watchdog or battery failure in the standard output window every 15 minutes or so. The fuse in the UNC-410 and UNC-520 is soldered into the board and is not field replaceable. The UNC-510 fuses are field replaceable.  Remove the shield from the UNC enclosure and remove the board from the shield. The main fuse (F1) is a 5 X 20 mm Fast Acting 1.5 amp 250 volt (Bussman GMA-1.5). The battery fuse is a 5 X 20 mm Slow Blow 2.0 amp 250 volt (Bussman GMD-2A). The battery fuse is the fuse on the right when the power connector is oriented to the upper right. Both fuses are labeled on the circuit board legend. The control board tests the battery’s charge every 5 minutes by placing a momentary short across the battery and monitoring its recovery. A failing battery will cause the unit to reset and reboot when self- tested. Remove the battery red wire and if the unit continues to operate, replace the battery. To test the battery, disconnect the battery and measure the voltage across its terminals with a voltmeter. It should read above 12 Vdc. The charging circuit in all UNCs usually provides a voltage of 13.5 Vdc (approximately).   Replacement battery, part number UNC-500-BAT. Notes: UNC will power itself down within 5 minutes after the power fails. The battery will retain the clock and other dynamic memory data for about 12 hours. A fully discharged battery will recharge in about 12 hours. The life of a battery is 3 to 5 years under normal conditions. Excessive discharge cycles or operation at high ambient temperature (>122F) will shorten the life of the battery. UPDATE: There are some additional issues that have been identified since this article was originally published can cause the UNC to continuously execute a Watchdog Reset and become disabled. See I/A Series R2 (Niagara) station opened in the Admin Tool displays "Disabled"), for more information on this issue. Symptom: AC power failure or Transformer problem The UNC-410 and UNC-520 have an internal transformer. The transformer voltage and wiring should be verified before returning the unit.. This is a center-tap transformer and is wired to the first three terminals on the circuit board connector.  The wires, top to bottom, should be Green, Green Yellow, and Green respectively. The voltage should read approximately 30 VAC Green to Green and approximately half the value (15 VAC) between either Green wire to the Green Yellow wire. Returning unit for repair The symptoms above are a sample of common, sometimes field repairable, failures in a UNC. If the UNC-410 or UNC-520 needs to be sent to the factory for repair, you will only need to return the circuit board (UNC-410-500 or UNC-520-500), not the entire UNC. The printed circuit assembly will be exchanged or repaired and returned. The repaired UNC will come with a 3 month warranty. To issue a Return Authorization (RA#) the factory will need to know the following information: The product part number Is the unit still under warranty? Warranty note: Warranty on a new UNC is 2 years from date of manufacture. The date code format is yyww. Example:  0815 is  2008 week 15 Serial number Job name (site name for unit) Factory order number Project ID Host ID (in the license file) The reason for return Network settings (IP, Subnet, name) Username and Password Station DB Username and Password Any special shipping instructions Have a purchase order number ready when you call. Note: Customer Support Services sends/bills for advance warranty replacement units. When the customer returns the correct unit within 30 days, a credit is then issued., Call Schneider-Electric at 888-444-1311 and select option 2 (Product Support). Product Support will enter a support case identifying the unit and that an attempt to troubleshoot was done prior to issuing the RA number. The caller should request the Product Support Case number and RA number for future reference. An RA will be issued based on the following criteria: Credit AWR (Advance Warranty Replacement). Customer is sending back an inoperable unit to the factory for credit and needs a replacement unit right away. OOWR&R (Out of Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. IWR&R (In Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. NOTE: When issuing an AWR, hold the defective unit and use the packaging from the replacement to return the UNC board. This will help guarantee that the units are not damaged during shipment. When the units are received damaged and improperly packed, they are returned as received and no credit issued. Ship the device to: Schneider Electric 1354 Clifford Ave.   Dock 3 Loves Park, IL. 61111 Attn: Repair Dept. RA ###### Put the RA # on the outside of the box. Include your return address in the box.

Issue After a power failure, the Automation Server has a designed procedure to restore script programs in to a particular state. This process should be taken in to consideration when designing the system.  Product Line EcoStruxure Building Operation Environment Automation Server Cause Automation Server loses power and restarts, unsure where script programs will start from once the Automation Server comes back online. Due to the onboard "super cap" saving the database to flash on power loss, are the last script program line and variable values retained for when the Automation Server starts back up? Resolution The Automation Server saves it's current active database to flash before losing power completely, the super cap has enough power for it to do this one last task before the Automation Server loses power completely. See AS Power supply interruption or failure on how this is accomplished. On startup from power fail, any script Programs in the Automation Server will start scanning at the first program line. Make sure to keep this in mind and write your programs so that the first line sets your control values to the default "safe" value before moving on to further control logic.

Issue SigmaX was installed but will not open. Sigma will not seat a client and BAS 2800+ is looking for a dongle. Product Line Satchwell Sigma Environment Sigma SigmaX BAS 2800+ tools Cause SigmaX requires an unlocking code. Resolution SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded.   With the release of SigmaX 7.0.9 the following procedure is no longer required and will not be available in 2017 If you are a Schneider Electric employee you register your PCID number via Lotus Notes, or use the SigmaX Registration Portal if you do not have Lotus Notes. Finding PCID: The SigmaX PCID number for your SigmaX installation is provided by running t.he "RegSigmaX.exe" program (C). The "RegSigmaX.exe" program (B) is located under "C:\SigmaX\Bin" (A).     For Schneider Electric employees with Lotus Notes The engineer must be on the Schneider Electric network via VPN or office to be able to follow the steps below. From the Lotus Notes client, From the top menu, choose File then Application or Ctrl + O to bring up the Open application dialog box.   Click on the down arrow to the right of "Look in:" text area and choose AAGB0010.GB.Schneider-Electric.com/A/SVR/Schneider from the list.  If it doesn't exist, then either type it in or select another server and modify the entry. The list in the scrollable window should look like the picture above.  Scroll down the list until you see a directory called "apps".   Double click on this entry.  Scroll down the new list until you see "Sigma X Registration 2015" Select the entry and then click on Bookmark.  From the next dialog box, choose "Bookmark bar" from the "Add to" list. See below.     will appear in their bookmark bar or Open list.  To access the application, click on the icon.     For partners and Schneider Electric employees without Lotus Notes 1. Go to https://sigmaxregistration.schneider-electric.com to register all new SigmaX code   2. Log in If you do not have access you will need to register using one of the options provided on the landing page If you do not know your access details, you will need to communicate with your local sales representative   3. From the left hand side, select "Sigma Registration"   4. Click "Continue" to continue to the registration page   5. Enter the information required A - Check the correct name is displayed. B - Check the correct email address is shown, edit the address if it is incorrect. (The unlocking code will be sent to this email address) C - Enter your office region. D - Add the product identity number. E/F - Select whether the unlocking being requested is either an addition or a replacement. G - You can leave a comment regarding the request. H - Submit the request.   Once your unlocking code has been approved (normally within the hour), you will receive an email with your new unlocking code. Once you have registered your PCID number, you should receive an email each December with the next year’s unlocking code. Download the instructions as PDF

Issue The STR-250 will not respond to any input and the display is incorrect, typically flashing random characters or 00. During this behavior the Xenta 102-AX will remain offline and unresponsive, no longer controlling room temperature. Product Line TAC Vista Environment Xenta 102-AX STR-250 Cause A firmware error has been identified in the TAC Xenta 102-AX (and 102-AX-U8) version 2.14, when they are used together with STR-250, the LCD version of STAT. A certain sequence of key strokes will cause the Xenta 102-AX to lock up. A firmware upgrade is available. Until that has been downloaded a power cycle will in most cases recover the controller. See the full TPA-MALR-10-0004.00. Resolution The 102-AX Firmware error is fixed in version 2.16 and later. Instructions on how to properly upgrade the 102-AX are located here: Upgrading a Xenta 102-AX to version 2.16 or later

Issue Essex Pin Pad Reader Programming in I/Net Seven. Product Line TAC INET Environment Any Windows OS Version and I/Net Seven Version Cause Need to program an Essex Pin Pad reader in I/Net Seven. Resolution Here is the link to programming the Essex Pin Pad Reader Essex Pin Pad requires the site is not using Large Numbers The Essex Pin Pad is for site which wish to use Pin only for entry. Not Pox Card + Pin or Prox only. For information on a Prox card access which includes Pin Pad see HID PIN Pad reader for I/NET Part Number. For a higher security Pin Only option comparable to the Essex see Code-Guard Scramble Pin Pad Reader Programming.

Issue Need to protect Continuum Workstations from Virus and Malware threats. Product Line Andover Continuum Environment Continuum Workstation Cause There are many Anti Virus applications on the market, how to choose which one to use on a Continuum Workstation machine. Resolution We do not qualify any specific Anti Virus applications or definitions for use with Continuum software. You can use whatever Anti Virus you want on the machine Continuum is installed on as long as Continuum was installed when that Anti Virus was disabled as this can hinder files from being copied, dll's from being registered, and registry entries from being created / modified. If there are conflicts with Continuum and the specific Anti Virus application being used, you may need to add the Continuum folder and / or the Continuum processes to the exclusion lists. For details on specific environments that have been qualified with Continuum see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue Installing I/NET on a PC using MSDE and MSDE won't start. Product Line TAC INET Environment I/NET Version 2.40 and above Windows 7 MSDE Cause MSDE does not run on Windows 7. Resolution If the user has attempted this, more than likely the OS has corrupted SQL. There are a couple of things that can be done as described in Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL. However to return the PC to its original state the best bet would be to reinstall the OS, or a backup prior to the installation of I/NET.

Issue During Vista Installation, receive error message “SQL server service cannot be started” or "Failed to start SQL Server service!". Product Line TAC Vista Environment TAC Vista 5.X.X (Tested on Windows XP SP3 with SQL server 2005 EXPRESS) Cause This issue typically happens after uninstall an earlier version of Vista, and then install a newer version of Vista with the built in SQL server (SQL server 2005 express). Sometimes the SQL server registry key is remained on the computer during the uninstall process. When new installation happens, Vista thinks there is an existing SQL sever; however a failure will occur when try to start the SQL Server service. Resolution It is recommended to use the installation file to uninstall TAC Vista 5.X.X. Follow How to uninstall and completely remove TAC Vista 5 to make sure all files and folders are removed.   Check if SQL Server Service still exists: Right click on “My Computer” and choose “Manage”. Chose “Services and Applications" -> "Services". Check if “SQL Server (TACVISTA)” is listed, if yes, go to next step. Otherwise, restart the computer then run the installation again, issue should be solved now.    Go to “start->Run->regedit” to open “Registry Editor”.   Go to “HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/”. Find “MSSQL$TACVISTA” and “MSSQLServerADHelper”. Then delete both registry folders.   Repeat step 4 for “CurrentControlSet001” and “CurrentControlSet003” under “HKEY_LOCAL_MACHINE/SYSTEM/.   Restart computer and run the installation again. Issue should be solved now.

Issue Error Codes: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Product Line Andover Continuum Environment Continuum Site with BCX Controllers and an Error Log Cause Crash of BCX and log reveals: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1629 E 04/05/2012 10:51:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000 Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1630 E 04/05/2012 10:53:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Resolution It is in the range of “Global System errors” that is usually not good, either faulty controller or need reloading of the O/S. Cold start and update O/S with the latest version supported by the Cyberstation version. Then run it on a test rig with different ID and see if it still crashes, if so will need to be repaired or replaced.

Issue The B0cfglog.txt file located in the Vista database $log folder and Alarms in Vista are getting the error: Physical unit "Unit Name" on node "Node Name" is a duplicate by uid=### with "Unit Name" on node "Node Name" Product Line TAC Vista Environment Noded Vista Server Master / Slave Vista Cause Conflicting UID in a Master/Slave node network. Master Vista Server or Master. In a Vista network/system containing several Vista Servers, one of the Vista Servers is the Master Vista Server, managing and communicating system-specific information and global settings throughout the Vista network/system. Slave Vista Server or Slave. The Slave Vista Servers in a Vista system receive system-specific information and global settings from the Master in the Vista network/system. If once standalone servers are all added to one Master network, the Master assigns a unique ID to each slave. Normally when a UID gets duplicated the master tells the servers correct the duplication. Sometimes this automated fix cannot occur because the duplication prevents the proper communication. In this case, the slaves need to re-establish communication with each other and be restarted. Resolution Delete the slaved node Update Vista to reflect the node is removed Adding the node back Restart Vista Server The UID should be resolved and the error should not be present.  If the error still comes up please try the following steps: Make current backups of all Vista Databases Close the slave server Open the mater server When asked, "Do you want to change identities on this node?" select Yes Close the master server and reopen both the mater and the salve server and the error should be gone Instructions on how to add the Vista Slave node onto the master can be found in Creating TAC Vista multi-server network. For this to work, the slaves need to be able to see each other as well. If you do not want the slaves to see each other, add them while balancing the load on the network. They can later be removed when the problem is not occurring anymore. 

Issue "No license available" message appears some while after having logged in to Webstation. Product Line TAC Vista Environment Vista 5.1.6 Windows 2008 Server Internet Information Services (IIS) IIS 7.0 or higher Cause This is most likely due to a corrupt IIS installation. Resolution Reinstall IIS Reinstall Webstation The steps for this are outlined in Problems installing Vista Webstation 5.1.5 or newer.

Issue Are Standard and Enterprise Editions of Windows Operating Systems supported for use with Continuum / WebClient Software? Product Line Andover Continuum Environment Continuum Cyberstation Continuum WebClient Continuum SQL Server Cause The Compatibility Matrix does not stipulate if the supported Operating Systems are Standard or Enterprise editions. Resolution You can use either Enterprise or Standard Editions of the various supported Operating Systems with Continuum / WebClient. See Software and Firmware compatibility matrix for older versions of the traditional product lines for the current Compatibility Matrix showing supported Operating Systems.

Issue The user logged into Windows doesn't have permissions to the folder that contains the Continuum.mnu file,  the file is set to read only or the path in the continuum.mnu is incorrect. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Permissions are restricted to the Continuum.mnu file or the path in it is incorrect. Resolution One of the follow solutions will resolve this: Click to download an edited default path Continuum.mnu and Menu.bmp  (links for the default path C:\Program Files (x86)\Continuum) Copy these files to each workstation that has an incorrect path Manually edit the file yourself if you have a path that is other than (C:\Program Files (x86)\Continuum) Grant permissions to the folder. The folder that contains the Continuum.mnu can be located by editing the Cyberstation in Continuum Explorer. WS Edit> Preferences tab> The file name of the main menu  Ex. c:\program files\continuum\userprofile\continuum.mnu Right click on Continuum.mnu and select properties. Deselect Read Only if it is selected. Change the path to the Continuum.mnu file to a folder that you have access to and copy the continuum.mnu to it. Ex. c:\program files\continuum\continuum.mnu While in edit mode, right click on each of the buttons and select Properties Use the browse button to select the correct x86 path (C:\Program Files (x86)\Continuum) Repeat this for each of the buttons and then save the Continuum.mnu file Copy these files to each workstation that has an incorrect path Also see Continuum.mnu file with C:\program files (x86) on 64 bit PCs points to C:\program Files and shows a blank screen.