Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
1293 views

configupdate.sh problems


I am having problems when working to migrate from a 4.0.2 server to a
4.5.2 server when running configupdate.sh. The error is:

com.netiq.internal.installer.idm.ldap.ConfigStoreException: Error
storing configuration.
at
com.netiq.internal.installer.idm.ldap.IdmConfigSource.commit(IdmConfigSource.java:148)
at
com.netiq.internal.installer.idm.ldap.LdapConfig.commit(LdapConfig.java:353)
at
com.netiq.internal.installer.idm.ldap.LdapConfig.main(LdapConfig.java:171)
Caused by: java.io.IOException: Error initializing User App
configuration values from directory
at
com.netiq.internal.installer.idm.ldap.AppConfigBase.initialize(AppConfigBase.java:323)
at
com.netiq.internal.installer.idm.ldap.AppConfigBase.initialize(AppConfigBase.java:274)
at
com.netiq.internal.installer.idm.ldap.UserAppAdapter.commit(UserAppAdapter.java:301)
at
com.netiq.internal.installer.idm.ldap.UaConfigBase.commitAdapters(UaConfigBase.java:219)
at
com.netiq.internal.installer.idm.ldap.IsmConfig.commit(IsmConfig.java:346)
at
com.netiq.internal.installer.idm.ldap.IdmConfigSource.commit(IdmConfigSource.java:143)
... 2 more
Caused by: LDAPException: Error reading Email password. (80) Other
com.novell.security.sso.SSException: [LDAP: error code 2 - Unrecognized
extended operation]
at
com.netiq.internal.installer.idm.ldap.AppConfig$EmailPassword.read(AppConfig.java:554)
at
com.netiq.internal.installer.idm.ldap.AppConfig.readConfig(AppConfig.java:372)
at
com.netiq.internal.installer.idm.ldap.AppConfigBase.initialize(AppConfigBase.java:316)
... 7 more
Caused by: com.novell.security.sso.SSException: [LDAP: error code 2 -
Unrecognized extended operation]
at
com.novell.security.sso.ldap.jndi.JNDISecretStore.checkException(JNDISecretStore.java:487)
at
com.novell.security.sso.ldap.jndi.JNDISecret.read0(JNDISecret.java:234)
at com.novell.security.sso.Secret.read(Secret.java:699)
at com.novell.security.sso.SharedSecret.read0(SharedSecret.java:905)
at com.novell.security.sso.Secret.read(Secret.java:699)
at com.novell.security.sso.Secret.read(Secret.java:646)
at
com.netiq.internal.installer.idm.ldap.AppConfig$EmailPassword.initSecret(AppConfig.java:607)
at
com.netiq.internal.installer.idm.ldap.AppConfig$EmailPassword.read(AppConfig.java:549)
... 9 more


The issue occurs when I change the servername from the 4.0.2 host to the
4.5.2 host. I do not get an error when looking or modifying the email
username/password from within iManager.


--
schwoerb
------------------------------------------------------------------------
schwoerb's Profile: https://forums.netiq.com/member.php?userid=2338
View this thread: https://forums.netiq.com/showthread.php?t=54507

Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: configupdate.sh problems


I am using IDM45-configupdate-HF-1.


--
schwoerb
------------------------------------------------------------------------
schwoerb's Profile: https://forums.netiq.com/member.php?userid=2338
View this thread: https://forums.netiq.com/showthread.php?t=54507

0 Likes
Knowledge Partner
Knowledge Partner

Re: configupdate.sh problems

Odd..... Is IDM already working properly on your 4.5.2 engine system, I
presume, running drivers and similar?

Which exact version of eDirectory is present there?

If you run 'ndstrace -c moudles| grep ss' do you see the following (if not
more) loaded?
lsss Running
ssncp Running
sss Running
ssldp Running

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: configupdate.sh problems


Thank you. I hadn't noticed a SASL issue on the install of edir. It
ended up being a problem with the CRL for the CA. It is outlined in
http://tinyurl.com/o9g7zjs


--
schwoerb
------------------------------------------------------------------------
schwoerb's Profile: https://forums.netiq.com/member.php?userid=2338
View this thread: https://forums.netiq.com/showthread.php?t=54507

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: configupdate.sh problems


schwoerb;261738 Wrote:
> I am having problems when working to migrate from a 4.0.2 server to a
> 4.5.2 server when running configupdate.sh. The error is:
>
> Caused by: LDAPException: Error reading Email password. (80) Other
> com.novell.security.sso.SSException: [LDAP: error code 2 - Unrecognized
> extended operation]
> at
> com.netiq.internal.installer.idm.ldap.AppConfig$EmailPassword.read(AppConfig.java:554)
> at
> com.netiq.internal.installer.idm.ldap.AppConfig.readConfig(AppConfig.java:372)
> at
> com.netiq.internal.installer.idm.ldap.AppConfigBase.initialize(AppConfigBase.java:316)
> ... 7 more
> The issue occurs when I change the servername from the 4.0.2 host to the
> 4.5.2 host. I do not get an error when looking or modifying the email
> username/password from within iManager.


I had a similar issue after restoring eDirectory contents from backup
and Default Notification Collection lost access to it's secretstore.
Deleting the default notification branch with ldapdelete and restoring
by deploying from Designer solved the issue. Earlier, we had already
generated new CA's for the tree.


--
jnevala
------------------------------------------------------------------------
jnevala's Profile: https://forums.netiq.com/member.php?userid=11223
View this thread: https://forums.netiq.com/showthread.php?t=54507

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.