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
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.'.
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
All services are not started yet
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:
Reading the logs is recommended. Most times the reason for a failed start can be found there.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to explore data assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.