Web server don't start

[MariaD]

Hi folks, 

We have a really old server, I know is very old but we need to maintain for regulatory purpose. 

So, we have an environment with SAS 9.3 installed on 3 Unix servers. One for metadata, one for compute and one for web components. We received the following error when we tried to start the web server. The metadata server is up and it running. Same with compute server. We already boot, physically, the server but the problem persist. Any idea?

ServiceLoader - Unable to obtain service deployment from the SAS Metadata Repository metadata source.

PlatformServices - Exception encountered starting services defined in metadata source

om.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: No foundation service definitions were found using the metadata source:

Regards, 

[gwootton]

The messages you've provided appear incomplete, after "using the metadata source:" I would expect it to list the source. Does that information include the correct connection information for your Metadata Server?

[MariaD]

Thanks @gwootton . Follows the completed log:

2022-04-11 14:17:19,584 ERROR ServiceLoader - Unable to obtain service deployment from the SAS Metadata Repository metadata source.

2022-04-11 14:17:19,586 ERROR PlatformServices - Exception encountered starting services defined in metadata source 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxxxx"

port: "8561"

repository: "Foundation"

}

.

com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: No foundation service definitions were found using the metadata source: 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxxx"

port: "8561"

repository: "Foundation"

}

 ] 

at com.sas.services.deployment.ServiceLoader.deployServices(ServiceLoader.java:868)

at com.sas.services.deployment.PlatformServices.startLocalServices(PlatformServices.java:530)

at com.sas.services.deployment.PlatformServices.startServices(PlatformServices.java:485)

at com.sas.services.deployment.CorePlatformServices.startServices(CorePlatformServices.java:182)

at com.sas.framework.services.PlatformDiscoveryServiceFactoryBean.afterPropertiesSet(PlatformDiscoveryServiceFactoryBean.java:99)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:563)

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)

at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)

at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83)

at com.sas.framework.services.bootstrap.SASRemoteServices.main(SASRemoteServices.java:65)

Caused by: com.sas.services.ServiceException: No foundation service definitions were found using the metadata source: 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxxx"

port: "8561"

repository: "Foundation"

}

at com.sas.services.deployment.ServiceLoader.deployServices(ServiceLoader.java:821)

... 18 more

Received error while starting the application.

2022-04-11 14:17:19,592 FATAL SASRemoteServices - Error creating bean with name 'discoveryService' defined in class path resource [jps-config.xml]: Invocation of init method failed; nested exception is com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: No foundation service definitions were found using the metadata source: 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxx"

port: "8561"

repository: "Foundation"

}

 ] 

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'discoveryService' defined in class path resource [jps-config.xml]: Invocation of init method failed; nested exception is com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: No foundation service definitions were found using the metadata source: 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxx"

port: "8561"

repository: "Foundation"

}

 ] 

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:563)

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)

at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)

at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83)

at com.sas.framework.services.bootstrap.SASRemoteServices.main(SASRemoteServices.java:65)

Caused by: com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. [ com.sas.services.ServiceException: No foundation service definitions were found using the metadata source: 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxx"

port: "8561"

repository: "Foundation"

}

 ] 

at com.sas.services.deployment.ServiceLoader.deployServices(ServiceLoader.java:868)

at com.sas.services.deployment.PlatformServices.startLocalServices(PlatformServices.java:530)

at com.sas.services.deployment.PlatformServices.startServices(PlatformServices.java:485)

at com.sas.services.deployment.CorePlatformServices.startServices(CorePlatformServices.java:182)

at com.sas.framework.services.PlatformDiscoveryServiceFactoryBean.afterPropertiesSet(PlatformDiscoveryServiceFactoryBean.java:99)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1417)

... 12 more

Caused by: com.sas.services.ServiceException: No foundation service definitions were found using the metadata source: 

Server {

software component: "Remote Services"

group: "Stored Process"

group: "Core"

host: "xxxxxx"

port: "8561"

repository: "Foundation"

}

at com.sas.services.deployment.ServiceLoader.deployServices(ServiceLoader.java:821)

... 18 more

[gwootton]

Assuming the "xxxxxx" was obscured by you and prior to that contained the correct hostname for your Metadata Server, the error here seems to be saying it can't find the Remote Services component when querying Metadata. Do you see Remote Services in SAS Management Console under the Authorization Manager plugin's Resource Mangement/By Application folder?

[MariaD]

Thanks @gwootton . Yes, you're correct, the "xxxxxx" was obscured by me. 

As you can seen on the images below, the Remote Services appears on the mentioned folder. Regards, 

 

[gwootton]

It looks like the thing it's saying it can't find is there. That makes me think either it is failing to connect to Metadata at all (no network route, credentials incorrect), or the credentials being used to connect to Metadata do not have the necessary permissions to view that object.

You may wish to engage SAS Technical Support to help explore those possibilities.

[MariaD]

Thanks @gwootton . 

Is there any way to validate if we can reach the metadata server from the web server from the desired port? Something like ping or telnet...

And is there any way to valide the credentials used by the remote services? 

Regards, 

[gwootton]

For Linux servers you can use the netcat command to establish a test TCP connection (or telnet as you mentioned). On Windows the PowerShell Test-NetConnection has similar functionality.
I'm not very familiar with how the middle tier works in 9.3, I think Remote Services configuration path is <SASConfig>\Lev1\Web\Applications\RemoteServices, do the files there have the credentials?
You could also check the Metadata Server log to see if any connection attempts are coming in from the middle tier and as what user.