• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 821
  • Last Modified:

ODBC Driver security in Windows Server 2003

I have a brand new Server 2003 / Citrix Metaframe box.  It has an ODBC driver for Providex (Mas200).  An administrator can run an ODBC query via Excel or Crystal Reports but an ordinary user cannot.  

They get error:
[odbc driver manager] Data source name not found and no default driver specified.

A file DSN exists for SOTAMAS90 but the fields are empty- when I am logged in as admin the fields are filled in correctly.  This works for more that one administrative user so it appears to be a Server 2003 security issue...  This same setup works fine for the old Windows 2000 server.  Any advice?  

Thanks in advance.
0
jcneil4
Asked:
jcneil4
  • 3
  • 2
1 Solution
 
CarlWarnerCommented:
Can you make it a System DSN instead of a File DSN?
0
 
jcneil4Author Commented:
CarlWarner- That worked perfectly.  Thanks!  Should I delete the file DSN or just leave it be?
0
 
CarlWarnerCommented:
I believe you can delete it.  You don't need redundancy in this case.
0
 
jcneil4Author Commented:
Great Thanks for the advice.
0
 
CarlWarnerCommented:
You're certainly welcome.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now