Hi,
I'm a sys admin and I'm having a strange problem with permissions. It was
necessary to set up one of our development computers so that some developers
that we're contracting with can access it remotely. They are just normal
users on the network, but they've been give full rights on all of the
folders that contain the code that they are working with. They can check
stuff in and out of Source Safe and even modify the files, but when we try
to hit the play button to test the code we get a msgbox that says Permission
Denied. I tried using F8, but that didn't work because the application
wouldn't even run. It doesn't compile, or anything. Any ideas on what the
problem might be? Ideally, we'd like to not have to give admin privileges
if we don't have to.
Thanks--
--John
Remember, the early bird gets the worm,
but the second mouse gets the cheese.
Ken Halter - 20 Sep 2005 22:11 GMT
> Hi,
>
[quoted text clipped - 14 lines]
> Remember, the early bird gets the worm,
> but the second mouse gets the cheese.
This may be related....
How to grant users the access to add Visual Basic components
http://support.microsoft.com/default.aspx?scid=kb;en-us;274484

Signature
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..
John Rosenlof - 20 Sep 2005 23:39 GMT
Thanks for the help and response. It looked promising, but it didn't work.
Back to the drawing board :)

Signature
--John
Remember, the early bird gets the worm,
but the second mouse gets the cheese.
>> Hi,
>>
[quoted text clipped - 19 lines]
> How to grant users the access to add Visual Basic components
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274484
Joseph Geretz - 23 Sep 2005 05:24 GMT
> users on the network, but they've been give full rights on all of the
> folders that contain the code that they are working with.
Maybe VB wants to build some intermediate temp files? Where would those Temp
files be built and what access permissions do these users have to that
location?
- Joe Geretz -
> Hi,
>
[quoted text clipped - 14 lines]
> Remember, the early bird gets the worm,
> but the second mouse gets the cheese.
Someone - 23 Sep 2005 07:08 GMT
I am not sure if this is what you are having, but some admins restrict
"Everyone" group or even remove it, presumably to enhance security. This
however leads to problems. See the following articles:
http://support.microsoft.com/kb/109076/EN-US/
http://support.microsoft.com/kb/130016/EN-US/
Also, are you cloning hard disks? This can lead to problems because 2
computers might share the same system identifier. You can view the SID by
using the following software:
http://www.sysinternals.com/Utilities/PsGetSid.html
To fix the problem, use the following:
http://www.sysinternals.com/Utilities/NewSid.html
> Hi,
>
[quoted text clipped - 14 lines]
> Remember, the early bird gets the worm,
> but the second mouse gets the cheese.
Someone - 23 Sep 2005 07:44 GMT
I read somewhere an article that if you remove Everyone group, you also
disable access to the SYSTEM account. This will cause permission problems
mostly to services, like IIS service. The solution is to either add Everyone
back, or add SYSTEM with full permissions.
Also, the user must be at least a Power User in order for the user to run
ActiveX projects in VB6 IDE. This is because only Administrators and Power
Users have write access to HKEY_LOCAL_MACHINE. When you run an ActiveX
project in the IDE, VB6 registers the following file first:
C:\Program Files\Microsoft Visual Studio\VB98\VB6DEBUG.DLL
If you compile, VB6 will create the necessary registry entries and points
them to your compiled file so you don't have to register it. This obviously
fails if the user is just a member of Users group. Members of Users group
can't install most software.
INFO: Registry Entries Made by an ActiveX Component
http://support.microsoft.com/default.aspx?scid=kb;en-us;183771
>I am not sure if this is what you are having, but some admins restrict
>"Everyone" group or even remove it, presumably to enhance security. This
[quoted text clipped - 31 lines]
>> Remember, the early bird gets the worm,
>> but the second mouse gets the cheese.
John Rosenlof - 23 Sep 2005 23:20 GMT
Thanks! That is probably the best answer that I've gotten yet. MS support
has been LESS than helpful with this. All I really needed to know from them
was if the users needed to be part of the local admin or power users groups,
but they decided instead to try to troubleshoot each and every permission
denied error.
Thanks a bunch! I'm going to try to put their group into the local power
users or admin group so that they'll be able to develop and test problem
free. I think that I've locked down our network well enough so that that
won't cause any access violations, but time we'll see if there are any holes
that I might need to close. In any event, thanks for your help.
Regards,
--John
Remember, the early bird gets the worm,
but the second mouse gets the cheese.
>I read somewhere an article that if you remove Everyone group, you also
>disable access to the SYSTEM account. This will cause permission problems
[quoted text clipped - 51 lines]
>>> Remember, the early bird gets the worm,
>>> but the second mouse gets the cheese.