JDBC errors on the Integration Server logs

Hi Experts,

I was trying to bring up the MWS server in our environment and was seeing this error on the logs,

[POP.001.0002] A "java.sql.SQLSyntaxErrorException" occurred with the Message "[SoftwareAG][SQLServer JDBC Driver][SQLServer]Invalid column name 'PASSWORDVALIDUNTIL'."java.sql.SQLSyntaxErrorException: [SoftwareAG][SQLServer JDBC Driver][SQLServer]Invalid column name 'PASSWORDVALIDUNTIL'.
        at com.wm.dd.jdbc.sqlserverbase.ddb_.b(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddb_.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddb9.b(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddb9.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserver.tds.ddr.v(Unknown Source)
        at com.wm.dd.jdbc.sqlserver.tds.ddr.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserver.tds.ddq.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserver.tds.ddr.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserver.ddj.m(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddek.e(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddek.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddde.a(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddek.v(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddek.u(Unknown Source)
        at com.wm.dd.jdbc.sqlserverbase.ddde.executeQuery(Unknown Source)
        at com.webmethods.portal.service.sql.core.BaseSqlWorker.executeQuery(BaseSqlWorker.java:490)
        at com.webmethods.portal.service.sql.core.BaseSqlWorker.executeQuery(BaseSqlWorker.java:445)
        at com.webmethods.portal.service.sql.core.BaseSqlWorker.executeQuery(BaseSqlWorker.java:421)
        at com.webmethods.portal.service.meta2.dbo.DBOStorageService.loadExtendedInfo(DBOStorageService.java:243)
        at com.webmethods.portal.portlet.wm_xt_sysdiruser.SysdiruserThing.loadBasicAttrs(SysdiruserThing.java:331)
        at com.webmethods.portal.portlet.wm_xt_sysdiruser.SysdiruserThing.getDn(SysdiruserThing.java:204)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.webmethods.rtl.util.ObjectUtil.getProperty(ObjectUtil.java:675)
        at com.webmethods.portal.portlet.wm_xt_sysdirsvc.service.SystemDirectoryService.wrap(SystemDirectoryService.java:218)
        at com.webmethods.portal.portlet.wm_xt_sysdirsvc.service.SystemDirQueryProvider.lookupByID(SystemDirQueryProvider.java:298)
        at com.webmethods.portal.mech.dir.impl.DirSystemMechanics$1.visit(DirSystemMechanics.java:234)
        at com.webmethods.portal.mech.dir.impl.DirSystemMechanics.visitDirServices(DirSystemMechanics.java:572)
        at com.webmethods.portal.mech.dir.impl.DirSystemMechanics.lookupPrincipalByID(DirSystemMechanics.java:232)
        at com.webmethods.portal.bizPolicy.impl.ContextFactory.acquireContext(ContextFactory.java:208)
        at com.webmethods.portal.bizPolicy.impl.ContextFactory.acquireContext(ContextFactory.java:202)
        at com.webmethods.sc.directory.impl.DirectorySession.<init>(DirectorySession.java:77)
        at com.webmethods.sc.directory.impl.DirectorySystem.createSession(DirectorySystem.java:158)
        at com.wm.app.b2b.server.cds.CDSUserManager.initialize(CDSUserManager.java:164)
        at com.wm.app.b2b.server.UserManager.jndiInit(UserManager.java:542)
        at com.wm.app.b2b.server.UserManager.init(UserManager.java:473)
        at com.wm.app.b2b.server.Server.run(Server.java:379)

We are running Webmethods 8.2. Appreciate any help.

Thanks!

Is it the first time start up of MWS or did it worked before?

Did you check and make sure the MWS related tables in the backend any thing associated to the invalid column?

Any recent changes to config xml above?

Please contact SAG support on these such errors as it related to the Product itself.

HTH,
RMG

Thanks RMG.

It looks like we didn’t run our UpdateManagerCMD.sh script against the DB directory first for getting the latest fixes before running on other directories. This led to version/fix mismatch.
We are re-doing this again and hope to see the site up again.

I’ll respond to this thread on how it went.

Glad you found the resolution self: