Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Reports: run for Citrix users; fail for network users

Status
Not open for further replies.

ajacode

Technical User
Aug 21, 2002
66
US
I have a connectivity problem with:

Microsoft Access Data Project App (ADP file each user has own file on their Cirix Window desktop or their lan workstation desktop)

Calling
crystal report 8.5

Using File DSN to access SQL Server 7.0

Report files located on:
File Server = NT 4.0

Citrix Server Services on NT 4.0 (seperate Box)


USERS:
Citrix Meta Frame
Windows 2000 Desktop

I originally developed the app using Cirtix to tunnel into customer site and build the reports.

The data connection is not a trusted connection but a SQL Server internal user/password


Here's the problem.

All the Citrix Server Users can open the Application and run the reports fine. Once they pick and run a report, they get the report parameter input scrren adn choose their parameters then choose print; and then they get the login challenge dialog and then the report runs.


However regular network users with the same ADP application on their desktop, can run the app, do all the functions except when it comes to running the reports.

They can see the report list (shich are in a table on SQL Server so we know they can get to the data..)

But when a regualr desktop user launches a report they get the same parameter window as the Citrix users but when they click "print" the password dialog box comes up and after the user enters the proper User/password the dialog login dialog returns and ignores the inputs. This does NOT happen to the Cirtix users.

Originally, the reports were developed with the file DSN to avoid having to create a system dsn on each users box.

The file was referenced using UNC //fileserver/reports/flashodbc.dsn not a mapped drive method to avoid a letter- mapping conflict.

I don't think it is a permissions issue for the Desktop users because the report input parameter dialog is always launched and not challenged. I think if the Deskto users did not have permissions to the //fileserver/reports folder they would not even get this far; and the file DSN is in this folder.

Anyone have any ideas?

Thanks

AJ
 
First thing I would do is certainly look at moving away form a file dsn. These are nice but you are adding a layer. Stick with System DSNs

Also, I suspect this is a rights issue. The REPORT is going to prompt for the database login when it can not reach the one specified in the report.

The fact that when the user enters the log in, the dialog returns is proof that the user request can not be passed successfully to the source.

Make sure you check the folder location of the file.dsn to make sure all users have FULL access to the location.

Citix users will be accessing the location locally from the server itself in their Citrix registry space. N/W users have to come in and need the rights.

UNC path require full network access and permissions. You may try mapping the drive, but you may need to update the report for this (another reason a System DSN is nice).



Cheers,

SurfingGecko
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top