TOG-10 Spring Toggle Cavity fixing

Thorsman SpRing Toggle Cavity Fixing, 3X50Box, 50Pcs

Catalogue Number: 1208016
TOG-10 Spring Toggle Cavity fixing
Retail
$0.7*
RRP (Inc. GST)

Specifications

hide show
Range of product
Thorsman
Product or component type
cavity fixing
Product name
Thorsman TOG
Device short name
TOG
Provided equipment
screw
Mounting support
board material
Device application
board material
Mounting support
wall mounted
Thread type
M3
Screw diameter
3 mm
Screw length
50 mm
Drilling diameter
11 mm
Colour tint
metal
Quantity per set
set of 50
Sale per indivisible quantity
50
Material
  • screw: steel electroplated
  • cavity fixing: sheet metal electroplated
    • Practical load capacity
      pull-out load: 100 N for 13 mm plasterboard
      Thickness
      0-30 mm fixture
      Environmental characteristic
      fire resistance
      Sustainable offer status
      Green Premium product
      REACh Regulation
      Free of Substances of Very High Concern above the threshold
      REACh free of SVHC
      Yes
      EU RoHS Directive
      Pro-active compliance (Product out of EU RoHS legal scope)
      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)
      Environmental Disclosure
      ENVPEP111114EN

      Frequently Asked Questions

      hide show

      How to mount powerpoint on actassi trunking?

      Unistrut part, code 2087016

      What is the mounting accessory for Actassi trunking to mount power points on

      The Unistrut 2087016 will fit

      Is there a bracket to mount sockets onto Actassi trucking?

      You can direct mount onto the lid of the 80 or 155mm trunking or use the ISM15150

      Other options are the Unistrut 2087016 and adaptors can also be found at cccutting.co.nz

      What is the component breakdown of a XB4BS8444?

      Issue:
      Components of an XB4BS8444.

      Product Line:
      Harmony Push Buttons

      Environment:
      Harmony 22mm

      Cause:
      Product Features

      Resolution:
      It is a ZB4BS844 and a ZB4BZ104.
       

      What is the part number for the locking handle used on QM-WP enclosures?

      Issue:
      Replacement N3R handle

      Product Line:
      Panelboards

      Environment:
      QMB

      Cause:
      Maintenance

      Resolution:
      All QM style WP enclosures require (1) 80121-063-50 locking handle assembly.
       

      What is the recommended spacing for 22mm pushbuttons ?

      Issue:
      What is the recommended  spacing for  22mm pushbuttons ?

      Product Line:
      Harmony Pushbuttons

      Environment:
      All Products

      Cause:
      Product Features

      Resolution:
      Horizontal spacing is 1.18`` or 30mm, vertical spacing is 1.57`` or 40mm, hole size 0.88`` ( recommended 0.89`` ) or 22.5mm


       

      Where are the overload relays for use with LC2D reversing contactors?

      Issue:
      Identifying the appropriate overload relay to use with a reversing pair of contactors

      Product Line:
      Contactors and Starters - IEC

      Environment:
      TeSys LRD Overload Relays

      Cause:
      Overload relay needed for use in reversing application

      Resolution:
      Reversing contactors use the same overload relays as non-reversing contactors.

      What are the dimensions of the wall box to suit the B12/30/6 Multi-Gang Switch?

      The wall box to suit the 12/30/6 Multi-Gang Switch is a 164/6.

      The dimensions of the wall box is a 164/6 are 278mm(W) X 97mm(H) X 58mm(D).

      Some of the key features are:

      • 30 series rocker type
      • B-Style
      • Switch arrangement 6 horizontal and 2 vertical
      • Fascia size: 303 mm Width x 120 mm Height
      • 12 number of switch apertures


      For further information please visit www.clipsal.com/Trade/Products/ProductDetail?catno=B12/30/6

      What is the replacement lens for a ZB4BV or ZB5AV pilot light?

      Issue:
      What are the part numbers of the Lens Caps for the Pilot lights?

      Product Line:
      Harmony Pushbuttons

      Environment:
      All Products

      Cause:
      Product selection

      Answer:
      For LED light modules 

      White    ZBV0113  
      Green   ZBV0133 
      Red      ZBV0143 
      Yellow   ZBV0153 
      Blue     ZBV0163 
      Clear    ZBV017

      For BA9 light modules
      White     ZBV011
      Green    ZBV013
      Red       ZBV014
      Yellow   ZBV015
      Blue     ZBV016

      Clear    ZBV017
       

      DCOM Error 10016 on SQL Agent Job Execution

      Issue
      Each time a SQL job tries to execute, the following error occurs in the Windows System Event log:
       
      Log Name: System
      Source: Microsoft-Windows-DistributedCOM
      Date: 02.02.2013 16:00:02
      Event ID: 10016
      Task Category: None
      Level: Error
      Keywords: Classic
      User: SQL AGENT Service account
      Computer: SQL Server
      Description:
      The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
      {46063B1E-BE4A-4014-8755-5B377CD462FC}
      and APPID
      {FAAFC69C-F4ED-4CCA-8849-7B882279EDBE}
      to the user "SQL AGENT Service account "SID (S-1-5-21-) from address LocalHost (Using LRPC). This security permission can be
      modified using the Component Services administrative tool.

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

      Environment
      Power Monitoring Expert Server
      Windows Component Services

      Cause
      The SQL Server Agent service lacks the Local Activation permission for the MsDtsServer100 DCOM application. This typically happens when the SQL Server Agent service is configured using a domain user account, or is not a
      member of the Administrators group.

      Resolution
      *Warning: This article contains information about editing the registry. Improper changes to the registry can permanently damage the operating system. Always backup the registry before making any changes.*

      One solution would be to add the SQL Server Agent service account to the Local Administrators group on the server; however, this is not always allowed per the user's specific security requirements. To add an account to the Local Administrators group:
      1. From the Windows start menu, type lusrmgr.msc and hit Enter to open the Edit Local Users and Groups interface.
      2. Select Groups on the left, then right-click on the Administrators group and select Properties.
      3. Click Add and then type the name of the user running the SQL Server Agent service, click Check Names, and hit OK.
      Another solution would be modifying the Local Activation permission for the MsDtsServer100 DCOM application. To do this, follow the steps below.
      1. Open the Registry Editor by typing regedit in the windows start menu. Right click and select run As Administrator.
      2. Highlight Computer at the top of the list on the left of the screen.
      3. Open the Edit tab at the top and select Find.
      4. Paste the CLSID that was referenced in the error from the Windows System Event log.
      5. Expand the key titled as the CLSID, and highlight LocalService to confirm that the DCOM application in question is MsDtsServer100 (see image below).
      6. Check and/or modify the permissions assigned to the DCOM application (MsDtsServer100) by going to the windows start menu and typing DCOMCNFG, hit Enter.
      7. Expand Component Services > Computers > My Computer > DCOM Config
      8. Scroll down to the MsDtsServer100 application, and right-click the application to open its properties
      9. Go to the Security tab, and click the Edit button under "Launch and activation permissions"
      10. Edit the explicit local launch permissions by adding/modifying the account configured to run the SQL Server Agent service (see image below).

      PME 9.0 upgrade times out at 'Create Database' step, fails at 'Verify Databases' step

      Issue
      When upgrading to PME 9.0 from an earlier version, the 'Create Database' step times out, causing the 'Verify Databases' step to fail.



      Product Line
      Power Monitoring Expert 9.0

      Environment
      Software Upgrade

      Cause
      The default timeout for the 'Create Database' step is 20 minutes. If the databases are large, it can sometimes take longer than 20 minutes to finish upgrading the databases, resulting in this step timing out. Since the database upgrade doesn't complete, the installer does not pass the 'Verify Databases' step.

      Resolution
      *Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).

      1. Click Exit and close out of the installer
      2. The installation media cannot normally be edited, so either copy the install disc to the hard drive or download and extract the PME_9.0.iso using a .iso file extractor (e.g. 7-Zip)
      3. Navigate to setup\ BrokerFragments
      4. Right-click > Edit the Database.Core.broker.xml file

      If Windows Authentication was used during Database Software step:

      5. Locate the following line, where the current 'TimeOut' is set to 1200000 ms, or 20 minutes: 
      <Request Name="CreateIONDatabasesWindowsAuth" EstTime="500" TimeOut="1200000" UIName="#CreateDatabase" ActionOnFail="Stop">
      6. Change the 'TimeOut' parameter to 12000000 ms, or 200 minutes: 
      <Request Name="CreateIONDatabasesWindowsAuth" EstTime="500" TimeOut="12000000" UIName="#CreateDatabase" ActionOnFail="Stop">



      If SQL Authentication was used during Database Software step:

      7. Locate the following line, where the current 'TimeOut' is set to 1200000 ms, or 20 minutes: 
      <Request Name="CreateIONDatabasesSqlAuth" EstTime="500" TimeOut="1200000" UIName="#CreateDatabase" ActionOnFail="Stop">
      8. Change the 'TimeOut' parameter to 12000000 ms, or 200 minutes: 
      <Request Name="CreateIONDatabasesSqlAuth" EstTime="500" TimeOut="12000000" UIName="#CreateDatabase" ActionOnFail="Stop">



      9. Save the Database.Core.broker.xml file
      10. Navigate back to the root directory of the installation media, then right-click MainSetup.exe > Run as Administrator to re-run the installer with the new timeout setting
       

      SQL Reporting Services service will not start

      Goals and Symptoms

      Issue
      SQL Server Reporting Services fails to start with the following error:

      The SQL Server Reporting Services (ION) service failed to start due to the following error:
      The service did not respond to the start or control request in a timely fashion.

      Additional errors in the Windows System Log include the following:

      A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (ION) service to connect.

      Facts and Changes

      Environment

      ION Enterprise (IONE) or StruxureWare Power Monitoring (SPM) with SQL Reporting Services

      Causes and Fixes

      Cause

      If there are no other errors in the Windows Application or System Logs, the issue might simply be that Reporting Services is taking longer than the 30,000 milliseconds to start up, and the Service Controller is stopping the process.


      Resolution

      A simple registry key can be added to increase this timeout.

      Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

      1) Open up regedit.exe and browse to HKLM\System\CurrentControllset\Control
      2) If it is not already there, create a new DWORD called ServicesPipeTimeout.
      3) Set the value (decimal) to something higher than 30,000 ms (i.e. 120,000 ).
      4) Restart the Server and see if the SQL Reporting Services service starts up.




      If the service does not start, the timeout might have to be further increased.


      Legacy KB System (APS) Data: RESL209797 V1.0, Originally authored by MaTh on 11/28/2012, Last Edited by MaTh on 11/28/2012
      Related ranges: Power Monitoring 7.0, ION Enterprise V6.0
      Show More