Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Active Directory

Status
Not open for further replies.

dhulbert

Technical User
Jun 26, 2003
1,136
GB
I'm having problems getting Configuration manager to complete. I know there have been a couple of threads in here about it but they haven't completed.
I'm trying to get the following config to work

computer: advres-server
port: 389
Base DN: o=advres-server, dc=advres, dc=local
Unrestricted User: cn=Administrator,cn=users,dc=advres,dc=local

I get the error Unable to create default namespace could not connet to Advres-Server:389

Any ideas which setting I've got wrong...???
 
This may be a 'duh', but did you validate your password?
 
Yep.

Passsword is fine, I can install the netscape server and make it work but I want to sort it for Active Dir.
 
I do not htink you are supposed to enter any of that for anactive directory. Only the servername:389
That is how it works for Reportnet Cognos Configuration.

I have tried it and it works..but again for cognos cofiguration for Reportnet.
 
If this is for Activr Directory 2003, then the dsHeuristics setting is probably not set, or is wrong.
The value needs to be set to 0000002 for this to work.
 
This isn't my area of expertise, so not sure this will make sense, but...

We had some issues when switching to a new AD domain. One issue had something to do with the pdc emulator fsmo role. I asked my Network Admin for more info, I'll post it when (if) he gets back to me.

The other issue was with the 'Administrator' we were using for Active Directory. When we tried a user with administrator rights, the user still could not create the new AD tree for Cognos, so we ended up using THE Administrator for the domain.

Stacy
 
The user used to extend the schema must be part of the schema admin group or a member of whatever group currently owns the schema. Most companies for security reasons, will change the ownership of the schema from schema admin to another group, so you may have to consult with the AD team.
 
Check if the machine u are mentioning is the schema master.
It is possible that u might refer to machine X in cognos config but machine Y could the schema master...
also as flex mentioned make sure the user u use is part of schema admin group.

This is because wen u config ADS the cognos creates a schema for itself in the ADS. For this we need the user to have schema admin rights.

Good Luck!
Ramesh
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top