Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

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

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.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Needing to change the IP address on a Legacy NPR. Environment All versions of I/Net 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 When the IT department changes a subnet or network setting that prevents the device from communicating to I/Net. Resolution There are two ways to change the IP address on the Legacy NPR. 1. This can be done on a Direct Connect by creating a new configuration called NetPlus Router. 2. Make this active and connect the CBL 072 to the upper left connection on the back of the device. 3. Start I/Net and when connected, go to NP Routers, the device will be online with the name that was previously in it or Wantap 1 which is the default. 4. Select it and then modify the IP address and put the new one in, save the changes and hit the okay button. The second way to do this is from the Host PC, 1. Right click on I/O Server and select Configure 2. Modify the Active Profile. 3. Select NPR Routers and follow steps 3 and 4 above.

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.

Issue Replacement battery for the DC1100 / DC1400 Product Line Field Devices Environment DC1100 DC1400 Replacement Battery 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 Controller battery has failed. Resolution The battery lifetime will vary over a very wide range depending on use and temperature so cannot easily be predicted, but about 5 years under normal conditions, would be a guide. The battery in a DC1100 and a DC1400 is soldered to the underside of the CPU PCB. It is a 3.6V 150mAh NiMH battery. The factory part number is S2218121100 and the manufacturer’s part number is Varta 55615 603 940. Please Note: - Good soldering skills will be needed to replace the battery. The battery can be sourced from CPC Farnell Varta 55615603940 details at CPC Farnell

Issue 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C 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 I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B. If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software. Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C. If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important: Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board. If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.

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.

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.

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.

Issue ASC stopped communicating Continuous Lost/Restore Reset the memory in an ASC Controller Product Line TAC INET Environment I/NET SubLAN Controllers All ASC 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 for assistance. Cause When the MR-AHU resides on a communication sub-LAN, it is susceptible to communication errors from external sources. These communication errors could result in corruption of the ASC's NOVRAM. When this occurs, the ASC will stop communicating, or will cause continuous Lost/Restore messages. For this reason, the ASC is provided with a means of clearing its NOVRAM. Caution: Clearing the MR-AHU memory causes the binary instruction set for the controller to be deleted. In order to reload the binary instruction set, you must have a TAC I/NET host with the appropriate UPD files, and the ASC Controller must be communicating through an interface controller (MRI, MCI, or I/SITE LAN). Resolution Prior to clearing NOVRAM of the ASC and you are using MR-VAV's and they have already been balanced, VAV parameters must be recorded (screenshot may be the quickest method). Follow the following steps to RESET the device Remove power from the ASC. Set DIP switches 6 through 12 to the "On" position and restore power. Remove power again. Set DIP switches 6 through 12 to the "Off" position and restore power. Remove power again and reset the switches to their normal configuration. Normal communication should be restored to the ASC. If not, then the problem lies elsewhere. Once communication is restored, perform an "ASC Update" from the TAC I/NET host to restore the NOVRAM image to the ASC. Refer to the TAC I/NET System Operator Guide for ASC Update instructions.

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.

Issue After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server 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 Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

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.

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.

Issue How to restore and view a Log backup without overwriting current database How to view backed-up events without overwriting current database How to restore a SQL database without overwriting current database Environment TAC Vista 4.3 and higher running a typical (not custom) SQL. 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 event and logs will be backed up as a SQL backup file. This means that restoring a backup on the same PC that it was made on replaces the SQL database. Resolution To view old data, restore the log database backup file on a different PC that has the same TAC Vista database on it. Create a copy of the TAC Vista database (or make a backup) Copy / restore the database to a computer that is running the same version of TAC Vista Go to the Server application and log in Go to File > Restore Log Database Browse in the backup file, the path should be filled in automatically

Issue taclogdata_log.ldf file is too big Environment 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 Fail to perform frequent SQL DB maintenance Resolution To Shrink the LOG file (.ldf) follow the procedure. Connect to taclogdata.mdf using SQL server management studio. Run the following command: dbcc shrinkfile (taclogdata_log,100,truncateonly) This will reduce the size (taclogdata_log.ldf) to 100 mb. Note : You can get the logical file name for the log by running the following select statement: (select * from sysfiles) The following are the query results: 1 1 6400 -1 6400 2 0 taclogdata c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata.mdf 2 0 2624 268435456 1280 66 0 taclogdata_log c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata_log.LDF If the database has the truncate log checkpoint turned off, then the transaction log file will be shrink to the target size only when the transaction log is backed up. OR If the truncate log on checkpoint is turned on then go to Enterprise Manager - all tasks - and click "truncate log". This will shrink the file down to the target size and will release all the unused space to the Operating System.

Issue SevenReports Error when attempting to open report directly from Windows Explorer or Graphics link Error received: Error in command line parameters: Report Type: 255 Duration: 255 Error Text: C:\INETSevenData\Reports\xxxxxxxx.rpt The Icon for SevenReports is incorrect: Environment SevenReports Windows7 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 File association has some how become corrupt or it has been associated with the SevenReport.exe file after installing the SetupCrystalReportsXI.exe. Resolution In most cases the file association will occur automatically and there is no need to manually do this. Best practice is to restart the computer after installation, this should stop this error from occurring. Should this error still occur then this will require manually repairing the .rpt file association within the registry. Edit the following Registry keys so they appear as shown below: 1. HKEY_CURRENT_USERS\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rpt If there is an additional sub-key (folder) under the .rpt entry called UserChoice; then delete this key. 2. HKEY_CURRENT_USERS\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rpt\OpenWithList If there are any other entries here they should be removed and this entry must match exactly as shown in this screen. 3. HKEY_CURRENT_USERS\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.rpt\OpenWith\Progids 4. Close the registry editor and Windows Explorer (if opened) 5. Re-open Windows Explorer, browse to the INET Seven Reports folder (default "C:\INET Seven Data\Reports") and see that the ICON has changed back to the correct type and that double clicking on any of the reports now opens correctly. If not please contact Product Support.

Issue Dependencies for Vista Server running as a service Product Line TAC Vista Environment Vista Server 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 Vista server can run into issues if it starts up before other services. Resolution Ensure that Vista Server does not start up before Aladdin Privilege Server by making some changes to the registry. Select the start menu, select run, and type “regedt32”. Once the program opens you should browse to the following path: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TACOS\ The key named DependOnService should by default contain the value RPCSS. To add a dependency to this service just modify the value of the key and add the name of the service you wish to start before this one. In the case of Aladdin Privilege Server just add the text “Privilege Win32 Server” to the registry key. Close the registry editor and the dependency will be visible in the services properties window for TACOS. Note: If you need Vista to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value "Depends on Service". Services commonly selected are Spooler and Messenger.

Issue How to Reset a 7798 Controller Environment I/SITE LAN 7798 / 7798B / 7798B1 Controllers 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 following steps will give end users the ability to reset a 7798 Controller. Resolution Unplug all terminals on the controller i.e. Power Connecter first, then Sublan Connector and LAN if there is a CLX card present. Place unit on static free, flat surface with front face down away from any electrical devices. Now, looking down at the unit there are two capacitors (C2 and C3) just above the battery. Take a paper clip or small piece of wire and place it across the capacitors. First short C2 and then C3 (do not go from one leg of C2 to one leg of C3). Now, place all terminals back on the controller, make sure power on and start I/NET. Go to Edit, Host Computer, Network Configuration and save the controller. Go to Edit, Host Computer, Software Restore and restore the bin file to it and database if there is one. Verify that the unit is on, communicating and all points are displayed.

Issue A system Format of the file system will remove all files to return device to a factory condition. Product Line TAC Vista Environment TAC Xenta 5xx TAC Xenta 7xx TAC Xenta 9xx Xenta Server 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 A need to reset to factory defaults exists Resolution These actions clears the filesystem and remove all files and information in it. Make sure you have IP and any other information you need to save from the file system. All files and configurations will be lost. Access Xenta using a serial interface via the RS232 port and a HyperTerminal program. obtain a connection to the dsh> prompt Type format. Wait for formatting to be ready , then enter command setip to enter DHCP enable ,ip-address , subnet mask , default gateway , DNS , local name. Default user/password will then be root/root. Remember to change password. Restart system to accept new ip-address. Install Xenta using the install kit. Use ftp transfer and alternative A (We have just formatted the system). Download WebTool project and user defined files. Update bindings using LonMaker.

Issue How does one get a clean database for the Enterprise Server or Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central 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 Need for clean database either for testing or start from scratch. Resolution Stop Enterprise Server or Enterprise Central using Software Administrator Go to the location of your database using Windows Explorer. In EBO V3.2 or higher, software administrator has a shortcut button for the databse folder. For this example it is C:/ProgramData/Schneider Electric EcoStruxure/Building Operation 2.0/Enterprise Server/db Delete the following folders if (some might not exist): Configuration, Historical, Persistent, System, UDT Start Enteprise Server or Enterprise Central using Software Administrator, the system will create a new folders and files as needed. Note: Restoring a different database over the current database does not require the clean database state. Using the backup and restore procedure allows you to switch databases.

Issue After an uninstall of I/NET Seven and MS SQL, you might verify in the Windows Registry that all the items were deleted. Having issues installing I/NET what can I look for. Product Line TAC INET Environment I/NET all 2.4X 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 In some cases when re-installing, installing I/NET after a failed attempt or upgrading I/NET you may want to start fresh. After an uninstall of INET Seven and MSDE if items remain in the registry they will cause issues with future installations. Resolution Go to the bottom Task Bar and choose the “Start” button. Select the “Run” option and enter “Regedit” Once in the Windows registry go to “HKEY_CURRENT_USER, if the “CSI” entry is present delete this entry While still in the HKEY_CURRENT_USER look in the Microsoft File Folder for any “SQL” entries and remove them if they are present. Minimize the HKEY_CURRENT_USER folder and open up the HKEY_LOCAL_MACHINE File Folder, if the “CSI” entry is present delete this entry. While still in the HKEY_LOCAL_MACHINE, go to the Microsoft File Folder and look for any “SQL” entries. If you find any delete then from this file folder. Caution: Before editing the SQL registry items you should ensure that no other software using SQL is still installed - all software that is installed should be uninstalled prior to modifying any registry entries. See also, MSDE and Windows 7.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Changing the Address on a Legacy NPR

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

Drayton DC1100 / DC1400 controllers - Replacement battery.

7798C stops communicating after BIN file download

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

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

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

Reset the memory in an I/NET ASC Controller

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

SmartStruxure Automation Server has solid red status LED

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

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

How to restore and view a Log backup (.LDB) without overwriting current database

How to shrink taclogdata_log.ldf file?

SevenReports Error: "Error in command line parameters" when attempting to open report directly from Windows Explorer or Graphics link

Dependencies for Vista Server running as a service

How to Reset a 7798 Controller

Formatting the file system to remove all files and information on a Xenta 5xx, 7xx, or Xenta 9xx

Clean db for Enterprise Server or Enterprise Central

Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!