Validating SASAppOA in SAS Management Console - How long should this take?

[JohnJPS]

I'm in SAS Mangement Console, Environment Manager > Server Manager > SASAppOA

Under there, I right-clicked "SASAppOA - Logical Workspace Server" and selected "Validate"

I am pushing two hours.  Is that normal, or is just spinning and unlikely to finish?

[JuanS_OCS]

Hi there @JohnJPS,

in case that "pushing" means "waiting" then it is not normal, otherwise we might need additional info about what "pushing" means.

A similar validation to that one, and normalli providing additional info, would be if you go to the host that has the SASAppOA, then go to Config/LevX/SASAppOA/WorkspaceServer and execute WorkspaceServer.bat or .sh, and read the logs.

[JohnJPS]

Sorry... yes, my wait is pushing two hours. Thanks for the tips.

Any damage to anything if I simply stop my Management Console task?

[PaulHomes · Accepted solution]

It should normally only take seconds. All it does it launch/connect to a SAS Workspace Server instance then run some simple code as a test. If it is taking minutes/hours then something is wrong. I would:

• Check the SAS Object Spawner log file to see if you can see the incoming connection and the attempt to launch the server, checking for errors and/or warnings.
• Check the SAS Management Console error log to see if there are any stack traces.
• Verify the load/activity on the machine(s) running the SASAppOA app server.
• Verify your connectivity from the machine running SAS Management Console to the machine(s) running the SASAppOA app server.

Is this a SAS Grid-based installation?

[JohnJPS]

Hi Paul,

Thanks for the tips.  Will certainly follow up on these as well. It is not a grid install, although we do have a very small (two node) cluster.

[PaulHomes]

If it's not grid then it should be a little easier to diagnose. As a 2 machine load balanced cluster then I would check SAS Object Spawner logs on both machines. The 2 spawners will also need to talk to each other to share load info and so I should also check the connectivity between the 2 machines - e.g. any firewall software blocking ports.