Error Code 403's description is "Error description was not found."
I'm just trying to open a master file in App Studio. This is a brand new Version 8 install, Server and App Studio.
More to the point, ladies and gentlemen on the programming team, if you don't have an error description to offer, don't pass up the opportunity to present inside humor to the user base. "Mr. Cohen forbids this action at this time" would have at least lent some levity to the situation, and would be no less valuable than the current message.
I'm certain the erudite user base here in the tech forums could recommend other, far wittier options in the event there's no error description available.
J.This message has been edited. Last edited by: <Kathryn Henning>,
I get the same error in 8.1.4 App Studio, so for now, I am just using DS 8.00.8 to edit a master file.
Sorry no help from me, but at least your not alone.
We have been on 8.1.04 for a several months and found quite a few weird errors, but not this one.
Any resolution to this issue. I am a fairly new install as well and have been able to do this until today. Not quite sure why this just started happening.
Sorry, no resolution to date.
This issue occurred in environments using a preauthenticated configuration. It has been resolved in release 8.1.05.
Still Getting this error in 8105 Dev Studio, What should i do?
Webfocus 8105,8808,7703,7611, EXL2K,HTML,PDF,COMT,AHTML Info Assist+ , Reportcaster
You should open a case with techsupport, based on the last post from almost 5 years ago it should have been fixed. I know there were multiple releases of 8.1.05 so that could be your issue but that is just a guess.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
A 403 error means FORBIDDEN. Meaning that there is an authentication issue with the userid/password combination being passed. I had a similar issue with 8202 in AppStudio. It had to do with my password using special characters and IBI then doing URI percent encoding on those special characters. For example, if a password was 'abc+123!' then the password being passed was actually 'abc%2B123%21' which was then not decoded on the reporting server side and the reporting server would interpert it as a bad password.
See this link for the Percent-encoding reserved characters and try changing your password to something that does not include those reserved characters.
If that doesn't work, I would suggest opening a case.
Hey, I still remember my login! Woot! haha
Yeah, good luck iBeny.... Good. Luck.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
|Powered by Social Strata|