Skip to main content
B
borourke11-Garnet
11-Garnet
August 30, 2023
Question

PDMLink 12.1 Error: User not found: unknown web name: "wcadmin"

  • August 30, 2023
  • 3 replies
  • 2310 views

We have 1 production PDMLink 12.1 server and 2 test/dev 12.1 servers that were created by upgrading from an existing 11.1 server. Built a 4th server with an OOTB installation, and copied over the production Oracle database and ldap export, but get the following error: User not found: unknown web name: "wcadmin". Now when I run the wt.auth.Authentication command, my user/password for wcadmin works. When I try logging on using that user/pw, I get the above mentioned error. I have tried installing PDMLink 12.1 with temp user and OOTB built database, and then changing the information to match the production info, and tried installing against an existing copy of the prod database and ldap info. Seems things are different now that the Windchill Directory Server is no longer bundled with the PDMLink installation. Just wondering if anyone has done something similar for PDMLink 12.1. Many thanks in advance!

3 replies

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
August 30, 2023

What are you using for your LDAP with 12.1?

What was your LDAP with 11.1, WindchillDS?

Did you run the Upgrade Manager on the copied data from 11.1 to the 12.1 system? There are some manual steps if using WindchillDS 11.2 with WIndchill 12.0, not sure of 12.1.

B
borourke11-GarnetAuthor
11-Garnet
August 31, 2023

We used the 11.2 WDS installed per the PTC article, and then did the ldap merge between our production ldap and the 11.2 ldap.

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
August 31, 2023
  1. Modify the LDAP for Windchill 12 per CS352917
    1.       Open Windchill DS Control Panel
    2.       Click on Manage Entries
      1. Right click o=ptc
        1. Select New from LDIF
        2. Create the following entries:
          1.       dn: cn=Windchill_12.0,o=ptc
          2.       cn:Windchill_12.0
  •       objectClass: ptcSubtree
  1. OK to complete
  2. Close
  1. Right click on cn=Windchill_12.0
    1. Select New from LDIF
    2. Create the following entries:
      1.       dn: cn=AdministrativeLDAP,cn=Windchill_12.0,o=ptc
      2.       cn: AdministrativeLDAP
  •       objectclass: ptcSubtree
  1. OK to complete
  2. Close
  1. Right click on AdministrativeLDAP
    1. Select New Organizational Unit
    2. Create the following entries:
      1.       Enter people in Name field
    3. OK to complete
    4. Close
  •       Close
J
jbailey18-Opal
18-Opal
August 31, 2023

Does wcadmin exist in your LDAP for the OOTB install of WC 12.1?

If not, you can set that user to be any user... and add other users from LDAP

 

xconfmanager -s wt.admin.defaultAdministratorName=<Your LDAP user replacement for WCADMIN>
xconfmanager -s wt.sysadm.administrators=<Admin 1 from LDAP>,<Admin 2 from LDAP>

 

 

B
borourke11-GarnetAuthor
11-Garnet
August 31, 2023

Wcadmin does exist in our 11.2 WDS and successfully authenticate using the wt.auth.Authentication command.

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
September 1, 2023

I think the disconnect might be in the database. Check the RemoteObject (I think) table and see if the path to the user matches. Authentication via the webserver seems correct which is why you are able to log in but the user records in the database do not match its stored path. Sry, doing this from memory.

B
borourke11-GarnetAuthor
11-Garnet
September 1, 2023

Avillanueva,

Thanks for the info. I checked that table on our prod database, and of course it is the same as the copy on our dev database. The prod system is obviously working, but was created through an upgrade. I am hosing up something doing a straight install rather than an upgrade. Never had this issue before 12.1.

Terms & ConditionsCookie settingsAccessibility statement