Designer Cannot Connect To The Database After An Install and Error "Workflow history reporting activation check has failed' Occurs
Last updated on APRIL 13, 2018
Applies to:
Oracle WebCenter Forms Recognition - Version 11.1.1.8.0 and laterInformation in this document applies to any platform.
Symptoms
After a new WebCenter Forms Recognition (WFR) 11.1.1.8.0 installation, the machine is configured to connect to an existing database schema. When attempting to open Designer and create a new database job in the "Settings" window the following error messages are returned:
Designer cannot instantiate workflow history controller. Please check if your database connection configured correctly.
Workflow history reporting activation check has failed.
Workflow history reporting activation check has failed.
and
Run-time error '-2147467259 (80004005)':
Can't instantiate Batch controller ---> Initialization failed ---> The underlying provider failed on Open. ---> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provder : Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Can't instantiate Batch controller ---> Initialization failed ---> The underlying provider failed on Open. ---> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provder : Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Changes
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms