Issue Is there a limitation to the size the database can be on a Single User system in Continuum? Product Line Andover Continuum Environment Single User Continuum system MSDE database Cause Microsoft has put a limitation in the size of the MSDE database. Once you hit this limitation your Single User Continuum system will not operate properly. Resolution The size limitation is 2 Gb. It may be possible to recover after hitting this limit by removing un-needed log entries from the database, but this is not always a guarantee you will be able to recover the database. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation. From this point you can remove any unwanted logs and shrink the database. Then you can back up the database and restore it back to the Single User system. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation and convert the Single User system to a LAN installation. Finally if all the above do not work for your system you will have to restore from the last known good backup of the database. See Microsoft Database size Limitations and Continuum for SQL Express information.

Issue How to disable credential access on Doors at different controllers using a single variable. Product Line Andover Continuum Environment Continuum Access Control Cause Require a method of securing multiple Doors at the same time. Resolution The best way to secure a number of Doors from a single variable is to use the Door Force Lock Schedule attribute in the Door object. This is accomplished by adding a numeric to the attribute on the Options tab of the Door object; IMPORTANT: The attribute name Door Force Lock is misleading, it DOES NOT lock the door in any way, all it does is disable credential access at the door. For Area/Door Lockdown refer to the linked KB article And also on the Entry Reader or Exit Reader tabs, ticking the checkbox under either Normal and/or Comm Fail for Door Forced Lock Schedule. Setting this Door Force Lock Schedule field to a local or remote InfinityNumeric point will provide the following conditions: When the Numeric is on, access is permitted to all personnel by card swipe and/or keypad entry. (Allow use of the door.) When the Numeric is off, card reader and keypad access are denied to all personnel. (No Access) You could have this numeric located in a central controller and all the rest of the controllers reference this numeric from the Door objects. No other points or plain English is required. If you want to ensure that the updates are received, you can force the IE entry for this numeric to update on a regular interval, see Use just one schedule to control doors or access to areas across different controllers that discusses how to accomplish this.  

Issue How to do alarm escalation in Continuum? Product Line Andover Continuum Environment PEAlmFunction, PERtnFunction Cyberstation Alarm Workstation PE function Cause The customer requires the ability to time how long an alarm is active, and based on its status (acknowledged-unacknowledged), escalate the active alarm, by email or other means. Should the alarm be acknowledged in time, the escalation does not occur. Resolution One method is to use the PEAlmFunction and PERtnFunction in a Workstation Program to capture the various alarm conditions off the alarm stack to trigger the activity that you want. As an example, the PEAlmFunction could be used to initiate a timer for the alarm by recording the time of the alarm and the alarm point. The PERtnFunction is then used to clear this recorded information if the alarm is acknowledged. A Workstation program is then used to constantly monitor this alarm information and comparing the recorded alarm time to the current time, if this is above the escalation time then a numeric is set to trigger another alarm that is then escalated. For details on how to configure the PEAlmFunction and PERtnFunction, consult Can Plain English interact with the Continuum Alarm Engine?

Issue Database initialization completes with errors Product Line Andover Continuum Environment Cyberstation installation Cause When running database initialization you will need full access to all of the database. Otherwise you may see errors similar to the following: Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]The SELECT permission was denied on the object 'syscategories', database 'msdb', schema 'dbo'.> Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the procedure 'dt_IsColumnDifferent', because it does not exist or you do not have permission.>   Resolution Ensure that the Andover97 account has DBO privilege to the ContinuumDB, if not run the "Change DB Owner" query to restore Andover97 as the DBO, see Unable to Initialize Continuum Database following installing no SQL instance.   The above errors relate to setting up the SQL Server Agent Jobs that are held in the MSDB part of the database. Check that Andover97 does have the user mapping to this part of the database as per the following screenshot:     Also ensure your Windows User account has the required Administrator privileges to allow full access to the SQL database and its files.

Issue MFC errors when starting or running Cyberstation or Webclient Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Windows 10 Windows Server 2012 Cause Microsoft Function Class (MFC) errors are typically caused by missing, damaged or altered files that an application is looking for and is having problems using. Resolution There can be a number of reason why MFC errors are being received. Here are a few causes related to Cyberstation startup. Check the Continuum compatibility matrix. If you are using a version of Windows Operating System that has not been qualified for a specific version (i.e. Windows XP SP2 with 1.93) then this can cause MFC errors. Viruses and Malware can also affect MFC files. Be sure to run both types of scans on Cyberstation, but this should be done after the Cyberstation or Webclient PC has been installed. If these types of products are active during an install, they can flag some of the files that would normally get installed as suspect and cause problems with the operation of Cyberstation even if it appeared that the installation was successful. Removing Continuum, rebooting, running scans and then disabling the active scans at the time of the Cyberstation install will often resolve these issues. Windows XP, Vista and Windows7 have restore points that you can sometimes go back to in order to restore to a point earlier where the MFC errors were not happening. As a last resort, you may need to reformat the hard drive on the PC, reinstall the Windows Operating System including the appropriate service packs and hotfixes and then install Cyberstation or Webclient. Links to other MFC related articles: MFC errors on Continuum startup after moving a database to another PC MFC error on Continuum startup or Continuum won't start on HP PC Running a listview is giving a MFC error

Issue How to set up extended logging. Product Line Andover Continuum Environment Continuum Cyberstation Extended Log Cause Configuration of extended logging. Resolution Sample configuration for extended logging. This example would create enough entries for a 24 hour period. Create an Infinity Numeric Select the logs tab Number of entries (96) Type will be LogInstantaneous (Stores the current value of this point at the beginning of every interval) Interval will be 15 minutes (15 minutes in a 24 hour period is 96 which is what we set for the Number of entries) By default the Workstations are setup for 5 minute checks to the controllers to see if there are extended logs to enter into the database. For more in-depth configuration of extended logging, please review Extended Logs in the Continuum Online help system.  For performance and load balancing please see Extended Logging gaps, performance and load balancing.

Issue Downgrade SQL 2008 to SQL 2005 Restore from SQL 2008 to prior version. Product Line Andover Continuum, TAC INET, TAC Vista Environment SQL 2008 used by Building Management Software Cause Have database loaded on one machine using SQL 2008 and would like to move or change to SQL 2005 Resolution Golden Rule: A SQL 2008 database cannot be downgraded or restored to a SQL 2005 version. It is not possible to downgrade a database or a database backup. The SQL schema will not allow it.  For your current version of SQL: C:\Program Files\Microsoft SQL Server \80, \90, \100 Folders are the client tools. 80 = SQL Server 2000 90 = SQL Server 2005 100 = SQL Server 2008 How ever, it is not a rule. Since 2008 creates both 80, 90. The only way to find what versions are installed (besides regedit) is by the Sql Server Configuration manager.    For other SQL options related to I/NET, please visit SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL.

Issue IT departments want to install just the client software without attaching to the webclient server and want to know if there is a way to accomplish this. Product Line Andover Continuum Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Webclient deploys activex controls using several .cab file from the C:\program files\redist folder on the webclient server. These files must be delivered to the browser PCs with admin privileges on the client PC in order for webclient and webpinpoint to work. Here is a list of the .cab files and ActiveX controls that get installed AccWebUtils.cab - AccDotNetBootstrap Control, Crypto Class (Used for  regular webclient use) WebclientPinpointSetup.cab - PPBrowserMgr Control (WebPinpoint) WebclientVideo.cab - TACVideoControl.VideoControl (Viewing Video layouts) ** The other piece that doesn't get installed are the permissions for the caspol commands that must be set for zones in order to run schedules. See webClient schedules getting error 'request for permission of type' system.security.permissions or .net control error on Webclient reports related to webclient schedules and running the caspol commands 1.94 SP1 requires that Microsoft VC++ 2005 Redistributable SP1 x86 to be installed for webpinpoint, it prompts to install when accessing a graphic the first time Resolution There is no client side webClient PC installation. The method for delivering the necessary activex controls and files are triggered by the browser PCs access to the webclient server PC and then the files are delivered to the client.  Some IT departments use Microsoft  SMS or Active directory to deploy software in a locked down environment. To deploy webclient to these types of browser PCs, they would have to logon with Admin privileges to perform the one time install of these files. The only other method if the IT group has InstallShield or WISE package creation software would be to capture the browser PC installation and use the produced .msi file for client delivery. This is informational only and has not been tested by Schneider Electric.

Issue Effects of leap year with schedules and BMS Product Line Andover Continuum, TAC INET Environment I/NET Site Continuum Site Time, calendar, Gregorian Calendar Cause Leap year adjustment in calendar Resolution I/NET: I/NET will not be affected by Leap Year occurrence if DST and Time Sync is correct in the host computer. For Time Sync errors, please refer to Time Sync Error, Daylight Saving setup, please refer to Configuring Daylight Savings Time. Continuum: Continuum will not be affected by Leap Year occurrence to controllers or scheduling if the Cyberstation has the correct time. There have been no incidents in the past with regards to leap year. Leap year is no different than some months having 30 days, others having 31. More information on time sync of controllers check Time sync controllers to workstations. To sync Continuum to an external time clock read Synchronize Continuum system to external time clock.

Issue Enabling XDriver on the first generation of controllers, 9200, 9400, 9940, 9900 including the enabling of TCP/IP Product Line Andover Continuum Environment Older Continuum sites Cause Connectivity to third Party devices using the old NCI or First Generation Controllers requires an updated file. Resolution For 1st generation controllers, a .upd file is needed to turn on the bit for the Comm port. There is 1 bit per port to enable X Driver then a second bit to enable IP X Driver support required for the Modbus TCP/IP driver. The same principle applies to the generation1, 9200, 9400 controllers.   These controllers have flash memory just for things like the Serial number, model num, & X Driver settings, even though the controllers have EEPROM's for the firmware   As far as loading these drivers using hyperterminal, apart from firmware, one can load the X Driver file/ code through hyperterminal if required, but easier to do through Cyber'.   These files which enable the Xdriver for the Comm port, and TCP/IP are available by filling out the Driver Request Form, then they will be emailed directly to the customer from the factory in U.S.   X Driver list (Search for 'Third Party Driver List') and Order Forms (Search for 'xdriver order form') are located on the Exchange Download site  Difference between first and second generation controllers, visit What is the difference between 1st and 2nd Generation X Drivers. For information on Physical Ports, visit What controller ports and physical standards are supported by the Modbus X Drivers?  For Second Generation Controllers, visit How to order a controller with or upgrade a controller to have XDriver support.

Issue Cameras have learned in successfully but live video shows as black or the Video Administrator shows the preview as black. Product Line Andover Continuum, Pelco Environment Continuum Endura Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Live video is showing black because of a configuration issue. Resolution There can be a number of reasons why live video is showing as black in Continuum. Here are some steps to correct or troubleshoot this: Time between devices is not synced. Verify that the controller(InfinintySystemVariable Date), Cyberstation(DateTime Date), and the Endura system(SM) time are all synced. Video Driver or Card. To allow for Sarix cameras in 1.92 changes were made that could cause a standard VGA driver to not display video. Update the standard driver or change the video card. (Test with a different PC which uses a different card) Multicast traffic. Check that the switches on the LAN are broadcasting traffic using multicast. Run the Sherlock utility which is a free codec utility to determine the codec on the Cyberstation and send the results to Product Support. It can be found at the following web site: http://www.free-codecs.com/Sherlock_The_Codec_Detective_download.htm Ensure that the cameras were renamed from the default name in Endura (defaults to camera, but it's actually a null). Ensure that each camera has its own unique non-zero input/channel number. Both of these two items can cause the Continuum camera learn to not be successful and cause issue when trying to access video. Video.log files. Configure the video.log files per How to create a log file for troubleshooting video integration issues in Continuum. Send these files to Product Support for analysis.

Issue Where can I find datasheets, install guides and other documentation on the HID SmartID, iClass, HID Proximity and Indala Proximity cards and readers? Product Line Andover Continuum, Field Devices, TAC INET Environment Electronic Access Control cards and readers for Continuum and I/Net products. Cause Additional product information from HID may be required that is not available on Schneider Electric's own websites. Resolution Schneider Electric supply a subset of the full HID range of cards and readers and these are detailed in the Electronic Access Control Catalogue or see How to determine the part number for the card format required for part number information. For HID product information this can be directly downloaded from the HID Global website. This contains  datasheets, installation guides, application notes, feature lists, brochures and other documentation. HID also have a "Knowledge Center" website that allows you to search for product information and help: HID Knowledge Base. Information on the specific ranges can be obtained from the following links: SmartID: SmartID Cards iClass: iClass Readers iClass SE Readers iClass Cards HID Prox: HID Proximity Readers HID Proximity Cards Indala Prox: Indala Proximity Readers Indala Proximity Cards

Issue What is the process for converting a Continuum Single User system to a Continuum LAN system. Product Line Andover Continuum Environment Continuum CyberStation ContinuumDB SQL Cause Site wants to upgrade from Continuum Single User system to a Continuum LAN System. Resolution PRELIMINARY WORK Order Continuum Key Upgrades from all Continuum CyberStation workstations and WebClient Servers. Coordinate with customers IT department Order all TCP/IP node addresses Coordinate the purchase and installation of all software Order all necessary domain accounts Make sure all domain accounts have sufficient permissions to support the installed systems. PREPARE THE NEW CONTINUUM DATABASE ON SQL SERVER Set up your server and install SQL Server 2005 or 2008. SQL must be configured with the proper collation sequence.  (See CyberStation SQL collation) SQL must allow Name Pipes (See After installing Continuum 1.93 LAN, failure to initialize a new database) Install CyberStation on a service Laptop or PC . Disable all virus protection software Disable all spyware software Disable all firewall software. Install Continuum CyberStation Run Database Initialization on service laptop Create new Continuum database..  NOTE: The new database should be given a name that differs from the existing database. Create the service Laptop workstation with a unique Device ID and Network ID. Launch Continuum Logon and verify that Continuum appears to be running normally. MOVE FILES FROM EXISTING SU WORKSTATION TO THE SQL 2008 SERVER Backup PinFiles on original stand alone Cyberstation and move them to New Graphics Files folder on the new database server. Backup Background image files on original stand alone Cyberstation and move them to the background image files folder under New Graphics Files on the new database server. Backup the existing database and move it to the backup folder under SQL on the new Database server. Restore backup to Continuum database in SQL on the new database server.. Shut down all the Cyberstation workstations that are attached to the old database. Change DB Owner Run query on new Continuum database Enter the text SP_ChangeDBOwner Andover97 Execute this query.   Query should return Success. Run Database initialization on the service CyberStation and update the new SQL 2008 Continuum database. Launch CyberStation on the service laptop and verify that the system is fully functional. Shut down service laptop. CONNECT EXISTING WORKSTION TO THE NEW DATABASE SERVER Startup Existing CyberStation PC Launch Database Initialization Under Server, Update the new Continuum database with the same information entered via the service laptop..  Under Workstation update the server information and apply. Launch Continuum. Configure Graphic File Location From Start Programs Continuum, run Pinpoint Under the View menu select Options. Enter the path on the new Continuum database server for the Graphic (Pin Files) Enter the path on the new Continuum database server for the Image files Enter the path on the new Continuum database server for the Background files Select Check and verify that no errors appear (Red X) Ideally uninstall SQL Express or MSDE or at least stop the service from running. Delete the Windows Scheduled tasks: CS_Distn, CS_Hrly, CS_ Minute as these are now performed by Jobs on the SQL server. Test all Continuum functionality. Setup a scheduled automatic db backup routine in SQL. Setup a scheduled trend log truncation routine in SQL.

Issue Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents

Issue Getting DCOM errors when trying to access WebClient and need to determine which of the various permissions have not been set properly. Product Line Andover Continuum Environment WebClient IIS Cause DCOM permissions have not been set properly. Resolution Open EventViewer, go to System Events, and note the DistributedCOM error. Open the error and find the CLSID that it is referring to. In the DCOM Config, look through all of the DCOM objects and find the one with the matching CLSID. Make sure that it has the correct permissions according the WebClient installation document. If this does not resolve the problem, you can also consult WebClient most common installation problems for further troubleshooting steps.

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue Without knowing the Device ID / Device Instance these devices cannot add to the MSTP network in the AS or ES. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment Automation Server Enterprise Server BACnet SE7000 Cause Only the MAC ID / Com Address is shown in the display but not the Device ID / Device Instance. Resolution SE7200x Models Default Device ID is set to: 72000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7200F5045B controller with a MAC address of 41 is connected to a network, its default Device Name will be SE7200F5x45B-41 and its default Device ID will be 72041. SE73xxx Models Default Device ID is set to: 73000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7300C5045B controller with a MAC address of 63 is connected to a network, its default Device Name will be SE7300C5x45B-63 and its default Device ID will be 73063. Click here for the Integration Manual. Please refer to the SE7300 series BACnet controller does not come online in StruxureWare Building Operation if SE7300 controller does not come online.

Issue You get an error, "Unable to load the .Net control for this page." when trying to open a schedule in WebClient. Product Line Andover Continuum Environment webClient Cause The problem is that the .Net zone permissions are not set on the browser machines. Resolution Depending on the revision of the WebClient the procedure for correcting this on the browsing machines is different. If you are running WebClient version 1.73 or below then refer to the WebClient installation guide on setting the .Net zone permissions. If you are running WebClient version 1.74 or higher, which uses .Net 2.0, the procedure is different. Below is the procedure that will need to be performed on the browser machines at the command prompt to set the .Net Zone Permissions for .Net 2.0. The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success You should then be able to open the .Net 2.0 editors on your web.client browser machine. In some cases adding the webclient IIS PC to the trusted sites in the browser is needed Internet Explorer> Internet Options> Security> Click Trusted Sites> Click Sites Type in http://your server name/webclient and click Add (i.e your server name is specific to your install) Deselect the checkbox for 'Require server verification (https:) for all sites in this zone Click Ok, Ok Close explorer and access webclient schedules Note: Every browser PC that will be accessing schedules needs to have the caspol commands run on it. Download a batch file that can be run on each PC (Rename the .txt file to .bat and run at a DOS prompt  C:\> caspolwebclient.bat)   Note: When using 1.94 SP1 check the application pools .net version selected Name .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic 4.0 Classic .NET AppPool 2.0 Default AppPool  2.0 WebClient  4.0 Note: If .net framework 4.5.x has recently been installed on browser PCs, see Webclient Cannot open .net editor with .NET Framework - 'There was an error trying to create the .NET control for this page'.

Issue Unable to successfully install Continuum keyless license software. Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause Various causes. Resolution The following articles address issues with the Continuum Keyless license software. Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped Web based email should not be used to deliver Keyless Licensing information files (c2v) or activation files (v2c) How to determine the Continuum version, features and the Hasp license ID on a Keyless Continuum License Hasp Key Utility will not activate keyless license Version Error Getting Id. -- Key Id Not Found Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped

Issue Every so often one or two programs on the Continuum workstation stop working. Editing the program results in: A Cached Program cannot be opened while it is being written. Product Line Andover Continuum Environment CyberStation WebClient Continuum Programs Cause CyberStation was not installed properly. Too many demands are being placed on the workstation. Resolution If the problem results from a problem with the installation of Continuum Cyberstation, refer to Problems installing Continuum. Once Continuum has been properly installed, the problem may result from placing to many demands on the Continuum workstation.  Some questions that should be asked are... How many programs are being run on the Cyberstation concurrently. The default setting for Run on any workstation when a workstation program in created is false. This property should be checked for all workstation programs whether they must be run from another workstation or not. This setting can be found in the Program properties editor. An a cached program cannot be opened while it is being written error may occurring when a report program is writing to disk. Verify that the Cyberstation PC conforms to the Continuum Compatibility Matrix for the Continuum version. How many PE programs are running on this workstation, how complex are these programs and are high level commands such as: Rotate, Run, Shell, OpenFile, OpenList, GetName, GetObject being used frequently. How many report programs are running concurrently.  Is the report workstation 100% dedicated to running reports and nothing else; no alarm reporting, no schedules, no extended log downloading, no Access server functions? Is the workstation hardware and operating system sufficient for the work CyberStation is expected to do. Managing these demands may involve sharing the reporting load over several CyberStations and/or adjusting the timing of processor intensive programs so that the workstation is executing fewer tasks at any given time.  In some cases program performance may be impaired due to insufficient memory allocation. See Getting a Smart Heap error when starting Cyberstation or not all processes start and Cyber doesn't open.