BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
AzizZouargui
Calcite | Level 5

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

BStone
Obsidian | Level 7

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.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 16 replies
  • 8604 views
  • 1 like
  • 7 in conversation