When trying to do a publish with the TDM Portal, I am receiving the following error message:
Publish failed for job xxxx, Call to ConnectionManagerService failed: : HttpClientErrorException: 404 Not Found
Error message = Call to ConnectionManagerService failed with error: Connection profile not found.;
Error detail = Connection profile was not found or not shared or is not compatible. Oracle profiles must use an EZConnect String and other profiles must be DSN-Less.
The same publish through Datamaker works and I have verified that the connection to the Portal is working.
Jobs are successful when I submit them as an administrator.
In order to identify the root cause, you will need to enable debugging in the Portal, recreate the issue, and then analyze the logs (specifically TDMConnectionProfileManager.log).
Here are directions on how to enable debugging: https://knowledge.broadcom.com/external/article?articleId=9851
There are a few possible causes for this error message:
Here are several possible resolutions based on the possible causes listed above:
User not linked to connection profile:
Connection profile has same DB and schema as Datamaker:
Unable to find connection profile:
General Connection Configuration:
Ensure the Connection profile is configured as DNS-Less ODBC.
No conflicting Connection Profile in DataMaker and Portal:
If the user trying to access a DNS-Less connection profile in Portal has created an ODBC connection profile with same name and same data source, it may have issues mapping to the right one when used in Portal. To resolve this, first, check the connection profile in the repository with a particular name (prof_name) in "gtrep_profile" table and delete the ODBC one that is conflicting. Instead of each user creating their own profile for the same datasource, the connection profile can be shared at the User Group level to make it available for all members of that group.
More specific error message:
In TDM 4.1+ we have fixed the 404 error message with a more instructive message:
Connection profile was not found or not shared or is not compatible. Oracle profiles must use an EZConnect String and other profiles must be DSN-Less.
If you experience any further issues, please open a support case by going to https://support.broadcom.com