Search results for

#999

#1 Click this link to see Blog page --> 09/19/2010

Hi Mom,
I’m still getting them —— I don’t know what the problem is. My web host provider says it is my ISP which is Frontier and Frontier says it is the web host. I still get Error #999 YaHoo error messages every six or seven times I click on my site. I suppose eventually I will get to the bottom of this but I am getting tired of it!

MjL

#2 Click this link to see Blog page --> 09/20/2010

I have gotten the #999 error message going through the political cartoons, backing up eventually works to get back to one I’ve seen but then get the message on trying to go forward, come back to it in a few minutes and it works fine.

Michael T.

#3 Click this link to see Blog page --> 09/20/2010

#999
Thank you Michael,
I am becoming more convinced it is a spam prevention issue with YaHoo Web Hosting because it seems more prevalent with numerous clicks in a short amount of time. I know there is quite a lot they are not telling me about what is going on but I shall continue calling them. These things are always an aggravation. I wish we had the death penalty for spammers and virus code writers, maybe the rest of us wouldn’t have to pay the price for their mischief quite so much.

MjL

#4 Click this link to see Blog page --> 09/28/2010

Oh good grief! I wouldn’t be surprised they are planting shoes too!

On a different note I have spent some time on the phone with the Yahoo tech support dudes. They had me run a trace route and email it to them, then I took Tracey’s laptop to the Bob Evans WiFi where I also get the #999 error and ran a trace route from there to email to them as well. Nothing like having to do their job FOR them?!

MjL

#5 Click this link to see Blog page --> 10/05/2010

#999
Here’s an error screenshot for your Yahoo people, dad--I got it going through the eagle pictures

[Link is Broken]
http://i51.tinypic.com/eknbwj.jpg

Noah L

#6 Click this link to see Blog page --> 10/05/2010

#999
Thanks Noah, I don’t think the ninnies have clue one what is going on. I called again yesterday morning but they can’t seem to make any progress on what is happening. I don’t think they are even trying very hard. They are trying to prevent spambots with this error trap but aren’t concerned that they are screwing up legitimate traffic.

MjL

#7 Click this link to see Blog page --> 10/16/2010

Ok...I got an error last night and this morning -- #999 error whatever that means! The one this morning is when I tried to click the arrow button to go to picture #2 about the longest railroad. Maybe I just can’t see that picture?

Tammy

#8 Click this link to see Blog page --> 10/16/2010

Hi Tammy,
This is the #999 problem I have been having with Yahoo (they are my web host) for about a month now. I have called about 20 times and have never talked to the same person twice and only to someone who’s first language is English about half the time. They simply refuse to believe the problem is theirs even though the damn error message is clearly from them with their name on it. I don’t know what to do with it. I hate to move to another server because of all the hassle and I would have to change my domain name. Usually if you just keep hitting refresh it will eventually start working right. I am sorry and I will keep trying to get through to these bumbling “technicians and engineers”.

MjL

#9 Click this link to see Blog page --> 10/17/2010

I spent an hour and 17 minutes on the phone with the Yahoo Tech Support people again yesterday. My 13th call since this all started on Sept. 17th. Maybe it will be lucky number 13?

The guy managed to suggest I try just about everything that has already been discussed and I finally told him I was absolutely disgusted with this continued attitude that I was supposed to find a way to fix their rotten buggy software problem. I told him I thought they ought to track down the person who wrote the software routine that routes page hits to that stupid #999 Error Page and FIRE THEM!

There is just no excuse why everyone has to deal with this crap just because they can’t find a better way to stop people from spamming or attacking their networks.

“My Problem” is supposed to get “escalated” again, again. I have serious doubts they have “engineers” that can find their ass with either hand.

MjL

#10 Click this link to see Blog page --> 11/13/2010

After all these weeks I am still getting that goofy Yahoo #999 error on the #Blog. I keep calling but I’m down to once a week. I don’t think they will ever fix it but I have to run up their phone bill a little!

MjL

#11 Click this link to see Blog page --> 11/18/2010

I just spent another 45 minutes on the phone with the Yahoo Technical support dude —— If nothing else I am running up the bill on their 800 number.

I would like to hope they will eventually get to the bottom of these #999 Errors but so far they seem determined to make it my fault somehow without any evidence to point toward what I should be doing differently.

MjL

#12 Click this link to see Blog page --> 11/19/2010

I got a phone call last evening from Nathan. He spent some time trying to convince me the Yahoo #999 Error is an “IP error”.

What I heard is that he could care less about this #Blog problem caused by Yahoo and he wasn’t going to offer any reasonable explanation or make any effort to rectify the situation.

Somebody at Yahoo designed this crap software to prevent multiple connections and so if you get the error it is because your IP made multiple connections. No further discussion.

His reasoning is you wouldn’t get the error for any other reason because it was specifically written for that reason.

The same logic would say that if you shoveled horse manure into Nathan’s car he would spend the day looking for a horse in his glove box because only a horse could have done it?

Nathan’s best advice was if you get a 999 Error —— wait an hour for it to go away. Good grief.

Anyway, when I call again later today I want to make sure Nathan is not a part of the problem and get someone who might actually know what they are doing to look into this.

MjL

#13 Click this link to see Blog page --> 11/19/2010

#Blog I just thought of another analogy to explain #999 Nathan’s faulty logic circuits.

Smoke alarms are designed to warn you in case your house catches fire. So if Nathan’s smoke alarm goes off he is calling the fire dept. even when he can see the house is not on fire.

Because the smoke alarm wouldn’t go off unless the house was on fire and he just can’t find the fire.

Because he is looking for a house fire he neither looks for or sees the burnt toast in the toaster.

MjL

#14 Click this link to see Blog page --> 11/23/2010

#999
I just got off the phone with Frontier Tech Support to see if they could find any reason for the “IP multiple pings” problem reported by Yahoo.

He did a line test and said that I have “intermittent connection issues”. He asked me what brand modem I have and said that might be the problem because it is not the brand they use.

So now a new modem ($59.99+tax+etc.) is on the way. I have my doubts about this but he said they can’t “dispatch” anyone to investigate the problem until my equipment is to specification. It just keeps getting better doesn’t it?

MjL

#15 Click this link to see Blog page --> 11/23/2010

I have a feeling that your modem isn’t causing ME to get those #999 errors that I see every now and then

Noah L

#16 Click this link to see Blog page --> 11/23/2010

Hi Noah —— I think you are probably right. The yahoos at Yahoo say that once they receive 1000 pings in a minute they flag my site so that ANY IP can encounter #999 Errors. I think they are full of sh*t but I called Frontier anyway.

Since they say they have encountered a problem which might cause my computer to make multiple pings to resolve incomplete packets I thought I better play along. As long as either Yahoo or Frontier can find a problem to point to they won’t look any further.

So I have to get that resolved I guess before I can get them to look for what the real problem might be. I have to be able to prove there is not a single possible problem on my end before they will even try to fix it. Life in the tech world I guess.

MjL

#17 Click this link to see Blog page --> 11/29/2010

I am almost afraid to say anything —— and I sort of feel like holding my breath —— but I haven’t seen a #999 Error for quite a while today.

So far it seems I can browse throughout my site without triggering any. I hope I’m not premature but maybe I owe somebody at Google a thank you for fixing something because I sure didn’t do anything new.

MjL

#18 Click this link to see Blog page --> 11/30/2010

It is really nice to work on the Blog this morning without all those dag-nab #999 Error messages!

I have almost literally been holding my breath since yesterday afternoon for fear it was only a temporary fix or something. I have been able to breeze through my Blog updates without any trouble. I think it will be more fun again if this keeps up!

MjL

#19 Click this link to see Blog page --> 03/03/2011

Home again. Now I am sitting on hold listening to atrocious music waiting to find out if Yahoo Tech Support is ever going to do anything with the #999 Errors. Again.

I am told the “engineers” are looking into it. I asked her what was needed to “look into”. She didn’t know and put me on hold to talk to her “escalation team”. Ah, she just came back.

I am told, “The Escalations team is actively working on it.” The check is in the mail. And other vacuous platitudes. At least they haven’t closed it out as my fault - yet.

MjL

#20 Click this link to see Blog page --> 03/04/2011

I just got off the phone with Casey at Yahoo about the #999 Error messages. They have made some changes and it would appear they may have the problem fixed! I don’t want to be premature so I will give it some time, but I am very hopeful. I may have to take back one or two of the nasty things I said about them.

MjL

#21 Click this link to see Blog page --> 03/24/2011

I got a phone call from Hugh last evening. He told me he was an engineer for Yahoo Web Hosting and wanted to follow up on the #999 Errors I was getting a few weeks ago. I told him everything had been fine for weeks.

Notice I use the words “had been”? This morning it is all messed up again. I can’t imagine that is a coincidence. So I have to wonder why Hugh would change something when I had just told him it was working fine.

MjL

#22 Click this link to see Blog page --> 03/25/2011

I sent an email off to Casey at Yahoo yesterday and then later in the morning I called and talked to Shannon about my #999 Error problem. Later in the day things started working properly again and I got an email from Luke telling me they had made “some adjustments”. I am getting to know these people on a first name basis. That’s not really a good thing.

MjL