Building Automation Knowledge Base

Issue Need an alert message sent out to notify when a controller disconnects from the network Product Line Access Expert Environment Access Expert Controller Access Expert Premise Software Access Expert Hosted software Cause Controllers can potentially disconnect from the network. Knowing when can help troubleshoot the cause. Resolution Having an alert based on a long time disconnect event can help to prompt an investigation. The time considered for this disconnect event is adjustable within the instance settings. Right-click the event "Controller Disconnected (Long Time) in event definitions and select view event history Right-click any of the events and select add Email template Create an email template using the pre-canned expressions and plain text Create an Alarm Action, select Notification when adding the action Fill out the template with the Email Template and who the recipients should be Create an Alarm Definition Assign Event type: Controller Disconnect (Long Time) Assign Alarm Action: Alarm action created in step 5

Issue If a SmartX Server is using External Log Storage how often are new trend log data and events sent to the TimescaleDB? Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When a SmartX server is using External Log Storage many of the trend logs and all new event records are sent to a TimescaleDB for storage. Resolution New event records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them. Some records as "Edit" and "Comment" are sent immediately. New trend log records in the SmartX Server will be sent to the TimescaleDB when 500 records are collected but the SmartX Server will wait a maximum of 10 seconds before sending them.

Issue Need an alert message sent out to notify when a controller disconnects from the network Product Line Access Expert Environment Access Expert Controller Access Expert Premise Software Access Expert Hosted software Cause Controllers can potentially disconnect from the network. Knowing when can help troubleshoot the cause. Resolution Having an alert based on a long time disconnect event can help to prompt an investigation. The time considered for this disconnect event is adjustable within the instance settings. Right-click the event "Controller Disconnected (Long Time) in event definitions and select view event history Right-click any of the events and select add Email template Create an email template using the pre-canned expressions and plain text Create an Alarm Action, select Notification when adding the action Fill out the template with the Email Template and who the recipients should be Create an Alarm Definition Assign Event type: Controller Disconnect (Long Time) Assign Alarm Action: Alarm action created in step 5

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

Issue When mapping the EcoStruxure Building Operation (EBO) Trend Logs to EcoStruxure Energy Expert, not all trend logs are visible in the ETL Tool 'Load Sources'. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Energy Expert Cause The EBO user credentials entered into ETL for connect to the EBO Database must have access to BOTH the trend log itself, and the point which the trend log is logging. Resolution Edit the EBO user which the ETL is using to connect to EBO and give a minimum of Read Only access to both the Trend Log in question and the Point being logged  and then in the ETL re-run 'Load Sources'.  The additional points which were missing before should now be available for mapping

Issue Where Sigma utilizes the site Ethernet network, and that the network consists of multiple subnets, or is using Sigma DNN's with ARCnet or ethernet secondary LANs. Global object values are not received at the receiving controller when it is on a different subnet to the sending controller. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,

Issue Duplicated SFE Short Form Edit graphics Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Sigma Cause A duplicated set of Short Form Edit graphics are created but are in a different language appear along side the original SFE graphics when using Data Import with a Sigma transition into EBO The example below shows the original DataImport was completed in English, the second DataImport was completed in Danish. Resolution Before a Sigma DataImport is undertaken, ensure that the correct language is set in EBO. Delete the Sigma Interface, set the correct language and start the transition again. Note: By deleting the Sigma Interface, this will delete all the SFE graphic links on the objects and a clean set of SFE graphics will be created on all the objects.

Issue Is it possible to include the Comments field from Extended Logs into Report Server Reports? Product Line EcoStruxure Building Operation Environment Building Operation Reports Server Cause Regardless of the new Reporting Features in EcoStruxure Building operation (EBO) 3.2, users of existing systems up to and including EBO 3.1 are asking if it is possible to include the Comments field in Extended Logs within the Enterprise Sever to enhance the data in RS Reports? Resolution Extended Log Comments within the ES are not available to Report Server reports today and given the move to new Reporting Features now available in EBO 3.2 it is unlikely that an Enhancement Request for such a feature would be implemented quickly. Therefore, the suggestion here would be to migrate the Extended Logs to External Storage via TimeScaleDB where all the Extended Log data (including the comments) can be freely manipulated by 3rd party Reporting Products.

Issue Following a successful configuration of the Continuum Transition Tool (CTT) it has been noted that some ongoing changes in Continuum do not seem to then be migrated through to the Security Expert database. Product Line Andover Continuum Security Expert Environment Continuum Transition Tool Security Expert Data Sync Cause It would appear that on occasion, some changes made to Continuum Areas after the initial CTT Transition is completed, fail to be exported from the Continuum DB by the CTT in its periodic update, This can be verified by examining the actual CSV output and seeing that certain known changes to Areas  are simply not present.  The actual Security Expert Data Sync is working correctly but if the changes are not exported by the CTT then they cannot then be imported by the Data Sync Service Resolution Although this is not currently resolved, it is documented as a limitation of the Andover Continuum System. Page 21 of the Transition Guide Security Expert - Continuum Database - Transition Quick Start Guide states that the Last Changed field of an Area object is only updated if the object is edited in a specific way. Since the CTT uses the Last Change field to decide what new object changes need to be exported, this legacy issue in Continuum directly affects the update to Security Expert if the changes are not made as advised above.

Issue From a legal Microsoft Licensing point of view, it is important to be clear how many Client Access Licenses (CALs) are required when using a Report Server with SQL in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause While Microsoft Client Access Licenses are not required to make a Report Server installation function, ANY system which makes use of Microsoft SQL must consider the provision of sufficient purchased CALs to remain legally compliant and avoid potential fines. Resolution The Report Server Reporting Agent Service which is responsible for reading the data from the Enterprise Server (ES) and storing it the Microsoft SQL Server Database, will use one connection to the SQL Server. and therefore, requires one CAL. 

Issue On occasion IT Professionals may wish to know if Continuum can be installed/deployed via Microsoft System Centre Configuration Manager (SCCM). Product Line Andover Continuum Environment IT Installation/Deployment Cause Microsoft SCCM is a well-established platform for the deployment and management of installed software in an IT Environment, but since Continuum is now an older Legacy Schneider product it is unclear if it supports being deployed in this way. Resolution While Continuum 'may' work when deployed via SCCM, it is untried and untested at this time. Also given that Continuum is a Legacy product, there are no plans to test and support SCCM in the future.

Issue After moving the License server to another computer the license server address in the License Administrator is changed to the IP address of the new computer, but EBO Workstation gets a license error when trying to login to it. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The License Administrator can be used to select which license server EBO uses. This is done by going to the License Server Address tab and entering the license server address in the License Server Address field. Note that the license server address must be preceded by an @ in order for it to work, e.g. @servab48. The License Server Address in The License Administrator is not always used when Workstation or the Enterprise server asks for a license, Resolution The request for a license is handled in the following order:   If there are licenses located locally on the machine running WorkStation/Enterprise server (activated from ASR files), those are used first. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is used. This registry key contains all license server addresses that have been successfully used to obtain a valid license previously. If this key is not empty, each server contained in the registry key value is asked for a valid license until one is obtained. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, and the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is empty, the license server set in License Administrator is used. The license server address is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\StruxureWare\License Administrator\TACLIC_LICENSE_FI

Issue Implementing a pre-entry access card anti-passback using Plain English program Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause The anti-passback implementation in Continuum engages when the credential holder enters the area as detected by the door switch/contact. (if no door switch is configured, then the credential holder is considered to have entered the area immediately after access has been granted by the system) When doors are located in close proximity to each other, as is the case with a bank of turnstiles, for example, the built-in anti-passback scheme is easily defeated as a cardholder is able to unlock multiple nearby turnstiles before triggering the door contact and engaging the built-in anti-passback functionality. Resolution The simplest solution to the issue described above is to configure the door objects WITHOUT a door switch/contact, this, however, is not always possible depending on on-site requirements. A second solution is to take control of the doors using Plain English. The solution presented here is for a bank of three turnstiles, (A, B, and C), it uses a PE program per turnstile. The solution can easily be adapted for a bank of less or more turnstiles. NOTE: The PE programming here is provided as a sample, for guideline purposes only, the programs are not intended as a complete solution, significant modifications may be required for site deployment. Program code for door/turnstile A 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' |_____X______X______X______ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the 'initialization line which specifies which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileB, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_B, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_B, theLastCrdTime_C Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_A theTurnstileB = Turnstile_B theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_A_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileA_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM '------------------------------------------------------------------------------------------ Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile B 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of the following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_C '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_B theTurnstileA = Turnstile_A theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_B_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_B_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileB_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_B_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile C   'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileB 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_B, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_B '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_C theTurnstileA = Turnstile_A theTurnstileB = Turnstile_B 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_C_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_C_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum thisAlarmPoint = TurnstileC_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_C_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING        

Issue An SP-C-WEB needs to be upgraded.  Can this be done without removing the controller? Product Line Security Expert Environment Security Expert Controller (SP-C) Security Expert WEB Controller (SP-C-WEB) Cause Due to site expansion, it is necessary to upgrade an SP-C-WEB to an SP-C.  Resolution It is not possible to upgrade an SP-C-WEB to an SP-C in the field. The SP-C-WEB will need to be replaced and re-programmed via Security Expert 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. Issue During certain situations, it may be required to remove and re-install PCT to address software conflicts with other software applications. While trying to remove/install PCT you may receive an error preventing you from completing the installation. The setup had detected that no version of SBO Project Configuration Tool is installed.  The specific command-line options require that the application be installed to continue. The setup will now terminate. Error: -1603 Fatal error during installation. Consult Windows Installer help(Msi.chm)or MSDN for more information. Error 1722. There is a problem with this Windows Installer... Product Line EcoStruxure Building Operation Environment Client versions (64 Bit Only): Editions: Pro, Home, Enterprise Windows 10 Windows 8.1 Windows 8 Windows 7       Server versions (64 Bit Only): Editions: Standard, Enterprise Server 2008 R2 Server 2012 Server 2012 R2  PCT versions (64 Bit OS Only): SBO Project Configuration Tool v 1.0.0.487 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.0.0.510 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.0.47 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.1.49 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.2.57 - SmartStruxure Solution - Software Cause In order to get past a possible installation loop, you will need to locate and delete the following Windows registry key: [HKEY_CLASSES_ROOT\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B] Resolution Note: Always make a backup of your registry before making any modifications.   Run regedit.exe Locate/Search: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Delete Registry Key entry: B2A4F0AEC8BB0E2438706F07E2E2560B  

Issue Not sure how to configure sending emails to multiple recipients when an Input or Area goes into alarm. Product Line Security Expert Environment Security Expert SP-C-WEB Cause Correct formatting must be used when sending alarms to multiple email recipients. Resolution Separate each address with a semi-colon and surround the entire string with double quotes, see examples below.   Security Expert Navigate to Events | Actions, create a new Send E-mail Action and add your multiple addresses to the E-mail Address field. "address1@email.com;address2@email.com" Email Addresses The email address field is limited to a maximum of 128 characters. All email addresses must be within this 128 character limit to be sent correctly. SP-C-WEB To add multiple recipient addresses, navigate to Programming | Areas or Programming | Inputs. For an Area, select the Configuration tab and add a recipient email address to the command window and use the format:email:"address1@email.com;address2@email.com" For an Input, navigate to the Commands window for your selected input and use the format: email:"address1@email.com;address2@email.com"

Issue Import Vista Alarms and Events into an Excel file Product Line TAC Vista Environment Vista 5 SQL 2005 Cause Unable to import Vista Alarms and Events in to excel file from Vista Resolution Select Data > Import External Data > Import Data as shown in below screen capture.   Select New SQL server connection as shown in below screen capture.   Enter Vista SQL Server instance name as shown in below screen capture.   Select taclogdata from dropdown menu as shown in the below screen capture.   Select Event table as shown in the below screen capture.   Rename .odc as .dsn as shown in below screen captures.   Click finish button.   Select Edit Query as shown in below screen capture.   Select SQL as shown in below screen capture.   Paste the Query as shown in below screen capture. Click OK button to apply the query.   Click OK button as shown in below screen.   Click OK button as shown in below screen.   Events are imported in to Excel   Query for Events based on dates: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN '10/12/2009' AND '10/12/2009 23:59:59.997') Query for One Day Events: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE()) Query for Alarm based on dates: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (Event.EventDatetime BETWEEN '08/24/2010' AND '08/25/2010 23:59:59.997') Query for One Day Alarm: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE())

Issue   An error occurred while setting the system language property. Please validate that your language resource files are valid. Invalid format. (Subsystem: LNS, #40) Product Line TAC Vista Environment LonMaker Cause Resource File Languages have become corrupt. Resolution Restore the Resource File Languages:  Shut down LonMaker. Go to http://www.lonmark.org/technical_resources/resource_files/ At the time of this article, the latest version is LonMarkResourceFiles1304.exe.  Download this file.  If a later version exists, download the latest file. Run the executable. Restart LonMaker.

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue All values in the Xenta 102-AX Plug-in are blank. Product Line TAC Vista Environment Xenta 102-AX Plug-In LonMaker Cause If the Resource File Languages have become corrupted on your PC, then the plug-in will not know how to display the required data. Go to LonMaker > Network Properties > Resource File Languages.   If the only Language listed is "ENU," then the language files are corrupted. ENU is the default language and will display all data in the LNS environment -- plug-ins, browser, get values -- in an enumerated format that is not usable. Everything will continue to work, but monitoring data in the LNS environment and configuring ASCs via plug-ins will be impossible. Resolution Restore the Resource File Languages: Shut down LonMaker Go to http://www.lonmark.org/technical_resources/resource_files/ Download LonMarkResourceFiles1300.exe Run the executable Restart LonMaker Check Network Properties again. US English should be listed and the plug-in should populate with data. Note: There may be Beta versions 13.04 and 13.10 on this website. Do not use these LonMark resource files. The newer versions cause errors in the 102-AX plug-in. For more information see Opening the Xenta 102-AX plug-in results in "request for LonMark Object status" error .