Hi,

We are having the same major errors after installing the above Service Packs. The error is "Dynamic link Link failure.." & Can't read session or object...." These errors happens in quite a number of sessions and we have run the installation based on the guide provide by BaaN.
Any suggestions/Ideas will be highly appreciated?

Thanks

What more?
What version?
Did you ttiex3226m000?
Dit you ttadv5210m000 / create RDD?
Read and installed portingset requirement?
Installed solution 114812 for $BSE/include6.x dir?

What version?

- BaaN C4, Oracle 8

Did you ttiex3226m000?

- Yes

Dit you ttadv5210m000 / create RDD?

- Yes

Read and installed portingset requirement?

-Yes

Installed solution 114812 for $BSE/include6.x dir?

-We are on NT 4, is this Necessary?

__________________

Those error messages come from sessions that have not been converted to runtime properly, so it seems your creation of runtime was not properly done for sessions or you are using a language different from 1 to 4?

Run a creation of runtime for sessions (no need to get users logged out) for all package combinations to get rid of those messages.

If using a language other than 1 to 4, you may need to copy language software components to your language and then create runtime for sessions - see solution 70102 for more information on translation of solutions.

When using the compiler (bic.exe), your objects will contain the code that is generated because of the programmers code (the script), but also code that is pre-compiled in a kind of link objects.

These files are actually portingset independent (as is the application itself), but also contain fixes and modifications. These will show up in all objects generated with the new code, but also in own compiled objects.

There can be Dynamic Link Failures because of these bic_ files, like when reports and ttstprepdll is involved.

These files in solution 114812 are somewhere in between the application and the portingset, so applicable for all platforms, not platform dependent, but tools version dependent.

So use the solution on NT also.

But on NT you can install them best with a rename step: rename the tar-file (which is a *.dmp file) into *.tar and use winzip to extract the files. (best is: keep system date in tar-file, since the solution is generic and will be updated.)