PxPlus User Forum

Twitter Twitter Twitter

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MikeinFL

Pages: 1 2 [3]
31
Trying to get new customer setup and have run into this issue.  Help please.

I run simple client with a remote rdp (my customer's network support seutp) and it usually runs my startup program fast in 1 second.  But after 3 hours off I tried again and it delayed.  This has been happening since I've set them up.  After 2 minutes of no connection, and ae blank dialogue screen with a cursor in the top left corner, but my startup pgm not running,  I did one thing- I clicked on the desktop of the host (I have remote access) and when I did my startup program ran the moment I clicked on the host server desktop.  The server desktop was not in sleep or saver mode.

It's as if something is going idle on the host server and a mouse click on the desktop wakes it up.  The network support tech has no idea why this happens.   Display sleep was already set to never.  Wakeup was always enabled.  Power management is balanced.  I just set it to High Perf to see if that helps.

Setup:
1. Simple client host runs PxPlus V16.10.0000 DEMO on Windows Server 2019 Standard, port 4093:

Simple client host shortcut:
TARGET
"C:\PVX Plus Technologies\PxPlus 2019 Upd 1\pxplus.exe" -bkg *plus\cs\host -arg "4093;RECON=180"
STARTIN
"C:\PVX Plus Technologies\PxPlus 2019 Upd 1\"

2. Simple client client shortcut is located on another server with Windows 7 Ultimate:

TARGET:
 "C:\PVX Plus Technologies\Windx Plugin 2019 Upd 2\pxplus.exe" *plus\cs\client -arg SERVER1 mystartpgm
STARTIN
"C:\PVX Plus Technologies\Windx Plugin 2019 Upd 2\"

3. My remote rdp the network tech setup for me runs the the above client shortcut located on a different server, not the host


It seems unusual to me to setup a remote rdp not to a client shortcut on the the host server, but to a client shortcut on a different server.  Is this ok?  Also they tell me these windows servers are in a virtual environment.

Their network tech said the no connect might be that the second server, Windows 7 Ultimate, gets bogged down. But everyone was off the second server when my program could not connect.   Remote rdp app always connects ok.  Rdp starts client screen but the client doesn't run my startup program although the dialogue screen comes up and the cursor is 'stuck' at the top left of a blank screen.  As if waiting for a response from the host. 

The host server has no issues in task manager and everything looks normal.  Clicking on the host server desktop (not the second server where the client shortcut is located) makes my startup program run immediately. I've done this several times and clicking on desktop of server makes it run.  This no connect only happens after some time has gone by.   I just tried an hour later and it was ok. 

How to fix?

Mike

32
Using v16 and simple client I want to write a program that will display all active client processes on the host and have the ability to close a client process.  I did this on ProvideX by logging each fid and PID whenever a client logged in, and then checking that window was active and using the old *SNDMSG.API to find the open window and used PID to close it by executing kill.exe on the host..

On v16 simple client *winapi like this is not finding any window: 
CALL "*winapi;FindWindow",WIN_TEXT$,WIN_HANDLE

What's the right way to do this?

33
Registration and Setup / Re: PDF port range?
« on: March 16, 2020, 10:32:42 AM »
I will stick to Simple Client, thanks


34
Registration and Setup / PDF port range?
« on: March 16, 2020, 12:20:13 AM »
What port range do I need to open in the server firewall to allow remote pdf printing?   

I have nthost set on 20000-21999 and ntslave remote (rdp) works ok except pdf does not open unless I open firewall ports 59000-65000.    v16.10.0000






35
Registration and Setup / Re: Why two Activation Keys?
« on: October 16, 2019, 08:50:21 AM »
"Many companies buy new licenses then install old, sometimes unsupported, versions of PxPlus."

So if I order new keys for an old ProvideX ver5 user, and they will continue to use that older code, I should use the Activation Key not the PxPlus Key?

Also, for that user running old ProvideX v5 code, should I order Base or Pro?  Would Pro work on that old user?  Or is Base and Pro the same code wise?

36
Registration and Setup / Why two Activation Keys?
« on: October 03, 2019, 06:02:59 PM »
In the past when I ordered keys for a new system, I received two keys- "Activation Key" and "PxPlus Activation Key"

What's the difference and which key do I enter in the 5 boxes in the 'PxPlus product keys and registration' screen?

Thanks
Mike

Pages: 1 2 [3]