BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
1 ACCEPTED SOLUTION

Accepted Solutions
carl_sommer
SAS Employee

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

View solution in original post

7 REPLIES 7
gwootton
SAS Super FREQ
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.
--
Greg Wootton | Principal Systems Technical Support Engineer
Musheer1
Fluorite | Level 6

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.'.

carl_sommer
SAS Employee

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

gwootton
SAS Super FREQ
If the Metadata Server is already running, it would explain why a new one cannot start, as the port would already be in use.
--
Greg Wootton | Principal Systems Technical Support Engineer
Musheer1
Fluorite | Level 6

All services are not started yet 

Musheer1
Fluorite | Level 6

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:

Musheer1_0-1754550598849.png

 

 

andreas_lds
Jade | Level 19

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

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
  • 7 replies
  • 524 views
  • 3 likes
  • 4 in conversation