Looks like the issue may be your path to a certificate /pxp/ is just a directory and not a .PEM file path.

When doing the Webster+ install make sure to use a path that includes the filename of the .PEM file.

I am not sure just putting the .conf in the conf-available directory is enough to have that configuration used. You may need to use the a2enconf command to enable the configuration. This is a guess based on the existence of that directory. Please consult your Apache documentation for the exact setup for your Apache.

After updating Apache configuration you need to restart the Apache server for it to use the new configuration.

For the PxPlus Web Server do you have the access.log enabled? That should log all access to the server if enabled.

Considering the error is coming from the Microsoft SQL Server ODBC driver I would still suspect the problem is not the PxPlus version.

Have you confirmed that the ODBC connection made from PxPlus is the same in the 16.2 v 19.1 versions. ODBC connection settings can be set via INI file, link file, prefix file, or directly in the open directive. If the ODBC settings were done in anything other then directly on the open directive it is possible the new version is not matching the old version and that is were the issue is.

Hi Michael,

Sounds like it could be either a issue with the web request generated by the MS cloud app or an issue with the web server blocking the request from the cloud app IP address.

I don't know what type of web server you are using and how it is configured so I can't help much with that.

I would suggest checking the web request being sent from the cloud app to make sure it is the same as the one from postman that worked.

Hi Jeff,

That error is coming from the Microsoft SQL Server ODBC driver.

So the error appears to be happening on their end.

Is this using a different version of the MS SQL Server ODBC as when you were using PxPlus 16.20?

Is this a different DSN for the ODBC connection then when used with PxPlus 16.20?

My advice is look for differences with the SQL Server and ODBC driver setup since that is where the error is happening.

There is no training sessions or courses currently available for Webster+.

There are materials that discuss what Webster+ is and how to use it. In your last forum post I linked to these. There are additional resources from the Direxions+ conference presentations about Webtser+ which can be found here:

2024 (v21) - PxPlus on the Web Introduction
2024 (v21) - PxPlus on the Web File Maintenance Generator Demo
2024 (v21) - PxPlus on the Web HTML Editor Demo

It works for me in the latest version of PxPlus. What version are you trying this on?

• Yes a web licnese is required.
• Yes. Webster+ is compatible anywhere PxPlus can run (Windows, Linux, AIX , and MacOS).
• Yes that sounds like a good use case.
• Install PxPlus and setup Webtser+ on your web server. Create your Webster+ pages for the timesheet entry.
• There is several sources of documentation and examples that will help you along.
  
  https://manual.pvxplus.com/?Webster/Webster.htm  (Documentation)
  https://www.youtube.com/watch?v=c4UhjWkbEgM  (Webster+ setup video)
  https://www.youtube.com/watch?v=2YLPBMBPkPY&list=PLP2OOVHPpLwx3axRiOnnQXW5M5dDli4Bj  (Webster+ video play list)
  https://testdrive.pvxplus.com/  (demo with code examples available for download)
  
  
• No. Only the server needs a PxPlus license. Users are accessing it through a web browser and do not need PxPlus installed and therefor no license.

A common thing I have seen is the prefixes not been setup correctly in the new DNS entry. If the necessary prefixes are not defined then some tables can't be found. You can check the path field of the table in the data dictionary, you should be able to confirm if the path is correct and setup correctly on the server and if a prefix is needed.

Another thing to check is permissions.

Are you creating your own interface to Twilio or using *tools/sms?

Our tool supports Twilio.

This may be a bug that results in undefined behavior. That may be why you see it at one install but not another.

Can you try a newer version of PxPlus? That version is out of support and there have been many improvements to the SELECT directive logic since then. It is possible if this is a bug that it already has been fixed.

Other thoughts is it may have to do with a difference between the two installs. Maybe there is a difference in system parameters or something that could explain it not working. The 'SO' system parameter perhaps?

I would suspect it has something to do with "end %a0$+%lc$" in the SELECT directive.

If you do the same without a end do you get the records for %a0$ plus whatever is after them?

If so you may just need to get the end correct.

We had to figure this out for our own PxPlus web services. It is documented as part of the Apache configuration for PxPlus Web Services (https://manual.pvxplus.com/?Web%20Services/Overview.htm#configuration).

Apache by default will strip that out.

If you add:

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
to your httpd.conf it will put it back so the pxplus programs can see it.