Though I have not seen this, some thing is striking for the issue you are facing.
Check this out in KB#114890 (https://communities.informatica.com/infakb/faq/4/Pages/114890.aspx)
Maximum Execution Pool Size (mandatory)
If profiling is RDBMS sources, then this value can be set high based on the number of concurrent connections the RDBMS can handle.If profiling is flat file, then this value should be set based on the number of cores the Data Service machine has. 1.5X - 2X is reasonable.
Maximum DB Connections (default: 5)
The number of connections to the RDBMS sources per profiling job up to the Maximum Execution Pool Size.
The reasons are: Profiling all rows, and java.util.concurrent.ExecutionException
Kindly pardon if the solution is wrong, as the thought behind is to help you!
No luck so far, thank you for the suggestions. Support also sent me this:
This error occurs when the SQL Server database requires more than 15 seconds to respond to the connect call made by PowerCenter.
By default, PowerCenter server waits for 15 seconds for the connect call to succeed and then it fails with this error. This issue may be intermittent and may not occur at all times.
To modify this behavior and to avoid the database timeout, set the PowerCenter Integration Service parameter MSSQLInitTimeout
to nnumber of timeout seconds.
A minimum value of 60 seconds is recommended. Note, this value may change depending on the nature of the issue. Y
ou can increase the value until the error no longer occurs.
Evidently, the same setting can be made on the Data Integration Service. Unfortunately, that didn't correct the issue either.
Did you check for this:
SQL Server database name can be case-sensitive. Check for the SQL Server Collation from the SQL Server client tool. If the database is case-sensitive, use correct case when mentioning the database name.
The connectivity is there, that's been proven. The problem is the seemingly random "login timeout" error.
Thanks for the message, though!
As it turns out, the connectivity was in place, but the speed was just variable enough to be a prblem.
Thanks for all the messages, folks.
I am getting the same issue with Data Quality 9.61 HF1. What exactly did you do to fix it?
Can you please expand on "but the speed was just variable enough to be problem"?
It was the speed of our network between the app and repository servers, so not an Informatica issue.s
Thanks for your reply, Briggs.