Skip to main content
V
VINO12-Amethyst
12-Amethyst
February 16, 2015
Solved

Upgrade Issue when running upgrade manager. Standalone migrator fails

  • February 16, 2015
  • 1 reply
  • 5480 views

Hi All,

I'm in middle of upgrade from Windchill 10.1 M030 to 10.2 M020. Getting a issue while running upgrade manager in target

server in the Standalone migrator task.

Following is the error which I'm getting

Error occurred when executing the task of Populate the fields FullName, Last and Email in the WTUser table.
Error is

(com.ptc.windchill.upgrade.updates.directives.directivesResource/27) com.ptc.windchill.upgrade.updates.DirectiveExecutionException: Unexpected error executing a JavaMigratorDirective with className=wt.org.PopulateUserFullNameFields.

Nested exception is: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)Caused by:

  1. wt.util.WTException: Error in finding mapping key for "user.cn" in adapter : local.xxxx.EnterpriseLdap

Nested exception is: com.infoengine.exception.adapter.IEAdapterException; nested exception is:

  1. javax.naming.NameNotFoundException: [LDAP: error code 32 - The entry cn=Xxxxx xxx,ou=wma users,ou=sbusers,ou=users,ou=mybusiness,dc=xxxx,dc=local specified as the search base does not exist in the Directory Server]; remaining name 'cn=Xxxxx xxx,ou=wma users,ou=sbusers,ou=users,ou=mybusiness,dc=xxxx,dc=local'

at wt.org.UserFullNameFieldsHelper.readPrincipal(UserFullNameFieldsHelper.java:407)

at wt.org.UserFullNameFieldsHelper.processPersistedUsers(UserFullNameFieldsHelper.java:187)

at wt.org.UserFullNameFieldsHelper.populateUserFullNameFieldsAndUpdate(UserFullNameFieldsHelper.java:107)

at wt.org.PopulateUserFullNameFields.runMigration(PopulateUserFullNameFields.java:29)

... 24 more

Caused by: com.infoengine.exception.adapter.IEAdapterException; nested exception is:

  1. javax.naming.NameNotFoundException: [LDAP: error code 32 - The entry cn=Xxxxx xxx,ou=wma users,ou=sbsusers,ou=users,ou=mybusiness,dc=xxxx,dc=local specified as the search base does not exist in the Directory Server]; remaining name 'cn=Xxxxx xxx,ou=wma users,ou=sbsusers,ou=users,ou=mybusiness,dc=xxxx,dc=local'

at com.infoengine.jndi.JNDIAdapterImpl.processRequest(JNDIAdapterImpl.java:254)

at com.infoengine.procunit.adapter.Adapter.send(Adapter.java:198)

at com.infoengine.SAK.ObjectWebject.invoke(ObjectWebject.java:262)

at com.infoengine.compiledTasks.file.D$3a$5cPTC$2dWindchill$5cWindchill$5ctasks.wt.federation.queryprincipals$2exml.invoke(queryprincipals$2exml.java:100)

at com.infoengine.SAK.Task.invoke(Task.java:1806)

at com.infoengine.SAK.Task.invoke(Task.java:1714)

at wt.org.UserFullNameFieldsHelper.readPrincipal(UserFullNameFieldsHelper.java:359)

... 27 more

Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - The entry cn=Xxxxx xxx,ou=wma users,ou=sbsusers,ou=users,ou=mybusiness,dc=xxxx,dc=local specified as the search base does not exist in the Directory Server]; remaining name 'cn=Xxxxx xxx,ou=wma users,ou=sbsusers,ou=users,ou=mybusiness,dc=xxxx,dc=local'



I found a similar issue in ptc knowledgebase at document CS59225 and also tried those solutions. But this exception is coming for every user. Already I have disable

three users so far. That document is talking about disconnected users in ldap. I got that issue while running my WinDU but later I fixed that and

completed my WinDU task without any failed tasks or problems.

Source system is using Active directory server. Will that be a root cause of this issue.? How should I proceed now. Please advice

Best answer by ChrisSpartz

Has the target server been configured for Active Directory? The error message is saying that the search base configured for your EnterpriseLdap adapter doesn't exist in the Directory Server. Make sure this adapter is properly configured for Active Directory.

1 reply

C
ChrisSpartz13-AquamarineAnswer
13-Aquamarine
February 16, 2015

Has the target server been configured for Active Directory? The error message is saying that the search base configured for your EnterpriseLdap adapter doesn't exist in the Directory Server. Make sure this adapter is properly configured for Active Directory.

    V
    VINO12-AmethystAuthor
    12-Amethyst
    February 19, 2015

    Thanks for your reply. And yes that was the issue then I've fixed that by properly configuring the Active Directory

    in the target server.

      B
      BuddyHudson1-Visitor
      1-Visitor
      February 20, 2015

      Hey Vino,

      How did you configure the Active Directory on the target? I thought that the upgrade manager did this automatically during the upgrade? Can you explain? I too am in the middle of an upgrade testing from 10.1 M020 to 10.2 M010.

      Thanks,

      Buddy

      Terms & ConditionsAccessibility statement