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

ThinApp Applications only work for Domain Admin

We thinapp'd an application. It works fine if user ID is a domain Admin. Does not work for standard or power users. The application requires an ODBC connection to SQL Server. Error message comes back that "SQL Server cannot be found or access is denied." We are able to browse the the SQL Server so we think this is a permission error.

Using Thinapp v4.7 and VMWare View 5.0

Does anyone have any insight on this?
0
SullivanMIS
Asked:
SullivanMIS
  • 3
  • 2
1 Solution
 
Ayman BakrSenior ConsultantCommented:
Was the ODBC connection created using User DSN?

If yes try creating it through System DSN.

Otherwise try adding the domain users group in the security of your DB on SQL. You might want to consult the application vendor to understand what level of permissions you should set for the domain users.
0
 
SullivanMISAuthor Commented:
The ODBC was created using System DSN.

We tried adding the domain users group in the security of the SQL DB and we continue to get the same error.

I have attached the error message we get.
ThinAppError.jpg
0
 
Ayman BakrSenior ConsultantCommented:
At this moment I am suspecting that it is a permission issue on the folderof the application. The reason I am saying so is that the app is returning an Object variable....not set error. This error occurs when either you attempt programatically use an object that is not set yet or is set to nothing or when the app tries to access a .dll file to create the object when it is not able to, because the .dll file doesn't exist.

Ofcourse the latter is also true when you don't have sufficient permissions to the folders or subfolders of the app where the DLL files exist. Add your domain users group to the security of the app folder (I guess it is Time and Attendance), give them the required permissions and don't forget to propagate the permissions to all the subfolders. Do the same in the registry key of the app.
0
 
SullivanMISAuthor Commented:
We resolved this issue by creating the ODBC connection using System DSN to our base image and then running the thinapp package as a full install instead of streaming.
0
 
SullivanMISAuthor Commented:
The expert comment was a good suggestion however it did not resolve the issue. The solution we came up with did resolve this issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

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