Just a quick update on this problem:

1.  dbg cannot connect into this running pvx web session.  However, the cpu cycle time shows it's running.
2.  I was able to trace the pvx web session on the client's SQL server and found this being reported in Activity Monitor Session:

-- network protocol: TCP/IP
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed

...suggesting a bad handshake?

Hi Eva,

Thank you for those two thoughts.  The DBG does not connect to these sessions, however I am able to identify what html pages they are viewing.  So, I'll investigate your thought about the SetTime function.

=) Thank you.

Best,
Yonman

Hi Alain, 
 
You mention in your note that 'the mail server is the one provided by a hosting company'.  That leaves a lot of questions, Alain. 

But, the fact that only one customer is not receiving your email suggests the problem lay with the recipient's Exchange server itself.  Is there an admin who manages that Exchange server?  They should be able to see in their error logs a need to whitelist your domain or add your domain or sender name to an allow-list.

Emails going to this same recipient through Gmail or Outlook are flagged as safe because they are going through authorized email servers, over a secure port, with full encryption.  Something about your email 'hosting company' is being flagged as suspicious.

Very best,
Yonman

As per documentation, we've a default timeout of 30 seconds for an Apache web service installation.  It's not been overridden for years.  Starting last year, we've noticed that pxplus sessions, periodically, do not terminate.  They don't seem to use any pxplus web licenses while they are hanging there.  But, it does slow down the performance hugely, however.

The hug sessions are a variety of web pages, not any one specific page. 

Might be a port issue.  But, I thought this might be an easy answer for the Pxplus Developers here.

Thank you for any suggestions!
(attached)


timeout= nn

Changes the default 30 second timeout for the maximum run time that a task can take. If a spawned task takes longer than the number of seconds in the timeout period, the system will terminate the task and report an error.

Thank you Mike....in all the years, I never needed to this resolution.  And thank you for posting it!  Worked for me.

As per Mike:
Try removing the WindX INI file which contains the authorization information.

It should be:

C:\Users\<username>\AppData\Roaming\PxPlus\windxcfg.ini

Thank you, Mike!

That should be fine.  Here's the Pvx Help File Link if you need it: https://manual.pvxplus.com/PXPLUS/file_handling/~pdf~.htm

There's some examples in the help files, too.

Best,
Jonathan

Great question!  The Pvx docs caution that the Report Writer "is not suitable for character-based systems".  And from what I recall, lends itself best to files maintained within the Data Dictionary. I'm curious why no one asked what types of data files you were using nor the type of machine, so I'm curious why no one took the time to inquire.  Assuming you are using a Windows machine, you might easily slip in the *PDF* file handling feature into your existing code and take advantage of the numerous controls including fonts.

Hi Len,

I see that PxPlus 2023 has 2-Factor Authentication.  That is incredible!
https://manual.pvxplus.com/PXPLUS/NOMADS%20Graphical%20Application/System%20Maintenance%20Tools/Security%20Manager/Two%20Factor%20Authentication.htm

Congratulations to your dev team, Len.  Just wonderful!  Thank you so much.

Best,
Jonathan

We have a Multi-Segmented File (v11.65) and the main file has been moved to a backup folder but the segments were not.  The main file is currently open and active by users, as they've not logged off and the file is currently in-use.  Our question is, when the main file has reached it's capacity and when new segments are to be automatically created, will this actually take place?   Will the original segments be preserved in some manner or will they be replaced with a link to the new main file? 

We've noticed that hung/disconnected sessions impede the USERS console command from running.  Killing the session will allow >USERS to run properly.  We can confirm that the hung session cannot be connected to via DBG.  (Windows Environment).  Is it possible to adjust the USERS Console Command to not hang when it encounters a session that it cannot connect to? We can see the session listed via Task Manager, but no obvious visual queues indicate that it's hung. 

Thanks!

We have seen instances where two NTHost sessions are running on the same server, using the same installation folder, supporting active pxplus sessions.  We've confirmed that NTHOST can be launched under the 'administrator' account and under a standard user off the server console simultaneously.

We were under the impression that only 1 NTHost session can be running at a time. 

The message, "NTHost is already running" probably means that a session is already running under the same credentials that it was initially launched.

So, is there any benefit to having multiple NTHost sessions running?  Any conflicts or concerns?

Thank you for the suggestion.  That parameter works for the SETTRACE , not the PxPlus Tracing Window.  And, the 'current time (in seconds)  being displayed is actually the cumulative seconds the trace was started, not the actual time ie:  13:16pm.  But, I appreciate the suggestion!  I may be able to use the SETTRACE as a substitute.  Thank you again for your suggestion!

I've looked through the Trace Window options and don't see option to include Date/Time stamp in the PxPlus Trace Window, showing the date (YYYY:MM:DD)+time (mm:ss) when each line of code is being executed.

Is that a possibility?

James, we often get crashed processes and traced to an unstable core pxplus.  Restarting the server fixes the issue, particularly in a Terminal Server env.  We haven't figured out the cause, perhaps executable or dll is getting dropped from memory.

How large are the corrupted files?  And are they consistently corrupted each time they are restored?