- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
After resetting the password of internal account Sasadm@saspw sastrust@saspw in compute/metadata. We are unable to update the
password in mid tier for sastrust@saspw, we are getting the below error
cho] CFG-WAS: Results from command: "/usr/opt/WebSphere7/AppServer/bin/wsadmin.sh" -wsadmin_classpath "/usr/opt/SAS/SAS92/Lev1/Web/Temp/WebSphere/classpath/sas.core.jar" -conntype SOAP -host XXXXXXXXX-port 8879 -lang jython -f createDataSource.jy
[echo] Return code: 105
[echo] *sys-package-mgr*: processing modified jar, '/usr/opt/SAS/SAS92/Lev1/Web/Temp/WebSphere/classpath/sas.core.jar'
[echo] WASX7023E: Error creating "SOAP" connection to host "XXXXXXXXXX"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Unable to find a valid IP for host XXXXXXXXXX]
[echo] WASX7213I: This scripting client is not connected to a server process; please refer to the log file /usr/opt/WebSphere7/AppServer/profiles/SASDmgr01/logs/wsadmin.traceout for additional information.
We have started all the services in computer/metadata server. Also unable to start the remote services getting the below error:-
Received error while starting the application.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'discoveryService' defined in class path resource [jps-config.xml]: Invocation of init method failed; nested exception is com.sas.services.InitializationException: Unable to open a connection to the SAS Metadata Server on "XXXXXXXXXXXXX:8561". [ com.sas.services.ServiceException: Unable to open a connection to the SAS Metadata Server on "XXXXXXXXXXXXX:8561". [ com.sas.metadata.remote.MdException: Access denied. [ org.omg.CORBA.NO_PERMISSION: Access denied. ] ] ]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1337)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(AccessController.java:219)
Please advise. We have verified all the encrypted password in config/xml files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
In a similar scenario I would try a clean restart.
And if that does not work, would contact SAS Tech Support at the earliest.
If you have had a complete restart, then better to contact SAS Tech Support at the earliest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
we are trying to restart services after changing password of sastrust and sasadm,
metadata and compute services are up and running
However we are unable start the remote services its throwing the below error
Unable to open a connection to the SAS Metadata Server on "XXXXXXXXXXXXX:8561". [ com.sas.services.ServiceException: Unable to open a connection to the SAS Metadata Server on "XXXXXXXXXXXXX:8561". [ com.sas.metadata.remote.MdException: Access denied. [ org.omg.CORBA.NO_PERMISSION: Access denied. ] ] ]
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I hope you are running SAS 9.4. SAS Remote services not running should not be a show stopper.
I have servers running SAS 9.4 with remote services stopped.
See the following statement from SAS documents and that will help you understand things better.
"SAS Remote Services are not used by SAS 9.4. Although SAS Remote Services are still available to support custom applications, SAS Remote Services are not started by default."
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
OK
Approaching SAS Tech Support is what I would recommend.