Tag Archives: Error

Solving error “The trust relationship between this workstation and the primary domain failed.”

Last week I reverted an snapshot on an Virtual Server. When I restarted the VM, and try to logon, I received the following error:

“The trust relationship between this workstation and the primary domain failed.”

My domain admin account was unable to logon. My local admin account was able to logon. How to solve this issue without removing this VM from the domain.

Solution.

First, logon using the local administrator credentials.

Open an elevated Command Prompt and type the following command:

netdom resetpwd /s:[FQDN Domain Controller] /ud:[domain name]\administrator /pd:*

[FQDN Domain Controller] fill in the Domain Controller server name and domain.

[Domain name] fill in the domain name.

After running this command, restart the server and logon with the domain credentials. If everything went ok, you are able to logon on and the trust relationship is restored again.

For more information about the netdom command, see: https://technet.microsoft.com/en-us/library/cc772217(v=ws.11).aspx

Veeam Jobs fail after adding new ESXi hosts

Leave a reply

When you add new VMware Hosts to a VMware vCenter Cluster, please remember to do a rescan of vCenter in Veeam. Veeam now rescans the complete environment and adds the new ESXi hosts to its database so everything will work correctly.

My problem was after I placed new VMware ESXi hosts in the VMware vCenter cluster, the backup was failing on every VM that was placed on the new ESXi hosts. Veeam had detected the new VMware ESXi hosts, so I thought everything was good.

My Error message was: “Failed to create processing task for VM [vm name] Error: Host ‘ESXi host’ with type ‘ESX’ and parentId ‘e2afc39e-f38c-466b-9431-cd1b7aedc48b’ not found.”

A quick google action on this error message resulted in a Veeam Forum post. See http://forums.veeam.com/vmware-vsphere-f24/problem-with-backups-after-adding-new-host-to-vcenter-t18512.html

User v.Eremin is saying in his post:

As long as VMs are added to backup console via vCenter, backup server should be vMotion aware and you shouldn’t encounter any issues after VM migration. However, it seems that vCenter added to backup console didn’t know about the new host and about the fact that certain VMs had been migrated to it, thus, backup jobs failed. So, now, when the rescan is done, everything should be ok, even without manual re-adding of VMs.

This gave me the tip to first do a rescan of vCenter to see if this solved my problem. And this worked for me, thanks Veeam Forums!

Solving the vSphere Web Client cannot connect to the vCenter Single Sign On server error.

5 Replies

After a power failure in my home lab, I tried to login to my vCenter Appliance and get this error “The vSphere Web Client cannot connect to the vCenter Single Sign On Server”.

The solution for this problem is quite simple. For the vCenter Appliance, log in to the Management page of the vCenter Appliance. Stop and Start the vSphere Web Client Services.

For the Windows based vCenter, restart the vSphere Web Client Services.
After a few minutes everything is ok. Problem Solved.

** Edit 02-03-2016 **

Reboot of the vCenter Appliance should also solve the problem.

VMware Template unable to Convert to Virtual Machine

1 Reply

Sometimes the following will happen:

You have a couple of templates and want to update them, you right click the VMware Template and the option to convert to Virtual Machine is grayed out. In this case it was a VMware vSphere ESXi 5.5U2 environment.

Also the Rename and other options are grayed out. How to solve this issue?

Try to deploy a virtual machine from this template. After you successful deployment the options are available again. Strange, but in my case it works..

How to solve the ‘Cache 1’ Backup Power Source (Capacitors) Status = ‘Charging’. Warning

1 Reply

One of our HP Storevirtual P4530 server was giving the following Warning.

‘Cache 1’ Backup Power Source (Capacitors) Status = ‘Charging’. WARNING (E01020401)

When this error occurs the performance of the Storevirtual Storage environment is terrible. Very high latency’s with read and write.

This was the second time in a few months’ time. The first time HP replaced the Cache Battery. It could be the same problem, so I contacted HP support. It wasn’t, they told me the following.

With a Firmware earlier than 5.42 of the RAID controller there is an issue with the charging and discharging of the cache battery. When the warning occurs the Cache Battery is in an error state and therefor disabled. The HP Storevirtual P4530 is using a HP P420i RAID controller. For more information see HP Document id: c024258375

To check if the Cache Battery is disabled create a Support Log bundle of the Storage node. Then check the ADUReport and look for the Cache Disable Code. See screenshots.

Advice from HP Support is to upgrade to a supported level. In my case 5.42 for the P420i RAID controller.

To verify which firmware is supported and which isn’t see the HP Storevirtual Storage Hardware Firmware matrix. This document can be found at the HP SPOCK see link. If you have any questions, please contact HP Support. I’m not an HP employee….

Thanks HP Support for this fix.

Solve the “System logs on ESXi Host are stored on non-persistent storage” message

5 Replies

Recently I had to install a few VMware ESXi 5.5 host on removable SD cards. After the installation finishes and you connect the first time with the vSphere Client, a message is displayed.

This means that the log files are written on the SD card. After a reboot the log files disappear. This could be a problem when trying to trouble shoot a problem and the ESXi host has rebooted.

So how to solve this configuration issue. See VMware KB2032823 for instructions. This is very easy and highly advisable.

Verify the Location of System Logs in the vSphere Client

In the vSphere Client, select the host in the inventory panel.
Click the Configuration tab and click Advanced Settings under Software.
Make sure that Syslog.global.logDir points to a persistent location.
The directory should be specified as [datastorename] path_to_file where the path is relative to the datastore. For example, [datastore1] /systemlogs.
If the Syslog.global.logDir field is empty or explicitly points to a scratch partition, make sure that the field ScratchConfig.CurrentScratchLocation shows a location on persistent storage.

Verify the Location of System Logs in the vSphere Web Client

Browse to the host in the vSphere Web Client navigator.
On the Manage tab click Settings.
Under System, click Advanced System Settings.
Make sure that Syslog.global.logDir points to a persistent location.
If the field Syslog.global.logDir is empty or points to a scratch partition, make sure that the field ScratchConfig.CurrentScratchLocation shows a location on persistent storage.
Note: You must reboot the host for the changes to take effect.

Solve the Flex-common-lib-x.x.x.swf fail to load error 2032

Leave a reply

When connecting to the vSphere web client with Firefox the following error could occur. RSL https://vcenterserver:9443/vsphere-client/locales/rsl/flex-common-lib-5.5.0.swf failed to load. Error #2032

This happened to me after an upgrade to the latest version of VMware vCenter.

A quick search on google resulted in a solution. Clear your cache from your browser. In my case Firefox. Reload the site, and problem solved.

Unable to install VMware tools. Error 1606.

Leave a reply

Today I had to virtualize several Windows 2008 R2 Terminal server. After a successful conversion I ran into a problem when installing the VMware Tools.

Error 1606. Could not access network location [servername]\[sharename]\desktop\programs\startup\.

This error is caused by a Group Policies that was redirecting the start menu to another server (also for the domain administrator and local administrator). Because I started the VM in an isolated environment it was unable to check the free disc space of the network share and gave me this error. This error is discussed in VMware KB1017886.

In my case there were two directories redirected to a server that was not reachable for this server. I also checked the Current User settings, but there was nothing directing to the unreachable server.

To solve the error change both register keys to their original settings.

The “Common Startup” key should be “%ProgramData%\Microsoft\Windows\Start Menu\Programs\Startup”
The “Common Programs” key should be “%ProgramData%\Microsoft\Windows\Start Menu\Programs”

The original setting of all the keys.

Restart the VMware Tools installation and now everything should work without any problems.

More information:

Microsoft KB886549.

Veeam Backup & Replication setup or upgrade not starting

Leave a reply

A couple of weeks ago I tried to do an upgrade of the Veeam Backup & Replication 6.1 to v7.0. I mounted the fresh downloaded ISO of Veeam v7.0. The splash screen showed, and when I clicked on the Install / Upgrade options nothing happened.

This server is running Windows 2008R2 Service Pack 1, and is also the VMware vCenter server for the ESXi environment.

Because this server is a vCenter Server and purely a management server this server didn’t had all the Windows Updates installed that are available today. So my first guess was to update the complete server. After updating this server and a fresh reboot, I started the installation again. No success, still the same behavior. Splash screen disappears and reappears again without starting the Veeam installation.

There are also no errors in the event logs of the server. Always nice to trouble shoot…

When installing the Microsoft System CLR Types for SQL components there is an error.

So there was something wrong with the Windows environment, but everything was working like it should. I already checked all the perquisites, and everything was installed. I didn’t know where to look for, so after some time I contacted Veeam support. They checked the environment and reinstalled the .Net Framework. After this installation the Veeam installer was working correctly. Problem was a corrupted or damaged .Net framework installation.

Lessons learned:

Veeam Support is awesome, they contacted me very quickly and solved my problem within an hour or so.
When running into strange behavior with the installer, try to repair or reinstall the .Net Framework it might solve your problems.

Solving the com.vmware.sps.fault.QsConnectionException error

1 Reply

After en APD (All Path Down) in our hosting environment I had the following error when I tried to do something with the ESXi datastores.

The VMware environment was working correctly.
I started searching the VMware Knowledge base and found KB2064174. This KB describes exactly my problem.

Symptoms

Selecting/browsing a datastore, the VMware vCenter Server 5.1.x displays the error message:

com.vmware.sps.fault.qsconnectionException

Selecting the Storage Views of any datastore displays the error message:

cannot initiate storage service

vMotion or an offline migration of a virtual machines fails with the below error message:

pbm.fault.PBMFault.summary

Resolution

To resolve this issue, ensure the VMware inventory service and the VMware profile Driven Storage Service are running.

Log in as an administrator to the server that is running the vCenter Server.
Click Start > Run.
Type services.msc
From the list of services, check the status of the VMware inventory service and the VMware profile Driven Storage Service.
If any of these services are not running, right-click on the service and select Start. (A restart of the services may be applicable as well).

Note: If both of the services are not running, start the Inventory service first and the Profile Driven storage service second.

For VMware vCenter Appliance 5.x

Restart virtual center server through the web interface.

Log in to the vCenter Server Appliance’s VAMI (Virtual Appliance Management Interface) at http://<IP/hostname of VC>:5480
Select the Summary tab under vCenter Server.
Click Stop beside vCenter Server to stop the process.
Click Start beside vCenter Server to start the process

In my case all the services where running, so I restarted the VMware vCenter Inventory services. After this restart the error message disappeared when browsing the datastores.