Where should data for reports reside?

[Seabz420]

The data for our reports are held in one access file that resides on another server. From my workstation, running XP and CR Advanced Developer 10, I can open and run the reports. When I add the reports to the CMS, they add just fine. If I try to preview the reports through the CMS, I run into a logon screen. The Database Name is pointing to the location of the database on the other server but when I enter the user ID and password, the screen doesn't advance. Is there something I'm overlooking? I've setup the ODBC connection for Microsoft Access and tried to add the id and password there, but then I get a screen of "invalid credentials". Ideas? Thanks!

 

[Turkbear]

Hi,
Be sure the pageserver, at least, service is running under a domain account that has rights to the other server..

( The report job server shoud use it as well, for scheduled reports)

 

[Seabz420]

I've done this with no luck. How can I test my ODBC connection to know it's working? Also, when I try to open the access DB (located on server 1 - win nt 4.0) from server 2 (win server 2003), I get a message in Access that it can't open the DB because it's located outside the Intranet or it's on an untrusted site (both servers are on the same domain and can access each other just fine). Could this be the issue?

 

[Seabz420]

Here's a bit more info. From my computer, running Win XP and CR 10 AD, I have the proper ODBC connection setup (using the access driver) and I can open the reports and run them just fine. (there is no username or password). On the server running CE 10, I have setup the exact same ODBC connection. When I open the CMC and try to preview my report, I am taken to a logon screen. (I have used a system admin password for the page server, job server and web servers.) Since there is no user name or password used to access the database, I'm not sure what to use!

 

[Turkbear]

Hi,
have you tested the ODBC connection on the CE 10 server?

The prompting for username/password can happen if the Report cannot communicate with the datasource..

The Sysadmin user on the CE10 server may not have rights to the server that houses the database - that's why a domain user usually needs to be set up ( or grant access rights specicically to the user running the pageserver,
etc.)

 

[lyanch]

You need to uncheck "prompt user for password" on the database tab when you set up the report.

Lisa

 

[Seabz420]

How can I test the datasource? Without installing CR 10 on the server and checking....again, I'm new with this. Quite a while ago I used an app that tested this but for the life of me I can't remember what...and googleing doesn't seem return anything relavent.

 

[Turkbear]

Hi,
In the ODBC configuration applet, there is an option to test a DSN after it is created..At least for file system ones ( in W2k, XP and most other versions)
..If it works, then the problem is elsewhere..

 

[Seabz420]

I've been doing some reading and have come across this a few times but in my ODBC Data Source Administrator, the test option is no-where to be found. Could Win 2003 server be an exception?

 

[Turkbear]

Could be, but it would be strange..Check its help files for ODBC

In XP it is under Administrative tools..Data Sources(ODBC) and I cannot create a File system DSN without testing..For System DSNs I have a button on the configuration tab that says 'test Connection'

 

[Seabz420]

I think I know why you are assuming there is the test connection tab. The drive I'm using for the ODBC connection is the Microsoft Access Driver. (since the database I'm running reports from is and Access DB). If I setup a connect to an SQL database then I'm given the test option, when I setup and Access connection, no test option is given.