#Qlikview Responsibility Box

So this is a simple idea so that users know who to go to with questions about specific Qlikview i.e. who is the ‘SHMEEEE ‘

So use a variable in the load script

vDocOwner = ‘’

Now create a text object displaying the vDocOwner

If you want to be extra fancy (For extra fancy you can even include the name of the document in the subject…. & subject=)

In its properties, on “Action” tab, choose : “Open URL”

In the command line, write :

Now if they click on they can send the responsible party an email….

There, enjoy extra responsibility responsibly




Also, I should make a link to a wiki page that describes the Qlikview but I will save that for later.


#Qlikview rules of thumb

This is a short list but will continue to add more. These are mainly coming from the Qlikview masters summit

Declare all variables in the script (Especially important if you use source control)

Drop the seconds from DateTimeStamps if not needed (probably not needed most of the time)  I’ve been using cast(TheDate as Smalldatetime) as TheDate as a SQL way of doing it (any better ways??)

IF’s are evil, especially if the execute for every row

#mimecast getting ready to start sending outbound using their ‘smart host’

So far the documentation has been pretty good. We are running an old 2003 exchange server and I don’t really specialize in exchange so it has been a learning experience. Hopefully we won’t send everyone’s email into a black hole 🙂

#VEEAM VPower NFS volume already exists The specified key, name, or identifier already exists

Restart the management service fixed it for me.

[ warning] [vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.


(I didn’t have to reboot)

It seems that the upgrade didn’t create the file tools.conf

You can create it like this:


log = true

# Enable tools service logging to vmware.log
vmsvc.level = debug
vmsvc.handler = vmx

# Enable new “vmusr” service logging to vmware.log
vmusr.level = error
vmusr.handler = vmx

# Enable “Volume Shadow Copy” service logging to vmware.log
vmvss.level = debug
vmvss.handler = vmx

Save it as tools.conf in the appropriate folder for the guest OS.

Windows XP and Windows Server 2000/2003
C:\Documents and Settings\All Users\Application Data\VMware\VMware Tools\tools.conf

Windows Vista, Windows 7, and Windows Server 2008
C:\ProgramData\VMware\VMware Tools\tools.conf

Linux, Solaris, and FreeBSD

After saving and closing, restart the Tools service.

Just getting started with #mimecast

So far so good, they really have their ducks in order as far as laying out what needs to be done and how. I really think we will like this service.

Proper Etiquette For Unmounting a LUN or Detaching a Datastore/Storage Device from multiple ESXi 5.x #EqualLogic #VMWARE

So I was complaining to a group of fellow nerds about how much a pain in the butt it is to ‘properly’ remove a LUN from ESX… you know so that you don’t cause an APD incident (you know, accidentally freeze up all of your virtual machines…)

So the proper procedure is painful (less painful though than it used to be with 4.1 ESX though)

So then of course vmPete chimes in with I just use the EqualLogic HIT kit Virtual edition

Duh! I had been so busy getting ESX5.1 i setup and the new vcenter that I forgot all about it! Well let me tell you, it is a lifesaver! With just a couple of clicks I can create a volume, and with a couple of clicks I can delete a volume! Do you know how much time and pain that saves! So now I’m having fun recreating my volume with vmfs5.