Issue After installing Continuum Service Pack 1 2 and three for Continuum 1.62, received Error in Processing Bytecode when running the import/export fixup utility. Environment Continuum 1.62 WebClient 1.62 Cause Continuum Service Packs SP1, SP2 and SP3 were installed without updating the database using Database Initialization after each installation. Resolution Always read the release notes that are included with Continuum Service Packs.  The release notes provide information on how to properly install the service pack. In order to correct this issue follow this procedure. Backup the Continuum Database. Archive Continuum User profiles. Archive all pin files. Archive all graphic background files. Run Database Initialization and update the database. Install Service Pack 1 per the instructions in the release notes. Run Database Initialization and update the database. Install Service Pack 2 per the instructions in the release notes. Run Database Initialization and update the database. Install Service Pack 3 per the instructions in the release notes. Run Database Initialization and update the database.

Issue Using the "TemplateName" and "TemplateAlias" attributes in a ListView, does not show the attached Personnel Template. Environment Continuum Cyberstation Cause Not using the attribute "RefTemplate" to view attached Personnel Templates. Resolution  Use the attribute "RefTemplate". This is the Personnel's referenced template and is the field used to link to the template. Open the Personnel ListView where you want to view the attached template. Select View-> ListView Configuration. On the columns tab select "Add Column". Select attribute field and from the drop down list select "RefTemplate" Save Listview and re-run. It now shows the attached templates in the RefTemplate field.

Issue When a Vista trend is added manually or using the Trend Wizard on completion of the process the error massage  "Invalid Entrance" is displayed. Environment Vista 5.0.3 and Windows Server 2003. Vista Master and Slave configuration. Cause The trend is being added in the Master Vista Server and the point is in a Slave Vista database. Resolution To add a Vista trend log of a point residing in a Slave Vista sever use the following steps. Log onto the Vista Slave server. Add a new or use an existing directory (ensure this folder is visible to the Vista Master Server) that has been created on the Vista Slave. Add your Vista trend either using the trend wizard or manually.

Issue The AccessEventSize system variable determines the number of events to retain in a controller when it goes offline, what is the largest value you can enter? Environment Access Control systems using the Netcontroller II (9680) and ACX57xx (5740, 5720) Cause When designing an access control system, it is often required to know how many access events a controller will retain if the network connection to the workstations is lost. Resolution There is no fixed maximum number you can enter in the EventLogSize, it is dependent on the available free memory in the controller (Freemem). Typically you should have enough available memory be able to enter a maximum value between 100,000 and 170,000, but this will use up the majority of the controllers available memory. This may be OK if you are only doing Access control with the controller, but if you are also doing: BMS functions then you may have requirements to store logged data for temperatures etc.  Or you may be using X Drivers with thousands of numeric points           These would all use up the free memory and may only allow you to hold a few thousand events.  You have the flexibility to set the value, but the controller will not allow you to enter values that would exceed its available memory.

Issue Is it possible to set a delay on a change of state object in Vista? Environment TAC Vista 5.1.5 Cause Need to set a delay on a change of state object in Vista Resolution No it is not possible.

Issue The Plain English editing environment is made up of several windows that can be moved, closed, resized and generally re-arranged, it may be required to restore the default settings. Environment Cyberstation Workstation all versions. Cause The various windows in the editor may have been closed or shrunk down to a size that can not be found, or moved out of the viewable area so they can not be moved back to the regular positions. It is also possible that the initialization file has been corrupted. Resolution Stop the Continuum workstation  Find the PlainEnglish.ini file in the C:\Windows directory, this file holds the last setting of your Plain English editor environment. Delete the PlainEnglish.ini  file. Start up Cyberstation, log in. Open the PE editor this will create a new file and use the default settings for all window positions.  

Issue Vista Change of State object  monitoring an I/NET point value are in Alarm  but not changing state or getting through to Vista Alarm queue. Environment I/NET point monitoring Vista Alarm Queue Xenta Server Alarms I2V Cause Incorrect settings of the I/NET point Watch Status, and Vista Change of State object. Resolution There are a few settings unique to I/NET points that have to be properly modified in order for an Alarm to be passed into the Vista Workstation Alarm queue. In Workstation, navigate from your Xenta Server to the input/output point generating the Alarm in I/NET. Right click on the point and select Properties.  Set the Watch Setting to "Alarm". Navigate to the Change of State object that is referencing the I/NET point to create the alarm. Right click on the Change of State object and select properties. Set the Alarm triggering text field to the value expected in alarm condition, i.e. 1. Set the Alarm resetting text field to the value expected in back to normal, i.e. 0. Toggle the I/NET point manually into alarm and return to normal once to verify the alarm is in the queue.

Issue Alarm delivery server window popping up Environment Continuum Cyberstation 1.91 Cause Alarm delivery server window popping up Resolution Updated OS and applied all the current updates. The issue resolved after the updates

Issue Global Point Settings for DLA systems Global / Indirect Points connected over Ethernet continue to report "old data" Environment I/NET Cause When converting to DLA, a router is now between Global and indirect points that may be on the same link. The router will block any message that does not have a global level of "System" The NetPlus Routers (NPR) must have their reference hosts set correctly so that all IP devices know each other exists.  Resolution Connect to each global point on each link or DLA site. Modify each point so that its global point level is "System" If the global points are still not functional, follow this procedure: Modify the Reference host table on each device to point to one master (NPR or Workstation) Reset power on each device to request the routing table Restart the I/O server on the host machine

Issue Deny Entry Tenant when entering new badges after restoring from a system crash on a New Host workstation Environment I/NET Cause Devices in the field may still be looking for the former workstation due to a system setting such as automatic DPU restore. Resolution Connect to the controller Select Edit>Controller>Station Save Select Edit>Controller>Station Restore Select The DPU option Select the affected DPU and click okay Try a badge to verify results This error should only occur when badges are added immediately after a system recovery.  If the issue continues, contact product support.

Issue Go to templates folder Drag Event Enrollment to controller to create a new event enrollment It prompts for event notification and point reference and enrollment looks fine. When alarm is tested the event notification does not work and indicates fault. Environment Continuum BCX40xx B3 B4920 Cause A Send to Database was not performed on the controller in the BACnet side of the Continuum Object Tree. Resolution When objects are added or modified on the Infinity side of Continuum's Object Tree, the changes do not take affect in the controller until a Send to Database is performed on the controller from the BACnet portion of Continuum Explorer Object Tree.

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue MN-CI revision 4.1 returns an error 511 when sending a “Reset” command to a MicroNet 2000 controller. The controller does reset as commanded. Environment MN-CI rev. 4.1 software, MN-FLO, MN-FLO3T, MN-HPFC Cause The problem is caused because MN-CI rev. 4.1 sends the “Reset” command twice, and temporarily loses communications with the controller. Resolution The error is considered a nuisance and can be ignored.

Issue When accessing the VEO group of an LCM or GCM with XPSI revision 4.1 Terminal Mode, the data is displayed normally for about 90 seconds before it starts to become garbled. The problem begins at the top line of the display and progresses from the top down, one line at a time.   The arrow keys are not operable, cannot move the cursor to select attributes. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Unknown Resolution A work-around is to use a different terminal emulator instead of XPSI revision 4.1; possible alternatives are HyperTerminal or PuTTy.  PuTTY.exe can be downloaded at http://www.putty.org/.  Select putty.exe for Windows on Intel x86.

Issue In XPSI 4.1 Terminal Mode, there is a noticeable delay in the action of the “Escape” key when backing out of a Current Status or VEO group display screen. Environment XPSI rev 4.1, Windows XP SP3, Windows Vista Pro, Network 8000 GCM, Network 8000 LCM Cause Serial communications are slower with the Microsoft port controls used with XPSI version 4.1. Resolution The “Escape” key will work, it just takes a few seconds longer in version 4.1 than it did in earlier versions, such as 3.13.

Issue The customer can log off of Continuum, but he can't shut down Continuum. Environment CyberStation WebClient Cause Permission to exit Continuum has not been granted to the Continuum User. Resolution Right click on the Continuum icon in the Windows Active Icon tray Select Security Navigate to the appropriate object class or folder.  In this case navigate to the Miscellaneous folder. Look for the row named Terminate Continuum. Move left horizontally along the row until you get to the icon associated with the user group you wish to grant the permission to.  (The user group indicator will appears when the arrow is over each lock or key icon). If there is a lock icon, the permission is currently denied.  Click on the lock and the icon changes to a key.  The permission is now granted. Log Off of Continuum and log on with a user from the modified user group to test the permissions. NOTE:  There are cases when multiple permissions must be granted to allow a user to access specific functions.  For example, you can grant a user permission to reload a controller, but he will not be able to do so unless you have granted him access to launch Continuum Explorer.

Issue Attempting to access the infinet service tool using a bluetooth connection gives an "unable to wake up roamIO" error.  The bluetooth device was successfully paired with the laptop and the port has been changed to match this port in the infinet service tool preferences, but the device will not connect with the infinet service tool. Environment Infinet Service Tool Windows XP Windows Server 2003 Windows Server 2008 Roam IO2 Cause Unable to establish bluetooth connection with the Infinet Service Tool Resolution Upgrade the infinet service tool version to 1.1 Use a version of the bluetooth software for the laptop or PDA that allows specific configuration of the comm port in order to assign it to a port that is less than 9. Note: The 1.1 version of the infinet service tool allows for comm ports greater than 9 (i.e. comm39), but earlier versions would only allow up to comm9.  Some versions of the laptop bluetooth software differ allowing configuration of the bluetooth comm ports to a lower comm number.

Issue Having trouble Linking to a File from a TMGL Graphics page in Vista Workstation Environment TGML Vista Workstation Cause Most likely cause is not using the correct button type or script feature.  Below is the most basic means to link to a file. Resolution Add the "FileButton" object found in the Basic Controls Component Library to the TMGL file Select the object In the Properties Window, scroll down to the heading "Custom" and the property "File" Type in the complete path and filename. Example C:\Vista_Files\TGML.pdf Save the TGML graphics page Test the link in Vista workstation

Issue User limitations in a Xenta Server Environment Xenta Server Cause Setting up User rights on a Xenta Server Resolution Web Users: Web Users are created only from the Web Interface, not XBuilder The limitation on web users is based only on available controller memory A normal user should use less than 100 bytes Excess numbers of users will limit your potential use of controller memory Simultaneous Users: In XBuilder, click on the Xenta Server object Scroll down to TCP/IP Settings and select "Max. number of HTTP sessions" the default if 15, but this number can be modified to between 10 and 20 users. FTP Users: In XBuilder, click on the Xenta Server object Scroll down to FTP settings and select "Max Users" The default number is 4, and the maximum is 5 users.

Issue Get the following error message when trying to access TAC Vista Webstation on a Windows 2008 server: HTTP Error 500.22 - Internal Server Error An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode. Environment Vista 5.1.5 Windows 2008 server Webstation 5.1.5 Cause TAC Vista webstation can not handle "Managed Pipeline Mode" integrated for the application pool in the IIS. Resolution Open IIS Click on Application Pool For the Application pool used by Vista webstation set it to "Classic" instead of "Managed Pipeline Mode"