ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> Problem logging in from Terminal session
http://www.istechforum.com/YaBB.pl?num=1260551484

Message started by RPCAdmin on 12/11/09 at 10:11:24

Title: Problem logging in from Terminal session
Post by RPCAdmin on 12/11/09 at 10:11:24

This might be since SP5 - not totally sure.........
I have a Terminal server user who is trying to log into EVO - as of a couple days ago, no problem.
When he tries logging in now, he gets the error:

Title: Re: Problem logging in from Terminal session
Post by RPCAdmin on 12/11/09 at 10:17:37

Arrgh - now to finish....

This might be since SP5 - not totally sure.........
I have a Terminal server user who is trying to log into EVO - as of a couple days ago, no problem.
When he tries logging in now, he gets the error:
The file TASPRO7.ini doesn't exist in either your default or system directory. This program
will exit, please run TP6SETUP and create the file before continuing.
The file does exist in \Users\Username\ISTS
I've even tried running it by loggin in remotely as the Admin and get the same result.
TP6SETUP doesn't exist.

Title: Re: Problem logging in from Terminal session
Post by GasGiant on 12/11/09 at 11:10:24

I've received a number of odd errors from Evo on some workstations. In most cases, doing the recommended install fixes it...

Remove or rename the ISTS folder, delete the desktop icon, navigate to the network EVOERP or DBAMFG folder and run evoerp.exe to start the install. Answer the install prompts and life is good again. This gets rid of a lot of workstation gremlins.

In some cases I have also uninstalled and reinstalled the Pervasive client if they were getting PSQL or bTrieve errors.

Title: Re: Problem logging in from Terminal session
Post by RPCAdmin on 12/11/09 at 11:31:06

Colin,

Does this include Terminal Server Sessions? I know in some ways, they are different.

Title: Re: Problem logging in from Terminal session
Post by GasGiant on 12/11/09 at 11:51:25

We have a lot of TS users and we have put all user's ISTS folder on their personal share, which is mapped to drive Z. For each machine, including the TS, we have created a c:\ists folder and removed all permissions so that it is inaccessible. The install is set to go to the Z: drive where it creates the ISTS folder. Yours probably isn't set to do that, so you can let it create the C:\ISTS folder locally, then copy it to the user share, then disable the local C:\ISTS. If doing it that way you also have to fix the shortcut, obviously.

Title: Re: Problem logging in from Terminal session
Post by RPCAdmin on 12/11/09 at 12:28:35

I get into this so infrequently, that I forget the proper way to do this.
Our TS setup is similar to what you describe....Each TS user has an ISTS folder in their user directory.
Our alt drive for ISTS is M: Not sure about the mapping or how it should be set (again - it has been to long and too infrequently done).

It sounds like I want to log in as admin, do the directory manipulation, log in as the user, try running evoerp again and see what happens. If memory serves, the last time I did this, I got an error saying it couldn't find the M:\ drive and to contact Lynn.