I've got an issue with a worktop installation. Worktop and BW is installed on a server share with a couple of documents set up for central deployment. Typically this works without any problem.

Now on a terminal server when Worktop is launched the user is prompted for authentication which they provide and click ok. It looks like a BW shell is kicked off but after a minute or two the connection fails without any error.

The Worktop documents seem to work fine everywhere else. I'm not sure what has gone wrong with the Worktop on this TS.

Any Suggestions?

LN 6
Worktop 2.4.15
BECS 8.3a.01.3

13:47:20 06-03-2007 Error 003 : Dispatch for Baan Automation could not be created.

The above error appears in the wtError.log in the appdata\baan folder

Anybody ever seen this before?!? I've had this problem on workstations, I removed everything related to baan (worktop, BW, reg keys, folders in profiles...) rebooted a couple of times then it'll start working again, but not on the terminal server. I'm ready to reload a server 'cause worktop is fragged up!

If anybody has seen the error

Error 003 : Dispatch for Baan Automation could not be created.

and has any suggestions please reply.

Thanks!

I have the same problem on some customers.
Still could not find the cause for this.

Does anybody have a clue?

Thanks
Fred

Applied SP2 for Windows Server 2003 on the TS and the problem went away. I still have the same sort of issue with clients sometimes but we can usually get it working again by deleting the temporary copy of worktop that gets created in the users profile along with everything else related to LN/BW on the machine and rebooting.

Thanks for the tips.

Will try them next time I'm at a customer facing that problem.

Fred.

I've seen this in some computers with Windows Vista.
To solve the problem you must right click over becs.exe and worktop.exe and chose "Run as administrator" (even if you are logged in as a machine administrator) to configure the environment.
After that you can start Worktop normaly without special permissions.
Regards
Chavez

Dear Board,

to inform the worktop running on terminalserver you have to specify the following paramter on the desktop link:

/ts

Example:

.../worktop.exe /ts

64 Bit Terminalserver Windows 2003:

".../worktop.exe" "/ts"

Because of the empty space in the programm path ..."Programms (x86)".

Kozure