A security patch was applied to our development server last night. This morning, no fex can find it's meta data. When I right click on a folder, look at the properties, open up the app path option, there are no paths listed.

When I try to create a new procedure, I get an error, "Failed to get the list of master files".

I have looked on the server and the meta data files are still there.

It's been a while since I poked around Admin work in WF. Any thoughts on what to look for would be appreciated.

Thank you,

This message has been edited. Last edited by: Don Garland,

Have you looked at (GUI display) :
RS Console/Application/Application Path

Or (configuration file displayed from RS Console) :
RS Console/Workspace/Configuration Files/Server profile - edasprof.prf

OR (configuration file) :
yourServerDrive\ibi\srv8x\wfs\etc\edasprof.pfr

The console does not display application information.

Not sure what to look for in Edasprof. It looks right, but I've never looked at it before.

I'm getting a copy from production to compare the dev and prod.

In edasprof.prf you should have a line such as this one:

APP PATH baseapp ibisamp <your folder's name>

It does. In comparing PROD with DEV, it's looks fine. I don't think this is related. But, I did see something funny while navigating through both environments.

DEV Server has 3 drives; C:\ D:\ibi\... and E:\ibi\...
PROD Server has 2 drives; C:\ D:\ibi\...


What do I look at that tells me that WebFOCUS is looking in D:\ibi or E:\ibi?

Under RS Console/Workspace/Configuration Files/Workspace - edaserve.cfg

Once edited, at the top of the file it shows its location such as:

Edit Server Configuration drive:\ibi\srv8x\wfs\bin\edaserve.cfg

This is a good start to know to where it point to.

In the same file you it should have tell you where is located the edahome:

edahome = drive:\ibi\srv8x\home

and then other drive location under

[Applications]

You can also look on client side from WebFOCUS Administration Console/Configuration/Application Settings/Application Directories to find out what is the IBI_Approot_Directory. Something such as :

drive:/ibi/apps

The server Admins had rebooted several servers and never came back to ours to answer the prompts. So the patch was just hanging there (or chad). They answered whatever the question was on the server and it rebooted again, giving us back our meta data. No ransom was paid.

Thank you,

I thought this may be one of those Ransomware WannaCrypt Attacks Case