sulatna Absent Member.
Absent Member.
2580 views

Problem with ESM MC Standalone

Hello,

I want to test ZESM.

First I tried to install it with eDirectory as directory-service, with win2003-server and MSSQL 2008 - failed because of many SQL-errors on directory configuration in ZESM management console.

Now because I just want to test ZESM I installed standalone version of ZESM management console with SQL-express 2008 (supported for standalone) on Win2003-Srv.

Management console installation and open works fine - but if I want to create a policy I get a "unrecoverable error" an mc close.
In windows event viewer I could find these errors:

1) Exception Information
*********************************************
Exception Type: Senforce.PolicyEditor.Bll.FatalErrorException
Message: No default policy in policy table. One is required.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void btnRunImport_Click(System.Object, System.EventArgs)
HelpLink: NULL
Source: PolicyEditor


What could I do now?

Thanks for help,

Michael
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Problem with ESM MC Standalone

sulatna,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
sulatna Absent Member.
Absent Member.

Re: Problem with ESM MC Standalone

OK - Standalone doesn't work at all.
So I installed a Win2003Srv (Standard inkl. SP2) and a SLES10Sp3 with OES2 sp2a for testing.

On Win2003 I also installed MSSQL2008 and SingleServer installation procedure.

Installation of ZESM management console works also fine - BUT:
On configuration of directory service there I can't select my context - it only shows my tree name and no further context! But I need context to login to edirectory.

What I checked until now: no Firewall active, OES has SLP DA, Client Login works, write manually in context doesn't work, Servers could communicate in both ways, login on iManager works.

If more details are needed I could post them.

Perhaps anybody could help.

Michael
0 Likes
Highlighted
SimonMag Absent Member.
Absent Member.

Re: Problem with ESM MC Standalone

sulatna;2038762 wrote:
OK - Standalone doesn't work at all.
So I installed a Win2003Srv (Standard inkl. SP2) and a SLES10Sp3 with OES2 sp2a for testing.

On Win2003 I also installed MSSQL2008 and SingleServer installation procedure.

Installation of ZESM management console works also fine - BUT:
On configuration of directory service there I can't select my context - it only shows my tree name and no further context! But I need context to login to edirectory.

What I checked until now: no Firewall active, OES has SLP DA, Client Login works, write manually in context doesn't work, Servers could communicate in both ways, login on iManager works.

If more details are needed I could post them.

Perhaps anybody could help.

Michael



The Console will ask you for the LDAP host and port (usualy 389 for NON SSL)
NDS Partitions
Contexts for User Accounts
Contexts for syncronization

It should then go off and search your NDS tree and populate the console with all your users, you can then assign polices to them.

I would check what user account you are using to connect to LDAP, I am using an admin equiv. By default if you use Anonymous binds to LDAP you only see restricted attributes, using an admin equiv. might do the trick, as you may not be seeing all of your NDS partitions.

Simon.
0 Likes
sulatna Absent Member.
Absent Member.

Re: Problem with ESM MC Standalone

Hello Simon,

I am using admin account for LDAP connection - do I have to create a new one with equiv. rights???

Exactly thats my problem - it doesn't search my NDS tree.
If I enter my context manually on Console configuration screen I could generate 2 errors:

"The authentication attempt failed: Object reference not set to an instance of an object" and "username admin invalid".
For my first failure I found something in forum
But I don't know how to get this dll from Novell.

Thanks for help,

Michael
0 Likes
SimonMag Absent Member.
Absent Member.

Re: Problem with ESM MC Standalone

sulatna;2045791 wrote:
Hello Simon,

I am using admin account for LDAP connection - do I have to create a new one with equiv. rights???

Exactly thats my problem - it doesn't search my NDS tree.
If I enter my context manually on Console configuration screen I could generate 2 errors:

"The authentication attempt failed: Object reference not set to an instance of an object" and "username admin invalid".
For my first failure I found something in forum
But I don't know how to get this dll from Novell.

Thanks for help,

Michael


Michael,

On the credentials screen, you must use LDAP syntax:

So if your admin user is at the root of your tree it would be cn=admin,o=treename (it is a comma sepperating the two)

If you change the password on your admin account regularly I would reccomend creating another equiv. user and exempt that user from password changes. (Use a strong password though)

Let me know how you get on.

Simon.
0 Likes
sulatna Absent Member.
Absent Member.

Re: Problem with ESM MC Standalone

Hello again,

it's late - but I want to thank you - with LDAP Syntax it worked.

Michael
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.