TAS Not Accessible After UPD27 Deployment – "Value cannot be null" + Oracle & Assembly Errors

ollowing the deployment of IFS Application UPD27 on May 11, our Production Touch Apps Server (TAS) has become inaccessible. The landing page fails to load and displays the following error:

Server Error in '/' Application.
Value cannot be null.
Parameter name: key

This issue persists despite multiple recovery and reinstallation attempts.

Environment Details:

• IFS Application Version: UPD27
• TAS Version: 10.24.537.2
• Previous Working Version: UPD25 (Release 86)
• OS: Windows Server (IIS-hosted)
• No TAS included in UPD26 or UPD27

Symptoms & Observations:

• Web Error: Occurs immediately on accessing the TAS landing page.
• Stack Trace: Points to OracleInternal.ConnectionPool.PoolManager and AppManager.cs failing due to a null key.
• Installer Log: Shows successful deployment but ends with:

  ORA-01017: invalid username/password; logon denied
  System.ArgumentNullException: Value cannot be null. Parameter name: key
  

• TASTrace.log:
  • Frequent assembly resolution failures (e.g., Ifs.Cloud.Utility.resources, Ifs.Cloud.Push.resources)
  • PushClient creation fails due to missing Notification Hub parameters
  • Oracle errors: ORA-20110, ORA-20113, ORA-01031, ORA-06512
  • Authentication failures: OpenID token expiration, invalid credentials
  • Execution timeouts and stack
  • traces in ServerCommandCollection.cs and ProjectionFunction.cs
     

    Has anyone experienced a similar issue after UPD27 deployment or during TAS reinstallation?

  • What could be causing the Value cannot be null. Parameter name: key error?
  • Could this be related to Oracle schema inconsistencies, registry corruption, or PushClient misconfiguration?
  • Any known fixes for assembly resolution failures or PushClient setup?