Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Categories
  • Forums
  • Knowledge Center
  • Blogs
  • Ideas
  • Events & Webinars
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Improve your search experience:

  • Exact phrase → Use quotes " " (e.g., "error 404")
  • Wildcard → Use * for partial words (e.g., build*, *tion)
  • AND / OR → Combine keywords (e.g., login AND error, login OR sign‑in)
  • Keep it short → Use 2–3 relevant words , not full sentences
  • Filters → Narrow results by section (Knowledge Base, Users, Products)
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
  • Building Automation Knowledge Base
  • Label: Andover Continuum
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,197
  • TAC Vista 2,029
  • EcoStruxure Building Operation 1,897
  • TAC IA Series 1,688
  • TAC INET 1,444
  • Field Devices 722
  • Satchwell BAS & Sigma 402
  • EcoStruxure Security Expert 343
  • EcoStruxure Building Expert 222
  • Satchwell MicroNet 212
  • EcoStruxure Access Expert 153
  • CCTV 52
  • Project Configuration Tool 48
  • EcoStruxure Building Activate 19
  • EcoStruxure Building Advisor 13
  • ESMI Fire Detection 13
  • Automated Engineering Tool 5
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 1
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • CraigEl
    CraigEl
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Label: "andover continuum"

View in: "Building Automation Knowledge Base" | Community

2197 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 12
    • 13
    • 14
    • …
    • 110
  • Next »
Label: "Andover Continuum" Show all articles

Error Getting IIS object: IIS://LocalHost/W3SVC/1/Root/webclient. Automation error Invalid syntax when installing webclient

Issue Error Getting IIS object: IIS://LocalHost/W3SVC/1/Root/webclient. Automation error Invalid syntax when installing webclient Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Cause IIS must be installed prior to webclient or the webclient applications cannot be created Resolution 1. Install IIS prior to the webclient install (See the installation guide section Pre-installation Microsoft Tasks) 2. If IIS is already installed, run the following command from a DOS prompt (Start>Run>cmd) CD\ + enter Cd \Windows\Microsoft.net\Framework\v2.0.50727> aspnet_regiis.exe -i + enter Reboot the PC and reinstall webclient Windows 7: Ensure that all the specific IIS components are selected according to the webclient installation guide See the section Configuring IIS for Windows Vista and Windows 7. There are specific components that must be selected in order for the webclient applications to work properly. If a component was missed, select it, then restart IIS and Continuum.
View full article
Picard Product_Support
‎2018-09-06 01:21 PM

Last Updated: Lt. Commander Ramaaly Lt. Commander ‎2025-09-03 11:06 AM

Labels:
  • Andover Continuum
4096 Views

Get "Server error in '/webclient' application" when log on web client server

Issue After configure web client, the log on page appears, then type the user name and password,  the log on process not continue and get server error in '/webclient' application. When use IE browser on the IIS server machine to access web server will get the error as shown as the capture picture below:    When use IE browser on the client machine to access web server will get the error as shown as the capture picture below Product Line Andover Continuum Environment LAN Windows server 2008 R2 SQL server 2008 IIS 7.0 IE 7.0 Webclient 1.90 Cause Incorrect IIS server configuration, some items is unchecked except CGI and ISAPI Resolution Go to IIS manager, check all the items of web service extension except CGI and ISAPI Try to log on again from browser, that should be ok.
View full article
Picard Product_Support
‎2018-09-07 08:57 AM

Last Updated: Lt. Commander Ramaaly Lt. Commander ‎2025-09-03 11:07 AM

Labels:
  • Andover Continuum
3716 Views

Steps to connect a 4-20mA or 0-20mA sensor to a Universal Input

Issue Current transducers require an additional external resistor fitting to a Universal input to read the current flow, what resistor and input point settings are required? Product Line Andover Continuum Environment All controller with Universal Inputs (both 5V and 10V). 4-20 mA Cause There is a requirement to define the resistor value to be connected across the input, also the settings for the upper and lower voltage in the input point configuration. Resolution Download the attached Current Inputs.PDF file, although this was originally written for Infinity controllers it is fully applicable for i2 and b3 controllers. Controllers like the i2/b3920, i2/b3810 have 10V inputs other i2/b3 controllers have 5.12V inputs, check the product datasheet specification if you are unsure. The file details the value of the resistor to use in the circuit and the upper and lower voltage settings to enter in the Auto Conversion box in the input point, these will correspond to the sensor reading at 0mA and 20mA, or 4mA and 20mA depending on your sensor output. For controllers that allow the pull up resistor to be switched out, ensure that it is in circuit for these setting to work correctly. The UI-8-10-10V I/O Modules should be set to 0-5V input with the reference resistor On, then setup as per all other 5.12V input controllers. Note: The part numbers listed for the resistors are no longer available through Order Entry and should be sourced from your local stockist. Link to file: Current Input ISM.pdf   Suitable component resistors: For 10V inputs: RS 165-472 For 5V inputs: RS 165-185 0
View full article
Picard Product_Support
‎2018-09-07 06:01 AM

Last Updated: Lt. Commander Ramaaly Lt. Commander ‎2025-09-03 11:08 AM

Labels:
  • Andover Continuum
7243 Views

Reading a controller error log

Issue How to read a controller error log Product Line Andover Continuum Environment CX 9680 ACX 57xx BCX 9640 BCX 4040 i2 controllers B3 controllers Cause Need to decipher a controller error log Resolution Deciphering the controller error log can be accomplished by using a few of the fields of the error log. There is one field that is able to be deciphered very easily. The Error Code column of the error log is a code that can be matched to its text description. The other fields are used internally by PSS and engineering. To find out what one of the entries in an Error Code column means, open up the Continuum online help file. The Continuum online help file can be found by in the Continuum Explorer by selecting the menu item Help/Contents. From there select the Index tab and type in the keyword Error. A selection will be available for Error messages, Cyberstation. On this page you will be able to take the last 4 digits of the Error Code from the controller error log and match it up to its description. Example: Error Code  0x00001401 translated into decimal form would be 5121 The error code will be listed by both the hex and decimal format. Not all codes will be in the online Error description fields. Some of these codes are internal use only. If you find that you need a code deciphered, please open a case with Product Support.
View full article
Picard Product_Support
‎2018-09-06 12:48 PM

Last Updated: Lt. Commander Ramaaly Lt. Commander ‎2025-09-03 09:32 AM

Labels:
  • Andover Continuum
3633 Views

RH-Series Humidity Sensor Wiring Clarification

Issue Confused by RF-Series sensor wiring instructions. Do the controller's input return and the supplied power ground connect to the same termination on the sensor? Environment RH-Series sensor Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Documentation Resolution *** If connecting to a voltage input on the controller then use the VOUT termination instead of the 4-20 mA
View full article
Picard Product_Support
‎2018-09-06 09:26 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • Field Devices
1838 Views

Migrating Continuum controllers from a stand alone system into an existing LAN system

Issue What is the best practice for migrating controllers from a stand alone Continuum system into an active LAN system? Product Line Andover Continuum Environment Migrating Continuum Database Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Controllers must be migrated from a stand alone system into an existing Continuum LAN system. The ACCID of some or all of the controllers on the stand alone system are already in use on the LAN system. Resolution All address conflicts should be dealt with before the controllers are brought onto the LAN system. With the workstation in Offline mode, each controller on the Stand alone system is manually created on the LAN system.  If the controllers ACC ID will conflict with a controller on the LAN system an appropriate change must be made when creating the controller on the LAN database. Where the controllers are BACnet controllers and the intent is to have all controller on the same network, the Network ID (UDP) id must be changed to match the id of the LAN system. The Comm2 network ID of each stand alone controller should be noted and should be changed in cases where the id is already in use on the LAN system. Import files should be used to build the IP level controllers
View full article
Picard Product_Support
‎2018-09-06 10:11 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1991 Views

How to swap two infinet controller on the same system.

Issue What is the proper procedure to use when swapping two previously installed Infinet controllers on the same Continuum network. Environment ACCID Infinet Controllers Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Must prove determine whether an Infinet Controllers flow sensor is damaged. Resolution It is important to recommission Infinet controllers before relocating them in the same system. Recommissioning the Infinet controller purges all object handles and ensures that the controller will be brought on line virtually as a new "out of the box" controller. Infinet controllers are recommissioned by setting the InfinetID to 0 using a RoamIO. Using a RoamIO, set the InfinetID of both Infinet controllers to zero. Verify that the controllers InfinetID has been set to 0. With the workstation in OffLine mode, change the serial number of each controllers to a fictional serial number that does not exist in Continuum. Remove both controllers and install them in place of each other with out powering the controller. Before the controllers are powered, connect them to the Infinet bus while the bus is connected to the infinet port. Switch the workstation to Online Mode. Power up the controllers. Enter the correct serial number for each controller in the controller editor. Both controllers should come online. Reload both controllers.
View full article
Picard Product_Support
‎2018-09-06 10:12 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1753 Views

A previous version of Cyberstation is shown in the Detail page of the Workstation editor.

Issue Although Continuum 1.94 is installed, when the workstation is edited Version 1.73 is seen on the Details page under Software Revision and Firmware Revision. The Cyberstation startup splash screen shows Continuum 1.94. Continuum 1.94 is shown under Continuum Explore/Help/AboutContinuumExplorer. Environment Cyberstation. Warning Cause The erroneous version number is most likely an artifact of a Continuum upgrade that was done without fully uninstalling the previous version of Cyberstation. Resolution Uninstall Cyberstation from Control > Panel Add Remove Programs. Backup all profiles and graphic pin and background files, then delete the Program Files\Continuum folder. Delete all occurrences of the Andover Controls folder from the registry. HKEY_LOCAL_MACHINE/Software/Andover Controls and HKEY_CURRENT_USER/Software/Andover Controls Reboot the PC and install Cyberstation. Run Continuum Database Initialization and select Workstation to reinitialize the workstation.   .        
View full article
Picard Product_Support
‎2018-09-06 10:18 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1547 Views

AC256 Micro Energy Power Supply voltage reading and the port connection.

Issue How should the Micro Energy Power Supply voltage reading be checked? Can the Micro Energy Power Supply provide power to IOU only without CIU connected? Environment Infinity SX8000 Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Got the Micro Energy Power Supply repaired by 3rd party but the voltage reading seems to be incorrect. Resolution The voltage of the Micro Energy Power Supply should be checked with the load connected to the PS.   For the port_A voltage check, have the CIU connected to the port_A of the PS.   For the port_B voltage check, have the IOU connected to the port_B of the PS. Also the Micro Energy Power Supply can have either the port_A connected to CIU only or the port_B connected to IOU only or both ports connected to CIU and IOU respectively. For detail information of the voltage reading of each pin, please refer to page 2-86 ~ 2-88 of the AC256 Service Manual.pdf
View full article
Picard Product_Support
‎2018-09-06 10:20 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
2727 Views

How to move a net controller from one Continuum network to another.

Issue For various reasons there will sometimes be a need to move a controller from its existing Continuum network to a different Continuum network. Environment CyberStation ALL CX master controllers Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Configuration Resolution WARNING: MAKE SURE TO HAVE A FRESH BACKUP OF THE CONTINUUM SQL DATABASE HANDY IN CASE YOU NEED TO REVERT THE CHANGES FOR ANY REASON. Moving a controller from its existing Continuum network to a different network consists of copying the controller and its children to the destination Continuum network and then deleting it from the source network. Place CyberStation in offline edit mode. In the 'Copy' options make sure to select to 'Copy child objects and the children's children, this will ensure that all field devices get moved with the parent CX. Highlight the controller to be moved then drag it to the destination network and select 'Copy Here', please note that the IP address on the destination will be set to 0.0.0.0 to avoid a duplicate. On the original controller highlight the InfinityInfinetCtrl folder, select all the objects on the right side  and send to text file. Delete the original controller then set the IP address on the copy. Select the copied controller,  right click and select import into  and import the text file created on line 4. Return CyberStation to online edit mode, then reload the CX controller (not including the field devices) NOTES: a) After reload, the controller may have a different time if the original network was in a different time zone than the destination network. b) Controllers are only taught about other controllers in the same network, If you are moving multiple controllers move them all before reloading them. After reload controller will not know about any other controller that stayed in the old network and any references to such controllers will be lost.
View full article
Picard Product_Support
‎2018-09-06 10:39 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1936 Views

Error 'Operation was not performed' when trying to run a Graphic object.

Issue Error 'Operation was not performed' when trying to run a Graphic object. Environment CyberStation Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Corrupted Continuum installation Resolution Uninstall Continuum Delete Continuum folder  (make sure to save any needed files such as pin, menu etc) Delete Continuum entries in the registry (Make sure to backup registry as a precaution) HKEY_CURRENT_USER\Software\Andover Controls\Continuum HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum Re-install Continuum
View full article
Picard Product_Support
‎2018-09-06 10:47 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1716 Views

Update b3 firmware failed with error "The Infinity2 controller is currently being flashed or reloaded."

Issue In some situations, there is a network connection problem or PC power management issue that causes the b3 firmware update to be interrupted. When retrying the controller update, an error pops up: "The Infinity2 controller is currently being flashed or reloaded." Resetting the controller and even doing a power cycle with the controller will not fix this problem. Environment BCX1 B3 Cyberstation Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause The update interruption may be because the b3 is busy. Resolution Take the workstation offline Delete the b3 controller Reset BCX1 from the editor and reload BCX1 Bring the b3 controller online Try to update firmware b3 again. It should be ok.
View full article
Picard Product_Support
‎2018-09-06 10:55 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
2548 Views

Is it possible to downgrade a Continuum Database from one version to an older version?

Issue Is it possible to downgrade a Continuum Database from one version to an older version? Environment Continuum Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Want to go back to a previous version of Continuum after upgrading Cyberstations and the Continuum Database. Resolution No, this is not possible. You cannot downgrade a Continuum Database to an older version . You can upgrade but not downgrade. If you have a database that has been upgraded for a specific version of Continuum and you want to go back to using an older version of Continuum, you will need to use a backup of your original Continuum Database that was initialized for that older version...or upgrade all Cyberstations to the newer version. The Database structure is different between different versions of Continuum; corruption of the Database can occur if the above is not adhered to.   
View full article
Picard Product_Support
‎2018-09-06 11:13 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1247 Views

Replacing a CX9200,CX9300, CX9400 or 99xx with a bcx9640

Issue What is the procedure for replacing a CX9200, CX9400 or 99xx with a BCX9640 Environment BCX9640 CX9200 CX9400 CX99xx Convert Conversion Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause While Continuum Versions 1.91 and higher have a direct procedure for upgrading a CX9200, CX9400 or 99xx to a CX9680, no such option exists for converting a controller to a BCX9640 controller.  Resolution There is no quick and easy way to replace a 9200 (9400 or 9900) with a BCX9640.  In order to do this it will be necessary to bring the BCX9640 online as a new controller (with a new ACCID) and copy the contents of the 9200 (9400, 99xx) into the BCX9640.   Do not copy the System Variables from the 9200, 9400 or 99xx into the replacement controller. As always a backup of the Continuum database should be made prior to making any such changes to the system. External point references, point references on graphics and alarm links would have to be checked and repaired where they have been lost.  Other controllers that referenced points in the original 9200 (9400 or 99xx) will have to be corrected so that they point toward the corresponding object in the new BCX9640.  A full recommissioning of the controller may be required.  Once the conversion is complete the original controller object would be deleted from the system. While importing a text dump of the (9200, 9400 or 99xx) is another approach, this can be a messy process that requires the dump file to be manipulated.  This can lead to more substantial problems if done incorrectly.
View full article
Picard Product_Support
‎2018-09-06 12:09 PM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
2607 Views

Error in system variables when reloading ACX2 (5720, 5740) or NC2 (9680)

Issue Reloading ACX2/NC2 produces error when reloading the following system variables AllowedCreds PersRecordCount PIVReaderFormat Environment CyberStation ACX5720 ACX5740 CX9680 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The system variables in question (AllowedCreds, PersRecordCount, PIVReaderFormat) only apply to versions 1.1xxxxx and 2.1xxxxx of the ACX2 and NC2 respectively. Resolution Make sure the controller is running the appropriate version of the firmware. If the problem persists even with the correct firmware version then... Export the controller to text file Edit the dump file and remove ALL system variables Delete the controller Import the file to re-create the controller (the system variables will be created when the controller is created) Reload the controller, the errors should not longer appear.
View full article
Picard Product_Support
‎2018-09-06 12:20 PM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
1182 Views

Unable to truncate event tables in Continuum once ContinuumDB is at or near the maximum database size for MSDE or SQL Express.

Issue The size of ContinuumDB has reached or is near the 2Gb limit imposed by MSDE. The size of ContinuumDB has reached or is near the 4Gb limit imposed by SQL Express. Environment MSDE SQL Express Continuum Stand Alone. Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The database is well over the SQL size limit (2Gb for MSDE, 4Gb for SQL Express) Since the database size has already exceeded SQL's limitations it is not possible to use the deletion query statement to truncate the log tables.  This is because SQL will attempt to guard against data loss during the deletion process by making a copy of the tables contents before deletion occurs. Before a single row has been deleted from the table the size of the database will actually grow larger, exacerbating the problem. Resolution You must delete the contents of each log table entirely (Alarm, event, error, log) using the TRUNCATE statement. This will delete the contents of these tables entirely without first storing them the data. Please note, you must... Make arrangements with the customer so that they can archive any log and event data they wish to retain. Backup the database before using the TRUNCATE TABLE command. Here is the syntax for the TRUNCATE statements TRUNCATE TABLE ContinuumDB.dbo.AlarmEvent TRUNCATE TABLE ContinuumDB.dbo.AccessEvent TRUNCATE TABLE ContinuumDB.dbo.ActivityEvent TRUNCATE TABLE ContinuumDB.dbo.ErrorEvent TRUNCATE TABLE ContinuumDB.dbo.ExtendedLog Once the table have been truncated, Right click on ContinuumDB and select Shrink > Database. Once the database size has been reduced, check the size and retest. Please note that once the database size has exceeded SQL's limit it is likely that the database has been damaged.  This process may or may not correct damage that has occurred to the database.  
View full article
Picard Product_Support
‎2018-09-06 01:29 PM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:39 AM

Labels:
  • Andover Continuum
2790 Views

Unable to change the ContinuumDB database owner using the stored procedure sp_changedbowner

Issue When running the stored procedure sp_changedbowner to change the dbowner to "andover97", the following error message is received: "The proposed new database owner is already a user or aliased in the database". Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 (Keywords: drop user ) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The Andover97 user already has access to the database through an existing alias or security account within the database. This can occur when the DB is not restored properly to the SQL server. The database may have been detached and then attached again, which is not the preferred method of restoring a ContinuumDB. Resolution Under the ContinuumDB there is a "security" and then "users" folder. Check to see if the Andover97 user is in this folder. Continuum does not put this user in this folder. If it is there, then it will need to be dropped from the database before trying to change the dbowner. Do the following: Do a complete full backup of your ContinuumDB. Run the following SQL script to drop the user from the ContinuumDB. USE [ContinuumDB] GO DROP USER [Andover97] GO Re-run the stored procedure to change the db owner below. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO To minimize the chance of this occurring again, the correct procedure for moving or restoring a Continuum database is to do the following: Create a new ContinuumDB with Continuum's Database Initialization. This creates the DB, SQL jobs, stored procedures, adds Andover97 as an admin and a lot of behind the scenes security settings. Restore a previous backup over top of the ContinuumDB created in step 1. Change the db owner with the above query using the sp_changedbowner stored procedure. Re-initialize the Cyberstation into the Database using Continuum's Database Initialization.
View full article
Picard Product_Support
‎2018-09-06 01:32 PM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:38 AM

Labels:
  • Andover Continuum
2780 Views

CyberStation alarm does not show on Active Alarm View when an alarm arrives

Issue Alarms cannot be sent to recipient CyberStation (Workstation) when controller has lost the link to the CyberStation in regard to the alarmed point in Import/Export table. The new alarm shows up in Active Alarm View only after the CyberStation is rebooted Product Line Andover Continuum Environment Workstation, CyberStation NetController (CX99xx, CX96xx) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause Import/Export table in the NetController does not have the link to the workstation for the alarmed point. Resolution Backup current DB. Shutdown Continuum from all the CyberStations. Execute ImpExpFixupUtil.exe from Continuum install folder (C:\Program Files\Continuum). Reload all the NetController with the "Do not reload attached objects" option.
View full article
Picard Product_Support
‎2018-09-06 01:39 PM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:38 AM

Labels:
  • Andover Continuum
2732 Views

Is there an easy way to set up the different Security Groups?

Issue When setting up Continuum Security levels is there an easy way to set up the different Security Groups? Sites that have upgraded from Infinity SX8000 may require the same security settings. Environment Cyberstation all versions. Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause It can be time consuming and complex setting up multiple user security levels. Resolution In the Workstation you can edit the Security settings to define the access (keys) and blocking (padlocks) for each group against each object class. You can also import/ export these security settings with *.SDF files, attached is a file Default Security V1.sdf that defines a default set of 8 security levels as per the Infinity SX8000: Click here for default security file Administrate Program Configure Enable/Disable Change Values Acknowledge Alarms View Only No Access Click here for a description of each of the above levels (Source: SX8000 Programmer's Guide). To add the "Default Security V1.sdf" file to your Continuum you will need to do as follows, in the bottom right hand corner of your screen there is the Continuum icon, right click on the icon and select Security... then under the Actions tab, right click next to "Access Distribution View" and click import All... then all you do is select the "Default Security V1.sdf" file you have already downloaded and then click open, this will now install the new default security options. Warning! Always make a database backup before attempting to change the security setting so that if a mistake is made you can always revert back to the backup.
View full article
Picard Product_Support
‎2018-09-06 01:57 PM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:38 AM

Labels:
  • Andover Continuum
1899 Views

How to truncate event tables in Continuum databases

Issue How to truncate event tables in Continuum databases. Product Line Andover Continuum Environment Continuum 1.xx SQL 7 SQL 2000 SQL 2005 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Stand Alone Continuum Databases use Microsoft MSDE and SQL Express databases which have size limitations. Once these databases reach full capacity they will need to have data truncated from tables to try and reduce the size of the database. Databases should never exceed their size limitations, but if they do, reducing the size of some of the tables will in most cases allow the database to be functional again. Microsoft SQL MSDE database size limit is 2 gig Microsoft SQL Express database size limit is 4 gig Resolution Once logged into the SQL MSDE or SQL Express database, the queries below will reduce the size of the database. As with any database, make sure you backup the database before running any queries. The Usernames and Passwords used below are defaults, your UN/PW may differ. To log into SQL MSDE use the following commandline. osql -Usa -P To log into SQL 2005 Express us the following commandline with your servername sqlcmd -Sput_server_name_here\sqlexpress -Usa -Padminadmin Once logged in you'll be prompted with a 1> at which time you'll change the context of the database you'll be truncating information on. For example if your database name is ContinuumDB you would use the following. 1>Use ContinuumDB 2> Go 1>Now put in one of the queries below 2> type in Go to execute /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 ** To gain back the space after deleting rows SQL Express Right click on Continuumdb>Tasks>Shrink>Database MSDE(osql) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter)   To truncate from the Full SQL server or SQL Express non command line interface, see Removing unwanted entries from an Alarm log, Access Event log, Error log, and Activity log automatically.
View full article
Picard Product_Support
‎2018-09-07 03:43 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:38 AM

Labels:
  • Andover Continuum
5000 Views
  • « Previous
    • 1
    • …
    • 12
    • 13
    • 14
    • …
    • 110
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support

    Ask our Experts

    Have a question related to our products, solutions or services? Get quick support on community Forums

    Email Us

    For Community platform-related support, please email us

Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

Welcome!

Welcome to your new personalized space.

of

Explore