MWS instance doesnt start

Rahul_Gupta2 · December 16, 2008, 12:19pm

Hi All ,
Stuck with this error while trying to start new MyWebmethods Server(7.1.1) instance.
java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
object name ‘MWS_CONFIG’.

All steps mentioned at WM Install guide(Pg83 - pg95) and MWS Admin Guide (Pg43 - pg50) were carefully read and implemented and Database Component Configurator used for creating and connecting to the database,but the MWS server instance doesnt start.
It seems MWS_CONFIG is a table but it is not being created for some reason.
Several new instances were created and MWS uninstalled and reinstalled but the problem persists

Environment: WM 7.1.1
Database : Sql Server 2005
Could someone please help us with this.
Thanks & Best Wishes

Rahul_Gupta2 · December 16, 2008, 12:22pm

Log of error message :

C:\webMethods7\MWS\bin>mws -s w6 run
JAVA_HOME: C:\webMethods7\jvm\win150
MWS_HOME: C:\webMethods7\MWS
No registered exception delegate
java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
object name ‘MWS_CONFIG’.
at com.webMethods.rtl.locator.DBConfigLocator.getLocationStream(DBConfig
Locator.java:58)
at com.webMethods.rtl.locator.ClusterConfigLocator.getLocationStream(Clu
sterConfigLocator.java:59)
at com.webMethods.rtl.locator.StreamLocatorFactory.getLocationStream(Str
eamLocatorFactory.java:110)
at com.webMethods.rtl.util.FileUtil.getInputStream(FileUtil.java:199)
at com.webMethods.rtl.util.FileUtil.loadPropertiesFile(FileUtil.java:422
)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.loadSyste
mProps(DefaultPhaseProvider.java:212)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializ
ePhases(DefaultPhaseProvider.java:70)
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializ
ePhases(ClusterPhaseProvider.java:27)
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:868)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:827)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.webMethods.portal.system.start.Main.start(Main.java:131)
at com.webMethods.portal.system.start.Main.main(Main.java:48)
—> Nested exception
java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
object name ‘MWS_CONFIG’.
at com.webMethods.rtl.locator.DBConfigLocator.getLocationStream(DBConfig
Locator.java:58)
at com.webMethods.rtl.locator.ClusterConfigLocator.getLocationStream(Clu
sterConfigLocator.java:59)
at com.webMethods.rtl.locator.StreamLocatorFactory.getLocationStream(Str
eamLocatorFactory.java:110)
at com.webMethods.rtl.util.FileUtil.getInputStream(FileUtil.java:199)
at com.webMethods.rtl.util.FileUtil.loadPropertiesFile(FileUtil.java:422
)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.loadSyste
mProps(DefaultPhaseProvider.java:212)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializ
ePhases(DefaultPhaseProvider.java:70)
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializ
ePhases(ClusterPhaseProvider.java:27)
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:868)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:827)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.webMethods.portal.system.start.Main.start(Main.java:131)
at com.webMethods.portal.system.start.Main.main(Main.java:48)
[POP.001.0002] A “java.io.IOException” occurred with the Message “[wm-cjdbc36-00
39][SQLServer JDBC Driver][SQLServer]Invalid object name ‘MWS_CONFIG’.”
java.io.IOException: [wm-cjdbc36-0039][SQLServer JDBC Driver][SQLServer]Invalid
object name ‘MWS_CONFIG’.
at com.webMethods.rtl.locator.DBConfigLocator.getLocationStream(DBConfig
Locator.java:58)
at com.webMethods.rtl.locator.ClusterConfigLocator.getLocationStream(Clu
sterConfigLocator.java:59)
at com.webMethods.rtl.locator.StreamLocatorFactory.getLocationStream(Str
eamLocatorFactory.java:110)
at com.webMethods.rtl.util.FileUtil.getInputStream(FileUtil.java:199)
at com.webMethods.rtl.util.FileUtil.loadPropertiesFile(FileUtil.java:422
)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.loadSyste
mProps(DefaultPhaseProvider.java:212)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializ
ePhases(DefaultPhaseProvider.java:70)
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializ
ePhases(ClusterPhaseProvider.java:27)
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:868)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:827)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.webMethods.portal.system.start.Main.start(Main.java:131)
at com.webMethods.portal.system.start.Main.main(Main.java:48)
Shutting down…
Shutdown complete.
C:\webMethods7\MWS\bin>

creased · December 16, 2008, 2:10pm

MWS_Config as far as I am aware is a table that only came into existence in 7.1.2. I would check the database and also check the scripts used to create the database components, as either you are trying to run a 7.1.2 MWS against 7.1.1 database components or vice versa…

thanks,

Donald

Ankit · December 17, 2008, 7:08am

yes, as suggested by Donald. seems like you are running different instance of MWS over different instance of DB.

please check this for upgrading your database component.

Migrate My webMethods Server Data

Go to the My webMethods Server_directory\server\default\config directory and make
sure the mws.db.xml file exists.
On the machine on which you installed the Database Component Configurator, go to
the webMethods_directory\common\db\bin directory and open a command window.
Migrate the My webMethods Server database component by running this command:

dbconfigurator.{bat|sh} –a migrate –d {oracle|sqlserver|db2luw} –c MyWebMethodsServer –v latest –l db_server_URL –u existing_db_user –p password –fv 20

Make sure the MWS_CONFIG and MWS_CONTENT tables exist in the 7.1.2 My
webMethods Server database component.
Start My webMethods Server.

Rahul_Gupta2 · December 17, 2008, 12:08pm

Donald and Lion ,
You are both spot on.
The problem was due to different versions of Database Component configurator and MWS. In this case ,
Database Component configurator was 7.1.1 and MWS was 7.1.2.

Mws_config table used by MWS 7.1.2 is created only by Database Component configurator 7.1.2.
So installed Database Component configurator 7.1.2 which created the database components and MWS 7.1.2 started without a glitch.

Thanks a bunch Donald and Lion for your inputs.

Thanks & Best Wishes,

Topic		Replies	Views
Unable to start MWS in webMethods 8.2 webMethods , Integration-Server-and-ESB , webMethods-Archive	4	2140	September 3, 2021
MWS installation - should it be this hard? webMethods , webMethods-BPMS , MWS-CAF-Task-Engine	19	10191	April 2, 2021
MWS Giving Multiple Errors while starting up webMethods , webMethods-BPMS , MWS-CAF-Task-Engine	3	2174	April 2, 2021
MWS Configuration -Define Environment webMethods , webMethods-BPMS , MWS-CAF-Task-Engine	3	2004	April 2, 2021
Unable to start MWS 7.1 webMethods , webMethods-BPMS , MWS-CAF-Task-Engine	8	2652	April 2, 2021

MWS instance doesnt start

Related Topics