Good call. I just tried it and unfortunately that did not do the trick. I think we are going to have to schedule a reboot of the app server to see if that changes anything.
On Tue, Jun 21, 2011 at 9:55 PM, Francois Seegers < franco...@blueturtle.co.za> wrote: > ** > > What about the mid-tier cache (flush), I sometimes manually clear the > mid-tier cache from the mid-tier>cache directory as I saw some arslist > techies stated that the flush does not always clear the cache.**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller > *Sent:* Wednesday, June 22, 2011 5:39 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Getting error: "BMCATRIUM_NGIE000204: Error getting data > stores"**** > > ** ** > > ** Hi Francois, > > > Thanks for the input. Yes we started it from the command line. We > verified that it was up an running by accessing the web interface ( > http://localhost:20000). > > So by design the Carte process does not start at server start up? This > doesn't seem right: > > 1) seems like a really poor design choice > 2) because the documentation doesn't state it has to manually be started, > only to start as a troubleshooting step it if it is not currently running > [but documentation bugs happen] > 3) we were able to access the Data Stores initially without having to start > the process manually. > > The Data Stores are still accessible through the AI console on our test > server, only production has this issue. > > Any other ideas? Since it is production we haven't had a chance to reboot > the server. I wonder if things will magically work again after a reboot? > (it is Windows after all) > > Jason**** > > On Tue, Jun 21, 2011 at 7:47 PM, Francois Seegers < > franco...@blueturtle.co.za> wrote:**** > > ** **** > > Hi Jason,**** > > **** > > Did you start the Carte process on the server where you installed the > Atrium Integrator Server component? It does not start automatically; you > have to start it manually using the port you use during the installation > which is 20000 by default.**** > > **** > > 1 - Open DOS > cd to directory where the Carte.bat file resides**** > > 2 - run the following "carte <servername> 20000"**** > > **** > > Hope this helps.**** > > **** > > Regards**** > > Francois**** > > **** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller > *Sent:* Tuesday, June 21, 2011 11:24 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Getting error: "BMCATRIUM_NGIE000204: Error getting data > stores"**** > > **** > > ** We are trying to manage our AI data stores via the Atrium Core Console > -> Integrator (7.6.04 SP1). When we click on the "Manage Data Stores" > button we receive the following error: *BMCATRIUM_NGIE000204: Error > getting data stores.***** > > Screen print: > https://communities.bmc.com/communities/servlet/JiveServlet/showImage/2-191885-18198/AI_DatastoreError.png > **** > > It worked fine for a few days after the 7.6.04 upgrade. Using the AI User' > Guide I found that the Carte process was not running on the AR/AI server. > Using the instructions I started it from the command line and verified the > kettle web interface is accessible but the Atrium console still throws the > error.**** > > Does anybody know what might be going wrong here?**** > > Here is the full error:**** > > Error occurred while executing BaseConnector.getConnectorListFromRep > at > com.bmc.atrium.ngie.connector.BaseConnector.getConnectorListFromRep(Unknown > Source) > at > com.bmc.atrium.lcds.ngie.NGIEDataSourceConfigurationPentahoService.getDataSources(NGIEDataSourceConfigurationPentahoService.java:83) > at > com.bmc.atrium.lcds.ngie.NGIEService.getDataSources(NGIEService.java:170) > at sun.reflect.GeneratedMethodAccessor1078.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:421) > at > flex.messaging.services.RemotingService.serviceMessage(RemotingService.java:183) > at > flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1503) > at > flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:884) > at > flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:121) > at > flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:158) > at > flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:44) > at > flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:67) > at > flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:146) > at > flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:278) > at > flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:322) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > com.bmc.atrium.web.AtriumServletDispatcher.dispatch(AtriumServletDispatcher.java:209) > at > com.bmc.atrium.midtier.RealAtriumWidgetPlugin.dispatchServlet(RealAtriumWidgetPlugin.java:227) > at > com.bmc.atrium.midtier.RealAtriumWidgetPlugin.processRequest(RealAtriumWidgetPlugin.java:141) > at > com.bmc.atrium.modulelauncher.AtriumWidgetPlugin.processRequest(AtriumWidgetPlugin.java:103) > at > com.remedy.arsys.plugincontainer.impl.PluginServlet.postPluginInfo(Unknown > Source) > at > com.remedy.arsys.plugincontainer.impl.PluginContainer.processRequestInfo(Unknown > Source) > at com.remedy.arsys.stubs.AuthenticationHelperServlet.doRequest(Unknown > Source) > at com.remedy.arsys.stubs.GoatHttpServlet.postInternal(Unknown Source) > at com.remedy.arsys.stubs.GoatHttpServlet.doPost(Unknown Source) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) > at > org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859) > at > org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:574) > at > org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1527) > at java.lang.Thread.run(Unknown Source) > > Thanks, > Jason**** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > ** ** > ------------------------------ > > Blue Turtle Technologies (Pty) Limited | Reg. no.: 2003/002610/07 | Tel: +27 > (0)11 206 5600 | Fax: +27 (0)11 206 5606 | http://www.blueturtle.co.za > Midridge Office Estate, International Business Gateway, cnr New Road & > Sixth Street, Midrand, 1685 | P O Box 31331, Kyalami, 1684 > > DISCLAIMER: This email and any files transmitted with it are confidential > and are intended solely for the use of the individual or entity to whom they > are addressed. This communication represents the originator's personal views > and opinions, which do not necessarily reflect those of Blue Turtle > Technologies (Pty) Ltd. If you are not the original recipient or the person > responsible for delivering the email to the intended recipient, be advised > that you have received this email in error, and that any use, dissemination, > forwarding, printing, or copying of this email is strictly prohibited. If > you received this email in error, please immediately notify the sender. > Thank you.**** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > ------------------------------ > Blue Turtle Technologies (Pty) Limited | Reg. no.: 2003/002610/07 | Tel: +27 > (0)11 206 5600 | Fax: +27 (0)11 206 5606 | http://www.blueturtle.co.za > Midridge Office Estate, International Business Gateway, cnr New Road & > Sixth Street, Midrand, 1685 | P O Box 31331, Kyalami, 1684 > > DISCLAIMER: This email and any files transmitted with it are confidential > and are intended solely for the use of the individual or entity to whom they > are addressed. This communication represents the originator's personal views > and opinions, which do not necessarily reflect those of Blue Turtle > Technologies (Pty) Ltd. If you are not the original recipient or the person > responsible for delivering the email to the intended recipient, be advised > that you have received this email in error, and that any use, dissemination, > forwarding, printing, or copying of this email is strictly prohibited. If > you received this email in error, please immediately notify the sender. > Thank you. > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
