FDA URL Changes From HTTP To HTTPS - IIS - E2B Generation issue after importing existing Self-Signed Certificate (Doc ID 2660394.1)

Last updated on JULY 13, 2023

Applies to:

Symptoms

FDA URL Changes From HTTP To HTTPS - IIS settings - E2B Generation issue after importing existing Self-Signed Certificate

The solution below is working perfectly fine when a new certificate is created by “Create Self-Signed Certificate” ; however it doesn't work if an existing certificate is imported.

Setting up https binding in IIS
a. In IIS select the top level website, home.
b. In Feature View, under IIS find “Server Certificates” and open it.
c. On the right select “Create Self-Signed Certificate” (if you have a certificate to use you can import it here also)
d. Give the self-sign certificate a name, then click ok to close the dialog.
e. On the left, navigate to the website under the Sites folder and select 'Default web Site'
f. On the right select “Bindings…”
g. Click on Add, select type https, leave the IP Address and “All Unassigned” and Port as <xxxx>.
h. On the same dialog add the SSL Certificate. Then click ok to save.
i. On the site binding dialog you should see the line with type https, Port <xxxx> and IP Address as *
j. Close the site binding dialog.
k. Reset IIS for the setting to be applied.
l. Stop Argus Interchange Service
m. Go to Task Manager and make sure all the esmproc.exe processes and E2breceive.exe processes are gone
n. If there are any hung esmproc.exe processes or e2breceive.exe processes, go ahead and kill them
o. Start Argus Interchange Service
p. Verify that Argus Interchange Service is creating the XML files with out any error


Error message logged in the log file:
Unable to encode XML string due to following reason

Changes

 FDA URL Changes From HTTP To HTTPS - Hence needs changes in IIS.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.