Sequencing OBDC Entries
I have tried to sequence an application which is having ODBC entries(System DSN entries).
When I launch the application (login with the ID which have admin rights) able to see the ODBC entries, but when I login with standard user the entries are missing.
Can anyone suggest me to get the ODBC entries for standard user also.
Thanks in Advance.
Sushma
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
kkaminsk
16 years ago
Are you sure the DSNs are actually missing? I've seen issues if you are using Oracle 10 and your non-administrator users don't have the Create Global Objects right the connection will fail. Another thing might be that the user settings might need to be reset for the non administrator user if they aren't seeing the ODBC entry and the ODBC entry is in the sequence.
Posted by:
anonfoo
16 years ago
They should be there for all users if you used a system DSN. You can run regedit inside the bubble as a user and see if they show up under HKLM\Software\ODBC
I personally have found it more convienient (sp?) sticking DSN's in the OSD file. That way you can update them on the fly and you can be sure they're there. Give it a try... If its not SQL just create the dsn then export the key and insert appropriately like below.
<VIRTUALENV>
<REGISTRY>
<REGKEY HIVE="HKLM" KEY="Software\ODBC\ODBC.INI\<KEY_A>">
<REGVALUE REGTYPE="REG_SZ" NAME="Driver">"Driver"=%%windir%\\system32\\SQLSRV32.dll</REGVALUE>
<REGVALUE REGTYPE="REG_SZ" NAME="Description"><DESCRIPTION></REGVALUE>
<REGVALUE REGTYPE="REG_SZ" NAME="Server"><SERVER></REGVALUE>
<REGVALUE REGTYPE="REG_SZ" NAME="Database"><DATABASE></REGVALUE>
</REGKEY>
<REGKEY HIVE="HKCU" KEY="Software\ODBC\ODBC.INI\ODBC Data Sources">
<REGVALUE REGTYPE="REG_SZ" NAME="<KEY_A>">SQL Server</REGVALUE>
</REGKEY>
</REGISTRY>
</VIRTUALENV>
SQL2005 = <REGVALUE REGTYPE="REG_SZ" NAME="Driver">"Driver"=%%windir%\\system32\\sqlncli.dll</REGVALUE>
SQL2000 = <REGVALUE REGTYPE="REG_SZ" NAME="Driver">"Driver"=%%windir%\\system32\\SQLSRV32.dll</REGVALUE>
WINDOWS AUTH = <REGVALUE REGTYPE="REG_SZ" NAME="Trusted_Connection">Yes</REGVALUE>
I personally have found it more convienient (sp?) sticking DSN's in the OSD file. That way you can update them on the fly and you can be sure they're there. Give it a try... If its not SQL just create the dsn then export the key and insert appropriately like below.
<VIRTUALENV>
<REGISTRY>
<REGKEY HIVE="HKLM" KEY="Software\ODBC\ODBC.INI\<KEY_A>">
<REGVALUE REGTYPE="REG_SZ" NAME="Driver">"Driver"=%%windir%\\system32\\SQLSRV32.dll</REGVALUE>
<REGVALUE REGTYPE="REG_SZ" NAME="Description"><DESCRIPTION></REGVALUE>
<REGVALUE REGTYPE="REG_SZ" NAME="Server"><SERVER></REGVALUE>
<REGVALUE REGTYPE="REG_SZ" NAME="Database"><DATABASE></REGVALUE>
</REGKEY>
<REGKEY HIVE="HKCU" KEY="Software\ODBC\ODBC.INI\ODBC Data Sources">
<REGVALUE REGTYPE="REG_SZ" NAME="<KEY_A>">SQL Server</REGVALUE>
</REGKEY>
</REGISTRY>
</VIRTUALENV>
SQL2005 = <REGVALUE REGTYPE="REG_SZ" NAME="Driver">"Driver"=%%windir%\\system32\\sqlncli.dll</REGVALUE>
SQL2000 = <REGVALUE REGTYPE="REG_SZ" NAME="Driver">"Driver"=%%windir%\\system32\\SQLSRV32.dll</REGVALUE>
WINDOWS AUTH = <REGVALUE REGTYPE="REG_SZ" NAME="Trusted_Connection">Yes</REGVALUE>
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.