I'm doing an integration on a client and they have OracleDB (this is like working for the devil ) and I got this error.

What I did?

Provide the ASPNET, IUSR_MACHINENAME and IWAM_MACHINENAME, Read & Execute, List Folder Contents, and Read permissions accounts to the ora92 (Oracle installation) directory and all sub-directories and files. (An ASP.NET account will be created and added to your users list when you install the .NET framework). You must restart your machine for the permission changes to take effect.

Magic happens Oracly!

Vimeo was born with the goal to create a community of people who like to make and to share videos. Since the simple moments of day-by-day until the elaborated and complex videos more, everything can be found in vimeo.com.

This site presents as main characteristics, the power fact to be visualized in high definition (the years light of what it is made in the YouTube). Simply shining!

In Windows 2000 (and Windows Server 2003) servers that are configured as Domain Controllers only 5 groups have the right to log on locally on the computer. Those groups are:

Administrators, Account, Print, Backup, and Server Operators.

Without this right any user who will try to log on locally will receive this message:

(The local policy of this system does not permit you to log-on interactively)

To give a specific user or group the right to log on locally on the DC you must edit the Domain Controller GPO (or create another one and link it to the Domain Controllers OU in Active Directory Users and Computers). Most novice IT personnel find it harder to add user rights on W2K than in Windows NT 4. I agree, but life goes on, doesn't it?

To make life easier run this command and you won't have to edit the GPO:

ntrights -u Users +r SeInteractiveLogonRight

You must have the NTRIGHTS.EXE program from the W2K Resource kit (or d/l it from HERE).

(You can substitue USERS with the name of the user or group you want to configure).

If you still want to do it via the GPO, do the following:

1. Go to Start, Settings, Control Panel, Administrative Settings.

2. Double-click Domain Controller Security Policy.

3. Go to Security Settings, Local Policies, User Rights.

1. Double-click Logon Locally on the right pane.

2. Click Add, Browse, and double click the user or group you want to add.

1. Click Ok all the way out.

2. Reboot your computer, or even better, use SECEDIT:

secedit /refreshpolicy machine_policy /enforce

By the way, in Windows Server 2003 the same user right is called "Allow Logon Locally", and to refresh the policy you need to run a different command:

gpupdate /force