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.
196
Thin Client/WindX / Re: Windx Security on Terminal Server
« on: June 17, 2019, 03:08:56 PM »
Use the WDXTRUST environment variable.
https://manual.pvxplus.com/?PxPlus%20Installation%20and%20Configuration/Customizing%20PxPlus/Environment%20Variables.htm#Mark3
https://manual.pvxplus.com/?PxPlus%20Installation%20and%20Configuration/Customizing%20PxPlus/Environment%20Variables.htm#Mark3
197
Programming / Re: How to remove a file from an FTP server using Curl
« on: June 10, 2019, 08:13:44 AM »
Our FTP utility uses a command like that to do deletes so as far as I known it should work.
Maybe try getting rid of the space before the -DELE
Maybe try moving the path from the server URL to in front of the filename
If those suggestions don't work you may want to try curl support as this is now strictly a curl question.
Maybe try getting rid of the space before the -DELE
Maybe try moving the path from the server URL to in front of the filename
If those suggestions don't work you may want to try curl support as this is now strictly a curl question.
198
Programming / Re: How to remove a file from an FTP server using Curl
« on: June 07, 2019, 08:04:52 AM »
I missed the quotes and the URL and the delete command are separate. Try this:
curl -k -ssl --user username@servername.com.au:password ftp://ftp.servername.com.au/public_html/Future/Texts/ -Q "-DELE filename.txt"
curl -k -ssl --user username@servername.com.au:password ftp://ftp.servername.com.au/public_html/Future/Texts/ -Q "-DELE filename.txt"
199
Programming / Re: How to remove a file from an FTP server using Curl
« on: June 06, 2019, 09:11:44 AM »
cURL doesn't support FTP delete directly but it does allow you to execute FTP commands manually. To delete you can send a FTP delete command manually using cuRL.
-Q -DELE /path/to/filetodelete
-Q -DELE /path/to/filetodelete
200
Web Services / Re: Curl Syntax
« on: May 23, 2019, 08:12:07 AM »
I can confirm that it is -o /path/local that you want instead of -O.
cURL will not handle the * wildcard for you. You have to get the listing from the server and do the pattern match and then specify each file that matched the pattern to download from cURL. This is what *web/ftp has to do to support wildcards.
In a future release *web/ftp will support implicit and explicit FTP over SSL/TLS.
cURL will not handle the * wildcard for you. You have to get the listing from the server and do the pattern match and then specify each file that matched the pattern to download from cURL. This is what *web/ftp has to do to support wildcards.
In a future release *web/ftp will support implicit and explicit FTP over SSL/TLS.
201
ODBC / Re: sql server install alongside 5.
« on: May 21, 2019, 11:10:32 AM »
The old version needs to use the library it came with and the new version needs to use the library it came with. So do not just override the existing library with the new one as the old server would likely stop working.
While testing I would recommend keeping the libraries for the new ODBC server in the install directory of the ODBC server and not in the /lib directory. Then you can set the LD_LIBRARY_PATH environment variable before running the new ODBC server to search in the new ODBC server install directory. After it launches you can then set the back to normal.
While testing I would recommend keeping the libraries for the new ODBC server in the install directory of the ODBC server and not in the /lib directory. Then you can set the LD_LIBRARY_PATH environment variable before running the new ODBC server to search in the new ODBC server install directory. After it launches you can then set the back to normal.
202
ODBC / Re: [PxPlus][ODBC Driver][PXPIO]File is busy
« on: May 09, 2019, 10:24:16 AM »
Antivirus software could be possibly doing a scan causing the file to be busy.
Backup software doing a backup could cause the file to be busy.
You may be able to split your query up until several smaller queries and if one get's an error retry it. This way it won't have to do the whole thing over again and even with the busy error it can get done. This assumes whatever is using the ODBC driver can be scripted. If not you can look into using the pxpsql command line program to do the query as this can easily be scripted. It also is generally much faster as it avoid some Microsoft ODBC overhead.
Backup software doing a backup could cause the file to be busy.
You may be able to split your query up until several smaller queries and if one get's an error retry it. This way it won't have to do the whole thing over again and even with the busy error it can get done. This assumes whatever is using the ODBC driver can be scripted. If not you can look into using the pxpsql command line program to do the query as this can easily be scripted. It also is generally much faster as it avoid some Microsoft ODBC overhead.
203
Programming / Re: [DDE] Problem (Excel)
« on: May 07, 2019, 03:58:37 PM »
Are you 100% sure that the version of Microsoft Office installed is 32-bit?
Usually anything installed in C:\Program Files\ is 64-bit and anything in C:\Program Files (x86)\ is 32-bit. If you have installed 32-bit office in C:\Program Files\ then you may want to reinstall it in C:\Program Files (x86)\. I would suggest the default install directory so it matches the other working machines. This will also help rule out a path issue.
Usually anything installed in C:\Program Files\ is 64-bit and anything in C:\Program Files (x86)\ is 32-bit. If you have installed 32-bit office in C:\Program Files\ then you may want to reinstall it in C:\Program Files (x86)\. I would suggest the default install directory so it matches the other working machines. This will also help rule out a path issue.
204
Programming / Re: [DDE] Problem (Excel)
« on: May 07, 2019, 09:03:42 AM »
Hi Thomas,
It looks like on the new machine the 64-bit version of Microsoft Office was installed. While on all of the other machines the 32-bit version of Office was installed.
I believe the default for Microsoft Office is still the 32-bit version as it is the most compatible with add-ons and other software. I don't know why the 64-bit version was installed on your new machine you may want to find out if it was done on purpose or by accident.
My guess is that the [DDE] interface to Excel only works with the 32-bit version of Microsoft Office. I would recommend uninstalling the 64-bit version of Office and installing the 32-bit version and see if that resolves the issue.
Also note that the [DDE] interface to Excel is an older legacy interface. We now recommend using the COM interface to Excel. In more recent versions of PxPlus we have provided an easy to use object (*obj/excel) built around the COM interface that makes working with Excel easy.
It looks like on the new machine the 64-bit version of Microsoft Office was installed. While on all of the other machines the 32-bit version of Office was installed.
I believe the default for Microsoft Office is still the 32-bit version as it is the most compatible with add-ons and other software. I don't know why the 64-bit version was installed on your new machine you may want to find out if it was done on purpose or by accident.
My guess is that the [DDE] interface to Excel only works with the 32-bit version of Microsoft Office. I would recommend uninstalling the 64-bit version of Office and installing the 32-bit version and see if that resolves the issue.
Also note that the [DDE] interface to Excel is an older legacy interface. We now recommend using the COM interface to Excel. In more recent versions of PxPlus we have provided an easy to use object (*obj/excel) built around the COM interface that makes working with Excel easy.
205
Language / Re: sub() function with negative occurance not always working as expected
« on: May 01, 2019, 12:15:50 PM »
We will fix the documentation for SUB() in a future release. Thanks for bringing this to our attention.
We can't change the way SUB() works as it would break existing code. You can however accomplish what you want fairly easily using POS()
We can't change the way SUB() works as it would break existing code. You can however accomplish what you want fairly easily using POS()
Code: [Select]
str$="#####.000"
search$="###"
replace$=",###"
startpos=POS(search$=str$,-1)
lensearch=LEN(search$)
str$=MID(str$,1,startpos-1)+replace$+MID(str$,startpos+lensearch)
206
Language / Re: web/ftp & websftp
« on: April 25, 2019, 02:55:01 PM »
You should be able to look at the value of the Result$ variable after the error to find out what file the error 12 was reported for.
207
Web Services / Re: *web/email not working with PxPlus Webserver
« on: April 25, 2019, 08:48:53 AM »
What user is the webserver process being run as? Does that user have the correct firewall settings?
208
Web Services / Re: *web/email not working with PxPlus Webserver
« on: April 22, 2019, 09:40:08 AM »
I would look at the documentation for *web/email (https://manual.pvxplus.com/?Web%20Utilities/Email%20Utility/Overview.htm) carefully and make sure you are calling it correctly. It is fairly common to get one of the arguments wrong and that can cause issues.
Another possibility is internet security or antivirus software blocking the process from connecting.
Another possibility is internet security or antivirus software blocking the process from connecting.
209
Web Services / Re: *web/email not working with PxPlus Webserver
« on: April 18, 2019, 01:42:09 PM »
Hi Ken,
If you are using PxPlus 2016 or newer you can try to use the *web/testemail utility.
CALL "*web/testemail;test_name",from$,smtp_server$,username$,password$,to$
This will allow you to do a very simple test of *web/email. If it works it will display the *web/email command it used. This helps make sure you are calling it correctly. If it doesn't work it lets you know that none of the extra options are to blame.
The difference between the two programs I believe is that *web/email is our full featured email utility while *web/mail is a older simple bare bones utility. It is possible that a difference in how they are implemented is why one works but one doesn't.
The *web/mail program has a 20 second timeout. While *web/email uses whatever timeout you specify. If not specified passed in as 0 then it defaults to 60 seconds. Are you passing in a value to *web/email less than 20 for timeout?
If you are using PxPlus 2016 or newer you can try to use the *web/testemail utility.
CALL "*web/testemail;test_name",from$,smtp_server$,username$,password$,to$
This will allow you to do a very simple test of *web/email. If it works it will display the *web/email command it used. This helps make sure you are calling it correctly. If it doesn't work it lets you know that none of the extra options are to blame.
The difference between the two programs I believe is that *web/email is our full featured email utility while *web/mail is a older simple bare bones utility. It is possible that a difference in how they are implemented is why one works but one doesn't.
The *web/mail program has a 20 second timeout. While *web/email uses whatever timeout you specify. If not specified passed in as 0 then it defaults to 60 seconds. Are you passing in a value to *web/email less than 20 for timeout?
210
Web Services / Re: using *web/email for smtp.office365.com
« on: April 04, 2019, 09:16:40 AM »
According to the documentation (https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3) it looks like smtp.office364.com requires TLS1.2 or above.
As you are using PxPlus 2014 (v12.5) if you are using a Windows PxPlus the version of OpenSSL used should support TLS1.2. If you are using a UNIX/Linux PxPlus then the openSSL version used is whatever comes with the OS and you will need to check to make sure it is at least 1.0.1.
Other things I would look for are if you need to change any settings for the mail account to allow 3rd party access to send emails. The docs above don't mention any setting but we have seen this for some mail services.
You may also want to make sure a firewall is not blocking port 587 on your network.
As you are using PxPlus 2014 (v12.5) if you are using a Windows PxPlus the version of OpenSSL used should support TLS1.2. If you are using a UNIX/Linux PxPlus then the openSSL version used is whatever comes with the OS and you will need to check to make sure it is at least 1.0.1.
Other things I would look for are if you need to change any settings for the mail account to allow 3rd party access to send emails. The docs above don't mention any setting but we have seen this for some mail services.
You may also want to make sure a firewall is not blocking port 587 on your network.