Quantcast

Cable Management Fixing Accessories, 16mm Zinc Plated Metal Half Saddle

Cable Management Fixing Accessories, 16mm Zinc Plated Metal Half Saddle

Cable Management Fixing Accessories, 16mm Zinc Plated Metal Half Saddle

Item Number: 180/16

Retail
$0.74
RRP (Inc. GST)

Datasheet

Barcode

Qty UoM EAN Colour
-
-
-

Specifications

Design

Product brand

Clipsal

Surface treatment

zinc plated

Sustainable offer status

Green Premium product

Physical

Length

46 mm

Width

19 mm

Height

18 mm

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

ENVPEP110719EN

Material

Material

steel

Others

Diameter

16 mm

Package 1 Weight

11 g

Package 1 Height

17 mm

Package 1 width

20 mm

Package 1 Length

45 mm
Show all specifications

Frequently Asked Questions

hide show

Are the Clipsal Conduit Clips available in Electric Orange?

No, they are only available in grey.

This applies to the 280/16 (16mm), 280/20 (20mm), 280/25 (25mm), 280/32 (32mm), 280/40 (40mm) and 280/50 (50mm).

What is the alternate for part number 780/1, 1 way, switch multiplier?

780K1 can be used as an alternate for 780/1, 1 way, switch multiplier. 780K1 Switch Multiplier is 250V 10A, 1 way, supplied with 2 Gang Architrave, switch assembly.
For further information, please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=780K1

What is the replacement part number for the LCHS100 DATA SWITCH?

The part number is:
VDIR62301G  -  DATA SWITCH S1000/T 4 PORT 100/1G MBP 

What is the part code for a 3P B-curve 10Amp MCB

 The part code is 18416

PowerChute Network Shutdown unable to communicate with the NMC if the username is greater than 10 characters.

Issue:
PowerChute Network Shutdown unable to communicate with the NMC if the username is greater than 10 characters.

Product:
PowerChute Network Shutdown (PCNS)

Environment:
Network Management Card 2 (NMC2) firmware AOS 5.1.1 and above. SKUs AP9630, AP9631, AP9635, AP9640, AP9641

Cause:
With the latest release of Network Management Card 2 (NMC2) firmware AOS 5.1.1, with APPs SUMX/SY/SY3P 5.1.0, the NMC2 username can now be up to 64 bytes in length. (64 byte maximum supports up to 64 ASCII characters; Less for multi-byte languages OS). This was previously restricted to 10 characters and PowerChute Network Shutdown (PCNS)  will still only be able to communicate with the NMC if the username is 10 characters or less. The PowerChute installers do not restrict the number of characters that a user can enter for the username nor do they provide any warnings about the max length.

Solution:
If the user configures the NMC2 username to be greater than 10 characters and does the same in PowerChute side, they will receive an error when trying to register with the NMC - "Security information did not match information at <IP Address>".


 

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).
Show More