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.
We Have latest version of console, however the application build is 8861.
However even on publishing we are getting same error.
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?
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.
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"
<subNetwork mask="0.0.0.0/24" name="allInternet"/>
Are you sure your internet facing security zone is having the allowDebug enabled?
Please check the security zone is added in the server configuration xml file .
If your instance is adobe hosted, you may need to raise a support ticket for the same.
I am also having Same Problem in Production. Any resolution ?
BAS-010063 An error (-56 code) has occurred. Your rights do not enable you to view its details.
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