Loading...

qListForm (Image and Document manager) causing HTTP 403 Forbidden error

qListForm (Image and Document manager) causing HTTP 403 Forbidden error

Home Forums QuickApps Forum qListForm (Image and Document manager) causing HTTP 403 Forbidden error

  • This topic is empty.
Viewing 5 reply threads
  • Author
    Posts
    • #4785
      Anonymous
      Anonymous
      Participant

      …oh and we are using Sharepoint 2010 & v5.4.1 of the Quest Web Parts

    • #6822
      Anonymous
      Anonymous
      Participant

      We are seeing the same issue and it happens in all our environments Dev/Qa/Prod. Did you get solution for this?

    • #6823
      Anonymous
      Anonymous
      Participant

      Hi Daniel,

        I'm not able to see the issue using the version 5.7.

        Your version 5.4.1 is quite old now and I'd suggest you to try your scenario using the latest version QWP 5.7.

      You can try it online using the Quest Virtual Drive.

      Go to http://www.quest.com/web-parts-for-sharepoint/  then search for QuestDrive – Virtual Trial

      Please let me know how it goes.

      If you still can see the issue please attach the doc library and the web part template to this tread.

      Thanks,

    • #6824
      Anonymous
      Anonymous
      Participant

      Hi

      We are using 5.7 still we see the issue.

    • #3936
      Anonymous
      Anonymous
      Participant

      I’ve been trying to upload images and documents using both the Image and Document manager in a qListForm. After I have selected a file and click upload I get an error page telling me that “This website requires you to log in”.

      The page it is trying to access is “/_Layouts/QuestSoftware/WADialogHandler.aspx?DialogName=DocumentManager&Skin=Default&Title=Document+Manager….”

      Any ideas? I have full permissions to the site.

      Regards,

      Dan

    • #6825
      Anonymous
      Anonymous
      Participant

      Would you mind to attach the doc library and the web part template to this tread?

      This would help me in the investigation since I can't see the issue in my env.

      Thanks,

Viewing 5 reply threads

You must be logged in to reply to this topic.