Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X
Background:
OLD: Windchill PDM Essentials 10.2 M030 production server
New: 11.0 M020 test server
I have successfully installed Windchill 11.0 on a new VM, imported our SQL database from production to test using Microsoft SQL Management restore/replace function.
On the new test server I have a different SQL password. I've updated that using xconfmanager but still can't login.
"xconfmanager -s wt.pom.dbPassword=<NewPassword> -t db/db.properties -p"
However, I can login using those credentials directly to Microsoft SQL. Any help would be greatly appreciated.
--------------------------------------------
2017-04-05 11:51:31,996 INFO [main] wt.server.manager.startup - Registry created: RegistryImpl[UnicastServerRef2 [liveRef: [endpoint:[vdst-plm02.corp.vandynesuperturbo.com:5002,wt.boot.WTRMIMasterSocketFactory@1e240](local),objID:[0:0:0, 0]]]]
2017-04-05 11:51:31,996 INFO [main] wt.server.manager.startup - ServerManager created: ServerManagerImpl[UnicastServerRef2 [liveRef: [endpoint:[vdst-plm02.corp.vandynesuperturbo.com:5002,wt.boot.WTRMIMasterSocketFactory@1e240](local),objID:[0:0:0, 5002]]]]
2017-04-05 11:51:32,011 INFO [main] wt.server.manager.startup - ServerManager bound in registry.
2017-04-05 11:51:32,011 INFO [main] wt.manager.CacheMasterNegotiator - Cache master stub name: CacheMaster
2017-04-05 11:51:32,011 INFO [main] wt.manager.CacheMasterNegotiator - Using low-locking algorithm
2017-04-05 11:51:32,932 ERROR [main] wt.manager.CacheMasterNegotiator - Failed to acquire JDBC connection
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'WindchillDB'. ClientConnectionId:9bcf6626-f85f-46be-a30a-7ba546b48bb4
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:254)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:84)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:2926)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:2243)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:42)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:2229)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1716)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1327)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:992)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:828)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at wt.pds.StandardDataSource$1.getConnection(StandardDataSource.java:114)
at wt.pds.StandardDataSource$ConnectionRetry.execute(StandardDataSource.java:399)
at wt.pds.StandardDataSource.getConnection(StandardDataSource.java:117)
at wt.pds.StandardDataSource.getConnection(StandardDataSource.java:83)
at wt.manager.CacheMasterNegotiator.getNewConnection(CacheMasterNegotiator.java:859)
at wt.manager.CacheMasterNegotiator.start(CacheMasterNegotiator.java:2268)
at wt.manager.ServerManagerMain.startServerManager_internal(ServerManagerMain.java:391)
at wt.manager.ServerManagerMain.run(ServerManagerMain.java:299)
at wt.manager.ServerManagerMain.main(ServerManagerMain.java:229)
2017-04-05 11:51:32,932 FATAL [main] wt.server.manager - ServerManagerMain abort
Check and confirm, if your Database User and Database Password are set correctly in db.properties (On your Windchill 11.0)
~from a Windchill Shell use the "xconfmanager -d <encrypted.password>" command to verify that they are correctly defined
The moving from 10.2 to 11.0 is possible only in during the upgrade process.
Update and clarification:
Windchill Directory Server starts, HTTP server starts, but the Windchill server will not. See error above.
Question:
Using xconfmanger -s wt.pom.dbPassword......... is that my LDAP password? If so, when I use that property to change/update a password and then open the Control-Panel.bat under WindchillDS, I receive credentials invalid (only way to login is using my initial password upon installation).
May be you need to restore your SQL Server user.
SQL for example
USE "wcadmin"
EXEC sp_change_users_login Auto_Fix, 'wcadmin', NULL, 'YOUR_PASSWORD'
go
Using "xconfmanger -s wt.pom.dbPassword" it will update your DB password in site.xconf and wt.property files... by executing this command it will impact/update your LDAP password...
Have you completed with your Upgrade from 10.2 to 11.0 without any failures of Upgrade Manager tasks?
New question/issue:
Almost have my upgrade working but running into this....
wt.org.WTPrincipal -
The principal <wt.org.WTUser:11> has invalid UFID data that prevents it from being inflated properly.
2017-04-25 17:46:37,012 INFO [main] wt.pom.properties - Connection: datastore=Microsoft SQL Server(12.00.4100) jdbcVersion=4.0 driver=Microsoft JDBC Driver 4.1 for SQL Server(4.1.5605.100) driverVersion=4.1
2017-04-25 17:46:45,961 ERROR [main] wt.org.WTPrincipal -
The principal <wt.org.WTUser:11> has invalid UFID data that prevents it from being inflated properly.
java.lang.Exception: Stack trace
at wt.org.WTPrincipal.inflate(WTPrincipal.java:1135)
at wt.org.WTPrincipal.getAttributes(WTPrincipal.java:625)
at wt.org.WTUser.setDn(WTUser.java:1708)
at wt.org.StandardOrganizationServicesManager._principalAdminUser(StandardOrganizationServicesManager.java:11452)
at wt.org.StandardOrganizationServicesManager._getPersistedPrincipals(StandardOrganizationServicesManager.java:11342)
at wt.org.StandardOrganizationServicesManager._getPersistables(StandardOrganizationServicesManager.java:11281)
at wt.org.StandardOrganizationServicesManager._getPersistable(StandardOrganizationServicesManager.java:11259)
at wt.org.StandardOrganizationServicesManager._getPersistable(StandardOrganizationServicesManager.java:11246)
at wt.org.StandardOrganizationServicesManager._queryPrincipal(StandardOrganizationServicesManager.java:7741)
at wt.org.StandardOrganizationServicesManager.getAuthenticatedUser(StandardOrganizationServicesManager.java:2342)
at wt.org.StandardOrganizationServicesManager.getUser(StandardOrganizationServicesManager.java:2464)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399)
at com.sun.proxy.$Proxy47.getUser(Unknown Source)
at wt.session.StandardSessionManager.getUser(StandardSessionManager.java:449)
at wt.session.StandardSessionManager.lambda$setPrincipal$35(StandardSessionManager.java:212)
at wt.session.StandardSessionManager.setPrincipal(StandardSessionManager.java:229)
at wt.session.StandardSessionManager.setPrincipal(StandardSessionManager.java:209)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399)
at com.sun.proxy.$Proxy35.setPrincipal(Unknown Source)
at wt.session.SessionMgr.setPrincipal(SessionMgr.java:33)
I have the same problem. Did you found solution?