Building Automation Knowledge Base

Issue Xenta application has crashed or become corrupted and may exhibit one or more of the following symptoms: Controller not online in Vista Workstation I/O modules will not associate with Master Xenta controller will not accept download through System Plug-in Reset the Xenta controller by wiring a reset dongle. Clear the application/memory by shorting certain pins on the RS-232 port. Product Line TAC Vista Environment Xenta version 3.61 or higher, Xenta 280 (281, 282, 283), Xenta 300 (301, 302), Xenta 401 Menta System Plug-in Vista Workstation RJ45 Reset Tool Reset Dongle Cause Xenta may have crashed during download especially if interrupted during download. There are various other possible causes. Resolution Verify whether cycling power corrects problem. If that fails then perform the following steps:   If a Xenta 280/300/401 application has crashed and refuses to accept a new download, both from Vista and Menta, there is a way to clear the application (Xenta version 3.61 or higher). Manufacture a RJ45 jack with the following pins short-circuited: Note: This can be done by cutting off the end of an old Cat5 network cable, leaving approximately 4-6" of cable, and connecting the wires that correspond to the pins shown above.   Turn off power to the controller or remove it from the base plate. Put the manufactured RJ45 jack in the RS-232 port. Turn on power to the controller or re-insert it into the base plate. A forced Clear Application will be made. Remove the jack. Cycle power to the device to perform a fresh boot-up.

Issue I2867 inputs all read 1000 Degrees. Change out of controller does not remedy the issue. Environment All Infinet/MSTP controllers Cause Field controllers have an electrical range that they will properly operate. Typically this is +10% and -15% of the required power as described in the installation manual. If the power supplied to the unit is below this threshold, the CPU and power LEDs may appear normal, however the inputs and outputs will not function properly or at all. They are out of range. This situation must be remedied or damage can also occur. One way this can occur is if a properly grounded secondary transformer is not supplied. Supplying power from a piece of equipment that uses a step down 220/208-24 etc power supply can cause electrical issues should that equipment experience electrical problems. Resolution Supply proper, grounded 24Vac power to the controllers. Always check the power with a multi-meter and verify grounding.

Issue Often data is required to be exported out from the Continuum system for record keeping or for further analysis, what keywords can be used to help with this? Environment Cyberstation Plain English programs - all versions. Microsoft Excel Product Line Andover Continuum Cause Specific help is available in the product for specific keywords but how can these be put together to export data to .CSV format. Resolution As we do not advocate 3rd party system trying to directly extract data from the Continuum database, you should create a Plain English program in a Workstation that can export logged data directly from the controllers out to a .CSV or .TXT file.   Keywords to use for this purpose are: OpenFile WriteFile CloseFile   Details of the above Keywords are available in the Cyberstation internal help pages.   The attached example dump file could be run on a daily basis to extract temperature logs from a controller and save them to files with a date stamped naming convention.   Click to download the example WriteFile dump file. 

Issue .MTA file not updated .MTA file does not show the correct value when exported/imported The Menta project does not have the correct value when imported into a new database Product Line TAC Vista Environment Vista Menta Xenta OP Cause The upload/download parameter does not save any changes in values to the .MTA file. It only saves it to the device and Vista database. This means that if you export a project and import it to a new database the .MTA file will contain the initial values chosen when you last saved the Menta project. To get the values saved to the .MTA file, you need to edit the Menta project and save it again. However, to trigger the save correctly, you need to change the project. For example, add a comment or move a block, then hit save. Resolution  Below is the correct way to edit a project in a new database.  On the client PC, start by doing an upload parameter; this ensures that the values stored in the Xenta are present in the Vista database. Edit the Menta project(s) and add a comment (This can be a comment like "John brings the project home to make some changes") now the project can be saved, and all new values will be stored in the .MTA file.  Export the database/project Import the database/project to the new PC Make the desired changes Edit the Menta project(s) and add a comment (This can be a comment like "John has made the following changes ....") now the project can be saved, and all new values will be stored in the .MTA file. Export the database/project Import the database/project into the client's PC Now make a download parameter; this ensures the Xenta will get updated with the changes you have made.

Issue When attempting to login to Security Expert Web Client the below error is seen. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause The typical cause of this error is a mismatch in the security bindings between the SOAP Service and the Security Expert Data Service. For example if you enable the Windows Authentication checkbox in the Security Expert installer but not in the SOAP Service installer (or vice versa) then you have a mismatch. Resolution Either uninstall the SOAP service and update the checkbox selection to match whatever was selected in the Security Expert installer, or follow the instructions under Troubleshooting | Communication Fault/Failure in the SX-WEB - Security Expert - Security Expert Web Client - Installation Guide for editing the config files of the SOAP service to match the Security Expert Data Service.

Issue How to configure Xenta 913 to talk to C-Bus devices Environment Xenta 913 C-Bus Cause C-Bus is a public protocol which is commonly used in lighting control. Xenta 913 can be configured to talk to C-Bus devices with proper settings. Resolution A. Device Preparation C-bus 5500PC (PC Interface) RS-232 port        Xenta 913 RS-232A port NOTE: Communication is between Xenta913’s RS-232A port (NOT RS-485A port) and 5500PC’s RS-232 port (NOT C-Bus port).   Communication Cable Xenta913   C-Bus 5500PC, PC Interface RS-232A    <---------------------> RS-232 3(TX) <---------------------> 5(RX) 4(RX) <---------------------> 6(TX) 5(COM) <---------------------> 4(COM) Above number are RJ45 jack (as shown below) pin numbers.   B. Configuration Configure C-Bus device with CBusToolkit. Make sure to write down the Application number and the device’s Group number which Xenta 913 needs to communicate with.   Configure Xenta 913 in Xbuilder. Set Application number to 38 (38 is the HEX value of 56).   In DeviceEditor   The Group number (Hex value) needs to be inputted. Such as ‘01’ in the figure below. Same Group number can be inputted in different lines; however the ‘IO’ type should not be the same, such as ‘R’ and ‘W’ in below figure. ON Only and OFF Only types are NOT applicable to read-only values.   C. Verification In Xbuilder, drag all C-Bus points onto Value page. Download Xbuilder project into Xenta 913. Login Xenta 913 webpage and check if all point are correct and can be modified.   D. Additional Information Since CBusToolkit communicates with 5500PC by 5500PC’s RS-232 port, and Xenta 913 also communicates with 5500PC by 5500PC’s RS-232 port. Therefore, Only ONE device can be connected to 5500PC’s RS-232 port for CBusToolkit and Xenta 913.

Issue Can B-Link repeaters be used with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site release 1.xxx and higher Cause Need to add repeater(s) for EcoStruxure Building Operation Resolution For communication using RS-485, the versions of B-Link BACnet MS/TP Repeaters repeaters shown below were tested and passed for EcoStruxure Building Operation use. Part Number Description B-LINK-AC BACnet MS/TP Repeater, 120/240VAC B-LINK-AC-OP BACnet MS/TP Repeater, 120/240VAC, open class no enclosure B-LINK-AC-S B-LINK, AC, SMK B-LINK-DC BACnet MS/TP Repeater, 24VDC B-LINK-DC-OP BACnet MS/TP Repeater, 24VDC, open class no enclosure B-LINK-DC-S B-LINK, DC, SMK B-LINK-F-AC B-LINK, AC, FIBER B-LINK-F-AC-S B-LINK, AC, FIBER, SMK B-LINK-F-DC B-LINK, DC, FIBER B-LINK-F-DC-S B-LINK, DC, FIBER, SMK   Note the supported cable diameter in microns: 62.5/125. The first number, 62.5, refers to the diameter of the fiber cable's core. The second number, 125, refers to the diameter of the outside of the fiber cable's cladding. For more information see: BACnet b-Link MS-TP Repeaters - Andover Continuum - Specification Sheet b-Link Series - Andover Continuum - Installation Sheet Additional information about Fiber diameters from The Fiber Optic Association Fiber cabling information for an Infilink i2210 and the B-link-F Series

Issue Replacements for Satchwell sensors Product Line Satchwell MicroNet, Satchwell Sigma, Field Devices Environment DR DR3253 DRT DRT3451 DRT3453 DRT4453 DRT3651 DRT3652 DRT3801 DRT3851 DU DU4301 DUS DUS4302 DUSF DUSF4351 DUSF4352 DRTE DRTE2201 DRTE2801 DRTE2851 DRH DRH7702 DRH7703 DRTH DRTH7712 DRTH7713 DOT DOT0001 DOT0002 DOS DOS0002 DDT DDT1701 Cause Replacements for Satchwell Room sensors Resolution DOT0001/0002 Outside temperature sensor For CSC, KMC, MMC, IAC, MNN New part number: STO600/5126060000 DOS0002 Outside solar sensor For CSC, KMC, MMC, IAC, MNN New part number:  SSO600/5126050000 DR3253 Room sensor non-adjustable For SVT New part number: STR614/004604900 DRT3451 Room sensor exposed adjustment For CZU, CSC New part number: STR612/004604700 DRT3452 Room sensor concealed adjustment For CZU, CSC New part number: STR611/004604600 DRT3453 Room sensor non-adjustable CZU, CSC, CXR, CZT, KMC, MMC, IAC, MNN New part number: STR600/004604100 DRT4451 Room sensor non-adjustable As DRT 3453 in S-Link housing Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3651 Room temperature sensor exposed adjustment For CXR, CZT, KMC, MMC, IAC, MNN New part number: STR602/004604300 DRT3652 Room temperature sensor exposed + LED For MMC, IAC, MNN Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3801 Room temperature sensor fan switch On/off for CZU, MNN, IAC Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3851 Room temperature sensor fan speed switches As above plus medium and high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DU4301 Room sensor temperature For MNN & URC New part number: STR601/004604200 DUS4302 Room sensor temperature setpoint advanced basic sensor New part number: STR613/004604800 DUSF4351 Room sensor temperature setpoint adjustable fan auto/on/off fan override New part number: STR609/004604400 DUSF4352 Room sensor temperature setpoint advanced fan Auto/1/2/3 fan override New part number: STR610/004604500 DRTE2201 Active room detector Basic sensor Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2801 Active room detector On/off Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2851 Active room detector Off/low/medium/high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRH7702 2% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRH7703 3% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRTH7712 2% 0-10V DC humidity with Satchwell NTC TEMP OUTPUT For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DRTH7713 3% 0-10V DC humidity with Satchwell NTC temperature output For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DDT DDT1701, DDT1702 and DDT0001 Duct sensor non-adjustable New part number: STD660 5126030000 Contact Details: Titan Controls: http://www.titancontrols.net/ Sontay Controls https://www.sontay.com

Issue As a last resort when a Cyberstation is offline or there are difficulties connecting to a database, it is necessary to change the Workstation Initialization fields using the Windows registry. Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Partial objects in a database and registry entries occasionally get out of sync. Resolution Caution! Editing of the registry can be potentially dangerous, make sure someone who is familiar with using regedit completes this procedure. It is best to get a restore point of the Windows PC, if the version allows, prior to taking the following steps. Shutdown Cyberstation From Windows, Start> Run> Regedit Expand the hives(folders) to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls Right Click on Andover Controls and select export, name the file and save. (This file can be used to restore the original settings of this branch) Expand the folder to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls\Continuum\Settings Double click on Workstation Name (Change this to the name required Ex. WS1) Double click on Network Id and select decimal (Change value data to the number needed Ex. 192) Double click on Device Node Id and select decimal (Change value data to the number needed Ex. 192) Double click on Container Name (Change this to the name required Ex. WS1folder) Close Regedit Go into database initialization and select Workstation and you will now see those settings there. Go to the database tab and enter in the password for andover97 and click Ok. If the database initialization screen comes back(resolves to the database)with no errors, then this new instance of the Workstation was successfully created in the database. Launch Continuum Note: On a 64- bit system the registry location is slightly different. HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Andover Controls\Continuum\Settings   Continuum queries to get some of the Workstation Initialization parameters (Comments in parenthesis are not part of the query) select  * from device  (Device is the table name, uiname is the column where the Workstation Name can be found) select * from container (Container is the table name, uiname is the column where the Folder Name can be found) select * from device (Device is the table name, networkid is the column where the Network ID can be found) Device ID is not available, but is often the same as the Network ID

Issue Attempt to download license and see the below error. Failed to request license Error: Failed to store licence file Exception HRESULT:0x8007051B) (0x0000051B)   Failed to request license Error: Failed to store licence file Exception HRESULT:0x8007051B) (0x0000051B) Product Line EcoStruxure Security Expert Environment Security Expert Cause This error could be caused by a folder permissions issue. Usually occurring when Security Expert was installed without proper permissions to edit the folder or parent folder of where the license is stored. Alternatively it can be caused by a domain user account and local user account having identical names since Security Expert doesn’t know which user to check the permissions of when trying to save the license file. Resolution The possible solutions are shown in the order that they should be attempted: Right click the Security Expert license folder, (usually "C:\ProgramData\SchneiderElectric\SecurityExpert\License")and ensure that the Windows user has permissions to modify and view the contents of the folder. Ensure that the there is no local windows user with the exact same name as a domain windows user (e.g. LOCALHOST\admin, as well as ACME\admin). If this is the case change the name of one of the windows users so it doesn’t exactly match the other.  Perform a manual registration. Generate the .req file, go on the Licensing page, fill the form and download the license file. Then use the Browse button to import you license in Security Expert.

Issue In some situations, netcontrollers including BCX,CX, and ACX controllers will go offline when doing "teach" and then go back online after a couple of minutes. When reloading the controller, during the period of "teach", controllers go offline. Controller is online with Cyberstation but goes offline during the reload, reloading by class (Numerics, inputs etc) works fine. Environment Cyberstation 1.90~1.93 Windows XP sp3, Windows 7 professional. Cause 1. Some offline cyberstation has same IP address or Network ID as the cyberstation which you are doing the "teach" 2. Also caused by Cyberstation configured for DHCP instead of static ip address Resolution SOLUTION  1: Get rid off the offline cyberstation in the system, or modify ID address and Network ID of your cyberstation. Restart Continuum SOLUTION 2: Assign static IP address to the Cyberstation.

Issue Unable to send out emails using Gmail SMTP server (smtp.gmail.com) with the following error messages in the station's standard output. "javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first." Authentication has been enabled in the system.properties file as per Mail Service in a Niagara R2 UNC station configured correctly but e-mails not being sent to the SMTP server. Product Line TAC IA Series Environment I/A Series R2 Cause As with most public SMTP servers, like Gmail, the outgoing mail SMTP server requires TLS (Transport Layer Security) or SSL (Secure Sockets Layer) which I/A Series R2 does not support. Resolution Use an SMTP server that does not require TLS or SSL.

Issue PT1000 temperature sensors RTD Input Product Line EcoStruxure Building Operation Environment AS Classic, ASP  UI16, RTD-DI-16 - Central IO Module ASB, RPC, MPC Need for temperature to be extremely accurate PT1000 platinum resistance thermometer, RTD Resistance Temperature Detector Cause The AS Central IO Module Universal Inputs (UI16) were designed to interface to various thermistors that can have resistance values that are usually much higher than 1000 ohms. They were not designed to interface directly to a PT1000 RTD, and will not provide good accuracy when measuring these lower resistance sensors. The resistance input type was intended to allow for measuring the position of a 10K potentiometer that is used on some wall sensors. The accuracy specification for a resistance input is: +/-(7+0.004*R) ohms. This would result in an error of +/-11 ohms at 1000ohms – therefore a temperature measurement error approaching +/-3.0C. Resolution AS, ASP For RTD PT1000 (Pt100, Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) use RTD-DI-16 - Central IO Module, then choose 2 or 3 wire RTD Temperature Input ASB Choose 2-wire RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) RPC, MPC, MPV Choose RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000)   For more details see SpaceLogic Hardware Reference Guide

Issue When using the STR-350/351 as an I/O module in Menta (Options > Device Specification > IO Expansion and Wall Module Table) some programming consideration must be made to keep the occupancy and setpoint in sync between the stat and the program. Both STRIN and STROUT Menta simple blocks should be used for the most robust synchronization. Environment STR-350/351 as an I/O Module Menta Cause The STR-350 takes roughly 30 seconds to recover from a power failure. The Xenta is much faster than that resulting in reading an invalid setpoint from the STR-350 on a power cycle. By storing the last known setpoint in a DELR block with the "backup" option set, the setpoint will be restored (provided the power has not been off longer than 3 days, in which case it would default back to the initial value of the backed up value). Resolution Click the pictures of the Menta macro below to download the source file. Occupancy To control occupancy from the programmable controller time schedule, the occupancy must be sent to the STR-350. In order to allow for local override commands from the stat, the occupancy must be read in from the STR-350. By allowing the programmable controller to control both the schedule and the override, the stat stays in synch with the program. Setpoint The setpoint requires a little bit of extra programming to account for a power failure. The stat will report invalid setpoints for the first 30 seconds, which will cause it to come back in an undesired state. By letting the programmable hold onto the last known setpoint, and write it back to the stat on power up, there is no change in the setpoint after a power loss. Looping the setpoint in/out from the stat keeps everything in synch with the program, including stat adjustments. Note: This code protects against unwanted behavior following a power failure. A download the Xenta base unit will not trigger the Reset block protection and will cause the stat to go outside the bounds of, and then be limited by, either the high or low setpoint limit. Precaution should be taken following a download to manually reset the setpoint to the desired value. Additional logic for controlling the setpoint remotely could be incorporated into this code. If these macros are going to be used with a STR-350/351 set in degrees Celsius; make sure to change all initial values within the setpoint range. If the initial values are outside of the setpoint range, then the setpoint will always default back to the last known value.

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue Supplemental Documentation on the Menta SEQ (sequence) block Environment Menta Cause The document is intended to clarify the inputs and configuration parameters of the Menta SEQ block and when/how to use them. Resolution Click here to download a copy of this document in PDF format Click here to download the example Menta macro   Supplemental Documentation: Menta SEQ   A Brief Overview of Sequence Block The Sequence block is used to start N of M stages based on a percentage input. Each stage is represented by a single bit in the output of the block which requires calculation to determine if each stage is off or on. The Sequence block also provides the ability to rotate the stages, specify a delay between multiple stages activating, and a hysteresis to adjust the activation or deactivation of stages. The Sequence block is ideal for rotating operating stages that have high frequency of change. It is not the proper block to use for run time balancing between multiple stages. Input of the SEQ Block The input expects a 0-100 value where a 0 represents zero stages active and 100 represents all stages are active. Configuration Parameters of the SEQ Block Stages The number of stages to activate at 100% input. Rotate Rotation Flag. If Rotate is set to 0 then the first stage will always be active if 1 stage is required. If Rotate is set to 1 then the first stage to activate will be the first stage to deactivate. Period Time delay(ms) between multiple stages activating. Hysteresis Hysteresis is used to offset the activation or deactivation % for each stage. If the Hysteresis is positive then it will shift the activation % higher by that amount. If the Hysteresis is negative then it will shift the deactivation % lower by that amount. Normal Operation of 4 Stages:    Stage 1 Activation Stage 2 Activation Stage 3 Activation Stage 4 Activation Input 20% 40% 60% 80%  Hysteresis of 10%    Stage 1 Activation Stage 2 Activation Stage 3 Activation Stage 4 Activation Input 30% 50% 70% 90%  Hysteresis of -15%    Stage 1 Deactivation Stage 2 Deactivation Stage 3 Deactivation Stage 4 Deactivation Input 5% 25% 45% 65% Output of the SEQ Block The number of stages active is based on the following formula: Active Stages = ((Maximum Stages +1) * Input) / 100 The number of active stages is then encoded into an Integer as the output of the SEQ block where each bit represents whether each stage is active or inactive. Since this is a single value it must be decoded using expression blocks to detect if each bit is active.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue At times it is helpful to know the default IP address of a new MNB-1000 and it is not in the documentation. Environment All MNB-1000 controllers regardless of firmware version ship from the factory with a default IP address. Cause Connecting to an MNB-1000 for the first time after it is shipped from the factory. Resolution The default IP for all MNB-1000 controllers when they are shipped is 10.1.10.2.

Issue Windows authentication is not working with Security Expert once configured. Product Line EcoStruxure Security Expert Environment Security Expert Server Windows Authentication Cause Windows authentication was not installed or configured properly during initial install/setup of Security Expert. Resolution Install the Security Expert Server, and any Security Expert Clients, with the "Enable Windows Authentication" option enabled during the installation process. If this was not initially done at install then it will be required to backup the SecurityExpert and SecurityExpertEvents databases, uninstall Security Expert (installing overtop or repairing install may not work) and then re-install Security Expert with the "Enable Windows Authentication" option enabled.  Refer to Determining Security Expert authentication settings after installation to determine the authentication used. When Windows Authentication is enabled in the client go to Global (1) and select Operators (2).  Create a new operator as below: Select to add a new operator (1).  Enter a Name (2).  The name does not need to be the same as the operator's username. Enter a UserName (3).  The username must match the domain name and domain username required to have access to Security Expert.  This is in the form of "DomainName\UserName" as shown in the example image. Set a Role for this operator (4). Enable the "Use Windows Authentication" checkbox (5) and save the changes. Go to Global (1) and select Home (2) and logout of Security Expert. On the login page select the "Use Windows Authentication" checkbox (1), set the Server to the Security Expert Server machine name (2).  Leave this blank if it is the local machine) and press Log in (3). The system should now be logged into Security Expert with the Windows username being used.   If an "Access Denied" is received or another error then confirm the following before contacting Product Support for further help. Ensure Security Expert Client and Server were installed with the "Enable Windows Authentication" option enabled.  Refer to Determining Security Expert authentication settings after installation to determine the authentication used. There is an operator object created in Security Expert with the same domain and user name as the domain user required for login. The "Use Windows Authentication" option is enabled on this operator object. At the login screen "Use Windows Authentication" is enabled and the Server is set correctly.

Issue Can not enter the unlock code in WorkPlace Tech Purchasing Software, the “Unlock” button is grayed out. Environment WorkPlace Tech Tool software, release 5.7 or newer Cause WorkPlace Tech Purchasing Program was not properly closed after the codes were generated.  The Purchase program was closed using the “X” button, not the “Done” button.  Registry and file information does not get saved to the computer when the purchase program is closed using the “X” button. Resolution Re-run the purchasing program and select the same options. This time close the purchasing program using the "Done” button, not the “X” button.