Belazir
asked on
"Class not registered" on ADO Recordset.Open
Odd one, this. I have a VB EXE using ADODB, in which I am creating and opening a Recordset. It is deployed in a Terminal Services environment. My admin users can run the EXE no problem, but my non-admin users cannot, getting a "Class not registered" error on the Recordset.Open method.
That two users on the same machine accessing the same files get different results suggests to me that something either in the registry or to do with permissions is at fault, but I'm damned if I can think what. Any bright ideas anyone?
Cheers
B
That two users on the same machine accessing the same files get different results suggests to me that something either in the registry or to do with permissions is at fault, but I'm damned if I can think what. Any bright ideas anyone?
Cheers
B
By the way I am assuming you installed a version of MDAC Update the same way.
ASKER
MDAC was already on the servers, and the app is a simple EXE with no other DLLs or anything else attached, so it doesn't actually need an EXE. Or are you saying it has to be "installed" despite that? Can't work out what difference that would make.
Yes, it's a 2000 box, sorry.
Is there any quick way of figuring out whether MDAC is the issue? Is there another common app for example that would give me the same issue, so I can narrow it down to that?
B
Yes, it's a 2000 box, sorry.
Is there any quick way of figuring out whether MDAC is the issue? Is there another common app for example that would give me the same issue, so I can narrow it down to that?
B
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, the EXE checks a couple of files but doesn't touch the registry.
I used the component checker but it looks fine, nothing obvious is missing. Because of the number of other apps using this server I'm loathe to update MDAC unless I can be certain that it is MDAC at fault. What I'd ideally like is for someone to say they've seen exactly this problem before and X is what resolved it...
I used the component checker but it looks fine, nothing obvious is missing. Because of the number of other apps using this server I'm loathe to update MDAC unless I can be certain that it is MDAC at fault. What I'd ideally like is for someone to say they've seen exactly this problem before and X is what resolved it...
Hai,
You have to create an install which supports both admin users and normal user accounts. in some setups we can found the screen asking that if this will be available for admin or other users. so if you create a setup like this then it will solves the problem.
Seshu123
You have to create an install which supports both admin users and normal user accounts. in some setups we can found the screen asking that if this will be available for admin or other users. so if you create a setup like this then it will solves the problem.
Seshu123
ASKER
seshu - I think I'm going to need a little more detail than that... i.e. how/why?
B
B
Hai,
because in the xp ot nt based system there is an option that if you install one software using the administrator account it will asks you for confirmation wether you are going to install this software for the admin or for entire users. if you select the admin then it will installs the application and gives the rights to the admin only. if you select the entire users then it will install this application to the entire users and gives the rights to entire users. So better try to install the application foe all users. I have the same problem and i solved like this only.
Seshu123
because in the xp ot nt based system there is an option that if you install one software using the administrator account it will asks you for confirmation wether you are going to install this software for the admin or for entire users. if you select the admin then it will installs the application and gives the rights to the admin only. if you select the entire users then it will install this application to the entire users and gives the rights to entire users. So better try to install the application foe all users. I have the same problem and i solved like this only.
Seshu123
ASKER
I meant - how do I create an install program like this? I've not seen this option in any of the tools I've used.
why don't you use the setup factory it is more user friendly that any other setup creators.
Seshu123
Seshu123
accept seshu123
ASKER
No... nothing here has actually helped to be honest, but if I have to award the points I will do so to RainUK.
nice decission
It maybe a registry issue, so make sure your administrators use the command to setup the servers installed applications for terminal server users applications.
Basically before installing your app:
1. Go to command prompt, type: change user -install
2. Install your application ( I hope you are using windows installer MSI )
3. Go to command prompt, type: change user -execute