Hey folks, I have a strange one for you.

I have dashboards that present Layout Painter reports to the users. Enter a name, select a status, click on Submit, that sort of thing. There are drop-down boxes in the set of selections for these pages that are filled by calls to focexecs -- provide a list of names to choose from. They don't run.

Now, if I have Dev Studio open and I run a report from the server they use (via Dev Studio) they start to run. That is, if I touch the server with Dev Studio first they magically come alive and function properly. At the moment I have no username/password specified in Dev Studio for that server, and I have security turned off on that server. The run in Dev Studio proceeds without prompting me for credentials.

Here's the other curve ball in the mix -- it's not the default server for the wf client.

It's almost as if it can't make contact with the server until I contact it directly first. Once first contact is made, all proceeds as one would expect.

Anybody have any ideas? I don't even know how to specify a search string for this critter to look for it here in the forums or on tech support. I figured I'd crowd-source it first since you guys often provide such good results and so quickly.

J.


By the way, Client is 7.6.1, Server is 7.6.5 running on Win2k, same box. Server is one of four, licensed to run WF and Maintain.

Generally, when this happens, it cannot find the focexec. If you open the html page in the editor, look for the line with the focexec that populates one of the dropdown boxes. Make sure that the IBIAPP_app variable points to the directory where the fex is. Then make sure that variable IBIC_server points to the server.

We have a joke around here that its always pathing.

Checked a dozen times because you're right -- pathing is always an issue and in this case it's server and app that need to be right.

What confuses me most is that the problem "fixes itself" once I've touched the server in Dev Studio.

Right-click the List box and uncheck the cacheruntime parameter, OR, if it is not checked, check it...

CacheRunTime made no difference.

Hi John,

Has this issue been resolved?

I passed this one to our internals and was told that the behavior is quite unusual. Please open a case with Information Builders' Customer Service so that we can help determine what is going on in the environment. To open a case, please either call 1-800-736-6130, or access InfoResponse.

Cheers,

Kerry