Problem: Errors accessing JDBC Data Sources from SQL builders
You see an error message about "Database metadata generation on the server failed" in the "Problems" tab of Designer when you are using the database builders such as SQL Call. Or, you get an error message when trying to use the "Fetch Datasource Names" button from one of the SQL builders.
Background and solution:
When using the database builders, the builders will often have to access the running development server application in order to get database metadata to generate a schema. The reason for this is that the database connectivity is controlled by a Data Source on the application server. This server dependency is why it is necessary to have the development server running when you are using these builders.
These error messages indicate that an error occurred when trying to get metadata from the development server. This can be because the builder can't connect to the server (because it's not running or the URL is wrong), or it may be because of an error on the server, such as a Data Source not being available. If there's a problem connecting to the server, you may see a message about "connection refused." If you can connect to the server but still have an error, the first place to look is in the WEB-INF/logs/event.log file in the development server WAR. That's where exceptions that occur on the server are logged. Hopefully, the exceptions logged there will provide information to help determine the root cause of the problem.
Here are some of the forum postings that discuss this problem and how to fix it:
If you are using the WASCE deployment configuration you need to set up your datasource and then configure your web.xml and geronimo-web.xml entries. See the WASCE Deployment options page