Hi, I get this errror when upgrading the vCenter applicance from 6.5 to 6.7
Has anyone had this before or any ideas on how to fix it.
Error
Resolution
Good morning!
We recently upgraded from 7.6 to 7.8 (Running vCenter 6.7U2a w/ vSAN) and are seeing two different and intermittent provisioning errors:
VC_FAULT_FATAL - Unexpected error occurred while monitoring VC task updates
and
VC_FAULT_FATAL - The name 'a workstation name' already exists
For the task updates one, I have verified that all the services are happily running on the vCenter. I can't seem to find anything really interesting in the connection broker or vCenter logs.
For the "already exists" scenario, I see where the VM does exist within vCenter (powered off) but the logs seem to indicate a new/different ID for it. We do currently have the "Allow resuse of pre-existing computer account" enabled but am not sure if that's a contributing factor. In this case, the best fix seems to be to delete the VM from vCenter and then let ViewDBChk clean everything up on the connection broker.
Has anyone seen similar issues/behaviors?
VMware Horizon View Blast Secure Gateway
The service is in a suspended state, and an error is reported after clicking recovery. First time installation, please help me.
Windows Server 2016 X64
New windows, first install VMware-viewconnectionserver-x86_64-7.5.0-8583568.exe
windows event information:
1.Started C:\Program Files\VMware\VMware View\Server\appblastgateway\run-absg.cmd for service VMBlastSG in C:\Program Files\VMware\VMware View\Server\appblastgateway\.
2.Program C:\Program Files\VMware\VMware View\Server\appblastgateway\run-absg.cmd for service VMBlastSG exited with return code 0.
3.Killing process tree of process 9448 for service VMBlastSG with exit code 0
4.Killing PID 9448 in process tree of PID 9448 because service VMBlastSG is stopping.
5.Service VMBlastSG action for exit code 0 is Restart. Attempting to restart C:\Program Files\VMware\VMware View\Server\appblastgateway\run-absg.cmd.
6.Registry key AppParameters is unset for service VMBlastSG. No flags will be passed to C:\Program Files\VMware\VMware View\Server\appblastgateway\run-absg.cmd when it starts.
7.Service VMBlastSG ran for less than 1500 milliseconds. Restart will be delayed by 256000 milliseconds.
C:\ProgramData\VMware\VDM\logs\Blast Secure Gateway\absg.log information:
[2018-07-06 12:17:13.143] [INFO] 188 [absg-master] - Node.js version: v6.14.1
[2018-07-06 12:17:13.146] [INFO] 188 [absg-master] - ABSG configuration: { PlayStoredLog: [Function],
fipsMode: false,
destHttps: true,
localPort: 8443,
localAddr: '0.0.0.0',
localHttps: true,
localHttpsCipherSpec: '!aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES',
localHttpsProtocolLow: 'tls1.1',
localHttpsProtocolHigh: 'tls1.2',
hmacAlgorithms: [ 'sha1', 'sha256' ],
enableUDP: false,
localUDPPort: 8443,
localUDPAddr: '0.0.0.0',
externAddr: '127.0.0.1',
externPort: 8443,
externHttps: true,
externDomain: '',
adminAddr: '127.0.0.1',
adminPort: 8123,
autostart: false,
logReplaceConsole: true,
logLevel: 'INFO',
logFilesize: 8388608,
logBackupCount: 16,
logFilename: 'C:\\ProgramData\\VMware\\VDM\\logs\\Blast Secure Gateway\\absg.log',
logTraceUDP: 0,
certificateStore: 'windows-local-machine',
certificateFolder: 'MY',
certificateName: 'vdm',
productMode: true,
displayConfig: true,
maxUriLength: 2083,
requestTimeout: 120000,
sessionIdleTimeout: 60000,
webSocketSessionIdleTimeout: 120000,
removeUserAgentHeader: false,
addProxyAgentHeader: true,
removeJSessionId: false,
allowMany2OneAccess: false,
allowManyRoutesToDest: true,
ipProtocol: 'IPv4',
useExternalForwarder: true,
labelGenerationMaxRandomAttempts: 10000,
auxFlowLabelPrefixGenerationMaxRandomAttempts: 10000,
auxFlowsAllowed: true,
externalForwarderFlowCleanUpPeriodSec: 600,
externalForwarderFlowCleanUpEnabledMainFlow: true,
externalForwarderFlowCleanUpEnabledAuxFlow: true,
logPath: 'C:\\ProgramData\\VMware\\VDM\\logs\\Blast Secure Gateway',
https: {},
localOnlyAddr: '127.0.0.1',
anyInterfaceAddr: '0.0.0.0',
numWorkers: 8,
hideToken: false,
doLoadbalance: true,
pidWidth: 7,
externalForwarderPath: 'C:\\Program Files\\VMware\\VMware View\\Server\\appblastgateway\\udpforwarder.exe',
numUDPWorkers: 0,
udpVersion: 1,
isTraceEnabled: false,
isDebugEnabled: false }
[2018-07-06 12:17:13.175] [ERROR] 188 [absg-master] - keystoreutil.exe failed to load certificate from [ 'windows-local-machine', 'MY', 'vdm' ] 1 Failed to acquire private key handle (error 2148073492)
I am trying to go through few hoops to get to it and finally will get it, but wondering if anyone already know how to get the cluster name or object of a ESXi host. I would like to avoid getting all hosts and get hold of it. As I have the host obj already in hand I would like to see if I can get it quickly than searching in the collection of all ESXi hosts.
Guys,
I've just started playing around with powershell. I have PowerCLI installed on directly on the vCenter. I login to vCenter server (Windows 2008 Server) using RDP and open the PowerCLI prompt and run the following command
Connect-VIServer server (I use thr FQDN).
It never failed to connect however I have just started receiving the followig errors when I try to connect
"Could not connect using the requested protocol".
As far as I'm aware nothing has changed and I dont know why its not workionganymore.
Any suggestions?
Using Google Chrome 72.0.3626.121 (Official Build)(64-bit) on Windows 10 generates the following when browsing to https://<vRA instance>:8283/vco-controlcenter/ :
Your connection is not private
Attackers might be trying to steal your information from <vRA instance> (for example,
passwords, messages, or credit cards). Learn more (chrome-error://chromewebdata/#)
NET::ERR_CERT_AUTHORITY_INVALID
[Hide advanced] [Reload]
<vRA instance> normally uses encryption to protect your information. When Google
Chrome tried to connect to <vRA instance> this time, the website sent back unusual and
incorrect credentials. This may heppen when an attacker is trying to pretend to be
<vRA instance>, or a Wi-Fi sign-in screen has interrupted the connection. Your information
is still secure because Google Chrome stopped the connection before any data was
exchanged.
You cannot visit <vRA instance> right now because the website uses HSTS. Network errors
and attacks are usually temporary, so this page will probably work later.
This seems to be relatively new, meaning that it has worked in the past but we don't know when it stopped working. If we use the Chrome "thisisunsafe" trick then we are able to bypass this error.
Anyone know what is causing this error how how to fix it?
Symptoms:
My guest is: rhel69 2.6.32-696.el6.x86_64
Host is: Windows 10 Enterprise 1809
I understand that all those gamers prefer the mouse to stay grabbed inside,
but could someone else help me please (do you find it annoying?)?
Hi,
My organisation writes monitoring software and we're creating a plugin to support vCenter. Can someone please tell me what the minimum set of permissions are for a read-only API user? It would appear the read-only role does not have API access. Any help would be greatly appreciated.
Cheers
Author : jacquiew
Topic Name : VMware Horizon HTML Access User Guide
Publication Name : VMware Horizon HTML Access User Guide
Product/Version : VMware Horizon HTML Access/5.0
Question :
how do I add server to access remote desktop
Hello Guys,
I know I am a little bit late to the party, I am just learning PowerCLI and automating as much as I can. My need is to export hosts and clusters ESXIs full path like below:
vCenter1
Datacenter1
Europe/host1
Africa/host1
Africa/host2
Aisa/host1
America/host1
Datacenter2
Australia/host1
New Zealand/host1
New Zealand/host2
So basically I need command to export to excel the output like:
datacenter1/Europe/host1
datacenter1/Africa/host1
datacenter1/Africa/host2
datacenter1/Aisa/host1
datacenter1/America/host1
datacenter2/Australia/host1
datacenter2/New Zealand/host1
datacenter2/New Zealand/host2
I have been trying with Get-View and Get-VMHost but nothing seem to return what I am looking for.
Are there hands-on-labs or documentation on installing & configuring Microsoft SQL for use by vCenter Server 6.7 and Horizon View 7?
I know I could go with the vCenter appliance, but I'd still need to stand up a SQL server for Horizon, and so I'd be in the same boat. I don't have SQL DBA experience, and the instructions in the normal vCenter installation guide clearly expect a decent working knowledge of MS SQL.
Thanks!
Jim Winner
I am working on Windows 10 Pro, VMware Workstation Pro 15 and ESXi 6.7 update 2 on Dell 7520 laptop. I understand this might not be officially support from hardware perspective. But let me explain:
1. First of all I was able to create a nested ESXi from Workstation. Then create VM (Linux) from this nested ESXi.
2. Few days later after I shut down the laptop few times none of the VM in ESXi can be powered on. After 10 min or so it gives PSOD with 'The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.' popup box.
3. If I power off the EXSi or even remove it and recreate it, it won't work either
4. If I uninstall and reinstall Workstation, it won't work
5. Only I re-image my Windows OS it will start working again but fails few days later. This pattern has been for a month and I have re-do my OS three times already
Any suggestions and ideas where I can start investigating?
Thanks,
I am having a recent problem with Horizon app on Mojave 10.14.5 where it will not log in and gives the error "Error in add connection - reason null". This began after my update to Mojave however, it will work on another macbook running Mojave 10.14.3. I am really hoping someone would be willing to help me figure this out prior to having to downgrade the OS again. I have tried going through my employer IT department however, due to it being a personal device they provide no assistance. I have attached a log file from my macbook below. The horizon app works on my other mackbook, ipad, iphone, etc. just not on this specific macbook. I appreciate any help figuring this out and thank all in advance.
Ever since the host and guest machines are upgraded to Windows 10 1903, the guest machine is no longer displaying battery status.
We get a disabled icon in the status bar and shows that the battery level is 255%.
I'm running the latest version of Workstation Pro (15.1.0).
Добрый день! недавно на ESXi 6.7.0 Update 2 (Build 13644319) получил предупреждение:
This host is potentially vulnerable to issues described in CVE-2018-3646, please refer to https://kb.vmware.com/s/article/55636 for details and VMware recommendations.
В статье описана уязвимость процессоров intel и решение этой уязвимости путем обновления vCenter, всех гипервизоров в кластере и включении функции ESXi Side-Channel-Aware Scheduler
1. Может ли bugfix ESXi670-201808401-BG (2018 года) отсутствовать в моем ESXi 6.7.0 Update 2 (Build 13644319) ???
2. При поиске на https://my.vmware.com/group/vmware/patch нужного мне ESXi670-201808401-BG я нахожу только ESXi670-201808001
3. При попытке наката этого непонятного ESXi670-201808001 на гипервизор с помощью
команды ( esxcli software vib install -d "/vmfs/volumes/Lun_001-vol-001_dx200-IpCores/dst/ESXi670-201808001.zip " )
я получаю лог ошибок:
Кто-нибудь сталкивался с этим?
Hi Vmware community,
I'm having a huge problem with a vm hosted on a 5.1 Esxi free.
I’ve deleted 2 old snapshots then created a new one before doing a huge upgrade of the CRM installed on that VM.
But after doing the (powered off) new snapshot, the VM didn’t start anymore !
I’m having a white non-blinking underscore in the top left corner.
And OF COURSE, I have no up to date backup !!!
Watching at the events, I saw I’m having an issue with the deleted snapshots. The files are still there (SRV-SAG-00001.vmdk, SRV-SAG-00002.vmdk …), but not anymore in the snapshot UI !
And now I can see the Esx complaining about a consolidation needed form that VM.
So I tried to do that consolidation, with the UI and in command line, but it failed each time at the end.
I tried to add/delete a new snapshot (UI/cmd), but it failed.
I’ve installed a Vcenter appliance to manage the esxi host and tried to clone the VM, but it also failed again.
I’ve realized that the *.vmsd file was nearly empty, so I recreated it, without more success.
My situation is really bad now, I need some help.
Anyone?
When SAP Logon client is provisioned on a server 2016 machine and attached to a server 2016 machine the title bar is messed up as follows:
is should appear as follows:
If installed locally on a server 2016 machine the title bar appears as it should.
When SAP Logon client is provisioned on a windows 10 machine and attached to a windows 10 machine the title bar appears as it should.
Any ideas on how to resolve this would be appreciated
Thank you
Hi there,
I am confused with all materials that I found. What I want to achieve is:
I have one physical disk on top of which datastore is created (VMFS 6). I want to remove that disk, move to another server (different ESXi installation), mount it and be able to see and access all files on this datastore in new ESXi (same version - 6.7).
Is this possible? What are the correct steps to properly umnount the datastore and then mount it again in new installation?
In regards to the last question, in the "New datastore" wizard I cannot see good option to achieve this. I can only create new VMFS datastore which basically erase all existing content on this disk (attachment) and this is not what I am looking for as I want to preserve it's content.
I have a vcenter 6.7 with vrealize operation 6.7.
When i try to connect on vcenter the plugin of vrealize a receive connection failed. I try with ip and name but same issue. I have a correct vrealize instance and work fine with vcenter.
So this is more of a general question/puzzling issue than a problem. In the interest of brevity, I kept the discussion title short, so here's full issue:
We have 4 standalone servers pertinent to this discussion (we'll call them Host 1, 2, 3, and 4). Hosts 1 and 2 have the same CPUs. Hosts 3 and 4 have CPUs from different families (so 3 different CPU families in total). Hosts 1 through 3 had been running ESXi 6.0 for a while and we were able to live migrate vms between them. We upgraded Host 3 to 6.5, and we still able to live migrate between hosts 1 through 3. We re-purposed one of our other on-prem servers and installed 6.7 U1 on it, giving us Host 4. We were able to live migrate vms from Host 3 to Host 4, so we cleared Host 3 off and shut it down (our license is only for 6 CPUs). Then, when we tried live migration from Host 1 or Host 2 to Host 4, it didn't work. I resuscitated Host 3 with an evaluation license thinking it would work as a man-in-the-middle until I could get Hosts 1 and 2 cleared off, but now we aren't able to perform live migration between any hosts except 1 and 2.
TL;DR: Hosts 1, 2 and 3 running ESXi 6.0 used to be able to live migrate vms between them, but after introducing Host 4 running 6.7 U1, only Hosts 1 and 2 can do it now.
I understand that the best solution would be to add the hosts into an EVC enabled cluster (or get another server with a matching CPU) but if we can get everything shuffled around to the point that we can upgrade all our hosts to 6.7 U1, then add them to a cluster, that would be ideal.