J
jo
I have a few crystal reports (XI) that uses JDBC to connect to MS SQL
Server. The JDBC Driver is JTDS 1.1. Now I am trying to update the data
source definition to include JNDI name so it can be more portable. The
trouble is I can't update it.
Here's what I've tried on existing working reports:
- Go to "Set Datasource Location" dialog, expand current data source
properties, add JNDI connection name. Crystal now pops up a dialog box,
asking me to confirm connection info. So I put in user ID and Password.
Clicking "Finish" and Crystal pops up a message saying "Logon failed.
Details: SQL Exception: [SQL State:] 08501 [Error Message:] Network
error IOException: Connection refused: connect". Then the same
connection fonfirmation dialog come up again as if i typed in wrong
user name and password.
- The next thing I tried (since I can't manually add JNDI name) is to
replace existing datasource with another one. Again, I go to "Set
Datasource Location". I've already defined another JDBC connection with
JNDI name in it. now selecting existing connection in the tree at the
top and select the new connection in the tree at the bottom, click
"Update". Now connection confirmation dialog pops up. After entering
user id and password, I click Finish. Then Crystal says
- "Data Object cannot be opened/accessed."
- "Database Connector Error: 'Unexpected error'"
- "Data Object cannot be opened/accessed."
- "Database Connector Error: 'Unexpected error'"
- "Some tables could not be replaced, as no match was found in the
new data source. Please specify the table required for any unmodified
tables."
Some more information regarding existing reports. When I created the
reports, Crystal complains about not able to find the tables and offer
me to remove the related fields from the report. I clicked "No" and the
reports still runs perfectly fine.
There isn't much I can do after this. So I look up on the web, I think
it may have to do with the not so well implemented "verify database"
functionality, but I have no way to prove or solve it.
Can anyone help me on this? The database is the same, so theoretically
there shouldn't be any problem updating the datasource defintion,
especially when the datasource is the same as before. And adding JNDI
name to the report shouldn't be a problem either because it won't get
use until a Java app try to run it.
Any suggestions?
Thanks,
Jo
Server. The JDBC Driver is JTDS 1.1. Now I am trying to update the data
source definition to include JNDI name so it can be more portable. The
trouble is I can't update it.
Here's what I've tried on existing working reports:
- Go to "Set Datasource Location" dialog, expand current data source
properties, add JNDI connection name. Crystal now pops up a dialog box,
asking me to confirm connection info. So I put in user ID and Password.
Clicking "Finish" and Crystal pops up a message saying "Logon failed.
Details: SQL Exception: [SQL State:] 08501 [Error Message:] Network
error IOException: Connection refused: connect". Then the same
connection fonfirmation dialog come up again as if i typed in wrong
user name and password.
- The next thing I tried (since I can't manually add JNDI name) is to
replace existing datasource with another one. Again, I go to "Set
Datasource Location". I've already defined another JDBC connection with
JNDI name in it. now selecting existing connection in the tree at the
top and select the new connection in the tree at the bottom, click
"Update". Now connection confirmation dialog pops up. After entering
user id and password, I click Finish. Then Crystal says
- "Data Object cannot be opened/accessed."
- "Database Connector Error: 'Unexpected error'"
- "Data Object cannot be opened/accessed."
- "Database Connector Error: 'Unexpected error'"
- "Some tables could not be replaced, as no match was found in the
new data source. Please specify the table required for any unmodified
tables."
Some more information regarding existing reports. When I created the
reports, Crystal complains about not able to find the tables and offer
me to remove the related fields from the report. I clicked "No" and the
reports still runs perfectly fine.
There isn't much I can do after this. So I look up on the web, I think
it may have to do with the not so well implemented "verify database"
functionality, but I have no way to prove or solve it.
Can anyone help me on this? The database is the same, so theoretically
there shouldn't be any problem updating the datasource defintion,
especially when the datasource is the same as before. And adding JNDI
name to the report shouldn't be a problem either because it won't get
use until a Java app try to run it.
Any suggestions?
Thanks,
Jo