Tag Archives: Problem

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!

Resetting an expired password in vCenter 5.1 Single Sign-On (SSO)

Leave a reply

A customer of ours was unable to login to their VMware vCenter 5.1 environment. I researched the environment and concluded that there SSO password was expired.

Error messages in the vSphere webclient: “provided credentials are not valid”. Also the admin@system-domain account was unable to logon, same error message. And I was 100% sure this was the correct password.

I started searching the VMware KB articles and found one that describes how to reset the password. See VMware KB2035864.

Resetting an expired password in vCenter Single Sign-On (SSO) (2035864)

Details

  • vCenter Single Sign-On account (SSO) passwords expire after 365 days, including the password for admin@system-domain.
  • In vSphere 5.1, you see this error on a login attempt with an expired password:
    Web Client: “provided credentials are not valid”
  • In the vsphere_client_virgo.log, you see the error:
    SOAP fault javax.xml.ws.soap.SOAPFaultException: Authentication failed

Solution

vCenter Single Sign-On administrator users can change expired passwords for System-Domain users. Request that an administrator resets your password.

If you are a vCenter Single Sign-On administrator user, use the ssopass command-line tool to reset the password.

On the Windows host running vCenter Single Sign-On:

  1. Open an elevated command prompt and run the command:
    SET JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre
    Note: This is the default path of the JRE folder for vCenter Server 5.1. If vCenter Server has been installed in a custom location, change command accordingly.
  2. Navigate to the ssolscli directory
    c:\>cd C:\Program Files\VMware\Infrastructure\SSOServer\ssolscli
  3. Run the following command:
    ssopass -d https://FQDN_of_SSO_server:7444/lookupservice/sdk username
  4. Type your current password, even if it is expired.
  5. Type the new password, and then type it again to confirm.

Note: If the above steps fail to update the password, see Logging in to the vSphere Web Client using admin@system-domain fails with the error: associated users password is expired (2060150).

From the vCenter Server Appliance (VCSA):

  1. Log in to the vCenter Server Appliance as root.
    Note: The default password is vmware.
  2. Navigate to this directory:
    /usr/lib/vmware-sso/bin
  3. Run this command:
    ./ssopass -d https://FQDN_of_SSO_server:7444/lookupservice/sdk username
  4. Type the current password for the user, even if it is expired.
  5. Type the new password, and then type it again to confirm.

This document helped me to regain access to the VMware vCenter environment. Problem solved.

Exchange 2010 error solved : The WS-Management service cannot process the request.

Leave a reply

When you try to open the Exchange 2010 Management Console, you may receive an error:

The attempt to connect to http://exchangeserver.domain.local/Powershell user ‘Kerberos’ authentication failed: Connecting to remote server failed with the following error message: The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least X milliseconds.

See screenshot below.


There is a very quick and easy fix for this error message.

Open an elevated command prompt and type:

IISRESET


Now try opening the Exchange 2010 Management Console again, it should be working again. 

Problem solved!

After partition extend file system displays wrong disk size in Windows

34 Replies

Recently I was working on a VM that has some free space problems on the Exchange partition of a Windows 2008 SBS server. So I extend the hard disk in VMware and Windows. That’s easy….

I extended the Hard disk size in VMware. Then I extended the Disk size in the Disk Management tool. All without any problems. But when I was checking the disk size in the Windows Explorer the size was incorrect. The old size was still showing. This is not good!!

 

Screenshot of the hard disk size in VMware.

 

Screenshot of the disk size in Storage Manager.

 

Screenshot of the disk size in Windows Explorer.

The fix is simple, open an elevated command prompt and start DISKPART

List all volumes of the server.

DISKPART> list volume

Select the volume that has the wrong file system size. x is the ID of the effected volume.

DISKPART> select volume [x]

Extend the file system

DISKPART> extend filesystem
 

Screenshot of the Diskpart commands.

If all went well diskpart fixes the size of the file system.

Go to the Explorer and the correct disk size is shown. Problem solved.
 

Screenshot of the corrected disk size in Windows Explorer.

Installation runs everytime we start Outlook 2013 application in Terminal services

5 Replies

I was installing a Windows 2008R2 Remote Desktop Services Host with Microsoft Office 2013 when I ran into a strange thing. Every time I started Outlook 2013 there was a installation screen, “installing Microsoft Office 64-bit Components 2013”. This screen appears for a few second and the Outlook started. This is very annoying! The application was working normally.

I found the solution at the Microsoft Forums, here.

What to do to solve this annoying screen.

Install Windows Search Services under the File Services role. Do not add any disk drive for indexing. Put the RDS server in install mode, start Outlook 2013. Now the installation screen is gone. Put the RDS server in Execution mode and the problem is solved.

Solving the Invalid configuration for device ‘0’ error

Leave a reply

Today I noticed something strange in our brand new VMware vSphere 5.1 environment. I was trying to patch a Windows 2012 template when I noticed it didn’t have a network connection. This VM is using a Distributed Switch Configuration.



So I checked the VM settings, and indeed it wasn’t connected.

So I checked the Connected box, and the following error appears. Invalid configuration for device ‘0’. See screenshot.

The solution for this error is simple. Connect the network card to another network. Than place it back to the original network. Now it works again.
For more information about this error see the following articles:

Veeam backup file is not getting smaller when removing a VM from backup.

3 Replies

I ran in to a problem with the VBK file size of a Veeam backup Job (running Veeam B&R 6.5). It didn’t fit on tape anymore. So I split up the Job into two different Jobs. One with important VMs and one with less important VMs. The important VM backup job goes to tape, and the other one stays on disk.

But after I deleted the VMs from the Job my VBK file size didn’t get any smaller. It was only growing. That was not what I expected.
So I contacted Veeam support and they pointed me into the right direction. See http://helpcenter.veeam.com/backup/70/vsphere/index.html?retention_deleted_vms.html

There is a Delete VMs date retention period. Default its configured at 14 days. See explanation and screenshot below.


In the VM retention section, specify the number of days to keep backup data for deleted VMs.  When a backup job starts, Veeam Backup & Replication checks the list of VMs included in the job. If a VM is no longer available (for example, it was deleted or moved to another location), Veeam Backup & Replication will keep its data in the backup for the period you specify in the Deleted VMs data retention period field. When this retention period is over, data of the deleted VM will be removed from backup files.

The retention period for deleted VMs is particularly useful if the job is configured to create synthetic full backups, and you want to make sure that the full backup does not include redundant data.
This was an option that I didn’t know it existed. So I changed this to 3 days, and indeed the backup job shirked. Problem solved, the Veeam job fits on tape again.

** Edit 14-02-2014, updated Veeam link to the new location. Thanks Cor for pointing that out.