Article ID: 943313 - Last Review: October 11, 2007 - Revision: 1.0

Engyro Connectors for MOM 2005: Active Directory Domain Services username authentication

Rapid publishing disclaimer
Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

SYMPTOMS

When you try to browse the web config it will give an error:
Server Error in \EngyroTECWebconfig application The user NT Authority/Network Services does not have sufficient privileges to perform this operation.

CAUSE

You experience the error due to use of username\password with active directory domain service.

RESOLUTION

To resolve it here are steps taken.

I was able to tweak my way around this issue by doing the following:
  1. We had to change the Application Pool identity to run as the SDK account.
  2. I had to reconfigure the Engyro website to point to the correct wwwroot path on D:\Inetpub.
  3. I had to change the Ops UI properties for the config page from DALAPPINFRA20 to Localhost.
Completing step 1, made the SDK service happy but then all attempts to authenticate were rejected for some reason.

I was, however able to browse the default.aspx page from the IIS admin and figured out that trying to authenticate via the Netbios name was giving back authentication problems.

Keywords: 
kberrmsg kbtshoot kbprb kbexpertiseinter KB943313

Note: This article is from Microsoft Knowledage Base


How we have helped PC users like you

In the News: Read More In ...

Related problems posted by other users

more...