We had upgraded to c4. Then I copied all the personalizations from the c2 vrc to the c4 vrc. Converted to runtime, compiled all scripts, dumped all forms and menus. When we try to open a personalized session, it gives the error 'can't read session or object (session code)'. The message in the log.bshell file states that it's a bdb_errno_111. Oddly, this occurs with most personalized sessions, but not all of them. Is there anything that I can check?

Thanks

-Tim

Looks like the personalized object does not exist. How about going to Maintain Session and re-compiling each one?

Nope..tried that already. Still get same error.

Please try explode6.1 on the object to see which VRC level it exist if it exists at all. Also check your fd6.1 file if you have the package combination existing there. Good luck.

ok.. i tried explode6.1 on the object file and it did appear to be in the correct vrc directory.

I'm not sure what to do with the fd6.1 file. I did a search for that file, but it was not found. How is the file supposed to be used?

That would be under your BSE/lib folder. It would have files like fd6.1<package combination>. I was curious if the file on the package combination contains a line like otd (object for sales) and then whether the VRCs are there.

good luck.

this is what the otd line in the file states:

otd:/app/baan4/bse/application/tdB40C_c4_obg4:${BSE}/application/tdB40U_c4_stnd:${BSE}/application/tdB40_c4:${BSE}/application/tdB40_c2:${BSE}/application/tdB40_c1

Hi,

The otd (object for td package) is just an example. Perhaps let us know what is the session number you have problem. So we know which package youre in. When you explode which VRC is it existing?

My suspicion was the object compiled correctly and placed it in a specific VRC but the fd6.1 file does not point to it. As this is personalization you might have personalized packages, etc.

This particular session code is: tdobg0400m200.
The obg is our personalized module.

The script attached to this session is: tdobg0400rec.
This is what I'm exploding on. The explode6.1 states that the object is located in: /tdB40C_c4_obg4/otdobg directory.

The object resides on your highest VRC. The only ones who can see it are the users linked to the highest level. Make sure you have a company linked the highest Package Combo and the user executing the session is linked to it. Other users below that will never see that object.

You can also try copying that object on lower level, say tdB40_c4. Explode6.1 to check and try running the session.

I checked what package comb. that my username is linked to and it looks to be the same level as the vrc that this session is copied to.

I did copy the session to a vrc lower (B40C_c4_stnd) ran the session and it worked. Then I deleted it. I ran the session and this time it did go right in without any errors. Am I going to have to copy every session down a lower level, and then delete it before those sessions will run?

I suggest to just leave the sessions and objects at a lower level. These are personalized sessions so you dont have to worry about patches delivered by Baan.

It shouldn't have worked after you deleted it. My only explanation is that shared memory thingy.

timb25
Try create runtime DD for you personalized session by VRC (no convert).

Hi,

Did you do ttadv1115m000 in which you have to maintain the directories for ALL software components for that VRC?

GN