/build/static/layout/Breadcrumb_cap_w.png

Why is KB Manipulator hanging on 'Mapping K2000'? I cannot build a KBE with KB manipulator

KB Manipulator is hanging during the 'Mapping K2000' process. K2000 Media Manager runs fine from the same machine and successfully builds my KBE. However, KB Manipulator will not create my KBE. If anyone has seen this before and has a solution that would be great!  I am running it on a Windows 7 VM, Iv'e tried reinstalling both Media manager and KB Manipulator with no success of fixing this issue.

4 Comments   [ + ] Show comments
  • I'm also having the same issue, since it prompted me to update KBE manipulator. Same this, but I've tried multiple machines as well. No Z drive mapped anywhere. - edavis1 6 years ago
  • Good to know, maybe I'll try to roll back to an older version of KBM. - jjvillani 6 years ago
    • Older version mapped drive fine but had an error regarding the user\xxx\appdata\temp\2\build directory. - jjvillani 6 years ago
  • FYI, I found KBM to work fine on a Windows 10 Box - jjvillani 6 years ago
  • I am also having issues where the KBE Manipulator it just sits on mapping drive. version is 3.7.1.25

    I have tried on a windows 7 and windows 10 machines both with PE3 and PE10 tools with no joy. - bobbinson 5 years ago
    • Bobbinson, see below and try what I did, it might work for you as well. - jjvillani 5 years ago

Answers (4)

Answer Summary:
Posted by: acox 5 years ago
White Belt
3

Top Answer

I am also having the same issue. Has anyone else ran into this issue, and resolved it?

Comments:
  • Did you ever find a solution for this? - jjvillani 5 years ago
  • I was able to fudge things to get it to work. I noticed that KBE Manipulator was running an application called get_network_drive.exe from the following directory: "C:\Users\USERNAME\AppData\Local\Temp\2\kbe_man". While the program was Hung on mapping drive, I reran the application as administrator and this seemed to pull it from the holding pattern it was in. Somewhat of a hokey solution but it worked for me twice. - jjvillani 5 years ago
  • I am hoping they come out with an Update soon to fix this... anyone listening.... anyone? - jjvillani 5 years ago
  • Was experiencing the same issue. Unfortunately it still hasn't been fixed, but your workaround did the trick. - JerradH 4 years ago
    • Jerrad, Glad I could help. - jjvillani 4 years ago
Posted by: fcaignard 5 years ago
White Belt
2
Hi All,

I also have the same issue.
By reading different posts on similar topics concerning KBEM issues, I found a workarround :
- run a CMD as administrator (same account than used to run KBEM) ;
- browse to the "%Temp%\kbe_man" folder : "cd %temp%\kbe_man" ;
- then run get_network_drive.exe.

The status windows messge should change from "Mapping K2000" to "Copying..."

Comments:
  • Thanks, Already posted that one. - jjvillani 5 years ago
Posted by: bobbinson 5 years ago
Senior Yellow Belt
0
They way I fixed the issue was to use the Manipulator on a vanilla VM which was not joined to the domain.

I believe a GPO was causing issues on our domain and this fixed it.
Posted by: chucksteel 6 years ago
Red Belt
-1
Make sure you don't already have a drive mapped to z:. The KBE Manipulator maps the K2000 share on that drive and it will fail if there is already a drive mapped. 

Comments:
  • Thanks Chuck, but that is not the issue. No existing mapped drives. This problem is strange because the Media Manager has no issue and I believe KBM uses the media manager. - jjvillani 6 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ