DLLs created in VB6 is not accessible to local users

Hi,

We are having some Dlls created using VB6. We are using Multi Active Wizard provided by Maximizer software for creating the VB code. This code is modified and compiled to create the dlls. These dlls are used within Maximizer application. For Administrators and power users these dlls are accessible through Maximizer. But for local users they are not accessible. I granted full permission to the folder where these dlls are located to all users. But still the issue remains. Anybody has any clues. Is there anything to do with the windows security policy?

Thanks,
Ajish

Why aren't these dll's in the system folder? Having them there would guarantee that they were accessible to all users.

Hi,

These DLLs are accessed by Maximizer software during execution. Maximizer has folder specification to which these DLLs are to be copied. So we cannot copy these files to System folder.

Thanks,
Ajish

Then that sounds like a Maximizer issue. Is the folder local or on a network? And is that where Maximizer says to have them?

The folder is inside the installation folder of Maximizer. Maximizer guys tell they never faced any such issues anywhere. So that felt like a configuration issue to me. Any clues?

I don't know Maximizer, so you will need to explain the security settings that it has.

Maximizer does not have any special security settings. Maximizer uses SQL server security accounts for logging in. Maximizer has provided us a wizard which is plugged into VB6 to create a code for DLLs. This code is for a Datasource and a VB form for editing. When Maximizer runs, this datasource is connected to a Grid in Maximizer and VB form is used for editing each row of the grid. DLLs are used by Maximizer depending on the access rights of the windows user logged in; not the Maximizer user. If the windows user has local admin or power user privilage, DLL works along with Maximizer. If user has only local user right, dll is ignored. I have given full access rights to the DLL and the folder in which DLL is located to all users. But no use. I have registered the DLL then also no effect.

If I understand what you mean... Maximizer uses the Database Security parameter for the dll usage. Why would it use the database's security instead of the Windows Security. If that is the case changing windows security will not work at all.

But Dll is being used when the windows login user has admin or power user privilage for same Database user. Dll usage is not depending on the DB user which used for logging onto Maximizer. It depends only on the Windows user's privilage.

For example: Assume we have two windows users; User 'A' is just local user where as User 'B' is a power user. We have DB user 'D' which is used for logging onto Maximizer.

Now if user 'A' is logged on to windows and user 'D' is logged onto Maximizer, DLLs wont be available in Maximizer. But if user 'B' is logged onto windows and again user 'D' is logged onto Maximizer, all dlls would be available in Maximizer.

So, who are you attempting to get to use the dll's the 'A' user? If so, then the reason you can't use it is a registry setting that is not available. It would have nothing to do with where the dll's are located.

There would be a registry setting that told maximizer where the dll's were and if you could not read the registry settings you could not load the dll.

But other entries in the registry including the Maximizer supplied Dlls are available for user 'A'. Maximizer software does not show any problem for user 'A'. Only the features provided by the new Dlls are not available for when user 'A' is logged onto windows.

Correct that is where Maximizer located the registry entries in an area that cannot be seen by user 'A'

But from Maximizer people we understood that they have not done anything like that. They are keeping all in the same way.

Of course they would say that. They don't want you to be looking around to figure out what registry entries you would need to get around their security.

But the wizard and custom dll is an important feature provided by Maximizer. As a part of Maximizer customization, we have created these dlls. As a result of this issue, we are not able to make the tool live. Thats why we are very much concerned about this. But since Maximizer has a large number of success stories, we have to beleave them.

Was Maximizer installed under an Admin account?

Was the DLL created under an Admin account?

Either of these could keep non-Admin logins from being able to access the DLL.

Yes. Maximizer was installed and DLL was created under Admin Account. But DLL was compiled in a different machine which is not a part of network where it is executed.

Ajish