Hi,

Thanks for reading this thread.

I have installed wM8 on a lab server and it has been working fine for few weeks. I am now trying to install My webMethods as part of it and although the installation was successful (no errors encountered) I am not able to get My webMethods to run be it I start it from Windows services or from command line using the batch “E:\SoftwareAG\MWS\server\default\bin\run.bat”.

The error I get is “java.sql.SQLException: No suitable driver found”. The database is up running and accessible; and already configured for My webMethods with DB Configurator. :uhoh:

We use SQL Server 2005 and I wonder were we should put the DB driver jar file (sqljdbc4.jar) for My webMethods to find it. The install is in the default path, i.e. “E:\SoftwareAG\MWS\server\default”. I tried copying the jar file in the lib folder (“E:\SoftwareAG\MWS\lib”) but that did not work. :sad:

Does anyone know where I should put the jar file or what I need to do to get My webMethods working?

Thanks for your help

Hi, did you check the file
C:\webMethods7\MWS\server\default\config\mws.db.xml

Sometimes DB Configurator write wrong the url. I had a problem where DB Conf. wrote
jdbc:wm:sqlserver://WEBMETHODSVMSQLEXPRESS;databaseName=WM
instead of
[COLOR=blue]jdbc:wm:sqlserver://WEBMETHODSVM[/color]SQLEXPRESS;databaseName=WM

Regards!

There is no need to put explicit client classes.jar file for MWS to connect to DB, the only thing you need to do/check the db.xml as pointed in above post. Make sure it point to correct url… you should be good to go.

Thanks for the help :). My webMethods did screw the URL and as soon as I fixed it it looked like starting but for some reason it crashes after a while.

After I start MWS from Window services, I go to the URL (http://localhost:8585) and i get the error “HTTP ERROR 503. Problem accessing /. Reason: SERVICE_UNAVAILABLE”. This is probably due to the fact My webMethods hasn’t completed the start, but after 5 minutes the service shuts down.:eek:

When I start the service from command prompt, it goes through million iterations and ends up being shutdown too. The last of the errors are as follow (please note the 2 lines in red):

2010-09-14 09:43:05 NZST (Framework:INFO) - Skipping: wm_discussion_board.war because it depends on: [wm_xt_discotres_category.pdp, wm_xt_discotres_forum.pdp]
2010-09-14 09:43:05 NZST (Framework:INFO) - ERROR installing: wm_discussion_board.war. Required component is not installed or available for install: wm_xt_discotres_category.pdp
2010-09-14 09:43:05 NZST (Framework:INFO) - Installing: wm_noodle.war (99%) …

2010-09-14 09:43:05 NZST (Framework:INFO) - Skipping: wm_noodle.war because it depends on: [wm_xt_usertabset.pdp, wm_xt_user_prefs_type.pdp, wm_xt_workspace.pd
p]
2010-09-14 09:43:05 NZST (Framework:INFO) - ERROR installing: wm_noodle.war. Required component is not installed or available for install: wm_xt_usertabset.pdp

2010-09-14 09:43:05 NZST (Framework:INFO) - Installing: wm_noodle_pack.war (100%) …
2010-09-14 09:43:05 NZST (Framework:INFO) - Skipping: wm_noodle_pack.war because it depends on: [wm_xt_imagefolder.pdp, wm_xt_workspace.pdp, wm_xt_attachments_
folder.pdp]
2010-09-14 09:43:05 NZST (Framework:INFO) - ERROR installing: wm_noodle_pack.war. Required component is not installed or available for install: wm_xt_imagefold
er.pdp
2010-09-14 09:43:05 NZST (Framework:INFO) - Installing: wm_tn.war (100%) …
2010-09-14 09:43:11 NZST (Framework:INFO) - Skipping: wm_tn.war because it depends on: [wm_xt_saved_search.pdp]
2010-09-14 09:43:11 NZST (Framework:INFO) - ERROR installing: wm_tn.war. Required component is not installed or available for install: wm_xt_saved_search.pdp
2010-09-14 09:43:11 NZST (Framework:INFO) - INSTALLED 0 components in 187 seconds
2010-09-14 09:43:11 NZST (Framework:INFO) - Initializing component: com.webMethods.portal.bizPolicy.biz.install.impl.SyncDeployService
2010-09-14 09:43:11 NZST (Framework:INFO) - Loading phase: [phaseID, phaseName] [startupComplete, startupComplete]
2010-09-14 09:43:11 NZST (Framework:INFO) - Initializing components of: startup Complete
2010-09-14 09:43:11 NZST (Framework:INFO) - Initializing component: com.webMethods.portal.system.PostInitStatus
2010-09-14 09:43:11 NZST (Framework:INFO) - My webMethods Server “default” Node “DNZPPPWMC10.chhnet.net-node1049” took 546 seconds to initialize
role: search
role: notification
role: autodeploy
role: taskengine
http listening at: DNZPPPWMC10.chhnet.net:8585
FrontEndUrl: http://DNZPPPWMC10.chhnet.net:8585

2010-09-14 09:43:11 NZST (Framework:INFO) - Initializing component: com.webMethods.portal.system.impl.SavePerfData
2010-09-14 09:43:11 NZST (Framework:INFO) - Initializing component: com.webMethods.jackrabbit.spi2mws.SearchIndexInitializer
2010-09-14 09:43:11 NZST (com.webMethods.jackrabbit.spi2mws.SearchIndexInitializer:INFO) - Initializing the search index synchronously
2010-09-14 09:43:11 NZST (Framework:FATAL) - [POP.001.0002] A “java.lang.NullPointerException” occurred with the Message "at com.webMethods.jackrabbit.spi2mws.
MwsRepositoryService._getVersionStorageFolderId(MwsRepositoryService.java:1098)"

java.lang.NullPointerException
at com.webMethods.jackrabbit.spi2mws.MwsRepositoryService._getVersionStorageFolderId(MwsRepositoryService.java:1098)
at com.webMethods.jackrabbit.spi2mws.MwsRepositoryService$2.run(MwsRepositoryService.java:423)
at com.webMethods.jackrabbit.spi2mws.MwsRepositoryService.startSearchIndex(MwsRepositoryService.java:446)
at com.webMethods.jackrabbit.spi2mws.MwsRepositoryService.initSearchIndex(MwsRepositoryService.java:357)
at com.webMethods.jackrabbit.spi2mws.SearchIndexInitializer.init(SearchIndexInitializer.java:33)
at com.webMethods.portal.system.init.impl.DefaultPhase$InitializableWrapper.init(DefaultPhase.java:126)
at com.webMethods.portal.system.init.impl.DefaultPhase.initComponent(DefaultPhase.java:107)
at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:601)
at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:169)
at com.webMethods.portal.system.init.impl.DefaultPhase.init(DefaultPhase.java:49)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initComponent(DefaultPhaseProvider.java:259)
at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:601)
at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:169)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializePhases(DefaultPhaseProvider.java:89)
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:53)
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:865)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:823)
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.portal.system.start.Main.start(Main.java:132)
at com.webMethods.portal.system.start.Main.main(Main.java:38)
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down PortalAxisServlet
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down PortalServlet
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down PortalServlet
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down PortalServlet
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down…
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down components of: MWS
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down components of: deploySync
2010-09-14 09:43:12 NZST (Framework:INFO) - Shutting down components of: webserver

Any idea why this is happening?

Thanks a lot

Hi, I’m sorry, I never see that error before.

looks like you really screwed up Have you installed TN UI’s?
May be try to delete the contents from the MWS\Server\Default\Temp directory and run it from from command prompt… if you stuck any errors post it again.

I knew I screwed it big time :biggrin:. I now have uninstalled MWS, then unconfigured the database with DB Configurator to get rid of MWS tables and views, I then reconfigured it for MWS, then I installed MWS without the components that relay it to Monitor and Deployer, i.e. I strictly only installed MWS server from all available MWS components. It is now working fine :crazy:. So I assume the problem was either an ill-configured database or the association with Deployer and/or Monitor . I will find out soon

Glad to know that you are on the go

Great!! I’m glad too. Thank you for let us know…