Issue An email alarm generated in Continuum in not sent on Outlook; the email remains in the Outbox. The attached error is displayed in Outlook:   Environment Continuum Cyberstation version 1.94, Outlook 2010 Cause In this instance, Outlook would not send the email because the PC was not part of the Windows Active Directory Domain. Resolution Add the PC to the Windows domain.

Issue Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause When configuring extended logging in the BACnet application folder, these objects are not available when performing a device discovery from the AS or ES. Prepare one AS with a BACnet point Create a trend log on the BACnet point Create an Extended log for that BACnet trend log From a second AS, the BACnet objects are available after a Device Discovery except for the Extended log object. StruxureWare Building Operation online help for “Configuring Extended Logging for a BACnet Trend Log” states:    ***Key Concept: Extended trend logs are not BACnet objects. These are StruxureWare Building Operation exclusive. The term "BACnet Extended Trend Log" does not exist and is a misnomer. Resolution The main reason is that extended logs are not defined in the BACnet standard; they are proprietary to EcoStruxure.  Everything that is proprietary to EcoStruxure Building Operation is not exposed to BACnet including graphics, script & function block programs and central IO points are not directly exposed, but have to be bound to BACnet I/O objects. The extended log serves the purpose of expanding a log on a larger capacity server.  A trend log on an AS would be more appropriate to extend on an ES. If you have a trend log in an external BACnet device (like a b3 or a 3rd party device/system) then you would want an extended log in the AS, to collect from that device (and then maybe a larger extended trend on a parent ES). If there is a local BACnet trend log in an AS (in the BACnet interface application folder) that is required to be larger, consider increasing the buffer size property of the one log that is needed (the default size of 10 may be too small, and increasing to 1000 up to 5000 (extended log size) may be an option). That would be most interoperable with other (3rd party) BACnet clients that need access to the trend log data.

Issue RJ11 cable has been lost and a new one is required. Environment Roam I/O Cause Unable to find the cable part number  for ordering. Resolution The P/N for the black RJ11 cable is 01-0100-315. This can be ordered through your local Customer Care Center. Please select your country from the list for local contact details.  

Issue The I/A Series G3 Platform Software Manager indicates "Not Available Locally" when connected to the remote platform (ENC or JACE). Environment I/A Series G3 - All versions Cause Upon start of Workbench, the modules residing in the local Workbench module folder are scanned by the software.  During this process, new and/or updated modules are copied and saved into the local software database.  "Not Available Locally" indicates the associated module is missing from the local Workbench software database.  The following example finds the Installed Version of tacMs at TAC 3.4.64.4 with the Available Version missing with the comment "Not Available Locally." Resolution There are two methods to correct this issue. Method 1:  Copy the module directly into ~\modules directory. This makes the module(s) available in your Workbench environment, and also available to install in other remote platforms.  When the installer runs, the module(s) are also copied into your software database, available for installation. This is the typical choice. Method 2:  Copy the module into your ~\sw\inbox directory (or, use the equivalent “Software Import” feature in the Software Manager). In this case, the module(s) are not used in your Workbench environment, but are available in your software database for installation in remote platforms. If the module is invalid or corrupt, the software manager will generate and place the module in the "failed_imports" folder (e.g. unable to read the manifest files, class files, etc.).  Verify the module is valid. Reference the Niagara AX Platform Guide - Software Manager for additional details.

Issue Unable to pass data to an Enterprise Server from a UNC Environment R2 Niagara Cause bad subscription access denied 401 error Resolution Check address book and system properties.

Issue When making changes to the Personnel Manager to show custom attribute names, are these changes seen on all Workstations or just on the Workstation where the changes are made? Environment Continuum Personnel Manager Cause Not sure if these changes will need to be made to all Workstations or if this is only required to be done once. Resolution Any changes to the display name of the various attributes in the Personnel Manager using the Customize Attributes setting are applied to the database and will be seen by all other Cyberstations on that network. Basically, you will only need to make these changes once and not for each Workstation in your Continuum system.  

Issue Getting error - Cannot start component: Asd Block Output Proxy Ext during the startup of the I/A Series G3 tacAsd driver.  The error appears as follows: ERROR [16:31:24 04-Mar-13 CST][sys.engine] Cannot start component: Asd Block Output Proxy Ext java.lang.ClassCastException: com.tac.tacAsd.point.BAsdPointBlockDeviceExt incompatible with javax.baja.driver.BDevice Environment I/A Series G3, tacAsd, ASD driver Cause The driver appears to operate however errors are displayed during the station startup sequence.  The error is typically related to a set of BAsdPointBlockDeviceExt objects that were duplicated as a child of the points deviceExt. Resolution Review the Points folder for each ASD device and remove the duplicated or improperly placed BAsdPointBlockDeviceExt objects.  The Batch Editor can also be used to assist in locating the duplicates. Open the Batch Editor from the Program Service and select Find Objects Using the BQL Query Builder - select (Custom Type), tacAsd, AsdPointBlockDeviceExt - select OK. This will list all AsdPointBlockDeviceExt extensions and their associated path.  There should only be one Points child folder for each device.  Locate and delete the duplicate Points folder and objects.

Issue Get "Device has a different hardware version (hardware version X) than the project (hardware version X)" error message, when downloading an Xbuilder project to a device. Environment Xbuilder 5.1.X Xenta Server 5.1.X with hardware 1, 2 or 3 Cause There is a mismatch between the project's settings and the device's hardware version. Resolution Correct the Xbuilder project's setting to match the device's. Ensure that the hardware version shown in the "Hardware Version"  property field is the same as the device's.

Issue After installing WorkPlace Tech, the Purchase program is accessed with no issue.  All the information is added including a Field Office Information, Shipping Information, End Customer Information, a WIBS serial number and a Part Number from the Package List.  When clicking on the Add to Order List button, a pop-up window indicates that the program cannot open the License File.   The license file does not accept any attempts to write to it. Environment WorkPlace Tech 5.x Windows 7 Cause A Windows user account setting is preventing proper operation of executable files. Resolution If the user account settings cannot be modified, then right-click on the executable file and select "Run As Administrator".  Right-click on the executable file and go to Properties > Advanced and select the checkbox for "Run As Administrator".  This applies the "Run As Administrator" setting always.  Now just double-clicking on the executable file is sufficient.

Issue Insufficient information for the STR602 terminal detail / assignment Environment Sensor Cause The installation instructions does not give insufficient information regarding the connections of a STR602 sensor. Resolution The STR602 combines the RPW4425 and DRT3453 into one temperature and setpoint unit. The STR602 is a 3 wire device using a common 0V between the setpoint adjust potentiometer and the temperature sensing negative co-efficient thermistor. The terminations are: STR602 term 22 (Setpoint) STR602 term 23 (Temp 'C) STR602 term 24 (0Vcom) - this is the common of both the temperature sensor and the setpoint potentiometer. Setpoint Resistance (for BAS/Sigma use Lookup table 1, for SmartStruxure use the Satchwell thermistor ) Sensor Resistance  (for BAS/Sigma use Lookup table 1, for SmartStruxure use the Satchwell thermistor )

Issue Getting errors when opening Web Pinpoint or a Web client schedule. Environment Web Client Browser. Cause Communication back to the Web Client server is being blocked for Web Pinpoint and Web Schedules but other parts of Web Client are operating correctly. Errors displayed are: Resolution These errors are caused by a proxy server or firewall used on the site that is blocking some of the Web client data. Typically to remove: • Go to the Web Proxy or Firewall software • Edit settings - typically in the Advanced Tab • Disable HTTP Strict Mode • Save • Restart Proxy/ firewall   These steps may vary from product to product, but it is letting the majority of the Web Client data through in order to logon and view points etc, but blocking the Web Pinpoint and Scheduler data.

Issue When running TreeTech revision 3.1 or 3.2 attempts to open projects and edit object properties could result in the following error messages: "Failed to start viewproperty.exe. Verify path is correct" "Failed to start propeditor.exe. Verify path is correct" Environment TreeTech 3.1, 3.2 Windows XP,Vista, 7 Cause In TreeTech 3.1 the default path for projects was changed to support newer operating systems. Operating System Default Path Windows Xp\P C:\Documents and Settings\All Users\TAC\TreeTech\Jobs\ Windows Vista/7 C:\ProgramData\TAC\TreeTech\Jobs\ In revision 3.2 the path changed to use Schneider Electric.  Operating System Default Path Windows Xp\P C:\Documents and Settings\All Users\Schneider Electric\TreeTech\Jobs\ Windows Vista/7 C:\ProgramData\Schneider Electric\TreeTech\Jobs\ This can be seen live by creating a new project in TreeTech and observing the default path. Resolution Due to the fact that any previously created projects will not be moved when installing TreeTech revision 3.1 or 3.2 these files must be moved manually to the new default path. Once the project has been moved it will function normally without the error messages.

Issue DPUs / SCUs with addresses 28 thru 31 will give you "Deny Entry Tenant" message Environment 7798C & I/Net Seven rev 2.41 & above Cause During this time period, was the release of the OP5. This device occupies this address range. In I/Net Seven Rev 2.41 and 2.41A the 7798C has BIN file rev 1.12. With this BIN loaded on the 7798C will give you a "Deny Entry Tenant" on any card read. Resolution Replace the existing 7798C.BIN file with the 7798C.BIN rev 1.13 (out of I/Net Seven rev 2.43)   Please note that this bin file is not SBO compatible. At this time SBO has only a limited feature set for access control integration from I/NET.  Any SBO integration will limit DPU and SCU to addresses 0-27 on the 7798C  

Issue Are replacement covers available for the MicroNet 2000 wall sensors (MN-S, MN-SO, MN-SDK)? Environment MicroNet 2000 wall sensors: MN-S MN-SO MN-SDK Cause Customer wants replacement covers. Resolution As of February 28, 2013 replacement covers are available, part number MNA-STAT-1. Contact Customer Service to confirm price and availability, as they are subject to change.

Issue Getting the following error when trying to add a license. System error message: A value for property SalesContactEmail is required. Environment License Administrator Cause Incomplete or incorrect registration details Resolution Make sure all fields in the registration details are filled. Any field with a red border has not been correctly entered.

Issue Values only appear to update in Workstation when performing an upload. Environment I/NET Seven 2.43 and above StruxureWare Building Operation 1.3.0.978 and above Cause I/NET Interface Global scan rates are set to 0 (disabled) Resolution The Global scan rates defined within the properties of the I/NET Interface should be set to a value greater than 0 to display and automatically update values and controller status from the I/NET system.  The default settings are set to 60 seconds and 5 seconds for the device updates and point updates respectively. Image below shows the location of these settings within Workstation:

Issue Attempting to download and commission a Xenta programmable controller beneath a SmartStruxure AS results in the following error. The application generates successfully, the application downloads successfully, but the commission step fails. Environment SmartStruxure Automation Server Xenta programmable controller Cause There is some difference in the files generated on a save from the old Vista Menta editor, and the new SmartStruxure Menta editor. Resolution Create the Xenta programmable device Browse in the existing Menta file Service pin the device Open the Menta file from StruxureWare Building Operation. Go to File > Save. Close the Menta file. Commission and download.

Issue After creating a new Project and a new E: Equipment Database in TreeTech, the following error message appears when adding a new Network: Product Line TAC IA Series Environment Windows 7 TreeTech Cause TreeTech requires administrative rights to the Windows user account Resolution Right-click on the TreeTech shortcut Select 'Run as Administrator'

Issue Auto Generated Reports not running in 64-bit Environment Environment I/NET 2.43 64-bit I/NET 2.42 64-bit Cause Issue with windows scheduler is causing Auto Generate reports to fail. Resolution Modify existing or newly created auto generate reports. Click on the Recurrence button On the "Task" Tab, modify the "Run" string. At end of the string you will notice sch=<ScheduleName>. Add the characters"/T0" or "-T0" as shown below Before:   After:

Issue When point goes in alarm nothing is displayed in the active alarm viewer but when the point returns to normal the RTN shows up in the alarm viewer. Environment CyberStation Cause The Alarm Enrollment allows you to specify the transitions that gets sent to the active alarm viewer, make you the appropriate check boxes are checked. Resolution Configure the alarm enrollment to deliver both the alarm and the RTN