Starting CMC from command line


In order to start and stop a service via command line within a windows environment,

 write the command line as follows:

Starting :
net start bobjcentralms

Unlike stopping via command line:
net stop bobjcentralms

Comments

Post a Comment

Popular posts from this blog

SAP HANA Introduction

Image
SAP HANA:The future of database technology The capacity of main memory in servers has continuously increased over the years, whereas prices have dramatically dropped. Today, a single enterprise class server can hold several  terabytes of main memory. At the same time, prices for server main memory dramatically  dropped over the last few decades. This increase in capacity and reduction in cost makes it a  viable approach to keep huge amounts of business data in memory. This section discusses  the benefits and challenges. In few words you can understand SAP HANA plus  analyzing this evaluation: Typical access speeds Disk     4,000,000 ns Memory         0.4 ns Speed   10,000,000 Falling prices move processing from Disk/SSD to In-Memory In-Memory Computing The elements of In-Memory computing are not new. However, dramatically improved hardware economics and  technology innov...
Read more

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=G-NL0CYP13VZ"></script> <script>   window.dataLayer = window.dataLayer || [];   function gtag(){dataLayer.push(arguments);}   gtag('js', new Date());   gtag('config', 'G-NL0CYP13VZ'); </script> Cannot find the BusinessObjects Enterprise report source. (LO 26608) Environment SAP BO XI 4.1 SP 5 two nodes Cluster Windows Server 2012 While refreshing dashboard (based on Live Office connection) from BI Launchpad with a no administrator user the above exception was erased. SAP says: Cause The document is not available; for example it does not exist, or it has been removed. Action Check the report path from CMS and use SetLocation in Live Office to re-define the report source. Otherwise, check if the user has sufficient rights to view the object. Solution In our case  we fixed this problem was to remo...
Read more

Error FWM 00001 Transport error: Communication failure.

Environment BO XI R 3.1 SP 4 On logging on Desktop Intelligence,  the following error occurs:  SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001) Cause The client could not talk to the Server . This is the main  reason.  1)SYSTEM:6400(J2EE) means you are using 3 tier Desktop Intelligence which happens through web works fine as there is no firewall in between.  2)SYSTEM:6400 is 2 tier login and your firewall is blocking the connection.  The first one is a key that gets created when you modify or create a new Desktop Intelligence document from Infoview, that is 3-tier. The second one is you entering manually the information for 2-tier. Others Possible causes of the problem are: The server may be down. There may have been a network communication problem. The request my have timed out. Could be also a database connectivity issue between the CMS server and the ...
Read more