Running into a problem with our KACE 2000 box.  I need to update the Source Media for a couple of OS's, but each time I try I get an error - Error connecting to Hashstore Server.  When I look at the source media tab, I see an entry for the OS I was trying to load.

Example - if I put in - > Windows 7 with SP1 - I will see an entry in Source Media with that title, but the file size will be at zero bytes.  When I try to delete it (since it is at zero) I get this -> Cannot delete Source Media while it is being uploaded or in use by a background process.

I have to then reboot the K2000, delete the entry, and try again. 

Eventually the upload will work, after several attempts, so it is not a password issue.  Not sure if this problem is related to the upgrade.  We don't change the Source Media all that often, so it could have been present for a while.

Wondering if anyone has seen this issue?  I am going to open a support ticket as well.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

this is usually a network/proxy issue or something blocking you from access the share.

Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 10/04/2012 by: cserrins
Red Belt

  • We are not using a Proxy. I am on the same subnet as the device.
    • It is recommended that Media Manager be installed in a clean virtual machine that is not on the domain and does not have any anti-virus, firewall or security software on it.
      As a note, Media Manager uses port 8108 to communicate with the K2.

      Corey
Please log in to comment

Answers

1

you mentioned you just upgraded. 3.4?  If so, did you download the newer media manager from the kbox?

Answered 10/03/2012 by: SMal.tmcc
Red Belt

  • I have downloaded the newest Media Manager. Went to upload Windows 8.1 today, and received the error. Will probably open a ticket with Support.
  • Should also advise we have upgraded to 3.5 and this error still appears.
Please log in to comment
0
I got the same error when I tried to use the kbox name for the hostname, but it worked when I used the IP address. DNS reg correct, so a bit of a mystery.
Answered 09/15/2014 by: tpr
Fifth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity