Baan IVc C4

Win 2000

Porting set: 6.1c.06.06

SP 10

I have installed Worktop but when I create a new document get the following message:

"Can't Read Session Or Object (ottdllreadmenu) "

Any Clues?

Thanks

Hi Abuibra,

Yes, this error means that the library "ottdllreadmenu" was not installed or detected on your Baan server. This library is used by Worktop to integrate the Menu Browser. The object should come with Service Pack 10 and so should have been installed on your system.
So first check if this library is installed on the system. You can use the session "Display Solutions By Update VRC" for this (ttpmc2501m000). Check if solution 125484 has been installed, this is the first update for ttdllreadmenu. The latest solution for ttdllreadmenu is 127095. If it isn't installed yet, install it. Note that you must restart the shared memory service after you installed the library, otherwise it won't be loaded.

For Worktop, all solution numbers required can be found in the generic solution 125180. This solution holds the solution numbers for the latest Worktop version, latest version of ttdllreadmenu and the latest version of tgintworktop (tgintworktop is a library used for integrating DEM into Worktop).

Regards,
Ivo

Thanks Ivo!

Hi Ivo,

I installed all the solutions but when I create a new document I am getting another error:

Fatal error: (bms.init) undefined function
Fatal error: Cannot continue in ottstpoledaemon ()

Thanks

Hi Abuibra,

This error means that it cannot find the function bms.init, which is a bshell function. This function has been introduced in porting set 6.1c.06.06, so my first reaction normally would be that you should upgrade your porting set. However, you already mentioned before that you do have this version of the porting set. So please check if 6.1c.06.06 is installed correctly. See solution 15219 for an overview of porting set numbers and solutions.
If you can't get this working and keep getting this error you could consider uninstalling solution 130014. This upgraded you ttdllreadmenu to use the bms.init function. So if you uninstall it, it is not used anymore and the error should disappear. The disadvantage is that Worktop won't run the objects mentioned in the BMS mask data (session ttadv4188m000) anymore on startup, since this has been resolved with solution 130014.

Regards, Ivo

Ivo,

Still not able to run Worktop under older portingsets? You were busy with that some while ago...

Hi OmeLuuk,

Worktop does work with older porting sets, however for the latest upgrade a modification in the porting set was required. So you can run Worktop under older porting sets, but then you shouldn't install the latest solution 130014.

Regards, Ivo

It was not possible to make WorkTop portingset "aware".

Hi Ivo,

I got the worktop working by uninstalling the solution you suggested, however, when I open a session I have to minimize the worktop in order to see it, I would like to open the session and see it infront of the worktop.
Furthermore, when I go to ttaad2100m000- Maintain User Data(Enviroment tab), I can't see the following fields on the screen:

1. Startup Program
2. Startup Desktop
3. Startup Menu
4. Level to Load at Startup

Is there any connection between the two?

Thanks,

Abuibra,

Refer to the thread - Controling Windows (http://www.baanboard.com/baanboard/showthread.php?s=&threadid=8583&highlight=tweak)

Hi Abuibra,

Regarding the window on the background problem; the thread mentioned by NPRao does indeed offer a solution to the problem by instlling TweakUI. Another fix is by manually editing the sustems registry (or create a .reg file and open it): Open regedit, locate the "ForegroundLockTimeout" key in HKEY_CURRENT_USER\Control Panel\Desktop and set its value to 0.
This problem has nothing to do with the other problem you mentioned. The fields you mentioned are not on the "environment" tab but on the "startup" tab (the second one from the left). If these fields are missing I really doubt whether SP10 was installed correctly, since again this should have been OK...

Regards, Ivo

When users with DEM menus login via the worktop, they don't see their DEM Menus, they only see the Menu Browsers? Any Idea?

Thanks

Hi Abuibra,

Yes, within the User Data session (ttaad2100m000) there are a few new options. In the "startup" tab of this session you will find a group called "Worktop tree". It contains the fields "Menu Browser", "Baan Process Browser" and "Baan Workflow". To enable DEM for a user you must check the "Baan Process Browser" option for that user (do not forget to convert to runtime and to restart Worktop\BW).

Regards, Ivo

Hi Ivo,

I have checked the "Baan Process Browser" option and convert to runtime, still can't DEM to work. I have also try to login via the normal BW client and I can see the DEM menu for that particular user. Any more suggestion?

Thanks.

Hi Abuibra,

If the "Baan Process Browser" is correctly set in the user data session then at least a "Baan Process Browser" node should appear in the Worktop navigation area (below the "Baan menu Browser" node).
It might be that the convert to runtime did not succeed, I know there have been some problems with that in the past. So please check manually if the convert to runtime went OK: open the file $BSE\lib\user\u<baanusername> in vi or notepad, where <baanusername> is the baan user you use. There should be an entry called "worktop_trees:" and this entry should have the value "MB PB" (the PB stands for Process Browser). If this entry is missing you can try to add it manually.

Regards, Ivo

Hi Ivo,

Your solution worked fine but the worktop_trees:MB PB was missing and I had to insert it. However, now I am getting both the Menu Browser and the DEM Menu. Is it possible to only have one?

Thanks

Hi Abuibra,

Yes, of course that is possible. There are two things that determine whether you have the Menu Browser and\or Process Browser:

-1- When you install Worktop locally (which I guess you did) then you will always have access to the Menu Browser. Reason for this is that when you install Worktop locally, you are considered to be an administrator which therefore always has the Menu Browser.
Usually customers are using the Central Deployment feature of Worktop. This means you don't have to install Worktop locally on all clients but install it only once on a central server. When users are using this "shared installation", they are considered not to be an admin and will not by deault have access to the Menu Browser.
If you plan to install Worktop locally on all clients, you can change this default behavior: remove the line "MBAccessAlways=1" from the setup.ini file of the Worktop installation media before installation.

-2- Access to the Menu Browser or Process Browser can be defined in the User Data session, as described before. In the 'manual' case; the entry MB in worktop_trees stands for menu Browser and the entry PB for process browser. So to have only the Process browser, define worktop_trees:PB

Regards, Ivo