This post is more than 5 years old
7 Posts
0
218021
June 26th, 2014 13:00
vWorkspace 8.0MR1 Powershell Error - Failed to locate permission for target
I've installed the version 8.0.306.0029 of the Powershell Module for vWorkspace and am seeing an issue with New-QVWManagedApplication cmdlet. I've specified all of the parameters according to the cmdlet wiki but it comes back with the message below pointing to an issue with targets. I couldn't find anything in the cmdlet reference relating to targets so I'm not sure what I'm doing wrong.
Below is the syntax I used and the result. I've tried leaving off a number of parameters but have gotten the same result.
New-QVWManagedApplication -Name "Powershell Test" -SessionHost P14TS4 -Path "C:\Program Files\Internet Explorer\iexplore.exe" -InitialWindowState Normal -SeamlessWindowMode vWorkspace -Enabled $True -LoadBalancingSetting NotSpecified -SessionSharingEnabled $True -DisplayName "Powershell Test" -farm "vworkspace database"
New-QVWManagedApplication : Failed to locate permission for target [PN_PERM_TARGET_MANAGED_APPLICATIONS] and action
[PN_PERM_ADD_APPS] .
At line:1 char:1
+ New-QVWManagedApplication -Name "Powershell Test" -SessionHost P14TS4 -Path "C:\ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-QVWManagedApplication], KeyNotFoundException
+ FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,Quest.vWorkspace.PowerShell.Clients.NewQVWManagedApplicationCommand
If it helps our environment has been 8.0 since launch with 2012 Gateway, IIS, Management and Broker servers with 2008R2 Session Hosts. I've installed the PowerShell module on one of the Management servers with .Net 4.0 and PowerShell 3 as required.
DELL-Andrew W1
378 Posts
0
August 8th, 2014 07:00
Hi,
Dev didn't find any thing interesting in that log.
If you have access to SQL Management Studio, please navigate to your pnadmin.dmdefinedpermissions table and select the top1000 rows.
If there are only a few defined permissions, please post a screenshot. If there are hundreds, export the lot to CSV and then we'll have to find a way of getting it across to me.
Thanks, Andrew.
DELL-Andrew W1
378 Posts
0
July 8th, 2014 03:00
Hello,
This works fine in my lab.
It looks like you don't have permissions to do the task - who are you running the Powershell as ?
Thanks, Andrew.
briangoudy
7 Posts
0
July 21st, 2014 15:00
I'm a domain administrator and in the vWorkspace Admins group, both of which are in the vWorkspace Administrators list. Domain Admins is also in the local administrators group on the server. The database user is pnadmin and I use my credentials when connecting to the farm, and I'm running PowerShell as administrator.
I'm installing the module onto a 2008R2 server to see if it changes anything but the reboot will have to wait until afterhours.
DELL-Andrew W1
378 Posts
0
July 22nd, 2014 05:00
How did your test go ?
briangoudy
7 Posts
0
July 22nd, 2014 07:00
No change. I had to reboot after installing the Windows Management Framework but I'm getting the same error as before. I've attached a screen snip showing that I'm connected to the farm, the command I'm running, and the results of Get-QVWAdministrators.
I feel like there's something really simple that I must be missing.
briangoudy
7 Posts
0
July 22nd, 2014 10:00
No change. I had to reboot after installing the Windows Management Framework but I'm getting the same error as before.
I feel like there's something really simple that I must be missing.
DELL-Andrew W1
378 Posts
0
July 23rd, 2014 01:00
Good Morning,
Can you start from the beginning but add this line in:
Start-QVWLogging –File C:\MyLog.txt –Level All
This should tell us more detail about what is failing.
Thanks, Andrew.
briangoudy
7 Posts
0
July 23rd, 2014 09:00
Here are the log entries:
CurrentFarm: Using explicit farm.
CurrentFarm: Using explicit farm.
CurrentFarm: Using explicit farm.
CurrentFarm: Using explicit farm.
Adding the current business object to the datastore.
A minute has passed since the last permission validation. Validating permission set.
The permission set is invalid. Reloading permission set.
Administrator GMT\vWorkspace Admins has 104 defined permissions
Administrator GMT\Domain Admins has 0 defined permissions
Administrator gmt\gmtbgoudy has 0 defined permissions
I noticed the lines which show "0 defined permissions" but since the vWorkspace Admins group has 104 definitions and I'm a member of that group.
I have someone else trying it with different credentials to see if he sees anything different as well.
DELL-Andrew W1
378 Posts
0
July 23rd, 2014 14:00
Hello,
I've sent the log off to one of our Powershell gurus.
I'll let you know when they reply - let me know how your colleague gets on with the other account.
Thanks, Andrew.
briangoudy
7 Posts
0
March 13th, 2015 13:00
Andrew,
I lost track of this one for a while. I'm attaching the results of the table you requested but it's all GUIDs.
briangoudy
7 Posts
0
March 13th, 2015 13:00
Andrew,
I lost track of this one for a while, but I've attached the results of the table you requested.
Brian