Paradox Community

Items in pnews.paradox-interactive

Subject:Re: Paradox crashing on terminal server leaves application unrunable
Date:Thu, 1 Dec 2016 15:32:12 +1000
From:Royce Lithgo <it@moregatebiotech.com>
Newsgroups:pnews.paradox-interactive
Thanks for the reply. I agree there could be a risk, but the application 
works under normal circumstances. The base pathname from %appdata% is 50 
chars - exactly what is "too long".

On 1/12/2016 7:55 AM, Anders Jonsson wrote:
>> PRIV directories are all in the %appdata% path so private to user.
>
> I would try to change that. There is a risk that the complete path
> becomes too long.
>
> I'm using P10 runtime on Windows Server 2012 in a terminal setup and we
> have been running smoothly for years.
>
> I have some memories about needing to reboot the server because we
> couldn't get into Paradox but that is many years ago.
>
> FWIW
>
> Anders
>
>
>
>
> The NETDIR location is one thing I am yet to rectify - i am still a
> little unsure about this one as i understood it's only an issue for
> shared paradox tables and there's only one of those in our system.
>
> BDE version is 5.01 (as reported from bdeadmin.exe)
>
> On 30/11/2016 12:24 PM, Tom Krieg wrote:
>> With a similar setup (P10 & PostgreSQL) I've always had rock-solid
>> performance on 2012 R2. How long has it been happening? The first place
>> I'd look would be the user's PRIV directories to make sure there's no
>> overlap. Then I'd look at the .NET file location and make sure it's the
>> same for each user. I'd also ask the Oracle dba if he's made any changes
>> to the ODBC driver or installed an updated one. Lastly, what version of
>> BDE?
>>
>> On 30/11/2016 11:55 AM, Royce Lithgo wrote:
>>> Server 2012 R2. Generally speaking it works quite well until this issue
>>> occurs. For printing, as long as we don't attempt to print to a domain
>>> printer, it works fine (only local server printers mapped to ip port
>>> work).
>>>
>>> We use Oracle databases as our main database and paradox files for temp
>>> tables (for reports etc.)
>>>
>>> I just can't work out what could be causing one user's crash to impact
>>> everyone.
>>>
>>
>>
>>
>


Copyright © 2004 thedbcommunity.com