After we upgraded to 8203, we are starting to get lots of issues with what appears to be our logins timing out when using AppStudio or running reports in one of our environments.

We will be working in a procedure and then go to save our code or open another procedure and we will receive an error stating:
"403 Forbidden - Access is denied. You do not have permission to view this directory or page using the credentials that you supplied."

We then are unable to save any of our work and have to restart our AppStudio instance for it to return to normal. But this will sometimes only last for a few minutes before the error happens again.

We have notified our system admin and IBI about this issue, but I wanted to see if anyone else had encountered this or had any ideas what might be causing this? We are on Windows and using SSO if that helps.

This message has been edited. Last edited by: FP Mod Chuck,

In App Studio, if you go to Options, under General, there's a Ping Interval (minutes): box. What's the setting for that? Can you raise that limit?

Also, are you using IIS or Tomcat?

Hi Capples,
We actually have this same issue. We get the 403 Forbidden Error when we try to run something. App Studio always seems to let us save the work, but not run anything until we hit save again. It's almost like it refreshes our connection and then it works okay for a few minutes.
This is not a constant issue however, very hit and miss and sometimes lasts for 30 minutes, and other times it lasts all day.
I'm very curious to hear if anyone has an answer as to why it's behaving that way.
-Larissa

Larissa

Do you have single signon as well?

We sure do Chuck, it is run through our Tomcat services.

My ping interval is set to 5 minutes currently and we are using Apache Tomcat. Similar to Larissa, I've had it go for hours before happening, other times it will happen every few minutes. However, we end up not being able to save our work when it happens. This isn't too bad when dealing with text files and code, but is much more annoying when dealing with changes to an HTML page via the HTML Canvas.

If it's reproducible, IB Tech Support can probably walk you through tracing it so you can get to the bottom of it. Let us know when you get a solution.

You're right BabakNYC, I bet they could trace it. However, it's so hit and miss, it would be a goldmine if you could catch it working while you were doing a WebEx!
I'll try running a savediag next time it happens to see if I can catch anything.

Hi Capples,

does your websecurity.log show you any extra info? This would be on your client under ibi\webfocus82\logs if its in it's default place. Or you can get to it through the admin console.

In 8.0 days, on occasion the websecurity.log might have some info. If you know how, you can also go turn on the com.ibilog trace in log4j.xml to watch your logon attempts.

Do you use single sign on via your Reporting server? Many questions I have right?

There's a lot I'd need to know to answer your question. If you hit a time where you are hitting this error consistently, it's worth trying to catch the com.ibilog info and your http traffic between your pc (app studio in this case) and tomcat.

The com.ibilog is not super heavy on slowing down your system which is good. It does work best to bounce tomcat though, so you'll have to choose a day to turn it on when you can bounce tomcat after you change log4j.xml. I'd make a backup too. You can see a little blurb about com.ibilog in the webfocus 82 security manual. Just search for log4j and I bet you'll find it.

Toby Mills, CISSP

Has anyone found a solution to this issue? We just upgraded to 8202M and I'm experiencing this exact thing.

You can add my name to this list. I've experienced this in the past occasionally but after our upgrade Wednesday night it was happening about 1 out 4 times I would make a change and try and run without saving. It's a real big annoyance. Looking forward to seeing if there's a solution.

See Toby's suggestion above and look at that log to see if there are any clues. A solution will only be provided here if someone works through this with techsupport, Due to the fact it is an intermittent problem they are tough to debug.

For me this exact problem hasn't necessarily revolved around saving. For me anyway didn't matter if I saved or not when I run out of AS every so often I'll get the 403. All I need to do is close the run window, and immediately run the FEX again and it works. An annoyance for sure, but I've just learned to deal with it

Good luck with this. I'm having all kinds of issues in my crAppStudio. I cannot access master files, edit HTML pages, or even run things in a modern browser. All due to authentication issues. However everything runs fine in the web, and I can access master files in the RS Web Console. I've had a case opened since July 12 on this and they cannot figure it out and have just stopped responding to the case notes.

IBI tech mentality = ignore it till they go away.... Ridiculous

Yeah, it's been a regular thing on our end too. Hence, we no longer use AppStudio AT ALL save to connect to fexes within VS Code. It's just bad...

We can't get to the metadata canvas, HTML canvas, etc. Always gets to a non-responding state, etc.

Oh, and we've tried the whole open a case thing to the point we are burnt out. They sometimes are helpful, but other times not so much.

This message has been edited. Last edited by: CoolGuy,

quote:

Originally posted by BabakNYC:
If it's reproducible, IB Tech Support can probably walk you through tracing it so you can get to the bottom of it. Let us know when you get a solution.

Apparently my last post woke up the help desk and I just got done with an hour remote session... Nope, they still don't know what is going on

I have experienced this as well. I have noticed that when I close all my IE browsers and perform a save it clears right up. I am thinking that IE might be timing me out or something when I run several times in a row after minor changes.

With that said, I have also experienced a few times when it just seemed to timeout with App Studio and I could not even get a save even after shutting down and clearing my cache.