none
Looking for help with long thread. RRS feed

Answers

All replies

  • Hi,

    If you don't get a reply from one of the admins here, you can try sending an email to fissues (at) microsoft [dot] com with a link to the thread and an explanation if what you're looking to do.


    Don't retire TechNet! - (Don't give up yet - 12,830+ strong and growing)

    Thursday, April 24, 2014 8:57 PM
  • Sorry for your issues Cal. We'll look into and try to rectify the situation soon. Stay tuned to this thread for updates.

    Life is one big road with a lot of signs.

    Friday, April 25, 2014 1:42 AM
  • I think the web interface should split a long thread automatically, only show the first 30 or 50 replies, and provide a "Show more replies" button.


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    | 1. In a particular long thread, I always get "Microsoft.com is not responding due to long-running script" when I try do scroll down initially.

    Saturday, April 26, 2014 2:00 AM
  • Sorry for your issues Cal. We'll look into and try to rectify the situation soon. Stay tuned to this thread for updates.

    I am looking forward to it. I may just try to close that thread before success at splitting, but that has some disadvantages. If the rectifying can't happen, that will be the best available option I think.

    Tuesday, April 29, 2014 2:06 PM
  • I think the web interface should split a long thread automatically, only show the first 30 or 50 replies, and provide a "Show more replies" button.


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    | 1. In a particular long thread, I always get "Microsoft.com is not responding due to long-running script" when I try do scroll down initially.

    Thanks. I feel better that it is not just me. Identifying and getting rid of that script seems like a solution.


    • Edited by Cal Learner Tuesday, April 29, 2014 2:18 PM
    Tuesday, April 29, 2014 2:08 PM
  • That's a really long thread! It kept loading for me before it even got to the script error, and I gave up and closed it. I think you have the right idea for the workaround until the bug can be permanently fixed... start a new thread, link to it from the old thread, and lock the old thread.

    Ed Price, Power BI & SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Saturday, May 3, 2014 12:13 AM
  • Thanks Ed. I am still hoping  Jah OSullivan has some success with it.

    It would be nice if that thread accidentally serves as an instance that a developer could use to identify a fix that would help forum performance for all.

    Closing the thread is an option, (presuming that works). However there is enough really useful info on the thread that I wish I could split it.

    Tuesday, May 6, 2014 9:52 PM
  • We've got it earmarked for addressing in a few weeks Cal. I'll keep this thread updated when the issue is resolved. Not a scenario we want to keep in this state for too long. Thanks for bringing it to our attention

    Life is one big road with a lot of signs.

    Tuesday, May 6, 2014 11:42 PM
  • Thanks. I went ahead and locked the thread. I have hope that I could later unlock it, and split it up. I had to use a non-IE browser to do the locking.
    Wednesday, May 7, 2014 4:36 PM
  • That's pretty good feedback Cal. Thanks a lot for your help. I'll update this thread when the issue is resolved.


    Life is one big road with a lot of signs.

    Friday, June 13, 2014 7:03 PM