Fail Error: The object has already been deleted or has not been completely created #VEEAM

So apparently there is some bug with Veeam connecting to ESX 4 servers and sure backup. It causes sure backups to fail with the “Fail Error: The object has already been deleted or has not been completely created”

They fixed it with

“After changing the protocol to 2 and removing SSH auth from the ESX 4 hosts (in our database) we were able to successfully create a new virtual lab.”

The sql statement they used looked something like this:

select * from dbo.hosts order by name asc

delete from dbo.ssh_creds

update [VeeamBackup].[dbo].[Hosts] set protocol=2 where info like ‘VMware ESX 4.%’


Some #Mobile #Qlikview Designs

So I have been working on setting up some scorecarding and dashboarding Qlikviews for display on iphone/ipads. One design tip: design it to be readable on an iphone and it will look perfect on an iPad.

So for lack of a better name I call the top of our “BI” pyramid the scorecard. This is simply a rolled up grade of some metrics.

It looks like this:



If something concerns you (or you want to know more, you simply press say the Bookings KPI) and that will open up the Bookings KPI Dashboard. I did this with an ‘Open URL’ Action and the use the

‘AJAX’ link to the qlikview http://qlikview.nffc.local/QvAJAXZfc/opendoc.htm?document=Sales/BookingsKPI/BookingsKPI.qvw&host=QVS@qlikview

bookings dashboard



Now, if you want even more specific information you can drill down by pressing the ‘To Bookings By Commodity”


This opens up the Bookings Commodity Dashboard

It looks like this

Notice buttons down the right (better ipad/iphone UI)

Sales Type COMMODITY customer

I use list boxes because this allows for single click (instead of click and hold which I find an annoying interface most the time) for charts I will overlay a listbox to accomplish this.



Random #Qlikview Learning

Need to create a list box that actually doesn’t show the excluded values create a ListBox with an expression (Scroll all the way to the bottom when picking a field)

=aggr(Only([Commodity code]), [Commodity code])

I’m overlaying a Listbox over a Chart because with the iphone/ipad a listbox allows single click to make a selection.

If you need to change the background of a list box then you need to pick a different style other than Qlikview Classic, then you are able to change to background color and do transparency.

Source Control (Subversion) With Qlikview 11.2

So, we already have an SVN server setup for our RedGate Sql Source Control. It is a easy install of visualSVN. (Subversion 1.7)

I haven’t compared it yet, but eventually want to compare it with the colab net version.

This is the doc I’m working from for Qlikview source control (It’s outdated but hopefully it will work good enough)

So I’ll download myself some TortoiseSVN 1.7.11, I had to specify that I want the command line tools (I’m pretty sure I will need these)

Based off of Page four of the Source Control Whitepaper it looks like it need to configure the Source Control Settings/SVN settings. The path in the guide is c:\program files(x86)\Subversion\bin\svn.exe

After installing tortoiseSVN it looks like there is a copy of svn.exe in the C:\Program Files\TortoiseSVN\bin\svn.exe  directory

C:\Program Files\TortoiseSVN\bin\TortoiseMerge.exe is in this dir as well

And the Merge Tool Parameters:  /base: %base /mine: %mine /theirs: %theirs /merged: %merged

Then you can check a project in, hmm so far so good it looks like it works.



Fun with #vmware ESXi5.1 #IBM 3690

So wanted to find the recommended settings for ‘UEFI’ for the 3690 for vmware. Finally found it here page 262

To Fix: System Management Software 1 SEL Fullness: Log almost full #VMWARE

To clear it

So you bought an #EqualLogic and now you are setting it up with #VMware ESXi 5.1

So I wish there was one consolidated doc of settings to change for ESXi 5.1 and EqualLogic. Anyone out there have more settings please let me know!!

To start from here

1.)  Delayed ACK DISABLED

2.)  Large Receive Offload DISABLED

3.)  Make sure they are using either VMware Round Robin (with IOs per path changed to 3), or preferably MEM 1.1.0.


4.) Set Login_timeout to 15 or 30 seconds

I contacted EqualLogic support and they replied:

Solution Title HOWTO: Disabling TCP Delayed ACK may improve read performance with ESX 3.x/4.x/5.x software iSCSI initiator.Solution Details ESX allows you to disable the delayed ACK on your ESX host through a configuration option and may improve the read performance of storage attached to ESX software through the iSCSI initiator. PLEASE NOTE: this change will require a reboot of the ESX server to take effect.

Disabling Delayed Ack in ESX 4.0, 4.1, and 5.x

1. Log in to the vSphere Client and select the host.

2. Navigate to the Configuration tab.

3. Select Storage Adapters.

4. Select the iSCSI vmhba to be modified.

5. Click Properties.

6. Modify the delayed Ack setting using the option that best matches your site’s needs.

Choose one of the below options, I, II or II, then move on to step 7 after making the changes:

Option I:

Modify the delayed Ack setting on a discovery address (recommended).

A. On a discovery address, select the Dynamic Discovery tab.

B. Select the Server Address tab.

C. Click Settings.

D. Click Advanced.

7. In the Advanced Settings dialog box, scroll down to the delayed Ack setting.

8. Uncheck Inherit From parent. (Does not apply for Global modification of delayed Ack)

9. Uncheck DelayedAck.


10. Reboot the ESX host.

NOTE:  From

One thing about Delayed ACK, is that you have to verify that the change took place.  If you just change it, it appears that only new LUNs will inherit the value. (disable)   I find that, while in maint mode, removing the discovery address and any discovered targets (in static discovery tab), then disabling Delayed ACK and re-add in Discovery Address and rescan resolves this.

At the ESX console run:   #vmkiscsid –dump-db | grep Delayed     All the entries should end with =’0′ for disabled. ( note that is a – – two dashes before the dump-db silly WP font)

I ran it and experienced the same, only some of the connections had the DelayedAck set correctly. So definitely remove the discovery address and static targets to fix.

iscsi log dump

To disable LRO  from

HOWTO: Disable Large Receive Offload (LRO) in ESX v4/v5
Solution Details
Within VMware, the following command will query the current LRO value.# esxcfg-advcfg -g /Net/TcpipDefLROEnabledTo set the LRO value to zero (disabled):# esxcfg-advcfg -s 0 /Net/TcpipDefLROEnabledNOTE: a server reboot is required.

Info on changing LRO in the Guest network.

To disable LRO, follow this procedure:

  1. Log into the ESXi host or its vCenter with vSphere Client.
  2. Select the host > Configuration Software:Advanced Settings.
  3. Select Net and scroll down slightly more than half way.
  4. Set the following parameters from 1 to 0:
    • Net.VmxnetSwLROSL
    • Net.Vmxnet3SwLRO
    • Net.Vmxnet3HwLRO
    • Net.Vmxnet2SwLRO
    • Net.Vmxnet2HwLRO
  5. Reboot the ESXi host to activate these changes.

Your guest VMs should now have normal TCP networking performance.

Set Login Time Out


This vmware 5.1 document points to this KB article

To change the login timeout from the vSphere client:
  1. Go to Storage Adapters > iSCSI Software Adapter > Properties.
  2. Select Advanced and scroll down to LoginTimeout.
  3. Change the value from 5 seconds to a larger value, such as 15 or 30 seconds.







On second review the Official Documentation for the EqualLogic MEM (Rev 1.2, which covers vSphere 5.1)


Deployment Considerations: iSCSI Login Timeout on vSphere 5.1 and5.0
The default value of 5 seconds for iSCSI logins on vSphere 5.x is too short in some
circumstances. For example: In a large configuration where the number of iSCSI
sessions to the array is close to the limit of 1024 per pool. If a severe network
disruption were to occur, such as the loss of a network switch, a large number of iSCSI
sessions will need to be reestablished. With such a large number of logins occurring,
some logins will not be completely processed within the 5 second default timeout
Dell therefore recommends applying patch ESXi500-201112001 and increasing the ESXi
5.0 iSCSI Login Timeout to 60 seconds to provide the maximum amount of time for
such large numbers of logins to occur.
If the patch is installed prior to installing the EqualLogic MEM, the MEM installer will
automatically set the iSCSI Login Timeout to the Dell recommended value of 60


Automatically setup is nice in theory but doesn’t appear to work with ESX5.1 ??? I had to set mine to 60 manually

I was able to find these three recommendations under the support portal under here

They are

HOWTO: Disable Large Receive Offload (LRO) in ESX v4/v5

HOWTO: Change Login timeout value ESXi v5.0 // Requires ESX patch ESXI500-201112001

HOWTO: Disabling TCP Delayed ACK may improve read performance with ESX 3.x/4.x/5.x software iSCSI initiator