raprap
12th February 2010, 17:42
Hi all,

One of my clients has a new PC with Windows 7 on it. Latest BW is installed on it. There is a user 'jos' who can't logon to Baan on this particular PC. He can login however on any other PC. Here is the story.

Jos types his username and password on the Windows 7 machine and the error
Not authorized to run as user 'tftp'
appears. Well, there is no user 'tftp'. Next he tries to logon as bsp: this is no problem. Even some other users can logon with BW on that PC, while jos is logged on as Windows user.

The problem is not in the user settings; the u file 'ujos' states
unixuser:jos
If the problem was in the user settings, jos would not be able to logon on another (non Windows 7) PC.

The command line in the BWC file is empty (there is no line like
-- -set USER=tftp
or something. I am beginning to wonder if this might have something to do with Windows 7...

Any hints?

Dieter
13th February 2010, 16:32
Hello raprap,

tftp is usually a protocol for filetransfer. Maybe the user jos has some scripts on the ERP server that uses this protocol for transfering files to/from the pc where the BW is running.

Which OS is running on your ERP server ? Do you have checked the log files ?

Are you using worktop ? if yes: Do you use central deployment for Worktop ?

Did you try Webtop ? Do you get the same error ?

regards
Dieter

raprap
16th February 2010, 12:01
Hi Dieter,

I am aware of the fact tftp is a protocol, but I cannot understand why this error solemnly occurs when logging in as user 'jos'.

The OS is HP-UX B.11.23 U ia64

The logfiles only show lines like
log.bshell:2010-02-12[15:46:22]:E:tftp: ******* S T A R T of Error message *******
log.bshell:2010-02-12[15:46:22]:E:tftp: Log message called from /view/port.6.1c.07.17/vobs/tt/lib/al_1/al_env.c: #833 keyword: user
log.bshell:2010-02-12[15:46:22]:E:tftp: Pid 16765 Uid 106 Euid 106 Gid 125 Egid 125
log.bshell:2010-02-12[15:46:22]:E:tftp: user_type S language 2 user_name tftp tty locale ISO88591/NULL
log.bshell:2010-02-12[15:46:22]:E:tftp: Errno 2 (No such file or directory) bdb_errno 0
log.bshell:2010-02-12[15:46:22]:E:tftp: Log_mesg: User file for user 'tftp' does not exist. Last searched location '${BSE}/lib/user/utftp'
log.bshell:2010-02-12[15:46:22]:E:tftp: ******* E N D of Error message *******
log.bshell:2010-02-12[15:46:22]:E:tftp:
log.bshell:2010-02-12[15:46:22]:E:tftp: ******* S T A R T of Error message *******
log.bshell:2010-02-12[15:46:22]:E:tftp: Log message called from /view/port.6.1c.07.17/vobs/tt/lib/ds_1/ds_bcnct.c: #189 keyword: DsSendNAck
log.bshell:2010-02-12[15:46:22]:E:tftp: Pid 16765 Uid 106 Euid 106 Gid 125 Egid 125
log.bshell:2010-02-12[15:46:22]:E:tftp: user_type S language 2 user_name tftp tty locale ISO88591/NULL
log.bshell:2010-02-12[15:46:22]:E:tftp: Errno 0 bdb_errno 0
log.bshell:2010-02-12[15:46:22]:E:tftp: Log_mesg: Not authorized to run as user 'tftp'
log.bshell:2010-02-12[15:46:22]:E:tftp: ******* E N D of Error message *******

This problem occurs without worktop, just with plain BW, so central deployment is not an issue

Webtop is not installed, so we can't try this.

Unfortunately I am not often at the customers site, so I cannot have a proper look at the Windows 7 machine on which this problem occurs. It is a problem on the specific PC, because Jos can login on another Windows 7 PC. Furthermore, it is the combination of Jos' PC and BW version B40c.97, because an old version of BW (version B40c.61) does not give any problems.

So I have a workaround now, but I am really curious what causes this problem.

Regards,
Ray

grzegorz
16th February 2010, 13:59
Please note, that bwc files for BW ver.61 and 97 are stored by default in different locations on local machine. For version 61 they are kept where BW is installed for instance:
c:\Program Files\Baan\Lib\User
Version 97 uses a directory in user area:
<user name>\AppData\Local\Infor\BW\Baan\Config

So, you may use different bwc files to connect with different BW version. Did you locate and check both?

raprap
18th February 2010, 10:29
Hi Grzegorz,

This is of course a major difference. It still does not explain why one user can login and the other can't. I think the cause of this problem can only be found by a thorough investigation of this particular PC. What doesn't help is that version 97 is uninstalled by now. The configuration of PC's is the customer’s responsibility, so I am afraid I will not get an answer on this one.