ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Installation >> Setup workstation problems
http://www.istechforum.com/YaBB.pl?num=1181222678

Message started by Karen Mason on 06/07/07 at 06:24:38

Title: Setup workstation problems
Post by Karen Mason on 06/07/07 at 06:24:38

We have had problems since the 2/14/07 update when doing workstation setups. Our original instructions have us mapping DBAMFG & PVSW on the server, turning off antivirus, and loading pervasive.

Next step is where we encounter problems. Browse to DBAMFG on server. Double click EVOERP.exe, at logon, we now get the WHOAMI error and get booted out of the program. I actually have to load TAS6EVO.exe to load a workstation.

2nd problem: During the last installation, went to the C drive to give write rights to the appropriate users but there is no security tab. Is that a function of the operating system?

Title: Re: Setup workstation problems
Post by Lynn_Pantic on 06/07/07 at 07:12:01

You should NEVER be using TAS6EVO.EXE anymore. It is outdated and not compatible with the current programs. You need to be using EVOERP.EXE. But when you double click on EVOERP.EXE in DBAMFG when loading a new workstation, it should not go to the logon screen. It should run the Workstation Setup and create the C:\ISTS folder, copy the necessary files, and the desktop icon.

What is the 4th line of the TASPRO7.INI in the DBAMFG folder? It should be

DfltRunPrg=X:\DBAMFG\EvoWkssetup.rwn

where X:\DBAMFG\ is whatever your server path is.

As for the user rights to C:, if you are going to have multiple users sharing the same workstation, then you will need to configure it using the instructions for Terminal server but in a normal single person at a desk type environment, you should have the user profile run the installation so they will be the owner of the C:\ISTS folder.

Title: Re: Setup workstation problems
Post by Karen Mason on 06/07/07 at 08:30:29

Here is what the 4th line shows:
DfltRunPrg=G:\EvoERPmenu.RWN,
I can change it, but I wonder if other things might be wrong also.

(This is the same program called out in TAS-C)