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.
211
Programming / Re: Cannot make secure [TCP] on RHEL7, PXPlus 14 (Certificates problem)
« on: March 27, 2019, 03:29:31 PM »
The problem is not likely that PxPlus is not recognizing the certificate but that it did not get one. You have connected to the server from a PxPlus and looked at the certificate so we know it is good. This points to the server not liking the clients that do not work. Maybe the server is requiring clients to use a specific cipher that is supported by the good servers OpenSSL and not the bad servers OpenSSL? This would not be based on OpenSSL version but how the OpenSSL was compiled.
212
Programming / Re: Cannot make secure [TCP] on RHEL7, PXPlus 14 (Certificates problem)
« on: March 27, 2019, 10:36:11 AM »
Hi Loren,
By default when you make the [tcp] connection to the https server PxPlus does not validate the certificate. Unless you are using PxPlus 2017+ and you had the option
CERTIFICATES= VALIDATE | TRUSTREQD
So validation of the certificate is not likely the issue.
I can't really guess what the issue actually is though. The results should be the same for both systems as they are talking to the same server. Here are some questions that may help lead to an answer.
1) Is the PxPlus where it works and the PxPlus where it doesn't work the same version?
2) Is the OS the same?
3) Is the OpenSSL version the same and are there updates available?
4) Is there internet security software that could be blocking things?
By default when you make the [tcp] connection to the https server PxPlus does not validate the certificate. Unless you are using PxPlus 2017+ and you had the option
CERTIFICATES= VALIDATE | TRUSTREQD
So validation of the certificate is not likely the issue.
I can't really guess what the issue actually is though. The results should be the same for both systems as they are talking to the same server. Here are some questions that may help lead to an answer.
1) Is the PxPlus where it works and the PxPlus where it doesn't work the same version?
2) Is the OS the same?
3) Is the OpenSSL version the same and are there updates available?
4) Is there internet security software that could be blocking things?
213
Programming / Re: Firewall changes to allow Port 4093
« on: March 27, 2019, 09:31:42 AM »
Hi Bill,
You should only need to allow incoming TCP connections on port 4093 on the machine where you are running *plus\cs\host.
One of the features of the Simple Client/Server is that it only needs the one port. By default it uses 4093 which is registered by ICANN to PxPlus so nothing else should be using that port.
You should only need to allow incoming TCP connections on port 4093 on the machine where you are running *plus\cs\host.
One of the features of the Simple Client/Server is that it only needs the one port. By default it uses 4093 which is registered by ICANN to PxPlus so nothing else should be using that port.
214
ODBC / Re: Error Log ODBC
« on: March 18, 2019, 12:30:02 PM »
Hi Jeff,
I use the debug logging all of the time and I have not had this issue. We have not had anyone report this issue before either.
When using Excel are you sure you are using the same DSN you turned debug logging on in?
When clicking enable debug logging do you then save the change by clicking apply or OK?
Do you have both 32-bit and 64-bit versions of the ODBC driver installed or just one?
I use the debug logging all of the time and I have not had this issue. We have not had anyone report this issue before either.
When using Excel are you sure you are using the same DSN you turned debug logging on in?
When clicking enable debug logging do you then save the change by clicking apply or OK?
Do you have both 32-bit and 64-bit versions of the ODBC driver installed or just one?
215
Programming / Re: https
« on: March 15, 2019, 08:38:33 AM »
Hi,
If this is for a website you probably need a trusted SSL certificate from a Certificate Authority (CA) in order from web browsers to trust your web site and not warn users and prevent them from accessing it. To get a trusted SSL certificate from a CA you need to purchase one and the CA then will verify you are who you claim and that you control the website. They will then issue you a certificate.
Here is some links to a couple:
https://ssl.comodo.com/
https://ca.godaddy.com/web-security/ssl-certificate
https://letsencrypt.org/ (free but certificates must be renewed every 90 days)
There are many more options as well.
If this website it for internal use only and you control the machines that can connect to it you can used a self signed certificate and add that certificate to the trust store of the machines that will access it yourself. If you are using PxPLus 2017 are newer PxPlus provides a tool for generating a self signed certificate (https://manual.pvxplus.com/PXPLUS/utilities/SSL%20Cert%20Generator.htm).
If this is for a website you probably need a trusted SSL certificate from a Certificate Authority (CA) in order from web browsers to trust your web site and not warn users and prevent them from accessing it. To get a trusted SSL certificate from a CA you need to purchase one and the CA then will verify you are who you claim and that you control the website. They will then issue you a certificate.
Here is some links to a couple:
https://ssl.comodo.com/
https://ca.godaddy.com/web-security/ssl-certificate
https://letsencrypt.org/ (free but certificates must be renewed every 90 days)
There are many more options as well.
If this website it for internal use only and you control the machines that can connect to it you can used a self signed certificate and add that certificate to the trust store of the machines that will access it yourself. If you are using PxPLus 2017 are newer PxPlus provides a tool for generating a self signed certificate (https://manual.pvxplus.com/PXPLUS/utilities/SSL%20Cert%20Generator.htm).
216
ODBC / Re: ODBC Connection string
« on: March 04, 2019, 09:45:56 AM »
If the connection string works in Excel there is no reason for it to not work in another ODBC client. My guess is it has something to do with not including the UID= when using Excel. I would either not include UID= when using the other application or include both UID= and PWD=.
Other thoughts are try to include SERVER=NotTheServer in the connection string.
Other thoughts are try to include SERVER=NotTheServer in the connection string.
217
ODBC / Re: ODBC Connection string
« on: March 01, 2019, 02:45:52 PM »
What is the error reported by the third party software when it doesn't work?
I would suspect it is not the connection string that is the issue. Is the third party software 64bit or 32-bit? If 64-bit you will need to install the 64-bit PxPlus ODBC Client.
I would suspect it is not the connection string that is the issue. Is the third party software 64bit or 32-bit? If 64-bit you will need to install the 64-bit PxPlus ODBC Client.
218
Programming / Re: Defining Function
« on: February 25, 2019, 03:40:20 PM »
Hi Jeff,
You could make it an object with the functions defined as methods and call it something like myUtilities.
Then in programs you want to use it you do a myUtilies=NEW("myUtilties"). Then you simply call the functions like myUtilities'pair$("Key","Value")
You could make it an object with the functions defined as methods and call it something like myUtilities.
Code: [Select]
DEF CLASS "myUtilities"
FUNCTION pair$(key$, value$)pair
END DEF
pair:
ENTER key$, value$
...
return result$
Then in programs you want to use it you do a myUtilies=NEW("myUtilties"). Then you simply call the functions like myUtilities'pair$("Key","Value")
219
ODBC / Re: odbc 5.1 vs 5.2
« on: February 19, 2019, 01:35:46 PM »
I believe that doing a replace of 'R' with 'revenue' would avoid the bug.
220
ODBC / Re: odbc 5.1 vs 5.2
« on: February 19, 2019, 10:25:01 AM »
A bug was fixed in version 5.20.0002 of the ODBC driver with the REPLACE scalar function. The bug was triggered when the replacement text contained the search text. In your Example the search text is 'R' and that replacement text 'Revenue' also contains 'R'. Therefore it is expected that the bug would cause an issue with version 5.10 of the ODBC driver without the fix.
The customer running 5.10 should upgrade to at least 5.20.0002. If they are licensed for 5.10 then they can run 5.20 with that license.
The customer running 5.10 should upgrade to at least 5.20.0002. If they are licensed for 5.10 then they can run 5.20 with that license.
221
ODBC / Re: ODBC licenses used?
« on: February 12, 2019, 02:10:14 PM »
Hi Chris,
The PxPlus SQL Server is a single process. Each client connection spawns a new thread and not a new process.
You can find out the IP address of all of the connected clients so you can then get them to shut down the application that is connecting to the server. To do this you can use the Windows command netstat from the Windows command line. Look for any line that has a local address with the PxPlus SQL Server port (default 20222). This should let you know who is connected.
There is also a useful Windows program called Process Explorer (download here https://docs.microsoft.com/en-gb/sysinternals/downloads/process-explorer) that will allow you to select the server process pxpsqlsvr.exe and right click it and select properties then see all of it's TCP/IP connections. You could also figure out who is connected this way. This tool will also allow you to see a list of threads where any thread with a higher TID then the ntdll.dll timer thread should be a client connection thread. I would not recommend killing the threads as it may not clean up nicely. In a pinch if you can't get a client to disconnect this may be worth trying before restarting the whole server.
The PxPlus SQL Server is a single process. Each client connection spawns a new thread and not a new process.
You can find out the IP address of all of the connected clients so you can then get them to shut down the application that is connecting to the server. To do this you can use the Windows command netstat from the Windows command line. Look for any line that has a local address with the PxPlus SQL Server port (default 20222). This should let you know who is connected.
There is also a useful Windows program called Process Explorer (download here https://docs.microsoft.com/en-gb/sysinternals/downloads/process-explorer) that will allow you to select the server process pxpsqlsvr.exe and right click it and select properties then see all of it's TCP/IP connections. You could also figure out who is connected this way. This tool will also allow you to see a list of threads where any thread with a higher TID then the ntdll.dll timer thread should be a client connection thread. I would not recommend killing the threads as it may not clean up nicely. In a pinch if you can't get a client to disconnect this may be worth trying before restarting the whole server.
222
ODBC / Re: PXPlus SQL ODBC Client Procedure
« on: January 15, 2019, 08:51:33 AM »
Hi Mike,
This is caused by a bug that we have already fixed but has not yet been released. We plan to do a release soon with this fix as well as a few other fixes.
If you need the fix now you can e-mail me and I can send you a updated DLL with the fix.
This is caused by a bug that we have already fixed but has not yet been released. We plan to do a release soon with this fix as well as a few other fixes.
If you need the fix now you can e-mail me and I can send you a updated DLL with the fix.
223
ODBC / Re: PxPlus SQL Server 6.10
« on: January 14, 2019, 08:27:50 AM »
Hi Mike,
The download/version is correct I just forgot to remove the flag that causes it to say pre-release before making the release. You can safely use that version as it is not the pre-release version despite what it says. Sorry about the confusion.
I will make a quick patch release for the Windows SQL ODBC driver that fixes the issue.
The download/version is correct I just forgot to remove the flag that causes it to say pre-release before making the release. You can safely use that version as it is not the pre-release version despite what it says. Sorry about the confusion.
I will make a quick patch release for the Windows SQL ODBC driver that fixes the issue.
225
There are no current plans to develop a JDBC driver.
There are products out there that allow you to use a ODBC driver with JDBC called JDBC_ODBC bridges. Here is one (https://www.easysoft.com/products/data_access/jdbc_odbc_bridge/#section=tab-1).
Another option would be to invoke the PXPSQL command line client from within java and read back the results.
There are products out there that allow you to use a ODBC driver with JDBC called JDBC_ODBC bridges. Here is one (https://www.easysoft.com/products/data_access/jdbc_odbc_bridge/#section=tab-1).
Another option would be to invoke the PXPSQL command line client from within java and read back the results.