Error after database upgrade, Job Server Status error: "The underlying connection was closed: An unexpected error occurred on a receive."

I would suggest to recreate the SQL server connection for that job server via job service configurator.

The issue is solved by renewing the certificate of port 1880: a .Net HTTP listener embedded in the One Identity Manager Service.

Hi, Hans, we're actually facing the same issue. Could you please explain how you did change this certificate? We're unable to know which cerficate the .net http listener currently uses. 

Thanks!

Make sure you have a valid certificate installed in Windows (Job Server).

There are 2 sides that need to be checked/set. You can choose to use SSL or not. For test purposes you can disable SSL to check if it is not another problem. 
- Server side: running via service "One Identity Manager Service"
  The Identity Manager job service uses System.Net.HttpListener for the web interface on port 1880.
- start: \Program Files\One Identity\One Identity Manager\JobServiceConfigurator.exe
  this will create/update "\Program Files\One Identity\One Identity Manager\JobServiceConfigurator.exe.config"
  path: Configuration > Use SSL: check!
  restart the service "One Identity Manager Service"

- Client: JobQueueInfo.Net
  The client setup can be found in the Designer
- Designer > Base Data
  Installation | Job Server
  New window appears: "Job Server editor", select your Job Servers
  Look below and select: One Identity Manager Service configuration > Configuration > Use SSL: check!
  Restart JobQueueInfo.Net

Link the new Windows certificate with the IP port in netsh (Job Server)
- show current settings
  netsh http show sslcert ipport=0.0.0.0:1880
  note: Application ID

SSL Certificate bindings:
-------------------------
IP:port : 0.0.0.0:1880
Certificate Hash : fc39077ea77a693534df63bb6c1711b1271570bc
Application ID : {3b5779ae-209e-4749-9cf4-a58a45779392}
Certificate Store Name : (null)
Verify Client Certificate Revocation : Enabled
Verify Revocation Using Cached Client Certificate Only : Disabled
Usage Check : Enabled
Revocation Freshness Time : 0
URL Retrieval Timeout : 0
Ctl Identifier : (null)
Ctl Store Name : (null)
DS Mapper Usage : Disabled
Negotiate Client Certificate : Disabled

- Delete the current SSL certificate bound to port 1880
netsh http delete sslcert ipport=0.0.0.0:1880

- Bind an SSL certificate to a port number
  netsh add sslcert
  - What 'appid' should I use with netsh.exe?
    stackoverflow.com/.../what-appid-should-i-use-with-netsh-exe
  - Find the GUIDs of SharePoint Web Application, Site Collection, Site, List, View and Columns
    www.sharepointdiary.com/.../find-guid-of-webapp-site-collection-web-list-view-column.html
  - You can generate a unique GUID in PowerShell: [Guid]::NewGuid().Guid
netsh http add sslcert ipport=0.0.0.0:1880 certhash=b877aa44b6fbca7596ba27ef80a7c1f310dce939 appid={6ea5e68b-77b0-4589-851b-552aca0f9a3d}

certhash = specify the thumbprint of the certificate (note: without spaces and delete the first character - check the thumbprint!
appid = the old Application ID or generate a new one.

Usefull links?
- Easy Way To Retrieve Certificate Thumbprint Using PowerShell
  blog.rmilne.ca/.../
- Installing and Configuring the One Identity Manager Service
  support.oneidentity.com/.../11

Use these troubleshooting tips to address errors or issues that you may encounter while upgrading your database.

Also review the related links to learn about changes that affect this release, which may be related to errors you receive, and to see how to rerun the upgrade after you resolve errors.

About Starting Oracle Database in Upgrade Mode
When you start Oracle Database in upgrade mode, you can only run queries on fixed views. If you attempt to run other views or PL/SQL, then you receive errors.
Running DBUA with Different ORACLE_HOME Owner
Review this topic if your Oracle Database homes are owned by different operating system user accounts, or you encounter an upgrade.xml not found error.
Invalid Object Warnings and DBA Registry Errors
Before you start your upgrade, Oracle strongly recommends that you run the preupgrade information tool (preupgrd.jar).
Invalid Objects and Premature Use of Postupgrade Tool
Never run the postupgrade status tool for the new Oracle Database release (utlusts.sql) until after you complete the upgrade.
Resolving Oracle Database Upgrade Script Termination Errors
Review this section if you encounter ORA-00942, ORA-00904, or ORA-01722 errors.
Troubleshooting Causes of Resource Limits Errors while Upgrading Oracle Database
Review this section if you encounter ORA-01650, ORA-01651, ORA-01652, ORA-01653, ORA-01654, ORA-01655, ORA-0431, ORA-01562, ORA-19815, or other errors that suggest resource limit errors.
Resolving SQL*Plus Edition Session Startup Error for Oracle Database
Use this section to understand and resolve SP2–1540: "Oracle Database cannot startup in an Edition session."
Error ORA-00020 Maximum Number of Processes Exceeded When Running utlrp.sql
This error may indicate that your Oracle configuration does not have sufficient number of processes available for the recompile.
Fixing ORA-28365: Wallet Is Not Open Error
If you use Oracle wallet with Transparent Data Encryption (TDE), and you use Database Upgrade Assistant (DBUA) to upgrade the database, then you can encounter an ORA-28365 "wallet is not open" error.
Resolving issues with view CDB_JAVA_POLICY
If the view CDB_JAVA_POLICY becomes invalid, then use this procedure.
Continuing Upgrades After Server Restarts (ADVM/ACFS Driver Error)
On Windows platforms, an error may occur related to ADVM or ACFS drivers if a server restarts during an upgrade.
Component Status and Upgrades
Component status settings are affected both by the components that you previously installed, and by the support of those components for upgrades.
Standard Edition Starter Database and Components with Status OPTION OFF
Starting in Oracle Database 18c (18.1), all OPTION OFF components are upgraded to the new release, but these options are disabled for Oracle Database Standard Edition (SE) remain OPTION OFF.
Adjusting Oracle ASM Password File Location After Upgrade
You must create a new password file for Oracle ASM after an Oracle Grid Infrastructure upgrade.
Fixing "Warning XDB Now Invalid" Errors with Pluggable Database Upgrades
Review this topic if you encounter "Warning: XDB now invalid, invalid objects found” errors when upgrading pluggable databases (PDBs).
Fixing ORA-27248: sys.dra_reevaluate_open_failures is running
Use this procedure to identify DRA_REEVALUATE_OPEN_FAILURES jobs that block upgrades.
Fixing Failed Upgrades Where Only Datapatch Fails
If only datapatch fails during an upgrade, then rerun datapatch directly.

This may help you,

Rachel Gomez