BackupEngine.exe -a Fails RRS feed

  • Question

  • I am unable to run BackupEngine.exe -a from the command line.  It fails on both my computers.  If I run it from the GUI by clicking Backup Now, it runs fine.  I know that the Backup Now from the gui runs via a different executable, but the BackupEngine.exe -a should also work with no issue.  Here is what my log looks like:

    Created at 2/27/2010 8:46:34 PM
    ***** Started at 2/27/2010 8:46:34 PM ***
    ***** Started at 2/27/2010 8:46:34 PM ***
    [1]100227.204634.8381: Status: Start
    [1]100227.204639.4433: Status: Exception: ClientException
    [1]100227.204639.4433: Status:          : Win32Exception
    [1]100227.204639.4433: Status:          : The credentials supplied to the package were not recognized
    [1]100227.204639.4433: Status:          :    at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
       at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
       at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
       at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
       at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation)
       at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost)
       at Microsoft.HomeServer.Backup.Protocol.TlsWrapper..ctor(Stream netStream)
       at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.StartTls()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()
    [1]100227.204639.4473: Status: Bytes sent=0, bytes received=0, 0 reconnects
    Sunday, February 28, 2010 1:51 AM

All replies

  • Which operating system are you using?
    Would it run from an elevated command prompt (open cmd As Administrator)? Or if you did so, instead using a non elevated command prompt?
    (The message points to an issue with the credentials.)
    If you did this already, would it help to assign the local Administrator account on the client the same password as the WHS console password?
    Best greetings from Germany
    Sunday, February 28, 2010 9:24 AM