Error While publishing Webapp. | Community
Skip to main content
A
asariaaara
Level 3
June 18, 2019

Error While publishing Webapp.

  • June 18, 2019
  • 4 replies
  • 19079 views

Hey All,
I have been getting following error while publishing a WebApp.

"BAS-010063 An error (-56 code) has occurred. Your rights do not enable you to view its details."

Someone on other post recommended adding the browsing IP to white list.
how would i add an IP to white list when i have an on-premise environment.

Regards.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    4 replies

    Anita_punmiya
    Anita_punmiya
    Level 5
    June 18, 2019

    Hey,

    Can you please check if the build number for client and server is same?

    Regards,

    Anita

      A
      asariaaaraAuthor
      Level 3
      June 18, 2019

      Hi Anita,
      We Have latest version of console, however the application build is 8861.
      However even on publishing we are getting same error.

      Regards.

      A
      Adobe Employee
      aneetaroraAdobe Employee
      Adobe Employee
      June 24, 2019

      Hello asariaaara​

      Considering you're facing this while in the "Test" on the WebApp, it's likely not a whitelisting issue. Can you please go to the Properties on this WebApp and check the Access Control specified in the Properties?

      Can you also try hitting this WebApp on the browser and see what is returns?

      Thank you,

      Aneet

        itsme
        itsme
        Level 3
        June 25, 2019

        I think you should enable the allowDebug="true" for the Zone you are in. The settings is in the serverConf.xml file. Once that is changed, you should be able to see the details of the error.

          A
          asariaaaraAuthor
          Level 3
          June 26, 2019

          Hi anitap82640902​

          We have been observing this issue in every webapp and tried every access control in properties.

          The same thing is displayed in browser after publishing.

          Aalokitoaami​

          debug is already on and nothing is returned in log. see screenshot.

          Appreciate your help.

          itsme
          itsme
          Level 3
          July 15, 2019

          I was trying to recreate the error and was able to do so by changing allowDebug="false"

          <!-- Security Zone Internet is Addded by Tarun Ghosh on 5/4/2019-->

            <securityZone allowDebug="false" allowHTTP="true" allowSQLInjection="false" name="internet"

                          showErrors="true">

              <subNetwork mask="0.0.0.0/24" name="allInternet"/>

            </securityZone>

          Are you sure your internet facing security zone is having the allowDebug enabled?

            andbrice
            andbrice
            May 26, 2021

            Hi there,

            I've experienced this so much it's painful. I have a few suggestions to make, as working with webApps in Campaign is the glitchiest feature of them all and, given that I am also unable to use the debug mode, these seem to keep me afloat:

            1. Ensure you are connected to a VPN (for whatever reason that actually displays more specific errors, as opposed to a more generic one)

            2. Choosing a user profile usually does the trick for me, as long as,

            3. One removes all other URL parameters.

            4. Change the internal name of the webApp, re-save, re-publish and try loading it on an external web browser. 

             

            I know this isn't ideal but I hope it helps.

            Best of lucks 🙂

             

             

             

            Terms & ConditionsAccessibility statement

            Loading footer...