1. Support
  2. Knowledge base
  3. 100001033

Status 58 can't connect to a Windows client

Article: 100001033
Last Published: 2010-01-22
Ratings: 0 1
Product(s): NetBackup & Alta Data Protection

Problem

GENERAL ERROR: Status 58 can't connect to a Windows client

Error Message

GENERAL ERROR: Status 58 can't connect to client

Solution

ISSUE:
GENERAL ERROR:Status 58 can't connect to client

ENVIRONMENT/CONDITIONS:
This issue hasbeen known to occur on Windows Client when the machine has run out ofnon-interactive desktop heap or has a memory issue of some kind. Typically theclient may work for several days then start getting status 58 errors.

EVIDENCE:
bpcd log fromthe client:
01:09:59.389[6560.6920] <4> bpcd valid_server: hostname comparison succeeded
01:09:59.577[6560.6920] <2> bpcd main: output socket port number = 1
01:10:02.374[6560.6920] <2> get_long: (2) premature end of file (byte 1)
01:10:02.374[6560.6920] <2> get_vnetd_forward_socket: get_string ipc_string failed:5
01:10:02.374[6560.6920] <16> bpcd main: get_vnetd_forward_socket failed: 23

SOLUTION/WORKAROUND:
Rebooting theclient will resolve the issue for a short time, however the issue could be theresult of the client running out of Non-interactive Desktop HeapMemory.
The issue isbetter seen if you connect to the problem host via RDP using the -console switchto see the problem program's/systems's pop up errors.
Suggestion isto increase the desktop heap setting on the client server-
HKEY_LOCAL_MACINE\SYSTEM\CurrentControlSet\Control\SessionManager\SubSystems\
TypeREG_EXPAND_SZ:
Value:Windows
Originalwindows key:
%SystemRoot%\system32\csrss.exeObjectDirectory=\ Windows SharedSection=1024,3072,512 Windows=OnSubSystemType=Windows ServerDll=basesrv,1ServerDll=winsrv:UserServerDllInitialization,3ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

New:
%SystemRoot%\system32\csrss.exeObjectDirectory=\Windows SharedSection=1280,4096,1280 Windows=OnSubSystemType=Windows ServerDll=basesrv,1ServerDll=winsrv:UserServerDllInitialization,3ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=32

Changed was:
SharedSection=1024,3072,512to SharedSection=1280,4096,1280
and
MaxRequestThreads=16to MaxRequestThreads=32

This doesrequire a reboot of the client server.
Here is a linkto Microsoft Articles on the issue. Once corrected that should allow propercommunication again.

Follow thefollowing article and Microsoft Q Article to address the memoryissues.
<https://support.microsoft.com/default.aspx?scid=kb;en-us;184802>
<https://support.microsoft.com/default.aspx?scid=kb;en-us;Q126962>





Was this content helpful?

Article Languages