topic Re: SAS 9.4 configuration failure at stage 11 in Administration and Deployment

SAS 9.4 configuration failure at stage 11

maheshtalla — Wed, 20 May 2015 06:50:41 GMT

Hi,

I'm installing and configuring SAS 9.4 on mid-tier server. I already installed all components and now doing configuration process. I'm getting error as below screen shot during stage 11:Start Web applications and not able to continue with configuration of SAS Web application server and error says that Application server has started, however web applications with following context failed to start. Can some one please help to resolve this issue and proceed further.

Thanks in advance,

Regards

Maheswara Talla

9980014060

Re: SAS 9.4 configuration failure at stage 11

Kurt_Bremser — Wed, 20 May 2015 07:20:18 GMT

If the log file is not helpful in getting a clue by yourself, open a track with SAS TS, and include the log file.

Re: SAS 9.4 configuration failure at stage 11

maheshtalla — Wed, 20 May 2015 08:25:45 GMT

yes I have done that parallely. but still i didn't get any solution

Re: SAS 9.4 configuration failure at stage 11

Kurt_Bremser — Wed, 20 May 2015 08:30:30 GMT

Did inspecting the log reveal anything?

Re: SAS 9.4 configuration failure at stage 11

maheshtalla — Wed, 20 May 2015 08:35:40 GMT

Not able to get from the log which is as below

[appserverTarget] 2015-05-19 09:49:13,120 [main] INFO com.sas.appserver.vfabrictcsvr.Server - Waiting for port (8080) to open on address (servername)[appserverTarget] 2015-05-19 09:49:23,124 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable(Servername) >>>

[appserverTarget] 2015-05-19 09:49:23,125 [main] INFO com.sas.appserver.utils.PortUtils - isAvailable=false

[appserverTarget] 2015-05-19 09:49:23,125 [main] INFO com.sas.appserver.utils.PortUtils - isPortAvailable() <<<

[appserverTarget] 2015-05-19 09:49:23,514 [main] INFO com.sas.appserver.vfabrictcsvr.Server - Server SASServer1_1 started successfully.

[appserverTarget] 2015-05-19 09:49:23,514 [main] INFO com.sas.appserver.vfabrictcsvr.Server - testServer() >>>

[appserverTarget] 2015-05-19 09:49:23,514 [main] INFO com.sas.appserver.vfabrictcsvr.Server - getFailedApps() >>>

[appserverTarget] 2015-05-19 09:49:28,986 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASLogon context failed to start

[appserverTarget] 2015-05-19 09:49:28,988 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASPreferences context failed to start

[appserverTarget] 2015-05-19 09:49:29,026 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASContentServer context failed to start

[appserverTarget] 2015-05-19 09:49:29,032 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASBIPortlets context failed to start

[appserverTarget] 2015-05-19 09:49:29,033 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASBIWS context failed to start

[appserverTarget] 2015-05-19 09:49:29,033 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASAuthorizationServices context failed to start

[appserverTarget] 2015-05-19 09:49:29,034 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASPortal context failed to start

[appserverTarget] 2015-05-19 09:49:29,036 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASPrincipalServices context failed to start

[appserverTarget] 2015-05-19 09:49:29,039 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASJSR168RemotePortlet context failed to start

[appserverTarget] 2015-05-19 09:49:29,040 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASBIDashboard context failed to start

[appserverTarget] 2015-05-19 09:49:29,041 [main] ERROR com.sas.appserver.vfabrictcsvr.Server - Webapp with SASBIDashboardEventGen context failed to start

[appserverTarget] 2015-05-19 09:49:29,041 [main] INFO com.sas.appserver.vfabrictcsvr.Server - getFailedApps() >>>

[appserverTarget] 2015-05-19 09:49:29,093 [main] INFO com.sas.appserver.utils.AppServerException - /en_US/AppServerMessages.properties does not exist.

[appserverTarget] 2015-05-19 09:49:29,095 [main] INFO com.sas.appserver.vfabrictcsvr.Server - testServer() - Throwing AppServerException

[appserverTarget] 2015-05-19 09:49:29,095 [main] INFO com.sas.appserver.vfabrictcsvr.Server - testServer() <<<

[appserverTarget] 2015-05-19 09:49:29,113 [main] INFO com.sas.sdw.SDWExceptionHandler - handle() >>>

[appserverTarget] 2015-05-19 09:49:29,113 [main] INFO com.sas.sdw.SDWExceptionHandler - handleSDWException() >>>

[appserverTarget] 2015-05-19 09:49:29,113 [main] INFO com.sas.sdw.SDWExceptionHandler - target=startMidtierServers, task=com.sas.sdw.SDWExceptionHandler

[appserverTarget] 2015-05-19 09:49:29,113 [main] INFO com.sas.sdw.SDWExceptionHandler - message=Application Server has started, however web applications with the following contexts failed to start. Please refer to Application Server logs for more details.</br><ul><li>SASLogon</li><li>SASPreferences</li><li>SASContentServer</li><li>SASBIPortlets</li><li>SASBIWS</li><li>SASAuthorizationServices</li><li>SASPortal</li><li>SASPrincipalServices</li><li>SASJSR168RemotePortlet</li><li>SASBIDashboard</li><li>SASBIDashboardEventGen</li></ul>

[appserverTarget] 2015-05-19 09:49:29,114 [main] DEBUG com.sas.sdw.ant.AntSDW - Invoking Ant Macro: setConfigStatusFile with 3 parameters.

Re: SAS 9.4 configuration failure at stage 11

Kurt_Bremser — Wed, 20 May 2015 08:42:42 GMT

The next step should be to inspect the application server logs. That's usually server.log in the configured directory of the jboss (at least I think that you're running jboss, from the SASServer1_1 notation). Could be that the apps are not deployed, or are deployed to a different context (our application server was configured as SASServer1)

Re: SAS 9.4 configuration failure at stage 11

EyalGonen — Wed, 20 May 2015 18:03:25 GMT

KurtBremser is right.

From my experience web apps don't deploy due to some other SAS service that did not start correctly (like Cache Locator) or some external problem like communication errors, etc.

The server.log should explain the problem very well

Re: SAS 9.4 configuration failure at stage 11

Kurt_Bremser — Thu, 21 May 2015 05:54:59 GMT

From my experience with SAS 9.2 on UNIX, YMMV:

The SAS web services need the SAS Remote Services to run. This is done with a separate script that resides in LevN/Web/Applications/RemoteServices. When that fails, everything else will fail.

So once the services start, ps -ef|grep Remote should reveal two java processes, one being the Remote Services and the other being jboss, which has a reference to the Remote Services in its commandline.

Newer SAS versions may/will have a different setup.

Re: SAS 9.4 configuration failure at stage 11

SASKiwi — Thu, 21 May 2015 22:33:08 GMT

This may sound like a dumb question but I'm assuming that you have already installed and configured the SAS metadata and application servers and these are running when you install your SAS mid-tier server?

Also SAS 9.4 has its own web server so no third-party web server like JBoss is required.

Re: SAS 9.4 configuration failure at stage 11

maheshtalla — Fri, 22 May 2015 04:18:16 GMT

Yes I have installed and configured SAS metadata and application servers and error i'm getting while configuring mid-tier. Exactly there is no tird-party webserver in SAS9.4

Re: SAS 9.4 configuration failure at stage 11

maheshtalla — Fri, 22 May 2015 04:22:04 GMT

in 9.2 on unix what you are telling is correct. but in 9.4 i cann't see any remote services running currently. in 9.4 web services are dependent on cache locator and i can see its running and up.

Re: SAS 9.4 configuration failure at stage 11

SASKiwi — Fri, 22 May 2015 05:30:49 GMT

I had a look at our SAS 9.4 install scripts and your job seems to be failing when it tries to configure web server SASServer11_1 immediately after successfully configuring SASServer1_1.

I would check to see you have the scripts for this server in a directory similar to this: \\SASWebServerName\SAS\Config\Lev1\Web\WebAppServer\SASServer11_1

Re: SAS 9.4 configuration failure at stage 11

Carus — Fri, 22 May 2015 13:01:27 GMT

Ensure you have followed the pre-installation steps for the Mid Tier

Pre-Installation Steps for SAS 9.4 Middle Tier

You may need to increase the nofile and nproc further than what is recommended.

Re: SAS 9.4 configuration failure at stage 11

maheshtalla — Mon, 25 May 2015 07:32:52 GMT

I have increased ulimits as mentioned in pre-installation steps.

Re: SAS 9.4 configuration failure at stage 11

maheshtalla — Mon, 25 May 2015 08:55:24 GMT

Hi all,

I'm able to find the solution and completed configuration part as per below. Hope this will help for some one.

1) I have recovered the metadata server on compute tier to the initial stage to the point before I started Mid-tier server configuration.

2) Restarted the Comput server.

3) Deleted the existing config/Lev1 directory on Mid-tier and

4) restarted configuration part from starting.

Re: SAS 9.4 configuration failure at stage 11

AzizZouargui — Mon, 09 May 2016 17:29:23 GMT

Solved the problem is with IIS and apache server they are using same port 80 to fix it

you have to stop iis first

second go to service and start Apache 2.29 service manual

and let the retry and works fine and after that start IIS again

Thanks

Aziz

Re: SAS 9.4 configuration failure at stage 11

BStone — Fri, 12 Aug 2016 15:14:10 GMT

Saw this and thought I'd clarify my experience, especially when using a clustered Mid-Tier writing to the same Data Server on Compute.

By default prostgres is configured on compute with 256 max connections, upping this to 512 will resolve the issue when starting the JVMs.

Note, when you get stuck on stage 11 (Starting Web Application Server), make the change in WIP Data server and restart WIP Data Server. stop any JVMs that is running on the server you are configuring and hit retry.

Restarting is fine, but the problem will not be resolved especially when you have scheduled restarts of JVMs.