Consider posting the full capture log here (or the lines that get appended when capture tries to begin), or at least selected columns/rows that get added in asn.ibmsnp_captrace when capture tries to begin from the replication-centre. If the database-name is mangled in the log file and ibmsnap_captrace then all bets are off as to the real cause.
Secondly, suggest you manually start asncap, taking care to specify all the arguments correctly on the command-line, simply to compare the behaviour and results. By doing it that way, you are temporarily eliminating any differences that might be caused by the GUI using unintended startup arguments for capture, due to misconfiguration.
------------------------------
Mike O'Reilly
------------------------------