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?

We are getting a rash of Error 105 on files that are not damaged in any way.  At the error occurrence, closing the file, issuing a wait 0, then re-opening the file will result in a successful read/write to that file.  We suspect that the file is getting loaded into local memory and getting corrupted. 

At some installations, the error occurs exclusively on one workstation in a company.  At other installations, the error occurs throughout all workstations, randomly through the day.

We have been researching Microsoft registries that controls caching, etc, but having found any solution yet.  Any thoughts?  Most appreciated in advance!

Note, we are using Mapped Drives.  No WindX used at all.

Error #105
Keyed file error (Short key block)

Reported whenever a key/data block is read from the file and the OS reports that the data read is less than was expected. Normally this indicates a truncated file caused by OS failure.

Can *ufar be used for mult-segmented files in all PxPlus release levels?  Are there warnings, cautions or other issues that can impact the results of the utility?