Building Automation Knowledge Base

Issue On attempted creation of new database receive the below errors. Database creation failed. Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]The database 'ContinuumDB' does not exist. Supply a valid database name. To see available databases, use sys.databases. > Installation Error! <[Microsoft][ODBC SQL Server Driver]Invalid cursor state> Installation Error! <[Microsoft][ODBC SQL Server Driver]Invalid cursor state> Environment Continuum Cyberstation Cause The "DB File Location" in the Database Initialization dialog is not specified properly. Resolution Check where the "Data" folder resides on the SQL server A typical SQL Express install will have this located at "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" but depending on the type of SQL, Operating System, and if any other instances of SQL - this location could be different. The correct folder contains at least six files:  master.mdf mastlog.ldf model.mdf modellog.ldf tempdb.mdf templog.ldf Type this path location into the "DB File Location" field Re-attempt the Database creation.  

Issue When logging onto Xenta Server's webpage (Xenta 701 and Xenta 721), "The Site Name" folder is missing. Xenta 701 and Xenta 721 cannot display a Value Page though the page has been created in the Xbuilder project. Environment Xenta 701, Xenta 721 XBuilder 5.1.X TAC Vista Workstation 5.1.X Cause Though Xbuilder allows the user to create a Value Page, it will not be displayed on the website. Xenta 701 and Xenta 721 only has "Service" level support of web services, therefore any web content ability is disabled. NOTE: Xenta 913 also only has "Service" level web services. However, Xenta 913 is a gateway; therefore, the Value Page feature is enabled in Xenta 913.  Resolution User can use other Xenta servers such as Xenta 731 or Xenta 913 to have Value Page feature. Or, viewing points values on TAC Vista Workstation.

Issue Vista Workstation displays a data point as a signed integer data type that reads from a modbus device, but the modbus point is defined as unsigned integer data type in Device Editor. When a modbus point's raw value is greater than 32768, Vista Workstation displays a negative value. Environment Xenta Servers Ver 5.1.4 or previous Xenta 511, 527, 555, 701, 711, 721, 731, 913 Device Editor Cause Xenta Servers will read Modbus data as 16-bit signed data, whether the modbus point is defined as 16bit SIGNED or 16bit UNSIGNED in the Device Template. Resolution Upgrade Xenta Servers firmware to 5.1.5 or above; Upgrade Vista software environment to 5.1.5 or above. include  Vista Server, Xbuilder, Device Template, Menta

Issue How do integrate an Xenta 913 in Vista? Do I need to give an IP address as well as a Neuron ID to integrate an Xenta 913 in Vista? Environment Vista 5.1.X Xenta Server 913 (applies to other models) Cause There may be some confusion as to whether an Xenta 913 is considered a LON device or IP gateway in Vista. Resolution If the device is being used as a Modbus\M-bus\C-bus\BACnet client only the IP address is required. In Vista workstation, right-click on the Server object and select New\Device\Xenta Server 913. Give the device a suitable name. Right-click on the device and select Properties. Set the IP address for the device. Right-click on the device and select edit. Configure the device in TAC XBuilder.

Issue Menta file Simulates (F12) and Generates OK and even downloads from Vista apparently OK, but monitored values shown the message 'Failed to read signal'. Connecting to the controller with the serial lead and entering online simulation mode gives a 'PARSER ERROR'. The Memory Usage stats show less free space than would be expected for a file of this complexity. Environment Vista Menta Xenta Cause The Menta file has some corruption that is not visible when viewing the Functional Block Diagram. Resolution Some files may be rescued by copying the FBD into a new empty Menta file: Create a new empty Menta file with the same Device and Program Specifications as the corrupted file. Open the corrupted file in a second instance of Menta. Drag a selection box around the entire visible FBD and enter Ctrl+C to copy. Switch to the new Menta file and enter Ctrl+V to paste the FBD. Please note that this procedure will copy references to named constants across to the new file, but it will not copy the constant definitions. Selecting F12 will highlight the function blocks containing the references to the missing constant definitions.  Edit the block and press 'OK'.  A dialog box will pop up for each constant where you can fill in the value, unit and public parameters.  Repeat this procedure by selecting F12 until Menta enters simulation mode without errors.  You will also need to create the OP tree and any trend logs from scratch. If you are lucky, the new file will download and run without errors.

Issue In our portfolio we currently only list VF208 series valves with elongated wafer type eyelets  Environment VF208L VF208W Cause Applications sometimes requires a valve with lugs instead. Resolution VF208 valves with lugged flanges are available on request. Please contact Product Management or Order Entry for information on ordering this option. The Specification sheet can be downloaded here.

Issue Data not showing up in the consumption report. Environment All versions of I/Net. Cause The points that are trending data are not matching up with the new host, therefore it is not collecting any data. Resolution After restoring the database, open up the trends editor and create or match the trends on the new Host PC.

Issue Site needs to change the IP address in Cyberstation Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is a need to be able to change the IP address in Cyberstation Resolution Shut down Cyberstation Go to the PC's network/LAN/TCPIP connection properties and enter the new static IP address Verify the IP address change by going to Start>Run>Cmd (DOS Prompt) and type Ipconfig/all. The IP address will show under the network card similar to the following: Description . . . . . . . . . . . : Intel(R) 82577LM Gigabit Network Connection Dhcp Enabled. . . . . . . . . . . : No Physical Address. . . . . . . . . : 5C-26-0A-45-7C-D8 Autoconfiguration Enabled . . . . : No IP Address. . . . . . . . . . . . : 192.168.203.2 Subnet Mask . . . . . . . . . . . : 255.255.255.128 Default Gateway . . . . . . . . . : 192.168.203.1   Launch Cyberstation Open the Workstation object using Continuum Explorer (Right click>Edit) Click on the "Teach" button (Distributes the New IP address to the controllers)

Issue Cannot bind an input with the name Intern.Temp. Environment StruxureWare Building Operation Binding Point Naming Cause While a "." may be used as a separating character within a point name, it is an illegal object name character when it appears as the last character. StruxureWare Building Operation will generate an Illegal Character error when you attempt to name an object with a trailing "." character. Resolution Rename the object without a "." at the end of the name string and rebind it to the object.

Issue When running Vista in high security level Vista will add the NT group "Domain admin" as a user group in Vista at startup. Is it possible to avoid this? Environment Vista 5.1.7 Cause When running Vista in high security level Vista will add all users in the computers administrator group as users in Vista at the startup of the Vista server . This is not possible to prevent.  Resolution Either run Vista in low security level or take away the "Domain admin" group from the administrator group on the computer.

Issue The data sheet only lists AC power supply as an option when using the 0-10V output signal Environment SHD100 006902320 SHD100-T 006902330 Cause Sensor configuration options. Resolution For a transmitter the operating (normal) current is at once the measuring signal. If a rectified output is requested this means that DC voltage as supply voltage is required.

Issue Xenta Server firmware installation takes several minutes before it starts up When launching an installation of the Xenta Server system software it takes several minutes before it starts Environment Xenta 7XX Xenta 5XX Xenta 9XX Cause This rare issue has been seen on some PCs with a huge amount of files in the Windows/temp folder. It could be various other programs conflicting, in one case it has been the process setpoint.exe that was conflicting. Resolution Delete all files in the users temp folder. Here is a sample of the path: "C:\Documents and Settings\user_name\Local Settings\temp" or "C:\Users\user_name\AppData\Local\Temp". Easiest way to access the temp folder is by entering %temp% in the path in explorer. If  setpoint.exe (Logitech) or KiesAirMessage.exe (Samsung) is an active process in task manager, end the process. It has also been seen that the process net.exe is blocking the installer. If the above steps does not work, try stopping that process.

Issue Since the M5/M15 series actuator is no longer available, a replacement actuator is requested.  Environment M15 M9B TRV mounting kit 8600991000 Cause Replacing obsolete actuator. Resolution M9B together with the TRV mounting kit should work.

Issue Are SNMP communication packets affected by controller's network encryption? Environment CX9680 ACX5720 ACX5740 Cause Documentation Resolution Enabling network encryption does not have any effect on SNMP communications.

Issue When tunnel through a UNC using an HTTP port other than 80 the Ax Serial Tunnel will not connect and locks up. Environment R2, G3 I/A Series tunneling Cause Including the port number after the IP address when entering the Host address in the Ax serial tunnel window will cause it to lock up trying to connect with the port entered. Resolution Do not include the port number after the IP address when entering the Host address in the Ax serial tunnel window.

Issue Encountered the following error when running the SNMP service: Start service: SnmpService [1272] SnmpService SnmpReceive: unable to create socketjava.net.BindException: Address already in use: Cannot bind Environment I/A Series R2 SNMP driver Windows Server 2008 Cause The SNMP ports are being used by another application / process. In this particular case, the SNMP Service (which is available in Windows Server 2008) has been enabled. Resolution The I/A Series R2 default ports for SNMP are 161 (receive SNMP requests) and 162 (receive SNMP trap messages). Check if the SNMP Service in Windows Server 2008 is enabled. If it is enabled and not in use: Disable it by stopping the service and setting it to 'Manual' so that it does not start whenever the computer reboot and starts. Uninstall it using Windows 'Add or Remove Programs'   Alternatively, you can change the SNMP ports in I/A Series R2. To do this,  in your station, go to the SnmpService properties, 'General' > 'Config' tab.

Issue How to automatically disable access for Personnel who's expiry date has passed? Environment Continuum Access Control Cause Want to automatically disable Personnel who's cards have gone beyond the expiry date. Resolution The below code sample can be used as a basis to provide this feature. It is a fallthru Workstation Program that can be triggered from one of the time related SystemVariables such as Hour or Minute. It uses the OpenList function to go through all Personnel in a specific folder and compare their expiry dates to the current Date and then disables them if required.   ========================================== 'Fall thru program that will search through the Personnel class for ' an expiration date that is less than today’s date. Object oAPerson Numeric nResult Line 1   nResult = OpenList("Personnel", oAPerson, Root\CardHolders) 'specify CH path Line 2   If nResult = Success then     While GetObject(oAPerson) = Success       'The next line will fail when the Expiration Date attribute is greater than 12/31/2037 (12/31/2099, by default)       If (Date > oAPerson ExpirationDate) then         Set oAPerson State = Disabled       Else         Set oAPerson State = Enabled       Endif     Print oAPerson Name, " is ", oAPerson State 'prints to message window for testing     Endwhile   Endif ==========================================

Issue Can Pelco's Control Point Software run on the same PC as I/NET Seven Software? Product Line Pelco, TAC INET Environment All Windows OS I/NET Seven Software Pelco Control Point Software Cause The two software packages are not compatible with each other. Resolution Pelco's client software cannot be installed on the same PC that is running TAC I/NET Seven. See TCON 301 - Chapter 6.

Issue An object’s override and set pop-up boxes do not fully open in Niagara G3. You have to grab and pull the corner of the pop-up to open it completely. Niagara version 3.5.x is installed on a Windows 7 PC. Environment Niagara G3 Version 3.5.x and older Cause Versions of WorkBench prior to 3.6.31 have not been officially certified with Windows 7. Resolution The issue is more of a nuisance, but does not affect functionality in any way. There are a couple of options you can try to try and correct the issue. The first option is to try to reduce the font size in Windows 7. - Click on the Start button and open the Control Panel - Open the Fonts folder and select Change font size. - Select smaller fro the font size and click apply The other option is to change the screen resolution slightly. Note: Since Niagara versions prior to 3.6.31 have not been certified for the Windows 7 operating environment, the above my not correct the issue.  

Issue LinePrinterRecipient 'Load Printer List' does not bring up a list of the available printers Environment I/A Series G3 Enterprise Network Server (ENS) or Enterprise Network Controller (ENC). Cause At this stage the reason that this occurs is unknown but the following resolution is the current workaround. Resolution Since you are not able to find the printer using the 'Load Printer List' button, you should just type in the name of the printer in the LinePrinter Recipient's properties 'Printer' field. To make sure you get the name correct, go to Windows Control Panel and go to 'Printers and Faxes'. Find the line printer and right-click on it to the properties. Copy the name of the printer. Go to Workbench and paste the name of the printer in the LinePrinter Recipient as per described above.