Problem Uploading Encrypted BITS to Library Server.

Hello. I am really hoping someone can help me, as I am completely stuck.

I have a HyperV cluster of 3 servers, who's VHD files are located on a scale-out file server over a 10GbE link. The VMs are running fine. But the fileserver, is also the VMM Library server. All of a sudden, I can no longer upload ISO resources into the library using the encrypted BITS method. I am certain I have all of the necessary permissions, because when I go un-encrypted, everything works fine.

However, when I try encrypted, I get the following error:

The library server certificate is not available on the client running the application. Try contacting

      the administrator to install the certificate in the trusted people store of machine account or run the

      client with local machine administrator privileges (Elevated) or try the transfer with -AllowUnencryptedTransfer parameter.

Run the client (Cmdlet/Admin Console) with elevated administrator privileges.

ID: 24364

I have searched on this error and cannot find much. I have made sure the library server's certificate is in the trusted people store of the VMM management server. I have also tried restarting the VMM management server.

Not sure where to go from here....

Any help would be greatly appreciated.

October 27th, 2014 3:25pm

Hi, I'm trying to fix the same error. Did you ever get an answer?
Free Windows Admin Tool Kit Click here and download it now
December 3rd, 2014 3:18pm

Hi.

I've just fixed similar problem.

1. Try to start VMM Console with elevated privileges, then try to upload ISO in the library.

2. If you've got an error " Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information " you should compose a configuration file to VMM Console and place it here - C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin

Filename - VmmAdminUI.exe.config

<?xml version ="1.0"?>
<configuration>
    <startup useLegacyV2RuntimeActivationPolicy="true">
                <supportedRuntime version="v4.0" />
    </startup>    
</configuration>

July 17th, 2015 9:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics