Yahoo Hosting Hell

[Finntastic]

Who are the rock solid commercial service providers with SLA options
and Frontpage native servers to consider for a web-hosting service
provider?

<flame>

I am finished with Yahoo. Last week, the service outage was 3 plus
days involving 38 hours of dedicated time trying to work with Yahoo to
solve the problem. Today the sites are down again. This really hurt.
Bad.

FP 2003 is my publishing product of choice. Over the past year FP2002
and FP2003 have functioned well with my two Yahoo Business evel Web
Hosting accounts. Except for linkbars and DWTs, the hosted product is
quite vanilla. A January 2005 upgrade to Yahoo Merchant services was
next. Not now.

Error code #2001d, or Frontpage Server extension remains the unfixed
problem. I full well appreciate that FP hosted on Unix servers with
FP extensions is a tricky business for an ISP. But after nine calls
last week and another 3 already today, I see what is behind the Yahoo
support curtain. It ain't pretty. It is a mess. Frontline support
people try thier best but are green. Yahoo provides nothing in the way
of tracking or CRM tools or technical Tier 2 support. Escalation and
process for problem resolution are the same.

Each call always starts from ground zero and involves the same rote
script. This is expected for the price. What is unacceptable are the
"I guess" and "I hope" recommendations. It's ground hog day on each
call. No escalation or process either. If the line is dropped or a
new call made, its a restart even with trouble tickets. The first line
is the only line of support at Yahoo.

<flame + flame>
And to top it off,after the 3 day outage comes this jewel in public
relations from a Yahoo support rep and after I am told the problem is
clearly Yahoo's and is escalated to Yahoo Engineering:

"Thank you for contacting Yahoo! Customer Support. case # xxxxxx

The reason you are having problems using FrontPage features is that you
have uploaded files with names that contain spaces or other alternative
characters such as "*", "&", "!", etc..

Here are a few examples of files we have located which have invalid
names: (five file name & locations)."

awwwwwh

AFter 8 times on 8 different calls of answering the same question that
yes all files are fine, I am told the 3 day service outage is my fault.
What the note failed mention is these "bad files" are not on the
broken domain.

What is next? Run from Yahoo Web hosting. </flame>

 

[Steve Easton]

Interesting.

However, the part about FrontPage Extensions on UNIX being "tricky" isn't true.
All of my webs run on "extended" UNIX servers, one of which receives well over a million hits a
year, and I have yet to have "One" issue with extensions.

? ;-)
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

 

[E. T. Culling]

Try these folks:
http://www.askenvision.com/ They are local for me (Wenatchee, WA) and are
hosting most of my client's sites.
Eleanor

 

[=?Windows-1252?Q?Rob_Giordano_\=28aka:_Crash_Gordo]

It's not tricky..just different...and usually the "techs" don't wanna deal with FP.


| Interesting.
|
| However, the part about FrontPage Extensions on UNIX being "tricky" isn't true.
| All of my webs run on "extended" UNIX servers, one of which receives well over a million hits a
| year, and I have yet to have "One" issue with extensions.
|
| ? ;-)
| --
| Steve Easton
| Microsoft MVP FrontPage
| 95isalive
| This site is best viewed............
| .......................with a computer
|
| | > Who are the rock solid commercial service providers with SLA options
| > and Frontpage native servers to consider for a web-hosting service
| > provider?
| >
| > <flame>
| >
| > I am finished with Yahoo. Last week, the service outage was 3 plus
| > days involving 38 hours of dedicated time trying to work with Yahoo to
| > solve the problem. Today the sites are down again. This really hurt.
| > Bad.
| >
| > FP 2003 is my publishing product of choice. Over the past year FP2002
| > and FP2003 have functioned well with my two Yahoo Business evel Web
| > Hosting accounts. Except for linkbars and DWTs, the hosted product is
| > quite vanilla. A January 2005 upgrade to Yahoo Merchant services was
| > next. Not now.
| >
| > Error code #2001d, or Frontpage Server extension remains the unfixed
| > problem. I full well appreciate that FP hosted on Unix servers with
| > FP extensions is a tricky business for an ISP. But after nine calls
| > last week and another 3 already today, I see what is behind the Yahoo
| > support curtain. It ain't pretty. It is a mess. Frontline support
| > people try thier best but are green. Yahoo provides nothing in the way
| > of tracking or CRM tools or technical Tier 2 support. Escalation and
| > process for problem resolution are the same.
| >
| > Each call always starts from ground zero and involves the same rote
| > script. This is expected for the price. What is unacceptable are the
| > "I guess" and "I hope" recommendations. It's ground hog day on each
| > call. No escalation or process either. If the line is dropped or a
| > new call made, its a restart even with trouble tickets. The first line
| > is the only line of support at Yahoo.
| >
| > <flame + flame>
| > And to top it off,after the 3 day outage comes this jewel in public
| > relations from a Yahoo support rep and after I am told the problem is
| > clearly Yahoo's and is escalated to Yahoo Engineering:
| >
| > "Thank you for contacting Yahoo! Customer Support. case # xxxxxx
| >
| > The reason you are having problems using FrontPage features is that you
| > have uploaded files with names that contain spaces or other alternative
| > characters such as "*", "&", "!", etc..
| >
| > Here are a few examples of files we have located which have invalid
| > names: (five file name & locations)."
| >
| > awwwwwh
| >
| > AFter 8 times on 8 different calls of answering the same question that
| > yes all files are fine, I am told the 3 day service outage is my fault.
| > What the note failed mention is these "bad files" are not on the
| > broken domain.
| >
| > What is next? Run from Yahoo Web hosting. </flame>
| >
|
|

 

[=?Windows-1252?Q?Rob_Giordano_\=28aka:_Crash_Gordo]

Excellent service, techs that know what they're doing and are willing to help...Windows/ASP etc:

www.alentus.com


| Who are the rock solid commercial service providers with SLA options
| and Frontpage native servers to consider for a web-hosting service
| provider?
|
| <flame>
|
| I am finished with Yahoo. Last week, the service outage was 3 plus
| days involving 38 hours of dedicated time trying to work with Yahoo to
| solve the problem. Today the sites are down again. This really hurt.
| Bad.
|
| FP 2003 is my publishing product of choice. Over the past year FP2002
| and FP2003 have functioned well with my two Yahoo Business evel Web
| Hosting accounts. Except for linkbars and DWTs, the hosted product is
| quite vanilla. A January 2005 upgrade to Yahoo Merchant services was
| next. Not now.
|
| Error code #2001d, or Frontpage Server extension remains the unfixed
| problem. I full well appreciate that FP hosted on Unix servers with
| FP extensions is a tricky business for an ISP. But after nine calls
| last week and another 3 already today, I see what is behind the Yahoo
| support curtain. It ain't pretty. It is a mess. Frontline support
| people try thier best but are green. Yahoo provides nothing in the way
| of tracking or CRM tools or technical Tier 2 support. Escalation and
| process for problem resolution are the same.
|
| Each call always starts from ground zero and involves the same rote
| script. This is expected for the price. What is unacceptable are the
| "I guess" and "I hope" recommendations. It's ground hog day on each
| call. No escalation or process either. If the line is dropped or a
| new call made, its a restart even with trouble tickets. The first line
| is the only line of support at Yahoo.
|
| <flame + flame>
| And to top it off,after the 3 day outage comes this jewel in public
| relations from a Yahoo support rep and after I am told the problem is
| clearly Yahoo's and is escalated to Yahoo Engineering:
|
| "Thank you for contacting Yahoo! Customer Support. case # xxxxxx
|
| The reason you are having problems using FrontPage features is that you
| have uploaded files with names that contain spaces or other alternative
| characters such as "*", "&", "!", etc..
|
| Here are a few examples of files we have located which have invalid
| names: (five file name & locations)."
|
| awwwwwh
|
| AFter 8 times on 8 different calls of answering the same question that
| yes all files are fine, I am told the 3 day service outage is my fault.
| What the note failed mention is these "bad files" are not on the
| broken domain.
|
| What is next? Run from Yahoo Web hosting. </flame>
|

 

[Chuck Davis]

-----Original Message-----
Who are the rock solid commercial service providers with SLA options
and Frontpage native servers to consider for a web-hosting service
provider?

<flame>

I am finished with Yahoo. Last week, the service outage was 3 plus
days involving 38 hours of dedicated time trying to work with Yahoo to
solve the problem. Today the sites are down again. This really hurt.
Bad.

FP 2003 is my publishing product of choice. Over the past year FP2002
and FP2003 have functioned well with my two Yahoo Business evel Web
Hosting accounts. Except for linkbars and DWTs, the hosted product is
quite vanilla. A January 2005 upgrade to Yahoo Merchant services was
next. Not now.

Error code #2001d, or Frontpage Server extension remains the unfixed
problem. I full well appreciate that FP hosted on Unix servers with
FP extensions is a tricky business for an ISP. But after nine calls
last week and another 3 already today, I see what is behind the Yahoo
support curtain. It ain't pretty. It is a mess. Frontline support
people try thier best but are green. Yahoo provides nothing in the way
of tracking or CRM tools or technical Tier 2 support. Escalation and
process for problem resolution are the same.

Each call always starts from ground zero and involves the same rote
script. This is expected for the price. What is unacceptable are the
"I guess" and "I hope" recommendations. It's ground hog day on each
call. No escalation or process either. If the line is dropped or a
new call made, its a restart even with trouble tickets. The first line
is the only line of support at Yahoo.

<flame + flame>
And to top it off,after the 3 day outage comes this jewel in public
relations from a Yahoo support rep and after I am told the problem is
clearly Yahoo's and is escalated to Yahoo Engineering:

"Thank you for contacting Yahoo! Customer Support. case # xxxxxx

The reason you are having problems using FrontPage features is that you
have uploaded files with names that contain spaces or other alternative
characters such as "*", "&", "!", etc..

Here are a few examples of files we have located which have invalid
names: (five file name & locations)."

awwwwwh

AFter 8 times on 8 different calls of answering the same question that
yes all files are fine, I am told the 3 day service outage is my fault.
What the note failed mention is these "bad files" are not on the
broken domain.

What is next? Run from Yahoo Web hosting. </flame>

.

I now have six sites hosted by
http://www.minnesotashopper.com Great prices, great
Control pages, and great service. Tell the
theminutemanfoundation.org sent you. The foundation will
receive a $15 credit for the referral.

 

[Craig Schiller]

Yahoo sucks. Bigtime. Period. Run like the wind.

Craig