F
finntastic
Anyone else stuck in this Yahoo Web Hosting support Catch 22?
Hosting provider: Yahoo Web Hosting, two business class service plans,
in place for about one year each.
Publishing environment: FP2003 with FP limited extensions: linkbar,
forms & DWT
Service outages: Three the past 45 days; total of about 124 hours of
total inoperability, plus an estimated >60 hours of time spent on the
in related troubleshooting including >20 Yahoo support calls.
The Problem: 1- Yahoo FP extensions error code #2001d, confirmed by
Yahoo Engineering. The third log/trouble ticket is open for 20 plus
days. All three outages, Yahoo engineering ultimately confirmed this
is a Yahoo Engineering problem.
The consequences: 1- FrontPage extensions break and must be reset by
Yahoo. Consequently, down time and my domains must be rebuilt from
scratch and FP republished. 2- FP publishing and FP site tools
utilities are inoperable. The FP client does not recognize what Yahoo
recognies as valid FP domains. 3- The use of FP Yahoo host based
utilities (recalc, author editing, and FP extension reset) cause an
instant FP extension crash and servcie outage. And the restart from
scratch. Each of the past three service outages started with Yahoo
support troubleshooting employing one of thse standard FP utilities and
rote troubleshooting routines.
The Catch 22? Yahoo Support refused to forward Yahoo Engineering
information related to the open trouble ticket today because I would
not allow troubleshooting using the domain busting Yahoo utilities.
Know this: EVERY Yahoo support call is treated as a new stand-alone
incident from the trouble shooting and escalation prospective.
This is no way to run a railroad.
Hosting provider: Yahoo Web Hosting, two business class service plans,
in place for about one year each.
Publishing environment: FP2003 with FP limited extensions: linkbar,
forms & DWT
Service outages: Three the past 45 days; total of about 124 hours of
total inoperability, plus an estimated >60 hours of time spent on the
in related troubleshooting including >20 Yahoo support calls.
The Problem: 1- Yahoo FP extensions error code #2001d, confirmed by
Yahoo Engineering. The third log/trouble ticket is open for 20 plus
days. All three outages, Yahoo engineering ultimately confirmed this
is a Yahoo Engineering problem.
The consequences: 1- FrontPage extensions break and must be reset by
Yahoo. Consequently, down time and my domains must be rebuilt from
scratch and FP republished. 2- FP publishing and FP site tools
utilities are inoperable. The FP client does not recognize what Yahoo
recognies as valid FP domains. 3- The use of FP Yahoo host based
utilities (recalc, author editing, and FP extension reset) cause an
instant FP extension crash and servcie outage. And the restart from
scratch. Each of the past three service outages started with Yahoo
support troubleshooting employing one of thse standard FP utilities and
rote troubleshooting routines.
The Catch 22? Yahoo Support refused to forward Yahoo Engineering
information related to the open trouble ticket today because I would
not allow troubleshooting using the domain busting Yahoo utilities.
Know this: EVERY Yahoo support call is treated as a new stand-alone
incident from the trouble shooting and escalation prospective.
This is no way to run a railroad.