• Recently Written

  • Kali Blue Screen & No Icons
  • Recover media files from HTC HSMBackup
  • RPC_S_Server_Unavailable error (0x6ba) and Microsoft Exchange is unavailable.
  • The Case of Metasploit and the Facebook Cookies.
  • Geoffrey Clifton-Brown MP
  • Extract embedded Flash (SWF) files from a PowerPoint presentation
  • What to look for in an IT support company
  • Jerky Mouse in Windows 2008 R2 under ESXi4.1
  • Moving shares between SBS 2003 & SBS 2008
  • Moving lists between SharePoint sites

• Categories

  • Funny
  • IT Tipz & Trix
  • Misc
  • News
  • pok3rz
  • Rants
  • Reviews
  • Sighs
  • Uncategorized

• Archives

  • January 2017
  • October 2014
  • April 2014
  • March 2013
  • March 2012
  • February 2011
  • October 2010
  • June 2010
  • January 2010
  • July 2009
  • February 2009
  • January 2009
  • December 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007

• Blogroll

  • Inferno - International Man Of Mystery. And a very good friend.
  • Merlijn - One of my best friends in Holland

• Admin

  • Log in
  • Wordpress
  • XHTML

RSS feed

Have you tried re-installing it?

Posted by bb on Wednesday 15th of July 2009 at 3:38 pm;.
Filed Under Misc, News 

You know what, I actually think I’ll get a reply from Ed – he is doing a good job of restoring my faith in support, if not Sage as yet. For that we’ll see how they deal with the actual support call when it goes in.

Well, to say not well would be an understatement.

I listened in on the support call that we made to Sage today. Apparently it is all the fault of someone else. Third party software you see.

No, it’s not ACT!’s fault that it incorrectly queries the OS for available TAPI interfaces. Its all to do with the way they link in you see. If the 3rd party software (a telephony interface, AFAIK, barely constitutes 3rd party software, but that’s why I’m not good enough to be a Sage tech support guy) isn’t written specifically to link in the right way with the way that ACT! links, well then the link is all wrong. And with wrong linkage – well – that’s out of supports hands! What can they do? No – of course they can’t tell ACT to requery the TAPI interfaces. No no no.

That is the sum total of the support I got. The TAPI interface was there, I uninstalled it, removed it as suggested by Ed and it still wasn’t there. I repeated this on a machine where ACT! had found the TAPI interface, and again ACT! lost it.

And this is where we got to the piece de resistance.

Have you tried re-installing it?

Why would I do that if it wasn’t ACT!’s fault? Maybe re-installing the software will rewrite the third party software’s bad linkage?

Why yes … that makes sense …

Whilt I commend Ed for trying to offer support, I condemn the actual support you get off them – especially the chap who tried to tell me the story of the never ending linkage. It was a stream of rubbish that nearly rivalled the salesperson who once told me the difference between a 486SX and a 486DX was that a DX could have an internal modem!

Sometimes, just sometimes, the person calling in for support actually has a fairly good handle on all things IT. Trying to baffle them with bullshit is a poor tactic in these cases -especially when you’re called on it and asked ‘how does ACT! query TAPI interfaces?’ and the best you can manage is ‘support doesn’t write the software’. This underlines your understanding of the problem and indicates that perhaps you are out of your depth a little.

Good luck buying support from Sage. You’ll probably end up spending good money to hear ‘it’s 3rd party software you see, not designed to link it properly with our linkage. Have you tried re-installing it?’.

Cunswups 🙁

(No Ratings Yet)

Loading...

Comments