Issue I/NET Host Tool with StruxureWare Building Operation Environment I/NET Site StruxureWare Building Operation Site Cause I/NET Host Tool support with StruxureWare Building Operation Resolution With the current release of Building Operation, I/NET Host Tool is not supported. Licensing of the Host Tool comes from a TAC Vista server and the graphics converter is not in the I/NET Host Tool. 

Issue Explanation and detail required for Client Access License (CAL). Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET Environment Windows  SQL Server Cause Information on Client Access License (CAL). Resolution Server licensing and Client Access Licenses (CALs) for the MS Server or MS SQL can become complex. It may be worthwhile to research further through Microsoft resources. SQL Server 2008 is available under three licensing models: Server plus device client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each client device. Server plus user client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each user. Processor license. Requires a single license for each CPU in the operating system environment running SQL Server. This license includes unlimited client device access. SQL Standard will normally come with 5 CALs. If more than 5 connections exist, then ore SQL CALs need to be purchased. See Microsoft Volume Licensing for more information. Note: MS Server CALs are separate and are also required. EcoStruxure Building Operation does not check CAL Client Access Licensing. EcoStruxure Building Operation Reports Server can be run using Microsoft SQL Express.  

Issue Changing one Filemaster to another Environment All versions of I/Net Cause Possible corruption on Filemaster and needs to be changed to a different Filemaster then repromote as a client. Resolution To resolve this the following steps needs to be followed: Demote the original Filemaster to a stand alone option and backup the database Demote all the clients to stand alone option Restore the backup from the original filemaster to the PC that will be the new Filemaster Promote to Filemaster Option and allow the icon to change states to where it allows clients to connect Promote all other clients to Equalized Clients by pointing to the new Filemaster Once Equalization is online again, the system should be working again.

Issue Unable to Bind to an I/NET Point Command Error Alarm after Binding to an I/NET Value Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Workstation Cause As of version 1.4, I/NET input points can not be bound to SmartStruxure outputs. A Command Error Alarm will occur when attempting to bind to an I/NET controller that does not have the current bin file Resolution If needed create an additional I/NET output point and use that to control the I/Net input point via a Calculation Point Extension. In I/NET, connect to the controller. Select Edit > Controller > Configuration If the Build Date is older than April of 2012, you will need to upgrade the controller. In StruxureWare, when setting up the bind to the I/NET point, be sure to edit the I/NET point objects bindings, if that is what is being controlled. Bind the desired StruxureWare value to Control Value (DO) or Value (AO) property of the point for I/NET.

Issue Card Reader gets a valid card read but does not unlock the Door. Environment All versions of I/Net using DPU's 7910, 7920 and SCU 1284. Cause The Door does not have an Exit Reader but the parameters are set for Anytime. Resolution To resolve the issue, the following steps need to be followed: Connect to the Controller Select Controller/Doors Select the door in question and click on the Modify button In the Editor, at the Exit Reader, click on the drop down menu and select None from the options. Click on Okay and close out the Editor.

Issue Trouble with I/NET to Building Operation bindings. Site can bind an internal I/Net AO to a analogue value in Building Operation but the value won't update. Value appears with a blue triangle that says "unresolved".  Environment I/NET Seven together with StruxureWare Building Operation Cause I/NET points are integrated into Building Operation as points. When you upload the device configuration to the Enterprise Server, the configuration and point information are created in the System Tree pane. You edit and command the points as needed, using WorkStation and I/NET Seven editors. There are ten possible point types available in I/NET: Analog input (AI) Analog output (AO) Discrete input (DI) Discrete output (DO) Discrete alarm (DA) Discrete monitor (DM) Discrete control (DC) Digital input (GI) Digital output (GO) Pulsed input (PI) Resolution For any I/NET inputs (AI, DI, DM, GI and PI) it is only possible for operator changes to be made via the Building Operation Properties. It is not possible to programmatically control I/NET inputs and therefore not to be able to bind an output to an I/NET input point. It is also not possible to programmatically change any points Test state, any outputs (AO, DC, DO and GO) Manual state. And finally it is not possible to programmatically acknowledge an alarm. Therefore it is not possible to bind any script, schedule, FB, etc to any I/NET Points Test, Manual, Alarm Acknowledge or input point.

Issue DMO and SMO from SQL Environment DMO and SMO from SQL Cause A site which was running I/NET and StruxureWare Building Operation, and as required, I/NET is running as a service. The SQL DMO caused an issue with I/NET running as a service and interrupted the INET service. What is SMO and DMO DMO is part of SQL 2005 backwards compatibility. Which has to be installed when going to SQL 2008 to allow the old I/NET database to be imported. With SQL 2008 they now use SMO instead of DMO. You cannot remove DMO without creating a new data base.  Resolution I/NET SQL interface is based on DMO (Distributed Management Objects) so it will not work with SMO (Server Management Objects). That is the reason the backward compatibility must be installed.  Sites that are using a 64 Bit Workstation and 64 bit SQL then there is a 64 bit backward compatibility that should be installed. The 64 bit BCM is in the Support folder on the original install CD called SQLBCM_64Bit.

Issue The thermostat appears to be in OFF mode and can't be cycled through the modes as indicated by the manufacturer's directions.   Environment Venstar T2700, VST2700 thermostats for red-wire control connected physically to a controller Cause It seems that the polarity of the dry contact was set to the default Normally Open (NO) state. Using the Venstar EZ-Programmer to apply the correct settings for use with an occupancy point did not overwrite the polarity of the Venstar's dry contact, but did overwrite the Dry Contact Operation. Also, by wiring everything up first, we did not power up the thermostat to change the mode before it got the closed dry contact command from the BAS. So when we did power everything up, the dry contact was closed, but the thermostat understood that this was an "unoccupied" command since it was still set to NO. Even though the security settings allowed the mode to be changed, when Dry Contact Operation is enabled, the mode can only be changed in occupied mode. When the thermostat goes unoccupied, it stays in whatever mode it was in previously, and controls to the unoccupied setpoints. By not realizing that the EZ Programmer didn't overwrite the polarity, we assumed the dry contact operation and polarity were correct and a closed dry contact would enable the occupied mode.   Resolution This issue can be resolved by powering up the thermostat before connecting the dry contact relay and changing the mode to "auto". If already wired, make sure the dry contact polarity is set to Normally Closed (NC) and Dry Contact Operation is "Yes". Then the modes can be cycled while occupied. < acc0432manualrev1.pdf="" manuals="" support="" www.venstar.com="">

Issue DDC lines from I/NET sublan devices are not showing up in StruxureWare Workstation Environment I/NET to StruxureWare integration Cause I/NET ASC devices, particularly the MR-VAV series, can sometimes be configured as MRs. When this is the case, most of the I/NET processes will function, so that this is easy to overlook. Resolution Open I/NET Workstation Connect to the controller that is not showing the DDC lines from the subLAN Select Edit>Controller>MCU Configuration Change any controller that is an MR-VAV to an ASC Change any MRxx series controller to an MR. Perform a Station Save Open StruxureWare Workstation Right Click on the Selected Controller and select Upload Check to see if the DDC lines are now showing up If not, you may need to update I/NET Network Configuration, then deleted and rediscover the I/NET devices affected.

Issue Unable to Edit I/NET Trends, Schedules or DDC from StruxureWare Building Operation Workstation on certain computers. Environment StruxureWare Building Operation Workstation Cause I/NET functions are launched from StruxureWare Building Operation Workstation using both graphics and Right Click menu items. These functions are not part of Building Operation Workstation, but are simply portions of the I/NET workstation application being launched from Building Operation. Resolution I/NET workstation should be considered an Engineering Tool for I/NET controllers. Any User that needs to make programming changes must have I/NET installed.

Issue When adding a filter, an error shows that Entry already exists. But this name is not listed in the Filters window. Sometimes the filter is defined, but it is not shown in Filters window, especially after a database restore in DBCreate. After defined a filter on the server, this filter can be chosen on the remote client or remote client with I/O. It works fine for the server, but after selecting it on the client, nothing shows up with a blank screen. Product Line TAC INET Environment I/NET Server/Remote Client or Remote Client with I/O Cause If your workstation type is configured as a Client or Client w/IO, a Global Filter option will be available. If you activate this option, this particular filter will be available to other workstations that use the same server. But if not, this filter will only show up on that specific client. So each filter will be bound with a hidden parameter called FilterHost. If the FilterHost is 0, then all the server and clients can see this filter, while if the FilterHost is a specific number, only the client with that Host Number can see this filter. But sometimes there is something wrong with the database that the setting of the filter setting doesn't match the record in the database. Resolution For issue 1, check the setting on all the clients to avoid name conflict with each other. The filter setting for all the clients are stored in the database of the server. For issue 2, change the Host Number of current client to match the original Host Number setting when the database is backup on this client. For issue 3, delete this filter, maybe defined in old version of I/NET, and re-add it again. If all the solutions don't work, please contact Product Support for help.

Issue Xenta 913 is locked up randomly, and it needs reboot to make it return to work. When referring to the error log on the web page, the following errors show up: event power PowerFail 1 System is safely shutdown (Error#:49154) event power InitSYS 1 System start - power on (WARMSTART) (Error#:49156) Environment Xenta 913 BACnet Cause Possible cause is the baud rate for BACnet communication is too high that Xenta 913 can't deal with it properly. Resolution It is recommended to decrease baud rate for BACnet communication to 9600 or 19200 bps, and then Xenta 913 should work fine now.

Issue When installing SQL server 2008 or SQL 2008 R2 to manually an instance for I/NET, Vista or Continuum, sometimes an error "Invoke or BeginInvoke cannot be called on a control until the window handle has been created" will show up. Environment SQL 2008 / SQL 2008 R2 Vista I/NET Continuum SmartStruxure Cause This issue is happening because of a behavior change in .NET that is exposing an issue with SQL Setup User Interface (UI). Resolution Generally, if you just rerun the installer, it won't hit the issue again. If this can't help, just manually create a C:\temp folder and it will work fine.

Issue HID Biometric reader product obsolescence. Environment HID Desfire and Mifare Smart card and Fingerprint readers. As used on Continuum and I/Net Access Control. Cause HID have discontinued these readers. Resolution HID have discontinued production of their SmartTOUCH SB10 and SBK10 Desfire and Mifare fingerprint readers. Part numbers affected are: HID Ref: 800-8052, SE P/N 654 1903 000 - SB10 Desfire Fingerprint reader. HID Ref: 800-8057, SE P/N 654 1904 000 - SBK10 Desfire Fingerprint reader with keypad. HID Ref: 800-8050, SE P/N 654 1901 000 - SB10 Mifare Fingerprint reader. HID Ref: 800-8055, SE P/N 654 1902 000 - SBK10 Mifare Fingerprint reader with keypad.

Issue When clicking on the Right Click Menu for I/NET Converted TGML Graphic on remote SmartStruxure Workstation, nothing happens even though I/NET has already been installed on this computer and I/O server has been registered as service. Environment SmartStruxure I/NET Seven 2.44a through to 2.48 Remote Workstation Cause On a 32 bit OS and a 64 bit OS machine, the I/NET Converted TGML Graphic are different because I/NET default software installation path is different: 32 bit OS: C:\Program Files\INET Seven\ 64 bit OS: C:\Program Files (x86) \INET Seven\ Since the Right Click Menu calls the I/NET program, if the graphic is converted on 64 bit OS machine on the Server, it will not work on the Client machine with 32 bit OS. And vice versa. Resolution NOTE: This right click menu option will only function when the graphics page is located on an Enterprise Server where a copy of I/NET is installed on the local Workstation. This feature provides access to graphic functions run using the installed I/NET software so will not work when that software is not locally available. It is therefore not available when using WebStation or when viewing graphics located within a SmartX Server. From I/NET version 2.49, this right click menu option will be removed from this editor and NO LONGER be available. there are mixed versions of 32 bit OS and 64 bit OS between ES and Remote Workstation, the I/NET graphics need to be converted on 64 bit OS machine. And then follow the steps below: 1. Manually create C:\Program Files (x86)\INET Seven\ folder on 32 bit OS machine. 2. Uninstall I/NET and reinstall it under the folder created instead of default one. Then the Right Click Menu should work now.

Issue Integrated NPR Dial on a Xenta 527 (Web) failed to connect Environment I/Net Site with Integrated NPR Dial Cause There is a current issue with Xenta 527 (Web) and the Firmware load of 5.1.9-15 at the present time. This release will not support the Modem connection. This issue has been given to Engineering for Repair. Resolution The "Work Around" is to go back a Firmware release. For the time being, until the 5.1.9-15 is fixed, load 5.1.8-10 in the Xenta 527 (Web) and the Modem will work in this load.

Issue Distributed Link Architecture DLA with StruxureWare Building Operation Environment Large TAC I/NET Seven site with StruxureWare Building Operation installed Cause Does Distributed Link Architecture (DLA) supported with StruxureWare Building Operation as the front end? Resolution TAC I/NET allows you to define a system-wide total of up to 100 links in order to connect controller LANs to the TAC I/NET system. In the traditional TAC I/NET system, if you use Xenta 527 Routers (NPRs) to connect remote controller LANs (i.e., sites) to TAC I/NET, each site consumes one unique link address. This limits the traditional TAC I/NET system to a maximum of 100 sites. The purpose for adding Distributed Link Architecture (DLA) capabilities to NPRs, and to the TAC I/NET IOServer, is to allow multiple NPRs to share the same link number. In a system that is configured to use DLA-enabled NPRs, up to 64 sites can share a single link address. The shared link is referred to as a distributed link. The use of distributed links allows the TAC I/NET system to support up to 6400 sites. Note: TAC I/NET’s system-wide limits of 6,400 controllers and 100 link addresses must be observed, regardless of whether or not DLA functions are enabled. For example, if your TAC I/NET system already contains 6400 controllers, implementing DLA will not allow you to expand the system with additional sites of controllers. TAC I/NET Seven DLA is supported with Building Operation

Issue Bindings on every I/NET point in a converted graphic show the Server 1 instead of the correct server name Environment StuxureWare Building Operation Workstation I/NET 2.42 or higher Cause The INET Interface path parameter set in the Export INET Graphics to TGML converter does not revert to default after each conversion.   If the parameter is set to: /Server 1/INET Interface All binds will use that path even if the Server is named 'Building 1' Resolution OPTION 1 - Reconvert Graphics Change the INET Interface path to reflect the correct location. The most common is: ~/INET Interface The '~' symbol points the remainder of the path to the Server that the user is logged into during the import. If the user is not logged into the correct server, this may cause errors. INET Interface is the default name of the I/Net Interface but can be changed. For a site where the I/NET interface is named 'INET' and the Server is name 'Enterprise Server' the INET interface path could be set to: /Enterprise Server/INET OR ~/INET Option 2 - Change Server Name If every path on the I/NET interface references the incorrect server name: Change the Server Name to match the bindings Verify that the bindings now function with the matching Server Name Change the Server Name back to the desired name. The bindings should follow the name change.

Issue Logging on to IPM from the web and the default password is not recognized. An error comes up saying Invalid user. Product Line EcoStruxure Building Operation, TAC INET Environment StruxureWare Building Operation, I/Net Cause The default password can be used on the I/Net side but it is not being recognized when logging in from the StruxureWare IPM. Resolution To resolve this issue, the following step needs to be followed: From the original installation folder, find and unzip the Sboscripts.zip from ‘\InetWeb\UpdateScript' folder. Follow the SQL patch delivery process of I/Net. Run 'Sboscripts.exe' on a DOS prompt. Enter the SQL Server Instance name and login credentials for the script to run If the SQL Serve Instance name is not known, open up DBCreate and it would be displayed on the editor, more than likely it would be 'SQLEXPRESS" or blank per the INetDB Configuration. Once the script is complete, launch StruxureWare and enter the default passwords again and it should allow you to successfully log into the program.

Issue Correct Boot Up sequence for I/NET Enterprise Server Level Integration to StruxureWare. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET to StruxureWare Enterprise Server Level Integration Cause Sites which are recovering from a power failure are are using Remote Client with I/O may have certain failures within the system. A site where I/NET works on the local PC but devices seem offline from the Enterprise server may have had the Enterprise Server Start before the I/Net I/O Server A site where I/NET points can be controlled from the ES, but messages are not received by either the ES or I/NET AMT may have had the SQL server start after the ES or I/NET IO Server started. Resolution Restart the SQL Server or Server PC Restart the I/NET I/O Server and ensure it is running as a service Restart the Enterprise Server In order to add the I/NET I/O Server as a dependency for the Enterprise Server use the command prompt line below. Be sure to change the 1.X to reflect the current version of SBO installed. Open the Command prompt Enter the command: sc config "Building Operation 1.X Enterprise Server" depend= inet7iosrv