BookmarkSubscribeRSS Feed
shoin
Lapis Lazuli | Level 10

RFW project node 1.0, sat spinning (usually 5 min run time) and resulted in an error symbol and an empty log. 

 

I checked the middle tier SASServer11_1 and SASServer8_1 had Risk context initialization hanging.  Re-started the platform, now both JVM initialized properly (server.log), yet the quote above is still occurring. All relevant logs (gemfire, wrapper.log, etc. are clean...)

 

Any idea?

 

TIA

S

2 REPLIES 2
RamsesSalinas
Fluorite | Level 6
Have you checked with other browser?
shoin
Lapis Lazuli | Level 10

Actually it was an issue with the HTTP sys driver that due to a WIN update package, changed the "Start" value in the WIN registry to enable (value 3) from 4 (disabled) as port 80 was used in the configuration (cringe).  The clue began with cache locator delay and time out to form a quorum > although the web app rendered and allowed login any code submitted did not register in obj spawn logs/workspace server logs (also pooled) (set to debug).  The request was not being sent plus local access logs remained static.  Looked in WIN registry of middle tier server 

 

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP  > Start value was 3 (enabled),

 

Stopped cache locator service on compute machine > on middle tier node, had to reset to 4, bounce the server > started cache locator again on compute node and then re-started middle tier.

 

I hope this helps someone.

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
  • 2 replies
  • 555 views
  • 0 likes
  • 2 in conversation