Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: Dot Feed failing

  1. 01-31-2012, 05:43 AM #1
    GotEcommerce is offline Junior Member
    Join Date
    Jan 2012
    Posts
    2

    Default Dot Feed failing

    We are having issues all of a sudden with Google not being able to pull the feed correctly. We haven't made any changes on the website or changed any rules in the feed but for the last few times that we have tried to pull the feed from the Google products console, Google is giving us this error message:

    Get file entry failed. (1 error)
    Failed to obtain the file information. Please make sure it's available.
    Examples: Examples:

    Url
    http://dotfeedviewer.aspdotnetstoref...a-12e8875c15df

    Has anything changed in the way to submit the feed that we are missing?

    Thanks!
    got ecommerce?
    ECommerce Consulting Services
  2. 02-03-2012, 01:51 AM #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    We had an email sent out yesterday to everyone RE Dotfeed but in case you missed that out...we've pushed a very important update today which will stop these failures -- they are essentially caused because we do so much real time processing, and they have been aggravated since we implemented load balancing. With this update, we’re pretty confident that it will allow for much greater stability and will definitely resolve this problem.

    If in case this happens again, please let us know by sending a ticket here.
  3. 02-08-2012, 07:56 AM #3
    jgiven is offline Member
    Join Date
    Oct 2004
    Posts
    50

    Default

    we're still having this problem. is our issue different than the previously mentioned fix?