It was working fine always, used to take not more than 5 mins. However, it started taking hours to start the SASServer1_1 after last month's Linux server patching activity. Although, no issues in start of services even after non-prod environment servers' patching ... View more

Hello @SASuser19,   it seems to me as you might be missing some java-jar libraries. The message mentions it is missing a class DisposableBean. Perhaps because the picklist of jar libraries is not correct.   For this question, I would definetely address it to SAS Technical Support. I expect the solution will be similar to this Problem Note http://support.sas.com/kb/46/234.html , but not this one because it solves another problem (similar problem, but not the same).  ... View more

Hello,   next time you will restart the SASServer1_1, try to delete/archive first the SASServer1_1\logs, \work and \temp folders content (you will clean what is chached). Then restart again.  If you do this, are you finding still the same problems? ... View more

@anja thank for your feedback. yes it after  applying the S63001 hotfix (http://ftp.sas.com/techsup/download/hotfix/HF2/S63.html#S63001)   environment info OS: win2012r2 (one tire) Product: SAS Enterprise Case Management 6.2_M1 Release: 9.4 TS1M2   note when I go to d:\SASHome\SASDeploymentManager\9.4\products\cfgwizard__94230__prt__xx__sp0__1\Utilities\configuration_scripts.xml :582 line as the error appeer in log file I see those lines        ... View more

Hi,   try the following:   See if you can find the following .jar files in the following directory: JBoss-home-directory/common/lib slf4j-api.jar slf4j-jboss-logging.jar    If they exist, remove these 3 files. Important is that you restart jboss afterwards. Try again and see if this helps.   Also:  PLEASE make backup copies of these files before deleting so you can copy them back if needed.   For more info see http://www.slf4j.org/codes.html#multiple_bindings   Thanks Anja ... View more

I have no experience with this product but the message suggests that to use SAS AML the user (sasdemo) needs to be set up in metadata to belong to a business unit. I suggest you would be best tracking this to SAS Tech Support as I doubt many users in the community have used this product. ... View more

can u also post your ISCAPABLE code? preferably the portion that u use for calling and defining. Eg. CASE and type and why you wanna use that. ... View more

Are you following the instruction in the Configuring One-Way SSL Authentication section in Configuring the JBoss Application Server for Secure Sockets Layer and Client-Certificate Authentication on SAS® 9.3 Enterprise BI Server Web Applications at https://support.sas.com/resources/thirdpartysupport/v93/appservers/ConfigureJBossforSSLandClient-CertAuthforSAS9.3.pdf   If so, I think you may have sasmc.ini and smc.ini mixed up in your statement "the pdf file say edit sasmc.ini file but it's not exist i only see smc.ini". The PDF (above) mentions smc.ini but in my installation the file is sasmc.ini (i.e. there is a typo in the PDF).   I have seen that PKIX message many times and it usually means that the server certificate offered by the web (application) server (JBoss in this instance) is not trusted, in that the required certificate-authority (CA) certificate in the chain of trust cannot be found in the JRE's trust store. There are 2 ways to resolve this 1) update the default JRE trust store JREHOME/lib/security/cacerts to add the CA cert so all applications using that JRE can use it or 2) direct a Java application to use a specific keystore using the javax.net.ssl.trustStore* system properties as describe in the SAS PDF on page 11   You can tell which JRE SASMC is using by looking in the sasmc.ini file. It usually refers to JREHOME which is defined in the included sassw.config in the SAS home dir (usually 2 directories above sasmc.ini). ... View more

Hi, I would do it manually. What you need is:     https://support.sas.com/resources/thirdpartysupport/v93/appservers/jbossdoc.html Configuring the JBoss Application Server for Secure Sockets Layer and Client-Certificate Authentication on SAS ® 9.3 Enterprise BI Server Web Applications Optionally: Configuring Apache HTTP Server as a Reverse Proxy Server for SAS ® 9.3 Web Applications Deployed on JBoss.   ... View more

I wasn't suggesting leaving it that way, just confirming the problem was a stale password entry. I'd open a track and provide the casemgmtmid_updatePassword*.log, hopefully a resolution can be found that way. ... View more

Thanks alot for all, I will starting configure SAS again. ... View more

Fot these kind of problems: 1: search support.sas.com for the key words in your log file, build failed etc 2: contact SAS tech support. ... View more

This points to a deeper problem. You already have a HTTP server running that listens on port 80. Make a decision: a) integrate SAS with the existing HTTP server b) remove the existing server and integrate the data into the HTTP server installed by SAS   I personally think that it is a bad idea to have two different HTTP servers (not two instances of the same server SW) running on one system I also think that it was a bad idea of the SAS people to use some obscure proprietary fork of apache instead of using the real thing. ... View more