on ‎2018 Apr 18 2:47 PM
Hello Expert,
we recently installed the:CMS database with new data access driver for BI 4.2 SP3
link:https://wiki.scn.sap.com/wiki/display/BOBJ/Unlock+the+CMS+database+with+new+data+access+driver+for+BI+4.2+SP3
In D and Q environment we had no issue but when promoted in Production (connection, universe and report) we get this error while refreshing Webi report

Unable to retrieve network layer aliases : com.crystaldecisions.sdk.exception.SDKException$OCAFramework: Unable to find servers in CMS [server]:6400 and cluster [server] with kind pjs and service CS_CORBA_NetworkLayer. All such servers could be down or disabled by the administrator. (FWM 01014) cause:com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$AllServicesDown: Unable to find servers in CMS [server]:6400 and cluster [server] with kind pjs and service CS_CORBA_NetworkLayer. All such servers could be down or disabled by the administrator. (FWM 01014) detail:Unable to find servers in CMS [server]:6400 and cluster [server] with kind pjs and service CS_CORBA_NetworkLayer. All such servers could be down or disabled by the administrator. (FWM 01014) (Error: INF )
Any idea?
thanks so much for the support.
alessandro
Request clarification before answering.
Is this issue happening only with CMS DB , reports only or with any other reports based of any other reports? Can you make sure connection works in IDT?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
on your Production System, in CMC check if the servers are enabled or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I misunderstood what you are looking for.
You talked about the new CMS driver to access the repository.
So, to check if the driver is installed in production or not:
Under the directory "dataAccess\connectionServer" it should have a "cms" directory
and the file "cms.setup" under the directory "dataAccess\connectionServer\setup".
if not, then you can copy it from your other servers (QA, DEV), and restart the connection server.
or as Dell Stinnett-Christy said, install it with modify install
It's possible that the CMS db driver was not installed in production. You would have to do an Update Install to get it there.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Because this is a production system, it probably won't be easy. You have to go to Programs & Features and do a modify install, then look at the options for what to add to the install. I can't remember whether the CMS driver is in the list of database connection types or somewhere else, but it's pretty obvious what it is. If it isn't checked, then it hasn't been installed. If you have a cluster of app servers, you would have check this on every one of them.
If you have to get approval for an install in Prod, you would then just exist out of the modify install until you can get the approval to do the update.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since this universe is for Admins only, you don't need to deploy to PRODUCTION, since it require the repair the installer. You can use in QA or DEV, point the connection to PROD CMS DB, Published it in QA in different location.
| User | Count |
|---|---|
| 9 | |
| 7 | |
| 7 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.