Crystal Reports 2020 connection issues

[Rene18]

My agency purchased a new upgrade license for the new SAP Crystal Reports 2020, and it was working perfectly fine up until a few weeks ago when I tried to modify a crystal report. I am currently running Windows 11 Enterprise with SAP Crystal Reports 2020 Support Pack 4 Version: 14.3.4.4773. I'm attempting to connect to an Oracle Database with Oracle Database 19c (19.3) for Microsoft Windows x64 (64-bit). The issue I keep running into is the error below:

When connecting to the database in crystal reports I use the OLE DB (ADO) connection -> then click on OLE DB Provider for Microsoft Directory Services -> enter the Data Source, User ID, and Password.

Do you have any recommendation that I can try and fix the connection issue that I am running into? Any assistance would be appreciated.

[JohnClark]

Did you try looking up the Database Vendor Code? This looks more like a problem with your database to me. Looking up the vendor code or sending it to you DBA should be helpful.

[DonWilliams]

As John suggested it could be your DB Client used, I've never used the MS Oracle Client, it has issue with more than one Table. Always use CR's Native Oracle connection or use Oracles Client.

The real question is What did you change in the report that caused this error?

[AA_SOI]

Try to install the Oracle Client (64bit option for CR 2020). Configure the Net Manager to connect to the Oracle database. Contacting your database admin or IT department might be necessary for the connection details.

Add a new Oracle Client connection by using the Edit menu, Create.

Add a new connection in CR from the Oracle Database option instead of the OLE DB (DAO).
Enter the Service Name [from the Oracle Client setup], userID and password.
The next time you connect, it will just ask for the password and autofill the userID.

Depending on your workstation's security setup, a call/ticket to your IT department may also be necessary to setup the connection(s) [due to the need for admin privileges].

Sidenote:
I have similar errors now when trying to use the Excel ODBC (DAO) connection.
I have [well, had...] a report that pulls data out and I would export it into an excel file that has been setup as an ODBC repository [basic CR 2016 export to ODBC]. Then, I load a second report and use that ODBC excel as a secondary data set [due to how the DB is configured].
This method broke after installing CR 2020. I have not found a solution yet.

- However, I have created a new connection using ODBC (RDO) to an excel file. This allows me to pull data from the Excel, but I still need to figure out how to push new data to the excel. Either updating or overwriting with current info, if possible. I'm not sure how to do that yet and might need to learn some additional SQL to see if this will even work.