I have the same problem, no explanation...
One client of mine that is running 6.0.1 is having the same issue. I have a ticket open with VMware and it is now in the developers hands. There is a lot of pressure on them to resolve as a lot of customers are experiencing this same issue.
I will update as soon as I get a resolution.
Thanks for your responses on this.
I've got to say though. I'm really disappointed with the amount of bugs that we've seen in the 6.0 release. "It will be fixed in the next version" is wearing thin as an excuse here.
I will put in a support call today as well and see what happens.
Turns out this is a new bug to do with the locale of the IAAS server. I had to change everything to English (United States).
Control Panel > Region and Language:
Format: English (United States)
Location: United States
Administrative > Language for non-Unicode programs: English (United States)
Apparently it will be fixed with the 6.1 release.
Hope that helps (if you haven't already got the same response from support)
thanks a lot - it works!!!!!
I have to change the settings on all IaaS servers in a ditributed install? Model Manager Data/Web, Dem orchestrator, Dem Workers?
I think the Model Manager Server should be enough.
Model Manager Web is enough, since WAPI (the API which VCAC -VA accesses IaaS ) is the component affected by locale.
Check out this blogpost I wrote about this issue, as i've found a useful undocumented system-url along the way...
Just wanted to report that the issue is still there in 184.108.40.206, I did not have it in 6.0.0.
Thanks for providing a resolution!
Not sure if this is implied or not but simply applying the required changes to the IaaS Server was not enough to remedy the issues we were having with the WAPI DateTime string conversion.
We discovered we also needed to change the Language Settings or Preferences at the web browser level on the "client" end by adding, or moving up in the order of preference, English (United States) [en-US] as well. It's believed this was required in order to synchronize calls being made to the WAPI Application. This additional workaround may not be required on all vCAC 6.X instances but this immediately resolved our VM Edit failures within the vCAC Portal. We're currently running vCAC 6.1 (Build 2041200). This was confirmed using both Chrome (v.33) and IE (v.11).
Hope this helps.
After having just opened an SR with GSS on this, we received confirmation that will be resolved in vRealize Automation Version 6.2.
I;m running vRA 6.2 and I've got this problem as well. Doesn't seem like they've fixed it. It's not good, as we can't be expected to have everything set to the US.
Has anyone else (on non-US settings) had this issue in 6.2?
Besten Dank für Ihre Nachricht.
In der Zeit vom 16.03 - 20.03 bin ich abwesend. Während meiner Abwesenheit können Ihnen folgende Inventx Mitarbeitende weiterhelfen:
Fragen zu Microsoft email@example.com
In der Zwischenzeit wünsche Ihnen eine gute Zeit und freue mich Ihnen nach meiner Abwesenheit wieder zur Verfügung zu stehen.
Microsoft System Engineer
IT Services & Operations
T 081 287 1730 M 079 793 05 17
Grabenstrasse 19 · 7000 Chur
Haldenstrasse 23 · 8306 Brüttisellen
Try and reproduce the error in firefox and chrome... It would only work in firefox for me.
It was down to the browser locale, client side.
What is your browser locale set to? US?
Still fails for me in all browsers (IE, Chrome, Firefox).
My locale is UK, as it should be. My question is, has VMware fixed the issue in 6.2 like they said they would? Doesn't look like they have.