Pipedrive and Zendesk Integration

If your Customer Service System and your Sales CRM are separated it is important to integrate the systems. Without a proper integration either your Sales or Customer Service team might be missing important informations. This free Pipedrive and Zendesk integration will help you solve this issue.

Recently I had to use Zendesk as our customer success system and Pipedrive as our Sales CRM. I have worked with Salesforce for the past 6-8 years and love it. Moving to Zendesk and Pipedrive was quiet a bit of change for me. While these two systems are cheaper than Salesforce they do have a couple of drawbacks. When I started out with both systems I was looking for a Pipedrive and Zendesk integration and came across the official Pipedrive plugin for Zendesk. Read More

Corrupt Snapshot Causing View Composer Service Crash

Error during provisioning:Unexpected VC fault from View Composer

The above error might show up in Horizon View, if you try to use a corrupt snapshot for the deployment of new VMs.

How To Identify If  A Corrupt Snapshot Is The Cause?

  • Look at the Microsoft System Event Log on your View Composer
    • You should see something like this:

      The VMware View Composer service terminated unexpectedly. M It has done this 2 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.


  • Search for FATAL messages in the vmware-viewcomposer.log
    • The following message will indicate a corrupt snapshot

      2015-10-06 17:52:53,956 | WFE thread 9 | FATAL | ServiceCore.WorkflowEngine.WorkflowEngine – Unexpected exception occurred.Error reading single property ‘config.hardware.device’ from managed object: snapshot-15587


Read More

Ultimate Bash Guide For Beginners

bashEveryone who is new to scripting always doesn’t know where to start. There’s countless websites and blog posts out there with endless number of commands and bash guides. I don’t want to share all those super complex commands which are difficult to understand when you first start out with writing some scripts. Instead, I am providing a short bash guide for beginners. This post will cover the basics, some good manners and some more advanced commands.

One of the reasons why I started to write scripts in bash is because bash was just the language I knew due to Linux distros. However, I’m by no means an expert in writing scripts. If someone would ask me about my level of expertise in this area, I would rate myself with a “C”, maybe a C+.

Even though I am not an expert, I think it will be useful to share my experience and the commands which I have used most often. Below some general tips and commands which have helped me in the past and I still sue every day for some basic scripting.

General tips and tricks

Use clear and precise comments.
This will allow other users to easily read and understand your code.

User proper indention
Indention will make your code easier readable. If your code is easily readable, it will be even easier to maintain it in the future.

Let your script bail out if any command fails
For debugging of your script, you should use set -e at the beginning of your script.
Using set -e ensures that your script exists as soon as any of the lines is failing.

Every bash script has to start with it
The first line in every bash script has to be #!/bin/bash
This will tell your terminal which interpreter to run.

Common Commands

Declare a timestamp function
For all my scripts I declare a function which stores the current timestamp when it is called.
I mainly use the timestamp variable for logging of events.

The output will look like this:

Use $? to check the previous command
You can use $? to verify whether the previous commands returned 0 or 1.
0 = successful | 1 = failed

If the script was able to create the file it will return:

Read a file with comma separated values and act on it
When querying a database and saving the results as a CSV file, each results will be stored in a line and each value will be comma separated. Below is s simple script which scans a CSV file for the 4th value in every line and prints it, if it is not empty.