The point I was trying to make, as Bert pointed out, was my frustration with tech support initially asking to log into my system, without really reading the error message I pasted into the chat window. This seems to be the default response no matter what I am asking in a tech support chat (except when I asked for v8.2.4, they very promptly and nicely sent me the links, for which I thanked them profusely).

FYI, this was the error message:
Quote
subject: An automated process failed: ACHubReceive

Error retrieving interface messages from the Amazing Charts Message Hub.
An Amazing Charts automated process failed.
Service Task Name: ACHubReceive
Service Task Description: Check ACHub for messages
This service task has 86 consecutive failures.
Error Details:
Unable to connect to the remote server
Please check to see if you are connected to the internet.
More details are in the service log file.

There is absolutely no reason for tech support to respond, "Can I log in and take a look?" when I ask "What generated this error message I just received? Especially the 86 consecutive errors. I'm not having any problems connecting to the internet."

It's a freakin' AC generated error message that came to my inbox. That should simply be a look up in their book of automated error messages and a response like "Your system has been unable to connect with the ACHub. Since you are not having problems with your internet connection, let me find out if there has been a problem on our end." With further discussion if there has been no problems with ACHub.

And to add to my frustration, the tech told me later in the conversation, "we normally don't walk people through a troubleshooting process."

Originally Posted by JamesNT
What you guys have to understand is that for every complaint you register about how someone in tech-support treats you like you know nothing about computers and how annoying it is, I've got at least 12 stories like the one above.
And for every story about a smart [censored] doctor with an advanced degree, I can give you at least 12 stories of tech support who don't listen to what I have to say, and can't understand that I've already done the first 20 steps on their troubleshooting algorithm.