Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
I am receiving an error when posting to one of my blogs on Live Spaces. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having problems publishing to this blog at http://technogranny.spaces.live.com again! Both of my other blogs are completely okay, it is just this blog where when I try to publish a new post I get the following error

    The server reported an error with the following URL:

    http://cid-9c72384a596282f7.users.api.live.net/Users(-7173609364469415177)/blogs('9C72384A596282F7!669')/entries

    500 Internal Server Error

    Runtime Error

    Server Error in '/' Application.

    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>


    HOw and why does this keep occuring with this particular blog?  And how on earth can I put it right?
    Wednesday, January 21, 2009 4:41 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    TG, we've asked the Spaces guys to look into this. In the meantime, maybe you can try again--when the error looks like that, often it's something temporarily wrong with a particular server in the farm. (I think. I don't know much about what actually happens in Spaces...)
    Thursday, January 22, 2009 4:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Joe Cheng [MSFT] said:

    TG, we've asked the Spaces guys to look into this. In the meantime, maybe you can try again--when the error looks like that, often it's something temporarily wrong with a particular server in the farm. (I think. I don't know much about what actually happens in Spaces...)



    Thanks for that prompt reply Joe, as ever your always on the ball! I will keep trying but it really is annoying when it happens! And why this particular blog? Thanks for your help on this matter.

    TG
    Thursday, January 22, 2009 5:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    TG, does that mean you've tried it recently (i.e. today) and it's still giving you the error?
    Friday, January 23, 2009 1:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes the error is still there and as far as I can see, still the same error as below

    The server reported an error with the following URL:

    http://cid-9c72384a596282f7.users.api.live.net/Users(-7173609364469415177)/blogs('9C72384A596282F7!669')/entries

    500 Internal Server Error

    Runtime Error

    Server Error in '/' Application.

    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

    So yes Joe it is still occuring. I have successfully posted since then to my two other blogs one on Spaces and one on LiveJournal with no problems, so why just this blog? I do hope that this doesn't mean a problem with this blog itself as I have loads of 'back posts on there and would hate to have to close it or wipe it for any reason.

    TG

    Friday, January 23, 2009 7:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    A clue that might have something to do with it (or might not!) is, if I click on the PREVIEW tab to preview the post, it is actually previewed in my blog at the wrong date! So say I am previewing a post that I have composed on the 22nd January, in the preview it will be placed inside my blog at 12th January (sometime back in the order of posts) and not as the most recent post???? Don't know Joe if this is happening for eveyone, in fact I will see if it occurs the same in my other Spaces blog just to check.

    In the preview it should surely be previewed as the latest post? Will get back to you on this.

    Friday, January 23, 2009 7:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Joe an update about this problem which actually confuses matters somewhat. I have since been able to post to that particular blog by using a 'workaround' as outlined here

    1. I clicked on FILE, then chose the SAVE A DRAFT TO EDIT ONLINE, and then my post went up to my Spaces blog no problems, where I could then simply click on Publish!

    Voila, its there in its entirety. My thanks go to another avid Writer user Jen Hemmings who has been having exactly the same problems as I and who discovered this workaround. All credit to her for discovering this, but it does rather complicate matters and also means that its not just me!

    Friday, January 23, 2009 11:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Wow. That is completely bizarre--I believe you, but I can't explain it.

    Can you try this again with a completely new post, without any images? Just hit Publish, do you get the same error?

    Wednesday, January 28, 2009 4:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Joe, didn't you get my twitter about it?  It was fixed the other day, I am sorry, I forgot to update this page!  Ooops!  Blame it on this granny's memory. I did twit you telling you it had been fixed, you must have not seen it.  Everything's fine now so I haven't a clue about what was causing it.

    And thanks to all the team for granting this old granny her wish to be able to add a video file from my computer into Writer without having to go to a video hosting site! You tease, you told me it was practically impossible to do, and then what do I find in the new Essentials version?

    That I can do just that without leaving Writer! Your the best Live team out there!

    Now let me see, I want to add a music file straight from my computer. without going anywhere and add a caption into that tilted Instant Photo at the bottom of it a la Polaroid .............LOL (only kidding!)

    TG

    Wednesday, January 28, 2009 6:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Joe Cheng [MSFT] said:

    Wow. That is completely bizarre--I believe you, but I can't explain it.

    Can you try this again with a completely new post, without any images? Just hit Publish, do you get the same error?


    Joe just getting back to you. I am getting the error occuring once more when trying to post to the same blog as before! Its been fine until today. Again, I used the work around of posting a draft to edit it online and this again worked! Is it a server problem at Windows Live end or is it a Writer problem?
    Monday, February 9, 2009 10:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Joe Cheng [MSFT] said:

    Wow. That is completely bizarre--I believe you, but I can't explain it.

    Can you try this again with a completely new post, without any images? Just hit Publish, do you get the same error?


    Joe just again getting back to you about this, I have a sneaky suspicion that it is somehow related to the 'Twitter notify' plug in that I have been using since its launch. I have just uninstalled that then re-installed and tried again and voila! I could post okay. So for some reason that I can't fathom, this particular blog 'server' doesn't like the Twitter notify plug in.
    Also I have noticed that this plug in can be eratic in that sometimes it will notify when  I publish to any of my blogs, and other times it does not get triggered to do so.

    yours TG
    Monday, February 9, 2009 11:03 AM