Thursday, February 01, 2007

[blogger] bX-vjhbsj error

This error is driving me crazy - anyone else having issues with it too?
It's popping up randomly all over the place and making it difficult for me to access old posts and archives.
Going to report it to the engineers...

505 error sucks too - they say they've fixed it but it just caught me out and I had to rewrite this post.

We're sorry, but we were unable to complete your request.

When reporting this error to Blogger Support or on the Blogger Help Group, please:

* Describe what you were doing when you got this error.
* Provide the following error code and additional information.

Additional information
uri: /2006/03/when-life-gives-you-meyers.html

This information will help us to track down your specific problem and fix it! We apologize for the inconvenience.

This Post was written by sam from Becks & Posh


ilva said...

It's been like that all day long over here in Europe. I have to try and retry to enter some blogs or my own blog posts. I suppose they are having some major problem with their server or something...

Kalyn said...

Same problem here. My pageloads for today is only about 1/4 of what it usually is at this time.

Mimi said...

Yes, same here. I find that if I am persistent and try again, it's OK.

I would say 3 out of 4 efforts on my part are bringing that message.

chanit said...

The same problem WAS here, now It's fixed (until next time..)

sarah said...

hm - yeap. i just got it while trying to post a question on food blog scool :(

Lydia said...

Getting this right and left when I try to log into many blogger blogs.

girlgastronome said...

I was getting it too this morning and solved the problem by going into a post and republishing.

neil said...

A reader sent me an email about the error message and when I checked this morning 7.30 Australian time, Blogger had this to say...

Some users see the error code bX-vjhbsj when trying to view a blog. We have identified the source of this error and will push the fix to the site shortly. In the meantime, hitting Refresh in the browser may workaround the problem. We apologize for the inconvenience.

Update 10:50AM(PST): The issue has been fixed. Unfortunately pushing out the new build involved a few minutes outage. We apologize for trouble.

Alanna said...

It's corrupting some hyperlinks in new posts, too.

Andrew said...

I just read a blog post somewhere offering a solution to this - I cant get into newsgator online to find it now though. What I recall is that you have to hit refresh a few times and it disappears... not sure how accurate it is but the post did say it is non-serious. Sorry I cant recall in more detail but I dont use blogger so didnt pay much attention.

Found this though on technorati - "There's no real solution but the blogger error disappears after you refresh the webpage a couple of times by pressing the F5 key. "

Meeta said...

Hi Folks!
This effected me too - the whole day yesterday. This is what I managed to find out. This problem seems to only effect those of us who, although have switched to the new Blogger are however still using the old template (they call it Classic Template). All the people who are using the new layouts on the new Blogger have not been effected by this.

And here is the proof. I switched my template to the new layout last night and low and behold that problem disappeared!!

So, rumor on the Google Blogger Group has it that this is a crafty way of Blogger to force everyone to move to the new layouts too. Not too sure how much truth there is to that but when sees the issue the way I experienced it one tends to believe it.

As Andrew says when you hit refresh a few times you eventually get to the page but to be honest when anyone sees an error message like that the first thing they do is panic - then they want to contact Support but did any one find a Support address? NO! Not very transparent from Google to be honest.

mae said...

Ah! That explains the error messages i've been getting in trying to visit all of you guys in the last couple of days.

Even uploading food blog s'cool, gives me the same error codes.