C120H, 1-pole and padlocking device

Multi 9 C120 PadLocking Device, for C120/NC45..125 Toggle, Set of 4

Catalogue Number: 27145
C120H, 1-pole and padlocking device
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Range of product
  • NC45...125
  • C120
    • Range
      Multi 9
      Product or component type
      padlocking device
      Accessory / separate part category
      locking accessory
      Quantity per set
      set of 4
      Keylock destination
      toggle
      Range compatibility
    • Multi 9 - Multi 9 C120
    • Multi 9 - Multi 9 C120 C120NA-DC -
      • Compatibility code
        Multi 9 C120
        Market segment
        small commercial
        REACh free of SVHC
        Yes
        EU RoHS Directive
        Compliant
        Toxic heavy metal free
        Yes
        Mercury free
        Yes
        RoHS exemption information
        Yes
        China RoHS Regulation
         Pro-active China RoHS declaration (out of China RoHS legal scope)
        Circularity Profile
        N/A
        WEEE
        The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
        Warranty
        18 months

        Documents & downloads

        hide show
        Filter items
        • All

        • Product Brochures

        • CAD Files and Packs

        • Technical Data Catalogues

        • Catalog Page

        • Installation Instruction

        • Product Environmental

        • End of Life Manual

        • Operating Manuals

        • Specification for Tender

        • Application Solutions

        • Certificates (MSDS)

        • Declaration of Conformity

        Frequently Asked Questions

        hide show

        If the C120H circuit breaker is locked ON with the 27145 padlocking facility will it still trip under fault conditions?

        Yes, all of the miniature circuit breakers have a "trip free" mechanism which enables them to trip under fault conditions even if the handle is locked ON or held ON manually.

        What is the degree of protection of 27046, 27047 and 27048 rotary handles.

        The degree of protection of rotary handles references 27046, 27047 and 27048 is IP40.

        These rotary handles are designed for C60, C120 and NC100 circuit breakers and "I switches".

        Unfortunately IP54 degree of protection given in the catalogue is incorrect.

        Replacement for a 28945

        The equivalent part number in Australia is 28943.


         

        What replacement code for a 27249

         18442 is the replacement BUT it is not a direct replacement

        I am looking for a wall fan with a 240mm cutout and is physically approx 300mm square

        You can use a Clipsal 7106A or 7108A both have a 230mm cut out and are 271mm square

        What is the end of service date for Symmetra Power Array and Symmetra RM 12kva?


        The end of service date for the discontinued Symmetra Power Array and Symmetra RM 8-12kva UPS systems is December 2014.  APC by Schneider Electric cannot guarantee spare parts availability for these systems past this date.

        Are replacement stop or start buttons available for the 56DOL range?

        No, they are not, as they are glued into the lid in the factory.
        Spare lids are available as a special order from Australia, and are likely to be a stock item by mid 2014.

        No communication between CNOE-211 and EXEC 2.14E

        Goals and Symptoms

        The Compact Exec V2.14 is delivered with Concept V2.6SR2.This Exec does not work with any comms modules like CNOE-211.

        Facts and Changes

        Concept V2.6SR2
        Compact Exec V2.14

        Causes and Fixes

        A new exec will be available with Concept V2.6 SR2 patch b.

        What are the dimensions for the 7106A ex-fan?

        The dimensions for the 7106A ex-fan are - Dimensions -
        Inlet - 271mm x 271mm
        Wall depth - 110mm - 310mm
        External Protrusion - 20mm
        Internal protrusion - 83mm
        Duct size - 220mm
        Cut out - 230mm
        For further information , visit link below:-
        https://www.clipsal.com/Trade/search-results?q=7106A
        User-added image
         

        Stabiloy cables with Altistart Soft starts

        Issue:  Can you use Stabiloy?

        Product Line:  Altistart Soft starts

        Environment:  All

        Cause:  Stabiloy is an Aluminum/Copper Hybrid

        Resolution:   Per the Installation Manual, Only Copper Cables are compatible with Schneider Electric Soft start terminals.  Can use Stabiloy only on the high hp range that require lugs.  You will, however, have to use Stabiloy compatible lugs to use those cables. 
        Aug 2014, Per US Engineering.

        What is the last version of toolkit that support on Window XP?

        Toolkit 1.14.0

        Clipsal by Schneider Electric ceased technical support for Windows XP in April 2014, in line with Microsoft’s End of Life schedule.

        C-Bus Toolkit now uses .NET Framework 4.5.2. This version of .NET is not available for Windows XP, as a result C-Bus Toolkit will no longer install or work correctly on that operating system.

         

        Soft starters and VSD Catalogue April 2003 (latest what I have in my hand) is not contains details about Interbus-S communication in Section 3, Commu...

        Goals and Symptoms

        Soft starters and VSD Catalogue April 2003 (latest what I have in my hand) is not contains details about Interbus-S communication in Section 3, Communication.
        There is only a short list on page 2/135 with the available solution.
        Why we have 3 different Part number in Vantive? In the catalog we have only the VW3-A58304E. Is it possible to buy VW3-A58304E, which not requires external power supply? If yes, it's missing from the Printed catalog.

        Would be nice to give detailed informations with each type of communication option board, like we provide for MBPLUS, FIPIO, ETHERNET in Section3. (I mean network topology, reccomendations, etc)
        Missing the Interbus-S, CAN-Open, Profibus-DP details there. Can-open will be intersting in point of communication, because Advantys and the new OEM strategy in Schneider is based on CAN!

        Pls see the possibility in the next version.

        Causes and Fixes

        VW3A58304 = First version, not recommended ( not exernal 24Vdc )
        VW3A58304E = Second version with an external 24Vdc to supply the option card even the ATV is switched off because Interbus-S is a circular ring and if a device is switched off, you loose the bus.
        VW3A58304EU = Version with USA documentation.

        For MBPLUS, Fipio, Ethernet you can find a large documentation in IANET, it's not possible to put more details in the catalog because it's a catalog and the customer or enginnering department is supposed to know the concerned field-bus.


        Legacy KB System (APS) Data: RESL160842 V1.0, Originally authored by on , Last Edited by on
        Related ranges: Altivar 58

        Will the ATV61 and ATV71 drives come with an complete programming manual or CD to print your own manual?

        Issue:
        Will the ATV61 and ATV71 drives come with an complete programming manual or CD to print your own manual?

        Product Line:
        Altivar ATV61 and ATV71

        Environment:
        All

        Cause:
        The programming manual and the CD is no longer showing up in the drives packaging.

        Resolution:
        Product Marketing stopped shipping the CDs as of July 2014.  The programming manual that was on the CD is now available online for download.

        ATV61 Programming Manual:
        https://www.schneider-electric.com/en/download/document/1760649/

        ATV71 Programming Manual:
        https://www.schneider-electric.com/en/download/document/1755855/

        Power Monitoring Expert 8.2 - In a new install, when the PME installer tries to install SQL Server Express, I see the error 'Database server has no response'

        The Power Monitoring Expert 8.2 installer uses SQL Server Express 2014. If the target server already has a SQL Server Express 2016 instance installed, the PME installer will still provide the option 'Install SQL Server Express on this computer', however it will attempt to install SQL Server Express 2014.

        Microsft SQL Server 2016 does not support any previous versions of SQL Server side by side on the same syste, which causes the attempt to install SQL Server Express 2014 to fail with an error dialog that says:

        'Database server has no response'.

        Our recommendation is to use the SQL Server Express 2016 instance that is already installed, or manually install a new ION instance of SQL Server Express 2016.

        See the following link for more information on Microsoft restrictions on SQL Server versions on the same machine.

         https://msdn.microsoft.com/en-us/library/ms143694.aspx

         

        Does PME support Always On Availability Groups (SQL Server)

        Issue
        Customer would like to know if the "always on" feature is supported by PME.

        Product Line
        Power Monitoring Expert 7.x
        Power Monitoring Expert 8.x


        Environment
        SQL Server 2012
        SQL Server 2014


        Resolution
        Always ON availability groups for SQL has not been tested in PME. We will not be able to support if user decide to test this configuration. See link below for more information on Always ON availability groups (SQL Server)

        https://msdn.microsoft.com/en-us/library/hh510230.aspx
         

        What is Microsoft OneDrive?

        Issue: 
        What is Microsoft One Drive?

        Product Line:
        Microsoft 

        Environment:
        Microsoft Windows

        Cause:
        Need to know what Microsoft One Drive is used for

        Resolution:
        OneDrive is Microsoft's service for hosting files in the "cloud", that's available for free to all the owners of a Microsoft account.
        OneDrive offers users a simple way to store, sync and share all kinds of files, with other people and devices on the Web.

        Until January 2014, OneDrive used to be named SkyDrive.Mar 3, 2016

        ATV61 programming assistance with the water solutions card VW3A3503.

        Issue:  
        Programming and wiring up a water solution card on the ATV61 drives?

        Product line:
        Altivar ATV61 with water solutions option card VW3A3503.

        Environment:
        All models, all serial numbers 

        Cause:
        Water Solution Card set up configuration.

        Resolution:
        First, go through the Pre-Configuration section in the manual.   Transducer is 0-145 PSI with 4-20mA Output. There are 2 additional External pumps.   Go to Page 86 to set System Units =1 (Imp, Gallon and Degree Fahrenheit)   Water Solutions/Expansion/PID PID Ref Local (Local PID reference will appear under Water Solutions menu) PID Max Ref 100 psi PID Feedback  Drive AI2 PID Gain 50 PID Integral 1   Water Solutions/Expansion/Sensors Outlet Transducer Maximum   145 psi Pressure Units PSI   Water Solutions/Expansion/Start Set Setpoint Ramp  5.0   Water Solutions/Expansion/Stage Number of External Pumps 1 Stage Speed  50 hZ  Jumper: +24 to CI_LI54 External Pump 1 No Fault +24 to CI_LI55 External Pump 2 No Fault +24 to CI_LI57      Auto enable   The Feedback Pressure(monitored under water Solution menu) must be lower than the Start Pressure(programmed in Start Set) when closing CI_LI57 and want the unit to start.
         
        Wiring examples:
        CLI57= auto enable or start
        CLI58= fault reset

        Transducer input
        AI2= Analog input on the drive
        AI52 and AI51= analog inputs on the water solutions card

        Fault feedback inputs from aux pump overload relays
        CLI54= for fault input for Aux pumpt 1
        CLI55= for fault input for Aux pumpt 2
        CLI56= for fault input for Aux pumpt 3

        Aux pump outputs
        CLO51= Aux output for pump 1
        CLO52= Aux output for pump 2
        CLO53= Aux output for pump 3

        Status outputs from the WSC
        CLO55= Run status
        CLO56= Fault status

        Jockey pump option
        CLO56= Jockey or priming pump output

        Programming manual VW3A3503

        PowerSCADA Expert 8.2 Update 5 - Release Notes

        Issue
        What is new in PSE8.2 and a detailed listing of resolved problems and minor enhancements.

        Product Line
        PowerSCADA Expert 8.2 (PSE8.2)

        Environment
        Installer
         
        Cause
        A new PSE8.2 cumulative update release.

        Resolution
        PowerSCADA Expert 8.2 Update 5 - Release Notes
        Release Notification (Updated 25 April 2018)

        This is a detailed listing of resolved issues and minor enhancements in this release.

         


         

        Prerequisite

        You must have PowerSCADA 8.2 installed prior to installing this update. No previous updates are required.

        Cybersecurity Announcement

        Floating License Manager v2.1 addresses vulnerabilities in the Flexera FlexNet Publisher component detailed in CVE-2016-10395, CVE-2017-5571 and CVE-2016-2177. Uninstall the current version of the Floating License Manager, and then install version 2.1.
        NOTE: The Floating License Manager v2.1 installer is included with this hotfix release but is not a part of the hotfix installer. Unzip "Floating License Manager v2.1.zip" and run "setup.exe".

        Important Notice: There is a known issue with the Floating License Manager v2.1.0.0 installer. When installing with a logged-in Windows User name containing a space, the install will not succeed. The workaround is to install the Floating License Manager with a user that does not include a space character in their name.

        Bug Fixes and Enhancements

        TFS 21482 - AlarmEvents with a state of normal returned in GetAlarmEvents response for EWS

        GetAlarmEvents was changed to not return alarms in the normal state.

        TFS 21483 - Incorrect timestamp information provided for AlarmEvents not in the Active state

        Alarm timestamps are now updated to reflect the true timestamp of occurrence for all state changes (active, drop out, acknowledge).

        TFS 21484 - Unable to filter AlarmEvents by Type using EWS

        Alarms are now filtered based on type. 

        TFS 21485 - Unable to successfully acknowledge alarms using EWS

        In some situations, EWS would not acknowledge alarms correctly.  This behavior has been fixed.

        TFS 21486 - Unable to filter alarms using the PriorityTo and PriorityFrom fields

        EWS did not observe the priority field correctly. This has been addressed and the minimum allowable priority has been set to 1 (to exclude non-alarm objects in the PowerSCADA alarm database).

        TFS 21557 - PowerSCADA projects - including the starter project, PLS_Include, and PLS_Example - need to be upgraded to support the new DBF schemas

        PowerSCADA projects have been upgraded to the latest DBF schemas.  If there are existing projects created from the starter project, set [CtEdit] Upgrade = 1 in the Citect.ini file using the Setup Editor, and then restart PowerSCADA Studio.

        TFS 21564 - Alarm Proxy does not show the analog alarm states

        Alarm Proxy now reports the analog alarm states (HIGH HIGH, HIGH, LOW, LOW LOW) instead of ON / OFF.

        TFS 21566 - If a CSV file that does not exist is selected in the I/O Device Manager, the application throws a runtime exception

         

        A message is displayed indicating that the file does not exist.

         

        TFS 21569 - On large systems with 200k configured alarms, the GetAlarmDefinitions call in Alarm Proxy is slow and causes ENM to timeout

        Performance issue in alarm proxy has been resolved.

        TFS 21649 - When CoreServiceHost adds and removes devices, it may lose the original IDs

        CoreServiceHost now keeps a device chronicle.  When the device is removed and then later added, the ID will remain the same.

        TFS 21913 - If the equipment name is changed in the system, but the I/O Device name is unchanged, CoreServiceHost will not refresh the equipment name

        CoreServiceHost now properly updates the equipment on name change.

        TFS 21935 - Logs that are too large for the Windows Event Log do not get logged properly

        Large logs are now broken down into smaller log entries.

        TFS 21970 - Profile Wizard and Automation does not support IPv6

        Profile Wizard and Automation now supports IPv6 for TCP/IP Board level drivers.  This requires the TCP/IP Driver version 4.0.0.0 or later.

        TFS 21975 - Open and Close buttons are disabled at runtime on equipment popup when separate digital tags are used for commands

        The form now enables the command buttons if the Pos_On or Pos_Off tags are defined.

        TFS 21979 - Alarm Proxy cannot return alarms that transition to inactive

        This setting is now configurable in the Application Configuration Utility.

        TFS 22043 - Single sign-on calls from a remote thick client do not work

        Single sign-on now detects remote clients.

        TFS 22060 - The I/O Device Manager cannot bulk import devices with device names greater than 16 characters

        The I/O Device Manager now reads the device name length from the equipment.profiles file for proper validation.

        TFS 22066 - Wonderware ArchestrA Logger Security Patch

        Wonderware ArchestrA Logger Patch 2017.517.2328.1 is applied.

        TFS 22150 - Alarm filters do not work on some resolutions

        Alarm filter AN numbers are fixed for all alarm page resolutions.

        TFS 22155 - Alarm filters perform exact matching

        The alarm filter screen allows the user to select the filtering mode. The default setting is read from the INI file [Alarm] FilterMode.  0 (default) = Exact Match, 1 = Starts With, 2 = Ends With, 3 = Contains.

        TFS 22306 - The equipment tree used on alarm pages is slow to render over the web client

        Any page using the equipment tree should set the default library and symbol on the equipment tree genie, or set 'Hide Symbol Icons' to 'TRUE' if a default icon is not available.

        TFS 22401 - Alarm filter and equipment tree filter operate independently

        The alarm filter and equipment tree filter operate together to filter the alarm tables.

        TFS 22896 - Core service host logs two warnings during shutdown - exception thrown during disposal.

         

        Cleanup methods were reworked to prevent the exception.

         

        TFS 22898 - EWS cannot obtain tag updates at a 5 second rate

        EWS and core services were updated to obtain data at a 5 second poll rate.

        TFS 23262 - Equipment popup alarm table does not acknowledge or disable alarms

        Alarms can now be acknowledged or disabled in the equipment page.

        TFS 23274 - Equipment.profiles cannot be imported into the Profile Editor in cases where the original Device Types and Device Profiles were lost

        The Profile Editor can import the equipment.profiles file to generate device types, device profiles, and tags.

        TFS 23437 - Citect 2016 Updates

         

        Citect 2016 Update (April 10, 2018) is included with this update.

        Project ID management was removed from Citect 2016.  Project IDs are now located in the ProjectInfo.xml file. 

        MinUnitNumber and MaxUnitNumber (previously stored in UnitNumberRange.xml) have also been migrated to ProjectInfo.xml.

         

        TFS 23637 - The Alarm Summary page does not display state information

        The Alarm Summary page now displays the state that caused the alarm.

        TFS 23650 - 8.2 install does not enable ASP feature within IIS

        The installer now enables the ASP feature under IIS. This server role feature is required to run the Citect web control client. (Previously the View-Only web client was the only option for web deployment.)

        TFS 24205 - When Core Services receives a timeout from the Client, alarm processing may halt until the service is restarted

        Core Services properly recovers from a ctApi deadlock condition.

        Files Modified

        Applications\AppServices\bin\Framework.dll
        Applications\AppServices\bin\Framework.ServiceHost.exe
        Applications\AppServices\bin\Modules.CoreServices.dll
        Applications\AppServices\bin\PowerLogic.Cipher.dll
        Applications\AppServices\bin\Modules.ProviderBase.dll
        Applications\AppServices\bin\Modules.ProviderEngine.TestHarness.exe
        Applications\AppServices\bin\ObjectFactoryTools.exe
        Applications\AppServices\bin\ProviderGatewayProviders.dll
        Applications\AppServices\bin\PowerSCADA.Common.dll
        Applications\AppServices\bin\Modules.Platform.Citect.dll
        Applications\EWS\bin\Framework.dll
        Applications\EWS\bin\EWS.dll
        Applications\EWS\Web.config
        Applications\EWS\DataExchange.svc
        bin\de\ProfileEngine.resources.dll
        bin\de\ProfileWizard.resources.dll
        bin\de\WizardLibrary.resources.dll
        bin\es\ProfileEngine.resources.dll
        bin\es\ProfileWizard.resources.dll
        bin\es\WizardLibrary.resources.dll
        bin\fr\ProfileEngine.resources.dll
        bin\fr\ProfileWizard.resources.dll
        bin\fr\WizardLibrary.resources.dll
        bin\it\ProfileEngine.resources.dll
        bin\it\ProfileWizard.resources.dll
        bin\it\WizardLibrary.resources.dll
        bin\ja\ProfileEngine.resources.dll
        bin\ja\ProfileWizard.resources.dll
        bin\ja\WizardLibrary.resources.dll
        bin\ko\ProfileEngine.resources.dll
        bin\ko\ProfileWizard.resources.dll
        bin\ko\WizardLibrary.resources.dll
        bin\ru\ProfileEngine.resources.dll
        bin\ru\ProfileWizard.resources.dll
        bin\ru\WizardLibrary.resources.dll
        bin\zh-chs\ProfileEngine.resources.dll
        bin\zh-chs\ProfileWizard.resources.dll
        bin\zh-chs\WizardLibrary.resources.dll
        bin\zh-cht\ProfileEngine.resources.dll
        bin\zh-cht\ProfileWizard.resources.dll
        bin\zh-cht\WizardLibrary.resources.dll
        bin\ProfileAutomation.dll
        bin\ProfileEngine.dll
        bin\ProfileWizard.exe
        bin\WizardLibrary.dll
        bin\ProfileAutomationUtility.exe
        bin\CommsMethodProperties.xml
        bin\DeviceManagementUserControlLibrary.dll
        Applications\Profile Editor\Tags.xml
        Applications\Profile Editor\ProfileEditor.Business.dll
        Applications\Profile Editor\ProfileEditor.exe
        Applications\Profile Editor\ProfileEditor.UserControls.dll
        Applications\Profile Editor\Resources\ProfileEditor.UserControls.resources
        User\PLS_Include\*
        User\PLS_Example\*
        Starter\Default_Starter.ctz

        Installation

        Unzip "PowerSCADA Expert 8.2 Update 5.zip" and run "PowerSCADA Expert 8.2 Update 5.exe".

        I am not able to operate my Smart Plug on wiserenergy.com.

        Issue:
        Customer can not operate the Wiser switch devices on the Wiser web portal.  This problem can apply to any of the 3 switch devices: smart plug, load control relay, large load controller.  

        Product Line:
        Wiser Home Management System
        Smart Plugs:  EER41200, EER40200
        Load Control Relay:  EER42300,  EER42200
        Large Load Relay:  EER260LLCR

        Environment:
        https://www.wiserenergy.com

        Cause:
        First, all Wiser devices that measure energy must be added to the home's Wiser network.  Next, the home owner must subscribe to either the Smart Energy Plus or Smart Energy Premium Service Plans.    Switch Device control is not included in the Smart Energy Basic Plan.  Finally, these switch devices which also measure the load attached to them must be must be configured as sub-meters of the main meter.

        Resolution:
        1.  Confirm that the device has been added to your Wiser network.  On wiserenergy.com, go to the Settings tab.  Click on Device list and located the device of question.  If it is not in the Device List, then add the device.  
        2.  Confirm that your account is Smart Energy Plus or Premium level.   There is no way at this time (January 2014) to check this on wiserenergy.com.   Wiser Technical support can check the customer service plan level.  If the user's needs to update his service plan, then Wiser Technical Support must delete the User's Account.  The User must then re-register his Gateway and recreate the home Wiser network.
        3.  Finally, configure the switch device to be a sub-meter of the main meter.  This task can be accomplished in 2 different ways.   On the wiserenergy.com Settings Tab, Device List, after a switch device or second power monitor is added to the Wiser Network, then a link for Advanced Meter Settings should appear in the lower right corner of the page.    Use the Advance Meter Settings to set the main meter as the upstream or parent meter of the switch device.   The other way to do this same task is on the Energy Screen, under Settings & Bill Information, there will be a Manage Energy Device section.   Use that section to program the switch device as a submeter of the main device.  

        More information about how to use the Wiser Home Management System may be found in a series of video tutorials published on sub meter.  Link to the the entire playlist of tutorials here.    Video #2, Adding and Controlleing Devices most closely pertains to this topic.   Click here to go to Video #2.


        How to identify and update outdated Statistics in SQL Server

        Issue
        A user may be experiencing performance issues when running SQL queries.

        Product Line
        StruxureWare Power Monitoring 7.0.x
        Power Monitoring Expert 7.2.x, 8.x
        ION Enterprise 6.0.x
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        Outdated statistics can make the SQL server choose a non-optimal execution plan causing undesirable slow response times for certain queries.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        To identify tables within the database which have outdated statistics, the following query can be used.

        SELECT OBJECT_NAME(id) AS Table ,st.[name] AS Tnaam, si.name,
                      STATS_DATE(id, indid) AS DateLastUpdate,rowmodctr rowsModifiedSinceLastUpdate
        FROM sys.sysindexes AS si
        INNER JOIN sys.[tables] AS st ON si.[id] = st.[object_id]
        INNER JOIN sys.schemas AS ss ON st.[schema_id] = [ss].[schema_id]
        WHERE STATS_DATE(id, indid)<=DATEADD(DAY,-1,GETDATE())
        AND rowmodctr>10
        ORDER BY[rowmodctr] DESC

        Once you have identified tables with outdated statistics, the UPDATE STATISTICS  statement can be used to
        bring the statistics back up to date.

        How to find when SQL Server (service/instance) was last restarted

        Issue
        When troubleshooting database issues, gathering some basic information can be very helpful in leading to the resolution or to identifying the cause of problems.

        Product Line
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Environment
        Struxureware Power Monitoring
        Power Monitoring Expert
        ION Enterprise
        ION EEM

        Cause
        Database maintenance and troubleshooting possible database issues.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        Listed below are three methods to find the last time SQL Server server/service was restarted.

        Method 1
        The first method uses the fact that 'tempdb' will be recreated with every restart. We can check the created date (crdate) from master..sysdatabases.
        SELECT crdate FROM master..sysdatabases WHERE name ='tempdb'

        Method 2
        The second method checks the master..sysprocesses database and check for the minimum value in the 'login_time' column.
        SELECT MIN(login_time) FROM master..sysprocesses

        Method 3
        Examine the Windows Event Viewer and search for the most recent event indicating that the SQL server service was started.

        Why can't I connect to Zelio SR2/SR3 device using a bluetooth interface SR2BTC01? I’m getting error popup window DC46_10

        Issue:
        What are the components of VBD1?

        Product Line: 
        Operating Mechanism and Disconnect Switches

        Cause:
        SR3B261FU connection issues Error code DC46_10
        Within the year 2014 a new hardware design has been made for the SR2BTC01 interface.

        Resolution:
        To identify if your device is a new one or old design -- there is no version indication -- a DOM ( manufacturing date ) within the year 2014 or later indicates the new design.

        In order to be able to have the ZelioSoft v4.5 version running correctly with this hardware level, we need to install a new version of the  M2Dc47_Comm.dll file  ( dated April 2014, attached into this FAQ)

        This standard M2Dc47_Comm.dll file to be replaced is located in the ZelioSoft2 V.4.5 directory (by default 'C:\Program Files\Schneider Electric\Zelio Soft 2)
         

        SQL Script to Find the SQL Server Listening Port

        Issue
        When troubleshooting application and database connectivity issues, verifying the port on which the SQL instance is listening
        for connections is a basic and important troubleshooting step.  This is also important information to obtain, to verify this port is open and
        not being blocked by any firewall rules.

        Product
        Struxureware Power Monitoring
        Power Monitoring Expert
        ION Enterprise
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        Although the default port is 1433, the SQL instance can be configured to listen on any other desired port.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        1) Open SQL server Management Studio and connect to the desired instance

        2) Start a new query

        3) copy the script below and execute

        DECLARE @key VARCHAR(50), @RegistryPath VARCHAR(200)
        IF (SERVERPROPERTY('INSTANCENAME')) IS NULL
        BEGIN
        SET @RegistryPath='Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp'
        END
        ELSE
        BEGIN
        SET @RegistryPath='Software\Microsoft\Microsoft SQL Server\'+CONVERT(VARCHAR(25),SERVERPROPERTY('INSTANCENAME')) + '\MSSQLServerSuperSocketNetLib\Tcp'
        END
        EXEC master.dbo.xp_regread 'HKEY_LOCAL_MACHINE', @RegistryPath, 'tcpPort'


        ** see attachment containing the SQL script text
         

        File cannot be loaded because the execution of scripts is disabled on this system error in PowerShell

        Issue
        When you try to run a Powershell script (PS1), you may get the following error:

        File testscript.ps1 cannot be loaded because the execution of scripts is disabled on this system.
        Please see “get-help about_signing” for more details.

        Product Line
        StruxureWare Power Monitoring 7.2.x
        Power Monitoring Expert 7.0.1
        ION Enterprise 6.0.x
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        This error is cause by the security setting on your pc that does not allow you to execute a script. 
        By default, the Execution Policy is set to Restricted. The Restricted setting means that you may not run any PS1 script at all.

        Resolution
        To change the Execution Policy to Unrestricted, type the following command in PowerShell

        Set-ExecutionPolicy Unrestricted

        An overview of the policy levels:
        Restricted: Individual cmdlets can run, but not saved Powershell scripts. This is the default setting.
        AllSigned: Scripts can run, but must have a digital signature even if written on the local computer. Prompts you
                          before running scripts from trusted publishers.
        RemoteSigned: Scripts written on the local computer do not need a digital signature, but any script downloaded
                                  from outside (email, IM, Internet) must have a signature to execute.
        Unrestricted: Any script can run, but scripts downloaded from outside will run with a warning.

        Script to find SQL Server service account

        Issue
        How to quickly find the account which the SQL Server service is configured using a SQL query.

        Product Line
        Struxureware Power Monitoring 7.0.x
        Power Monitoring Expert 7.2.x, 8.x
        ION Enterprise 6.0. x
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R 2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        SQL Server needs to be configured with an account with the correct permissions.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        SQL Server service account information can be fetched from registry or from sys.dm_server_services for versions
        starting from SQL Server 2008 R2 SP1 and above. This following script returns SQL Server service account.

        To retrieve the service account of current SQL Server installation from the registry. execute below query:

        DECLARE @DatabaseEngineAccount VARCHAR(100)
        DECLARE @SQLAgentAccount VARCHAR(100)

        EXECUTE Xp_instance_regread
          @rootkey = N'HKEY_LOCAL_MACHINE',
          @key = N'SYSTEM\CurrentControlSet\Services\MSSQLServer',
          @value_name = N'ObjectName',
          @value = @DatabaseEngineAccount output

        EXECUTE Xp_instance_regread
          @rootkey = N'HKEY_LOCAL_MACHINE',
          @key = N'SYSTEM\CurrentControlSet\Services\SQLServerAgent',
          @value_name = N'ObjectName',
          @value = @SQLAgentAccount output

        SELECT @@SERVERNAME           AS SQLInstance,
                     @DatabaseEngineAccount AS DatabaseEngineServiceAccount,
                     @SQLAgentAccount       AS SQLAgentServiceAccount

        Another method is to query sys.dm_server_services view. This gives the details for all installed SQL Server instances.
        It is available from SQL Server 2008 R2 SP1.
         

        STBNIP2212 Advantys Ethernet NIM Firmware Upgrade - Exec v.2.30, Kernel 2.03, Web 1.20.04

        Release Notice

        The purpose of this resolution is to inform STBNIP2212 users that the Exec., Kernel, and Web pages have been upgraded to the following:

          • Exec v.2.30
          • Kernel v.2.03
          • Web pagev.1.20.04

        Goals and Symptoms

        A single file named stbnip2212_upgrade_[k]_v.2.03_[fw]_v.2.30_[web]_v.1.20.04.exe, is now available and will automatically run the loader utility program when executed and prompt the user to enter the IP address of the Ethenet NIM. The Exec, Kernel, and web files will load sequentially and then reboot the NIM when completed.

        Facts and Changes

        The new Exec., Kernel and web versions are field upgradable and will work with any STBNIP2212 Ethernet NIM hardware versions. The files for the Ethernet NIM can be found on Planet or as the Attachment to this Resolution.

        Causes and Fixes

        The following issues have been resolved in this upgrade:

        1. Version 2.30 corrects a problem where the Ethernet NIM would sometimes fail to go into Run after a power cycle.
        2. When power is cycled to an ATV31 when it is connected as a prefered module on an STBNIP2212 island, the ATV31 would come back up operational but the Advantys Configuration software would continue to display the ATV31 as failed. With Exec. v.2.30, the Advantys Configuration software will not show the ATV31 as failed after an ATV31 power cycle.
        3. Output values in the 'Data I/O' web page would retain their last value if the client communications was stopped, regardless of the fallback state of the output. In this version, the 'Data I/O' values now show INVALID when this condition occurs.
        4. The STBNIP2212 'I/O Data Values' web page will now display the entire 16 bit field when an Input or Output value is displayed in Binary. The display window on previous versions was too small and would not display the entire 16 bit field.
        5. The 'Save' option in the web page 'Network Interface Module Register' now works properly.
        6. The RS232 serial communications port on the Ethernet NIM would respond to any request, regardless of the address in the request. It now responds to the appropriate address.
        7. The RS232 serial port communications was too slow. Compared to Exec v.2.14, the RS232 serial port communications is now approximately twice as fast as previous installed Exec versions.
        8. Previous firmware versions of the STBNIP2212 had problems reading web page applets using Internet Explorer 7 browsers. These issues have been resolved in v.2.30.
        9. Assigning an IP via DHCP could take a minute and a half or longer. With version 2.30, the time to assign an IP via DHCP has been shortened to approximately 30 seconds.
        10. I/O modules on an island would fail to go into Ready if 15 or more Ethernet connections are made to the NIM during power up.
        11. The 'Process Image area' did not get set to zero if the network cable was removed from the NIM. Outputs would write the last data if the cable was reconnected. In version 2.30, the Process Image area is now cleared if the cable is disconnected and then reconnected. New data from the client is then written to the outputs.
        12. In Ethernet NIM Exec versions 2.27 & 2.28, assigning an IP using DHCP also required a valid Gateway address. If a Gateway address was not provided or was assigned 0.0.0.0, the assigned IP would default to the MAC derived IP address. Exec version 2.30 does not require a Gateway address when assigning an IP via DHCP.
        13. New Faulty Device Replacement (FDR) functionality: (Refer to the FDR User Documentation Attachment below)
          * Multiple FDR servers
          * FDR Functionality
          * Device Parameter file backup/restore
          * FDR Diagnostics
           
        The following Enhancement is included in this upgrade:
        1. A Link failure occurs when there is a disruption in communications between the Advantys Ethernet NIM and the device (ex: PLC) communicating to it. However, the outputs of an island can behave differently depending on where a link failure occurs within a network. Therefore, to allow the outputs to behave the same regardless of where the link failure occurs, an option called Link Failure Mode was added to the web pages for Exec. v2.30 in the Ethernet NIM. Further explanation is provided in the attachment Link Failure Mode Option.
           
        The following is an open issue with 2.30 that will be resolved in the next Exec release.
        1. A behavior has been indentified with version 2.30, which differs from version 2.14. After being on for approximately 15 minutes to 1 hour, the STBNIP2212 will reboot if the Rotary switches are set to "Device/Rolename" (DHCP mode) and no DHCP server is available to assign an IP address. The STBNIP2212 will not reboot if the Rotary switches are set to "Bootp" (default position) or any other position. If a bootp server is available and an IP address is assigned via DHCP, the NIM will not experience a reboot.

          A reboot causes the outputs to go to zero, which is the fallback condition.

        Attachments

        FDR User Documentation

        • (Removed File URL: 191005_4CE2/FDR_User_Documentation.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/cc39d5d1fe079fe1c125760900108a76/fl_block_5/0.5C6?OpenElement&FieldElemFormat=gif)


        Link Failure Mode Option
        • (Removed File URL: 191005_4CE2/Link_Failure_Mode_Option.zip)(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/cc39d5d1fe079fe1c125760900108a76/fl_block_5/0.14A8?OpenElement&FieldElemFormat=gif)

        Legacy KB System (APS) Data: RESL191005 V2.0, Originally authored by DaDz on 02/06/2008, Last Edited by DaDz on 08/05/2009
        Related ranges: Advantys STB

        Why did StruxureWare lose comm with my Symmetra MW after DCE was upgraded?

        Issue:

        StruxureWare DCE loses communications with Symmetra Mega Watt UPS after DCE upgrade.

        Product Line:

        StruxureWare Data Center Expert Symmetra MW

        Environment:

        StruxureWare DCE upgrade to 7.5 (or MW DDF upgrade past version 11)
        Symmetra MW UPS and EBS

        Cause:

        The new Modbus DDFs for the Symmetra MW included in DCE version 7.5 poll registers that are not available in some older versions of the Symmetra MW firmware. When these registers are polled, the device reports them as unavailable. DCE sees this and sets the entire communications listing to off-line. The following is the list of firmwares that may see this issue.
         
        3.0.1.157 3.1.0.124 Symmetra MW UPS (up to register 211), Symmetra MW EBS (up to register 92).
        3.2.0.112 3.2.0.210
        3.2.1.105

         
        Symmetra MW UPS (up to register 217), Symmetra MW EBS (up to register 102).
        3.3.0.121
        3.3.1.105
        Symmetra MW UPS (up to register 228), Symmetra MW EBS (up to register 102).
        3.4.0.142
        3.4.0.145
        3.5.0.118
        Symmetra MW UPS (up to register 252), Symmetra MW EBS (up to register 117).
        3.4.2.107
        3.5.1.104
        3.5.2.101
        3.5.3.106
        3.5.4.108
        Symmetra MW UPS (up to register 260), Symmetra MW EBS (up to register 126).
        3.5.5.110
        3.5.5.112
        3.5.6.108
        Symmetra MW UPS (up to register 261), Symmetra MW EBS (up to register 126).
        3.5.7.111 Symmetra MW UPS (up to register 266), Symmetra MW EBS (up to register 126).
        3.5.8.103 Symmetra MW UPS (up to register 267), Symmetra MW EBS (up to register 126).
           


        Resolution:

        While this will be resolved in a future version of StruxureWare DCE, it is advised not to upgrade to DCE version 7.5 unless you have the newer versions of UPS and EBS firmware as noted in the chart below. If you have already upgraded or for some other reason must upgrade, please contact your local field service person / tech support representative for StruxureWare Data Center Expert. The newer version of the DDF will need to be removed and version 11 added back in. Additionally the best alternative is to make sure that the UPS and EBS are up to date on their firmware.

        The following UPS and EBS firmware should not see this issue:
        3.5.9.118
        3.5.9.118a
        Symmetra MW UPS (up to register 271), Symmetra MW EBS (up to register 126).
        3.6.0.120
        3.6.0.120a
        Symmetra MW UPS (up to register 274), Symmetra MW EBS (up to register 129).


         

        After updating to StruxureWare Data Center Expert 7.5, the server loses communications with a monitored Symmetra Megawatt.

        Issue:

        Symmetra MegaWatt may lose Modbus communications with DCE after upgrading to StruxureWare 7.5

        Product Line:

        StruxureWare Data Center Expert
        Symmetra MegaWatt

        Environment:

        Upgrade to StruxureWare DCE 7.5
        Symmetra MW monitored via Modbus

        Cause:

        Due to the upgrade of StruxureWare DCE, the modbus DDF for the Symmetra MW is also updated to version 12. If the Symmetra is running older firmware, some registers may report off-line and StruxureWare may report this as the server being off-line. The same issue may occur in an older DCE revision if you update the DDF to the most recent version. Older firmware should be fine with version 11 of the DDF.

        Resolution:

        If you have upgraded to DCE 7.5 and see this issue, please look into updating the Symmetra MW firmware. The table below shows the affected firmware revisions when used with the new DDF. If you can not update the Symmetra and have already updated DCE or need to do so, please contact tech support and if allowed to remotely access the DCE server, can remove and replace the DDF causing the issue. This should not affect the EBS, only the UPS.
         
        Symmetra Firmware Highest Register Highest DDF to use
        3.0.1.157 3.1.0.124 Symmetra MW UPS (up to register 211), Symmetra MW EBS (up to register 92). Version 11
        3.2.0.112 3.2.0.210
        3.2.1.105

         
        Symmetra MW UPS (up to register 217), Symmetra MW EBS (up to register 102). Version 11
        3.3.0.121
        3.3.1.105
        Symmetra MW UPS (up to register 228), Symmetra MW EBS (up to register 102). Version 11
        3.4.0.142
        3.4.0.145
        3.5.0.118
        Symmetra MW UPS (up to register 252), Symmetra MW EBS (up to register 117). Version 11
        3.4.2.107
        3.5.1.104
        3.5.2.101
        3.5.3.106
        3.5.4.108
        Symmetra MW UPS (up to register 260), Symmetra MW EBS (up to register 126). Version 11
        3.5.5.110
        3.5.5.112
        3.5.6.108
        Symmetra MW UPS (up to register 261), Symmetra MW EBS (up to register 126). Version 11
        3.5.7.111 Symmetra MW UPS (up to register 266), Symmetra MW EBS (up to register 126). Version 11
        3.5.8.103 Symmetra MW UPS (up to register 267), Symmetra MW EBS (up to register 126). Version 11
        3.5.9.118
        3.5.9.118a
        Symmetra MW UPS (up to register 271), Symmetra MW EBS (up to register 126). Version 12
        3.6.0.120
        3.6.0.120a
        Symmetra MW UPS (up to register 274), Symmetra MW EBS (up to register 129). Version 12

        Wiser Power Meter will not connect to Coordinator

        Issue:
        Wiser Power Meter will not connect to Coordinator.  Home Owner entered the catch phrase of Power Meter, but the device will not add the network.

        Product Line:
        Wiser Home Management System,  EER21200, WISERJLPM200

        Environment:
        Wiser Home Management System,  wiserernergy.com

        Cause:
        This issue can be caused by several factors.  The most common cause found in 2014, state of Texas, KB Homes, was that the contractors install the Power Meter in metal boxes on the outside of the house.  The metal box blocks the ZigBee radio signal.

        Resolution: 
        Some locations, such as Texas, it is common to install a Utility Meter / Circuit Breaker Combo panel on the outside of the house.   If the breaker panel is on the outside of the house, then the Power Meter is probably on the outside of the house as well.  Find out the condition of the Power Meter installation.  If the Power Meter is in a metal box, then test joining to the network with the cover the of the metal box removed.   If this works, then the metal box is the cause.   The first recommended action is to force the installing contractor to install the Power Meter in a plastic or fiberglass enclosure.   Another solution is to install the Coordinator or another Wiser Device very close to the Power Meter but on the inside of the house.  If the distance is short enough, the devices might be able to communicate even though the Power Meter is in a metal enclosure.  

        Verify that the breaker feeding power to the Power Meter is on.  Verify that the Power Meter indicator lights work properly and that and the Power Meter is in join mode.  

        UPS Network Management Card 2 Firmware Application Compatibility for Smart-UPS Online (SRT) Models


        Issue

        Which UPS Network Management Card 2 (NMC2) firmware applications work with my SRT model UPS?

        Users experiencing NMC2->UPS communication problems, such as "UPS: Lost the local network management interface-to-UPS communication" or no UPS information displayed after upgrading NMC2 firmware.



        Product Line
        • Smart-UPS Online models with model prefix SRT
        • UPS Network Management Card 2 - AP9630/AP9630CH, AP9631/AP9631CH, AP9635/AP9635CH (when supported)


        Environment
         
        • Aforementioned SRT UPS models
        • Users utilizing the embedded NMC2 available within SRT models
        • Users adding or upgrading a secondary NMC2 to the available SRT UPS SmartSlot accessory slot

        Cause

        This knowledge base will help outline which NMC2 firmware application versions support SRT model Smart-UPS Online UPSs as to prevent unwanted communication problems and inform users which firmware upgrades to perform and/or avoid.



        Resolution


        Beginning in June 2014, regions where Smart-UPS Online models with the model prefix SRT will begin shipping. These UPS models now have an embedded UPS NMC2 with the sumx firmware APP version v6.0.7. This version should not be upgraded to v6.1.1, even though v6.1.1 is presumably a newer version. v6.0.7 is currently required to access UPS information for users utilizing the NMC2.

        This also applies to users who wish to add a secondary AP9630 or AP9631 standalone NMC2. v6.0.7 firmware application must be used as v6.1.1 sumx is incompatible.

        A newer version of the sumx application has been made available available to replace both v6.1.1 and v6.0.7 for users - v6.2.0.


         
        NMC2 Firmware Application Version Compatible with SRT UPS?
        v5.X.X sumx No
        v6.0.7 sumx Yes
        v6.1.1 sumx No
        v6.2.0 sumx and higher Yes
         

        If you're unsure of your firmware application, in the web interface, go to About->Network menu. Via Command Line Interface, the firmware application version will be shown on the top right immediately after log in.
         

        How to view what queries are currently running on SQL Server

        Issue
        Inspecting the currently running SQL queries can be very useful for debugging issues on your database servers.
        Often, viewing the queries which are executing when a problem is occurring (ie. a query is running slowly) will help to identify the cause of the problem.

        Product Line
        Struxureware Power Monitoring
        Power Monitoring Expert
        ION Enterprise
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        Troubleshooting possible system issues

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        On SQL Server 2005 and later this can be achieved using the Dynamic Management Views.  
        DMVs were introduced in SQL Server 2005, so the queries won’t work with earlier versions.

        The following query will return a row for each request that is currently executing. Many of these will be internal sessions used by SQL Server but it
        will also include SQL commands currently executing. To filter out the internal sessions ignore any with a session_id of 50 or less.

        SELECT * FROM sys.dm_exec_requests

        This query can be further enhanced as below, to display the actual SQL statements executing by combining the dm_exec_sql_text DMV.

        SELECT      r.start_time [Start Time],session_ID [SPID],
                    DB_NAME(database_id) [Database],
                    SUBSTRING(t.text,(r.statement_start_offset/2)+1,
                    CASE WHEN statement_end_offset=-1 OR statement_end_offset=0
                    THEN (DATALENGTH(t.Text)-r.statement_start_offset/2)+1
                    ELSE (r.statement_end_offset-r.statement_start_offset)/2+1
                    END) [Executing SQL],
                    Status,command,wait_type,wait_time,wait_resource,
                    last_wait_type
        FROM        sys.dm_exec_requests r
        OUTER APPLY sys.dm_exec_sql_text(sql_handle) t
        WHERE       session_id != @@SPID -- don't show this query
        AND         session_id > 50 -- don't show system queries
        ORDER BY    r.start_time

        * Alternatively, the attached sql script can be run to obtain this information.

        How to Check Index Fragmentation on Indexes in a Database

        Issue
        SQL Queries taking longer than normal to complete.

        Product
        Struxureware Power Monitoring
        Power Monitoring Expert
        ION Enterprise
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        When a database is frequently updated via INSERT, UPDATE, or DELETE statements we can expect it to become fragmented over the time.
        If database indexes are fragmented, the SQL Server query optimizer may chose a non-optimal execution plan when using an index to resolve a query.
        This will affect the overall query performance and you may notice a query behaving slower than normal.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        The following is a simple query that will list every index on every table in your database, ordered by percentage of index fragmentation.
         
        SELECT dbschemas.[name] as 'Schema',
        dbtables.[name] as 'Table',
        dbindexes.[name] as 'Index',
        indexstats.avg_fragmentation_in_percent,
        indexstats.page_count
        FROM sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL, NULL, NULL) AS indexstats
        INNER JOIN sys.tables dbtables on dbtables.[object_id] = indexstats.[object_id]
        INNER JOIN sys.schemas dbschemas on dbtables.[schema_id] = dbschemas.[schema_id]
        INNER JOIN sys.indexes AS dbindexes ON dbindexes.[object_id] = indexstats.[object_id]
        AND indexstats.index_id = dbindexes.index_id
        WHERE indexstats.database_id = DB_ID()
        ORDER BY indexstats.avg_fragmentation_in_percent desc

        This query can be modified to focus on specific tables by append the table name to the 'where' clause:

        WHERE indexstats.database_id = DB_ID() AND dbtables.[name] like '%%'

        In order to reduce fragmentation we will have to reorganize or rebuild the indexes. Choosing between reorganizing or rebuilding depends on the query results.
        For heavily fragmented indexes a rebuild process is needed, otherwise index reorganization should be sufficient.

        The following table summarizes when to use each one:
        Reference Values (in %) Action  SQL statement
        avg_fragmentation_in_percent > 5 AND < 30  Reorganize Index  ALTER INDEX REORGANIZE
        avg_fragmentation_in_percent > 30  Rebuild Index  ALTER INDEX REBUILD

        How to Create a Copy of a SQL Table

        Issue
        Often when troubleshooting and\or correcting data issues, it is desirable to work on a temporary or subset of the production data
        to in order to test a solution or to focus on a small portion of some particular data item(s).

        Product
        Struxureware Power Monitoring
        Power Monitoring Expert
        ION Enterprise
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        Troubleshooting or correcting data issues.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        An easy way to create a copy of a table is to use a SQL command.

        Use SELECT INTO to extract all or a subset of the rows or from an existing table into the new table.
        The new table must not exist already.

        The following example will copy the Source table under the IonNetwork schema to a new table called MySource under the Test schema:
        SELECT * INTO Test.MySource FROM IonNetwork.Source

        You can also create the new table from a specific subset of rows in the original table.
        In this case, you would append a Where clause to specify the criteria for only those rows you are interested in.
        SELECT * INTO Test.MySource FROM IonNetwork.Source
        Where Name like '%MySources%'

         
        Additionally,  you could create the new table from a specific subset of columns in the original table.
        In this case, you specify the names of the columns to copy after the SELECT keyword.
        Any columns not specified are excluded from the new table.

        The following example copies specific columns to a new table:
        SELECT ID, Name, SourceTypeID, Description INTO Test.MySource
        FROM IonNetwork.Source

        Where is Wiser Panel Meter?

        Issue:
        Homeowner is setting up Wiser account on www.wiserenergy.com.   After creating the account, he/she must join devices to the account.   The homeowner may know that the home builder installed a Panel Meter (aka Power Meter) but can not physicially locate the device or the catchphrase.   The catchphrase is needed in order to setup communications between the Wiser Coordinator and the Panel Meter.

        Product Line:
        Wiser Home Management System

        Environment:
        Residential Home
        www.wiserenergy.com

        Cause:  
        Contractors may install the Panel Meter in a variety of locations.

        Resolution:
        The Wiser Panel Meter must be located within 6 feet of the Main Breaker Panel of the house.   The current transformers (CTs) have 6' long low voltage cables and therefore the panel meter must be installed within this cable distance of the circuit being measured.  The Panel Meter is typcially installed in one of the following locations.
        • If the breaker panel is inside the house or garage, then the Panel Meter is usually installed above or to the side of the breaker panel.
        • If the breaker panel is outside of the house, look for the Panel Meter inside the house on the inside surface of the exterior wall on which the breaker panel is mounted   Often, it is installed high on the wall, near the ceiling.
        • In KB Home installations in Texas, 2013 to 2014, the contractors often install the Panel Meter in a NEMA 3 box next to the breaker panel on the exterior of the house.  
        The catchphrase of the Panel Meter can be found on a sticker attached to the meter.   Also, a loose sticker is shipped with each Panel Meter.  It is intended for contractors to affix this loose sticker to the door of the breaker panel.  




        near the breaker panel

        Configure Automatic Archiving for an Alarm Server

        Issue
        How to keep alarms in the system for the past certain number of weeks and archive older alarms.

        Product Line
        PowerSCADA Expert

        Environment
        Citect Project Editor > Alarm Servers

        Cause
        A system generating many alarms.

        Resolution
        To configure automatic archiving for an alarm server:

        1.  Open Project Editor.
        2.  From the Servers menu, select Alarm Servers to open the properties form.
        3.  Locate the record for the required alarm server (in case there is more than 1 alarm server).
        4.  In the Archive Every field (available on extended form only), enter the number of days after which archiving will automatically occur.
        5.  Confirm that Archive Path and Archive Prefix fields are correctly configured
         
        Example 
        Archive Path = D:\Data
        Archive Prefix = AlarmArchive
        If archiving is executed on this server on 21 January 2014, the archive volume path would be D:\Data\AlarmArchive20140121.

        6.  Click Add to append a new record, or Replace to modify an existing record.
        7.  Configure the "KeepOnlineFor" and "ArchiveAfter" parameters.

        [Alarm.<ClusterName>.<ServerName>]KeepOnlineFor  
        This parameter defines how long event data remains on the Alarm Summary or Sequence of Events (SOE) pages.
        The default value is six weeks. After this time, the data will no longer appear.

        [Alarm.<ClusterName>.<ServerName>]ArchiveAfter 
        This parameter specifies how long event data is kept for before it is marked for archiving.
        The default value is four weeks. After the specified period of time has passed, event data that is marked for archiving will remain in the database but will be read only. When the data becomes read only it is no longer writable. You are unable to make it writable.

        8.  Compile and run the project


        Note: To view the archived data that is no longer available for viewing, see FAQ FA326474

        Network Management Card 1 (NMC1) Information Bulletin: Effects of Microsoft Internet Explorer and other web browsers blocking key lengths less than 1024 bits


        Issue

        Microsoft has released a critical update (KB 2661254) as of August 14, 2012, which will end support for certificates using the RSA algorithm that has key lengths less than 1024 bits. Shorter keys have been deemed more vulnerable to brute force attacks due to continued advances in computer processing capabilities. After applying Microsoft’s update, all certificates with key lengths less than 1024 bits will be treated as invalid. This update does not apply to Windows 8, 8.1 or Windows Server 2012 because these operating systems already include the functionality to block the use of weak RSA keys that are less than 1024 bits long.

        Users will likely experience a security certificate warning and then the browser will not be able to "Continue to this website anyway" or be sent to an error about "Page cannot be displayed."

        Update: In October 2014, Mozilla Firefox v33 has begun to block keys less than 1024 bits in length too. Security related release notes for Firefox v33 can be found here and refer to RSA certificates using weak signatures less than 1024-bit are no longer accepted section once you access the link. Users will see an error such as "The key does not support the requested operation. (Error code: sec_error_invalid_key)."


        Product Lines

        The following products Network Management Card devices and product lines are affected.
         
        Product NMC AOS Version
        AP9617 All Versions (1.X, 2.X, 3.X)
        AP9618 All Versions (1.X, 2.X, 3.X)
        AP9619 All Versions (1.X, 2.X, 3.X)
        Rack PDU (AP78XX, AP79XX) All Versions (1.X, 2.X, 3.X)
        Rack ATS (AP77XX) All Versions (1.X, 2.X, 3.X)
        Environmental Products (AP9320, AP9340, NetBotz 200) All Versions (1.X, 2.X, 3.X)
        S20/S20BLK A/V Power Conditioner with Battery Back Up All Versions (1.X, 2.X, 3.X)
        Other NMC1 product groups not listed All Versions (1.X, 2.X, 3.X)























        Environment

        All Network Management Card 1 devices listed above currently configured for HTTPS mode using the default 768 bit auto-generated self-signed SSL certificate.


        Cause

        All Schneider Electric Network Management Card 1 products have the capability of supporting SSL for secure web connections. All products listed above with any firmware version, auto-generates self-signed SSL Certificates 768 bits in length when HTTPS mode is enabled unless another user certificate has been pre-loaded.

        Please note: Network Management Card 2 products are not affected.


        Resolution

        Refer to the currently available workaround options listed below:
         
        1. Upload a 1024 bit SSL Certificate to the affected products - the aforementioned products all allow the user to create and upload their own 1024 bit SSL Certificate with the help of the APC Security Wizard tool, available on apc.com for download with the part number SFNMCSECWIZ104. A step by step guide is available in the Network Management Card 1's Security Handbook: https://www.apcmedia.com/salestools/ASTE-6Z5QF2/ASTE-6Z5QF2_R2_EN.pdf
        2. Use a different web browser (such as Chrome, Firefox, etc)
          • Update: In October 2014, Mozilla Firefox v33 has begun to block keys less than 1024 bits in length, too. Security related release notes for Firefox v33 can be found here and refer to RSA certificates using weak signatures less than 1024-bit are no longer accepted section. One possible option is to downgrade Firefox.
        3. Uninstall the patch
        4. Do not apply the patch
           
        Additional Resources

        Application Note #67 has more detailed information on the Network Management Card 1 & 2 products and their security implementation.
         

        How to find active connections, and related information to a SQL Server database

        Issue
        Having the ability to inspect the active connections to SQL Server, who is logged on and what they are doing, can be very important information when troubleshooting database issues.
        It can also be required when you want to perform some exclusive work on you database(s) or for other database maintenance activities.

        Product Line
        Struxureware Power Monitoring
        Power Monitoring Expert
        ION Enterprise
        ION EEM

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        Troubleshooting possible SQL database issues.

        Resolution
        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        There are several ways to find information about the active connections to your SQL Server. Below are some possible methods, each varying the amount and
        information returned.  This information can also be filtered to return only those processes that are not idle, those belonging to a specific user, or those belonging
        to a specific session in order limit the volume to only that information which is of interest.

        1) Activity Monitor
        - Use the SQL Server Management Studio --> Management --> Activity Monitor
        - This gives a list of users, database names, status, command, transactions, application with which they are using the database, CPU, IO and Memory usage, Login time etc.

        2) Stored Procedure(s)
        - Use the built in stored procedure(s) called sp_who or sp_who2
        - sp_who2 is an undocumented procedure which returns more information than sp_who
        - Run the command exec sp_who or exec sp_who2
        - This gives a list of users, database names, status, command, program with which they are using the database, CPU time, Login time etc.

        3) Sql Script (Systemprocesses)
        - Use the following script or a variation of it to query the required information from the sys.systemprocesses view of the Master database
        - This script can be tailored to obtain the information required (ie. more or less) for the individual purpose

        - This script returns the Database, Number of open connections and logged-in user credentials

        SELECT DB_NAME(dbid) as DBName, COUNT(dbid) as NumberOfConnections,loginame as LoginName
        FROM sys.sysprocesses
        WHERE dbid > 0
        GROUP BY dbid, loginame

        - This script returns the status, login name and host name for the database you specify.

        SELECT spid, status, loginame, hostname, blocked, db_name(dbid), cmd
        FROM sys.sysprocesses
        WHERE db_name(dbid) = 'databasename'


        4) Sql Script (Dynamic Management Views)
        - SQL Server 2005 introduced Dynamic Management Views, in this case we can just check if the is_user_process is 1 instead of checking for the value of spid.
        - This will work in SQL Server 2005 and 2008.

        SELECT count(*) as ConnectionCount
        FROM sys.dm_exec_sessions
        WHERE is_user_process = 1


        If you want both system and user information:

        SELECT count(*) as ConnectionCount,
        CASE when is_user_process =1 then 'UserProcess' else 'System Process' end
        FROM sys.dm_exec_sessions
        GROUP by is_user_process


        Also, can look at the sys.dm_exec_connections Dynamic Management Views. This view only shows user connections.

        SELECT  count(*)  
        FROM sys.dm_exec_connections

         

        ** see attachment containing the SQL script text

        How to Find and Fix Orphaned Users in SQL Server

        Issue
        When migrating or moving a database from one SQL Server instance to another SQL Server instance, orphan user(s) could be created.

        Product
        Microsoft SQL Server

        Environment
        SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016

        Cause
        When a database is moved or migrated, the database users in the migrated or moved database are not mapped to any
        particular SQL Server login within the new SQL Server instance. A database user for which the corresponding SQL Server
        login is undefined or is incorrectly defined on a server instance cannot log in to the instance. A database user not mapped
        to SQL Server Login is referred to as an Orphan user.

        Resolution

        *Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

        Below are some of the scripts to identify and fix the Orphan user issue.

        Script for finding list of Orphan USERS for a particular database:
        select db_name() as DBName,* from sys.database_principals 
        where sid not in (select sid from master.sys.server_principals)
        AND type_desc != 'DATABASE_ROLE' AND name != 'guest'

        Script for finding list of Orphan USERS from all the databases:
        exec sp_msforeachdb ' use ?
        select db_name() as DBName,* from sys.database_principals 
        where sid not in (select sid from master.sys.server_principals)
        AND type_desc != ''DATABASE_ROLE'' AND name != ''guest'' '
         
        Script to map a particular database USER with a LOGIN:
        ALTER USER userName WITH LOGIN = loginName
         
        Script to generate Alter User script which can be used to map all orphan USERS with LOGINS in a particular database:
        select 'Alter User '  + name + ' WITH LOGIN = ' + name  from sys.database_principals 
        where sid not in (select sid from master.sys.server_principals)
        AND type_desc != 'DATABASE_ROLE' AND name != 'guest'
         
        Note: These Alter commands will fail, if loginname with same name as username is not already present as a LOGIN, so first create the LOGIN if not already present.
         
        Script to generate Alter USER script which can be used to map all orphan users with logins in all databases:
        exec sp_msforeachdb ' use ?
        select ''Alter User ''  + name + '' WITH LOGIN = '' + name  from sys.database_principals 
        where sid not in (select sid from master.sys.server_principals)
        AND type_desc != ''DATABASE_ROLE'' AND name != ''guest'' '

        Note: These Alter commands need to be run on their specific databases and Alter commands can fail, if loginname with same name as username is not already present as a LOGIN, so first create the LOGIN if not already present.
         

        ** see attachment containing the SQL script text