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!

Citrix Metaframe XPs, Windows 2000

Status
Not open for further replies.

yert33

Programmer
Feb 19, 2002
255
US
Citrix Metaframe XPs, Windows 2000 Server, SP3.........

Visual FoxPro program connects to a Notes database via a system DSN defined in ODBC manager. Works fine if the Win2K user is a Domain Admin, but not if they are a Domain User.

How can I give access to the ODBC DSN to Domain Users?

I've tried using remon,exe and filemon.exe, but i'm not sure if I know what they're telling me.

Thanks in advance!
 
I haven't tried anything like this, but couldn't you simply install a client (in change user /install mode), set that up to use the system DSN, then publish it?

Hope this works CitrixEngineer@yahoo.co.uk
 
Some more background:
The VFP exe is called from our accounting system client and is passed values from the customer maintenance screen. The accounting system does not behave very well as a published app (we tried for a few months) and because of this we run our Citrix sessions as desktops.

We have perused the group policies for anything that would seem to be a clue...nada.

By running regmon.exe I do see some differences when a Domain User runs the exe vs. a Domain Admin: the user encounters various 'ACCDENIED' responses that the admin does not. But there are a lot and I'm not sure which ones, if any, are germaine. When I looked at the registry 'folders' where these differences occur I don't see any security blocks for the Domain Users. Still chasing this goose, though.

I'm not sure what you mean exactly when you suggest 'install a client'. Do you mean install a Citrix client on the terminal server?

Thanks for replying!
 
The client I was referring to was for the Foxpro database - not having used Foxpro, I assumed that it worked like most databases in that there is a server bit (the database) and a "front-end" (the client). Most client type apps I've installed work after some tweaking - usually of *.ini files that still seem to abound with the more "out-there" apps.

I know there are issues with Foxpro, because I've seen a couple on this forum. However, if you're getting "access denied" messages from regmon, it suggests that the app ,ay not have been installed in change user /install mode.

Access denied messages from Filemon are probably more helpful to start with, as Registry entries can be anyone's guess, unless you run Regmon as you install the product. If it's not terminal server aware, then this may take some time...


Hope this is helpful CitrixEngineer@yahoo.co.uk
 
Here's the solution I found:

The problem is with registry key permissions. I used regedt32.exe to give the group Domain Users access to the HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\(system dsn name here) key. I selected all Allow for all permissions and appied to 'This key only'.

whew... this took me 7 hours to crack....
Thanks CitrixEngineer for your reply.
 
Hmm. Out-there apps would seem to include the ODBC drivers then... [ponder]

Glad you sorted it out! CitrixEngineer@yahoo.co.uk
 
Citrix Engineer:

You know, I bet my problem may have stemmed from not being in change user /install mode. I really didn't even think about that. I just installed the ODBC driver straight up.

How do you enter change user /install mode?

Thanks,
Trey
 
Simply open a cmd prompt and type change user /install :)

When you've finished, either reboot, or type change user /execute as per the programs requirements.

Alternatively, any programs installed via Add/Remove Programs in Control Panel will automatically be installed to all users (ie in install mode).

Note: *.ini files for many older apps can still cause issues, though - you may find for some apps that a copy needs to be placed in the users' home directories, modified for user-specific parameters. This should not be the case for ODBC drivers, if all you're doing is pointing it to a system DSN.

Hope this is helpful CitrixEngineer@yahoo.co.uk
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top