Hi All,
I have created some AFS sessions in Baan IV c4 with tools SP 14. At a later stage the user upgraded to Tools to SP 16.

The AFS sessions which we have been created in the SP 14 are not working now. I am not sure what exactly the problem is at the client site.

In case any one has faced a similar problem and got a solution for the same, please post it.



regards
Sriks

Typically when we run into this situation we just call Baan and get the latest stpapi objects. Seems to me that has always solved our problems. I take that back, once we had to install an updated porting set with our new tools sessions. Either way a quick call to Baan should get you what is needed.

Mark

Sriks/Mark,

I have faced this too.

I have a client who upgraded to SP17 and also upgradedto the latest porting set. Suddenly, everything...I mean 'almost' every AFS resulted in an error or a database termination message.
It was erratic, sometimes slow, sometimes fast!
Surprisingly, it had worked fine in a test environment! (Before you apply the SP's and porting sets, please ensure that you test the AFS in the test environment with the latest SP's and porting set)

We tried getting the latest stpapi objects from BaaN and it still didn't work.

We finally found that it was not the SP, but the porting set that was causing the problem. I believe the latest Porting set is 6.1c.07.3.

We finally went back one Porting set and everything was fine.
The only drawback is the some of the solutions in the SP may need the latest porting set. In that case, you have to get BaaN to solve the problem directly.

Hope this helps.

Regards,

Arun

Hi Arun,
I am on the latest porting set 6.1c.07.05.
Does it mean I shall go for porting set 6.1c.07.02 or 6.1c.07.04?

Mark,
Could you please tell me the object / list of objects that are used for AFS .


regards
Srikanth

Hi Srikanth,

As per our case, try going to any porting set greater than 6.1c.07.02 but less than 6.1c.07.05. (The 02 porting set is the minimum requirement for SP's)
We tried 6.1c.07.03 and it worked. Apparently it's also documented somewhere that 02 is the minimum required porting set. I can dig in and find that out if you need.

Try going for 6.1c.07.03 and give me the good news that it worked!!!

Regards,

Arun

Srikanth/Arun,

In our 4c4 test environment for finance we are on porting set 6.1c.07.04 and it does work for us. I have several load API function servers for this company that check out just fine.

Mark

Mark/Srikanth,

You are right 6.1c.07.04 is alright!! But we were going from 6.1c.07.02 upwards and all worked fine at 6.1c.07.03. It was 6.1c.07.05 that caused the problem.

Srikanth Try out either 6.1c.07.03 or 6.1c.07.04

Regards,

Arun

Arun,

Sorry I missed the part but less than 6.1c.07.05. And it appears I also missed a question by Srikanth. Sigh. Rought Tuesday morning. In all honesty I do not have a list of all the objects - one of our app admins handles dealing with Baan, my job is just to whine when it does not work. The only files I know of for sure are in the ottstp directory and start with ostpapi. So I am really not sure what all goes into making it work.

Mark

Just a note on when you use BCK and upgrade your portingset from 6.c.07 to 6.1c.07.02 or higher: apparently the bshellxma default behaviour for processes like menu handling etc. is changed: these 'startup' processes would normally be supressed since you are calling baan logic remotely and there would not be a display to show the menu. Previously these processes would be supressed by default, after upgrading to 6.1c.07.02 we found that we had to add 'ottmidsleeping' as parameter to the login process. Sol. 146952