Unable to burn new feed after deleting old one

2 views
Skip to first unread message

gssq

unread,
Sep 16, 2008, 4:48:54 AM9/16/08
to FeedBurner Help Group - General Feeds and Syndication
Since my <a href="https://groups.google.com/group/feedburner-
statistics/browse_thread/thread/a123c39231f54bff">previous problem</a>
had been ignored for a week, I decided to delete my feed, <a
href="http://feedproxy.google.com/Balderdash">http://
feedproxy.google.com/Balderdash</a>, and reburn it in the same
location.

Unfortunately, when I try to create a new feed in the same location, I
am told that "The uri "Balderdash" is already taken. Please choose
another."

This is ridiculous not just because I've already deleted the feed in
question, but because visiting <a href="http://feedproxy.google.com/
Balderdash">the old URI</a> gives the error message:

"There has been an error of some kind. Ack!
FeedBurner could not deliver this feed to you because of the specific
problem listed below:

Feed Address: http://feedproxy.google.com/Balderdash

HTTP Error (Code) and Message: (404) Feed not found error: FeedBurner
cannot locate this feed URI.

What can I do about this?

1. If you are a potential or current subscriber, contact the
publisher to notify them that their feed content is not available.
This may be temporary problem that requires their intervention to
resolve, or the publisher may have permanently removed the feed from
FeedBurner.
2. If you are the publisher of this feed, sign into FeedBurner and
visit your feed's “Troubleshootize” tab to view FeedMedic, our
automated diagnostic report for your feed. A cause for the problem,
and tips for troubleshooting it, may be found there."

Unfortunately there is no option:

"3. Report the bug in our system to us"

because there is no way of contacting Feedburner technical support.

I will try again in the next 24 hours, but given the way things have
been going I'm not optimistic that it will work. My 200+ subscribers
are going to be cursing me, but that's the way Google tech support
works, I guess.
Reply all
Reply to author
Forward
0 new messages