ODBC SETTINGS
hi,
I have package which communicates with oracle clients at the back end or we can say some how it needs to communicate with oracle 10g to retrive some data. I'm using thinapp and my package.ini file is in merged mode. The app works fine for the users who have admin rights. the user who does not have admin rights are having issues as the package can't communicate with the oracle clients..
i'm sure the error is some thing with respect to ODBC settings .i'm not sure how to approach.can u guys help me abt this this is important...
NAME OF THE APP IS BUSINESS OBJECTS XI 3.1
THANKS --USHA
I have package which communicates with oracle clients at the back end or we can say some how it needs to communicate with oracle 10g to retrive some data. I'm using thinapp and my package.ini file is in merged mode. The app works fine for the users who have admin rights. the user who does not have admin rights are having issues as the package can't communicate with the oracle clients..
i'm sure the error is some thing with respect to ODBC settings .i'm not sure how to approach.can u guys help me abt this this is important...
NAME OF THE APP IS BUSINESS OBJECTS XI 3.1
THANKS --USHA
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
WiseAppPackager
13 years ago
Business objects is such a peculiar application, normal users do need access rights on some of the folders in C:\Program Files\Business Objects.
Please refer the vendor installation help docs to know the folder names. Have you done that setting in your package?
Please refer the vendor installation help docs to know the folder names. Have you done that setting in your package?
Posted by:
anonymous_9363
13 years ago
As usual, ProcMon will show EXACTLY what access is being requested by the application. If it is ODBC, I'd bet that you have the Oracle DSN set to be a System DSN. That means that the user requires rights to HKEY_LOCAL_MACHINE\Software\ODBC. If you were to make it a User DSN, that would involve HKEY_CURRENT_USER\Software\ODBC where, of course, ordinary users will have sufficient rights.
If the issue is file/folder access, ProcMon will show that, too. You can then include either a permission-setting Custom Action (using SetACL/XCACLS/SecEdit/whatever) or, if you're a masochist, use the LockPermissions table.
If the issue is file/folder access, ProcMon will show that, too. You can then include either a permission-setting Custom Action (using SetACL/XCACLS/SecEdit/whatever) or, if you're a masochist, use the LockPermissions table.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
