I'm having similar issue with viewplanner 3.0 which I recently setup. From the user guide it mentioned View Server is optional. I created a new pool manually from the View Connection Server and provisioned a few desktop vms, as I thought by creating those desktops VMs manually, ViewPlanner agent is no longer required to be installed on View Server. Please correct me if I'm wrong.
Thanks for your help in advance.
No, View server setup is not optional if you are going to do runs with View PCoIP. It is optional if you are only planning to do local mode run or RDP runs.
Please let me know the sections in the user guide if it was not very clear and we can make sure to get it corrected.
You need to install View Planner agent in View server using a local administrator account and the prefixes error should go away once you restart the vdiappd service on the harness and repeat the run.
Please let us know if you still see any issues.
Aha! Thanks heaps for that. I am going to do runs with View PCoIP.
The user guide page 17, 20 and 21 (Figure 1, Figure 2 and Figure 3), it shows View Server (optional) - that's probably why I got confused. I thought it's optional for all runs.
Thanks again for your help.
I installed the View Planner agent in View Server using local admin account and that worked fine now. Thanks heaps for your help!
I am having this same issue with View Planner 3.0 running Remote tests. Is there anything else that could cause this issue besides not having the View Server agent installed as Local Admin. Maybe a bad password or typo somewhere.
What do you get when you run "python c:\listener.pyc" on View server?
Also, can you attach the viewplanner.log from /root/ViewPlanner directory of the harness?
Thanks for the response, I am good now, it may have been a duplicate machine name for the Client machine.
Hey All, getting the same thing when trying to the described "Single-VM-remote-PCoIP" run.
When I run python c:\listener.pyc on the View connection server I also get the "string indices must be integers, not str" error message.
Previous to this the View Planner service wouldn't start because C:\IP.txt wasn't created during the install, so I made it as thus. I'm thinking this may be part of the problem...what is supposed to be in that file?
Rebooting View connection server & planner appliance
made sure view planner service was running on View connection server
Downloading the attached files aforementioned in this thread and replacing them on the connection server, restart
uninstalling the view planner files, rebooting, redownloading, reinstalling the View planner files
Changing the view planner configuration to be IP rather than hostname for vCenter and View
Few things I want to check:
- Are you using VP 2.1?
- Is domain AD name not like domain\user in IP.txt file, it should be just user.
- If you are using View 5.2, a registry change is required with VP 2.1 to make it to work and there are some patch files also needed.
Hey banit, I'm using VP 3.0, 1229598.
Correct, the AD name is simply the username, no fancy notation.
I am using View 5.2 with VP 3.0, is there something outside of the instructions I need to apply here?
Did you install the VP agent in View server as administrator? Can you open View power-shell and run "Get-Pool" command and see if that works?
I have one question regarding linked clone pool of desktops when trying to perform a Multi-VM View Planner Test.
Problem is that linked clone desktops don't have attached second 1GB disk with all test files. What I am doing wrong ?
Should I use vCenter to deploy desktop VMs instead of View ?
Sorry, "waiting for prefixes map error" disappeared suddenly after you SYSPREPped, regenerate View Connection Server SID and log off and on into domain? Or maybe you did something else?
I've tried this method but I'n not sure that SID was regenerated.