Can't compile - VS.NET Beta2 Enterprise Edition

[Gen]

Anyone using VS.NET Beta2 Enterprise Edition?

All projects like VB, VC# works just fine, but for VC++, when I build
a project, I always get the following error.

> Project error PRJ0016: The user's security settings prevent the process
> from being created. These settings are required for building.

Even the simplest project like Win32 Project (that the wizard creates,)
fails to build.

I'm running VS.NET as Administrator so I wonder what rights I need to add.
Can anyone help?

Gen.

[Michael (michka) Kaplan]

Are you trying to create it on a network share? Or is the source code on
another machine? Thats the easiest way to see this sort of problem.

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Gen" <ge...@bigfoot.com> wrote in message
news:#bLJyVsKBHA.796@tkmsftngp04...

[Gen]

I'm trying ones on local machine.

The project is created on local disk (c:\,) and of course, I have full access
to the disk/directory. I've also tried to convert & compile VC++6.0 projects
that I had, but the same result.

Since VS.NET Professional Edition worked just fine, I suspect there's
something special in Enterprise Edition...?

The VS.NET help said I need "Create process from process" right to compile the
project, but I don't know where this setting exists.

Hmm...

Gen

"Michael (michka) Kaplan" <forme...@spamfree.trigeminal.nospam.com> wrote in
message news:#b0h75sKBHA.1244@tkmsftngp02...

[Michael (michka) Kaplan]

Well, I cannot repro the problem on my own EE so I assume this is just some
basic config issue with the setup.

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Gen" <ge...@bigfoot.com> wrote in message

news:u$K82ruKBHA.936@tkmsftngp04...

[Gen]

Thanks MichKa,

I now know it's not Enterprise Edition issue (as yours works just fine,) maybe
I should take a look at other settings on my PC.

Gen.

[Michael (michka) Kaplan]

One thing to consider is that being an Administrator does not make one GOD
on a machine; it just gives one the ability to make oneself a god as needed
(in other words, you have the ability give yourself many permissions that
you may not have at the moment).

Because of this, even an Administrator can have permissions problems,
something that is even true before you consider issues like policy that
limit a local administrator's "god-enabling" powers. :-)

--
MichKa

the only book on internationalization in VB at
http://www.i18nWithVB.com/

"Gen" <ge...@bigfoot.com> wrote in message

news:#KmAxgwKBHA.1496@tkmsftngp05...

[Sven Carstensen]

Hi Gen,

Is your computer member of a Win2k domain and do you logon on to the domain
rather than locally to your machine?
There could be some group policy from the domain which disallows some user
rights. Check it under Start->Programs->Administrative Tools->Local Security
Policy - look at Local Policies->User Right Assignment. You might need
something like "Act as part of the operating system" or "increase quotas" or
"replace a process level token". Double-Click those and see if "Local Policy
Setting" is the same as "Effective Policy Setting". If not then you do get
policy from somewhere else, e.g. your domain. Ask your administrator to
change that or log on locally.

Bye, Sven

[Gen]

Sven, Thank you for the Info.

I'm running my computer in a workgroup, not in a domain.
Since I don't have "Domain Security Policy" and "Domain Controller Security
Policy," I have checked the "Local Security Policy" setting. I've added all
rights like you've listed (all possible rights I could set,) but it still
doesn't work.

I have never heard of such access right (for Win2k) as "create process using a
process," which was on the VS.NET Help file.

When I first encountered this problem, I thought setting all access rights are
the best thing to do, but probably it's not a good idea to use Administrator
account as MichKa said.

Gen

"Sven Carstensen" <Sven.Ca...@gft.com> wrote in message
news:99850623...@tux2.ham.acs-gmbh.de...

[Kevin Perry]

So this is only supposed tpo occur if you have the following registry
key set to something ...

\\HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\RestrictRun

In general this is a dumb registry key and the IDE only respects it
because it is a Win2k Logo requirement.

You can delete that key and you should be able to make the IDE work.
The restrictedRun key is the weakest form of security imaginable,
since it relies on Apps to volutarily respect it, and it relies on
users not knowing it exists because most users have write access to
that key.

If for some strange reason you actually need that key, you should
append "vcspawn.exe" to the list of entries in the key.

Kevin Perry
[msft]

"Gen" <ge...@bigfoot.com> wrote in message news:<O0M2Bk3KBHA.1424@tkmsftngp03>...

[Gen]

I had the value "0" for the key, and when I deleted the key, the project
compiled without a problem. Thanks!

Gen

"Kevin Perry" <kevin...@hotmail.com> wrote in message
news:e92acf9a.01083...@posting.google.com...