Wednesday, October 23, 2019

Amazon Alexa App / Echo Dot "Failed to authorize link code. Please try again."

This is just consumer gear, but Googling didn't turn up anything at all for the error, so here you go.

Symptoms:
Try to set up a freshly reset Echo device. When joining WiFi, you receive an error in a red banner at the top of the screen that says "Failed to authorize link code. Please try again."

Resolution:
Try from another device running the Alexa app. I tried from my wife's phone (where the Echo Dot order was originally placed) and it worked straight away.




Saturday, August 24, 2019

ESXi 6.7u2 update to 6.7u3 failed

Error on my host: Update manager fails to patch the host. When running the manual patch, the host profile update fails.

Error in esxupdate.log:
2019-08-25T00:45:24Z esxupdate: 2099348: root: ERROR: esximage.Errors.InstallationError: ('VMware_locker_tools-light_10.3.10.12406962-14141615', '[Errno 28] No space left on device')

Resolution:
cd /tmp
wget http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_tools-light_6.5.0-0.23.5969300.vib
esxcli software vib install -f -v /tmp/VMware_locker_tools-light_10.3.10.12406962-14141615.vib


Resume manual patching:
esxcli software profile update -p ESXi-6.7.0-20190802001-standard \ -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml 
esxcli network firewall ruleset set -e false -r httpClient
reboot

Done.

Thursday, March 7, 2019

DPM agent push to 2008 Fails 0x80990a1c



Install protection agent on node.node.com failed:


Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on node.node.com.


Error details: Unknown error (0x80990a1c)


Recommended action: Verify that the Agent Coordinator service on node.node.com is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.






Googling the error indicates that KB975759 may be missing.


This KB is not installed on the trouble server.






Manually installing the update MSU package says "update does not apply to your system".






Expand the update into a folder.


Expand –F:* c:\kb975579\Windows6.1-KB975579-x64.msu c:\temp\expandkb975579\






Run the installer (this takes a while!)


Start /w pkgmgr /ip /m:”c:\temp\expandkb975579\Windows6.0-KB975579-x64.cab






Reboot






Re-push the DPM protection agent.

Tuesday, March 5, 2019

ESXI 6.7 - Clone vmdk fails on change tracker error code 5948

vmkfstools -i /vmfs/volumes/ssd-ds1/filer/filer.vmdk /vmfs/volumes/ssd-ds2/filer/filer.vmdk
Destination disk format: VMFS zeroedthick
Cloning disk '/vmfs/volumes/ssd-ds1/filer/filer.vmdk'...
Clone: 100% done.Failed to clone disk: Invalid change tracker error code (5948).


Resolution:
  1. rm the change tracker file (filer-ctk.vmdk)
  2. vi /vmfs/volumes/ssd-ds1/filer/filer.vmdk , comment out the change tracker line. 
  3. Repeat clone (vmkfstools -i)