topic Re: faild to start SASMeta- metadata Server Service after a Backup Restoration in Administration and Deployment

faild to start SASMeta- metadata Server Service after a Backup Restoration

Musheer1 — Wed, 06 Aug 2025 13:14:28 GMT

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

gwootton — Wed, 06 Aug 2025 13:29:02 GMT

When the Metadata Server fails to start, it should still create a log file in <SASConfig>\Levn\SASMeta\MetadataServer\Logs (default path). That log would contain any errors causing the startup failure.
If no log is created, you may need to check the Windows Event Viewer for the failure.

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

Musheer1 — Wed, 06 Aug 2025 13:38:15 GMT

Host: 'SASS01', OS: 'WIN', Release: '10.0', SAS Version: '9.04.01M7P08052020', Command: '"E:\SASHome\SASFoundation\9.4\sas.exe" -config "E:\SASConfig\Lev1\SASMeta\MetadataServer\sasv9.cfg" -servicename "SAS [SASConfig-Lev1] SASMeta - Metadata Server"'
Log continued from E:\SASConfig\Lev1\SASMeta\MetadataServer\Logs\SASMeta_MetadataServer_2025-05-25_SASS01_8696.log
2025-08-06T11:48:06,806 INFO [07001443] 1094054:SYSTEM@SASS01 - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers.
2025-08-06T11:48:06,830 INFO [07000757] 1094672:SYSTEM@SASS01 - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers.
2025-08-06T11:48:06,832 INFO [00000007] :SYSTEM@SASS01 - NOTE: 20250806:11.48.06.81: 07001443:NOTE: The tcpSockRead call failed. The system error is 'The connection was reset by a peer.'.
2025-08-06T11:48:06,852 INFO [07001443] 1094054:SYSTEM@SASS01 - The Bridge Protocol Engine Socket Access Method was unable to read peer data.
2025-08-06T11:48:06,913 INFO [07000757] 1094672:SYSTEM@SASS01 - The Bridge Protocol Engine Socket Access Method was unable to read peer data.
2025-08-06T11:48:06,913 INFO [00000007] :SYSTEM@SASS01 - NOTE: 20250806:11.48.06.83: 07000757:NOTE: The tcpSockRead call failed. The system error is 'The connection was reset by a peer.'.

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

carl_sommer — Wed, 06 Aug 2025 13:47:39 GMT

This is not the startup log for the metadata server, as noted by the "log continued" line

@Musheer1 wrote:

Host: 'SASS01', OS: 'WIN', Release: '10.0', SAS Version: '9.04.01M7P08052020', Command: '"E:\SASHome\SASFoundation\9.4\sas.exe" -config "E:\SASConfig\Lev1\SASMeta\MetadataServer\sasv9.cfg" -servicename "SAS [SASConfig-Lev1] SASMeta - Metadata Server"'
Log continued from E:\SASConfig\Lev1\SASMeta\MetadataServer\Logs\SASMeta_MetadataServer_2025-05-25_SASS01_8696.log
2025-08-06T11:48:06,806 INFO [07001443] 1094054:SYSTEM@SASS01 - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers.
2025-08-06T11:48:06,830 INFO [07000757] 1094672:SYSTEM@SASS01 - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers.
2025-08-06T11:48:06,832 INFO [00000007] :SYSTEM@SASS01 - NOTE: 20250806:11.48.06.81: 07001443:NOTE: The tcpSockRead call failed. The system error is 'The connection was reset by a peer.'.
2025-08-06T11:48:06,852 INFO [07001443] 1094054:SYSTEM@SASS01 - The Bridge Protocol Engine Socket Access Method was unable to read peer data.
2025-08-06T11:48:06,913 INFO [07000757] 1094672:SYSTEM@SASS01 - The Bridge Protocol Engine Socket Access Method was unable to read peer data.
2025-08-06T11:48:06,913 INFO [00000007] :SYSTEM@SASS01 - NOTE: 20250806:11.48.06.83: 07000757:NOTE: The tcpSockRead call failed. The system error is 'The connection was reset by a peer.'.

There should be other logs in that E:\SASConfig\Lev1\SASMeta\MetadataServer\Logs directory, one of which is the startup log.

Carl Sommer - SAS Technical Support

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

gwootton — Wed, 06 Aug 2025 14:15:23 GMT

If the Metadata Server is already running, it would explain why a new one cannot start, as the port would already be in use.

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

Musheer1 — Thu, 07 Aug 2025 06:17:43 GMT

All services are not started yet

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

Musheer1 — Thu, 07 Aug 2025 07:10:10 GMT

The issue was related to license as the backup restore to a date before the license renewal date. However, I am facing a new issue while starting the share Server:

Re: faild to start SASMeta- metadata Server Service after a Backup Restoration

andreas_lds — Thu, 07 Aug 2025 09:08:27 GMT

Reading the logs is recommended. Most times the reason for a failed start can be found there.