Monday, 14 December 2020

Oracle Apex Form Download File link error - Server sent an invalid response.

I had the following problem reported by a user of one of my Apex applications when they were trying to download an attachment that had been added to a record as a clob using the built in functionality for Apex clob form fields. The error message wasn't very informative and gave "server name sent an invalid response."

The issue seemed to be that the file name the user was adding included commas in it which is obviously allowed in Windows but maybe not in other system processes. Once I removed the commas the download worked fine again.

In order to remove unwanted characters in file names I added the following code to the insert trigger on the Attachment table to automatically update them

-- Check and update Filename remove unwanted characters 

--*****************************************************************************

       :NEW.FILE_NAME := REPLACE ( REPLACE ( REPLACE ( :NEW.cat_FILE_NAME, CHR(44), NULL ), CHR(59), NULL ), CHR(39), NULL ) ;   

Monday, 7 December 2020

SecureDoc Password Different Windows 10 After Change

 SecureDoc is used to protect laptops so that the disc is encrypted before logging into the operating system. I have Windows 10 on my laptop and normally it's a seamless process to log in where you enter your credentials to SecureDoc on startup and this automatically logs you in to Windows.

However there seems to be an issue when Windows requires a password change and SecureDoc doesn't seem to be able to cope with this so you end up with the situation of needing a different password for SecureDoc to the one used for Windows and need to enter 2 different passwords.

The SecureDoc website is useless for finding information about this and doesn't have any support info - I guess because they expect support to be done by company helpdesks.

The answer seems to be to log in to the SecureDoc control center on your laptop once it has booted into the Operating System. Select the menu option to Communicate with Server and this appears to resync the password between Windows and SecureDoc. I don't know if the same process works for MacOS but it might be worth a try if you find that your password no longer matches SecureDoc.