Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Vc 5 posts 75 karma points
    Jun 13, 2016 @ 15:19
    Vc
    0

    XSLT file parsing Error

    Hi,

    Twitter oAuth was working before but all of sudden just stopped working. It gives this error "Error parsing XSLT file: \xslt\TwitterOAuthRenderTweets.xslt".

    done debug trace and it says something along this line:

    "An error occurred during a call to extension function 'GetTweets'. See InnerException for a complete description of the error."

    Not sure if this is to do with dll file, please can anyone point me to right direction?

    Thanks

  • Ismail Mayat 4511 posts 10092 karma points MVP 2x admin c-trib
    Jun 13, 2016 @ 15:33
    Ismail Mayat
    0

    Vc,

    Anything more in the umbraco log file?

    Regards

    Ismial

  • Vc 5 posts 75 karma points
    Jun 14, 2016 @ 07:48
    Vc
    0

    Thanks Ismail for getting back to me. No, nothing on logfile. I have attached screenshot of the full error message from debug trace: enter image description here

    Thanks

  • Jan Skovgaard 11280 posts 23678 karma points MVP 11x admin c-trib
    Jun 14, 2016 @ 08:24
    Jan Skovgaard
    0

    Hi Vc

    In the bottom of the stack trace it says that "The remote name could not be resolved: 'api.twitter.com'"

    So I'm wondering if it could be an issue with a firewall setting for instance?

    /Jan

  • Vc 5 posts 75 karma points
    Jun 14, 2016 @ 12:54
    Vc
    0

    Hi Jan,

    I'm going to check firewall settings then update you if I'm still facing same issues.

    Thanks

  • Vc 5 posts 75 karma points
    Jun 15, 2016 @ 13:13
    Vc
    0

    Hi Jan,

    I have checked firewall settings, it all looks fine. api.twitter.com is resolving as well. still not sure what could go wrong because it was working before but all of sudden just stop working with that error.

  • Vc 5 posts 75 karma points
    Jun 21, 2016 @ 07:51
    Vc
    0

    Hi Jan,

    The issue is now fixed, the issue had to do with DNS :) thanks for your help and your answer was actually helpful.

Please Sign in or register to post replies

Write your reply to:

Draft