vCheck keep prompting for credential

[vmk2014]

HI All,

When i'm trying to run the vCheck as batch file, but it still promoting for credential though i have stored the credential using the command.

New-VICredentialStoreItem -Host USvc1 -User domain\myvmk -Password Password@123

Thanks

V

[LucD]

And those are exactly the same User and Password you use on Connect-VIServer and in the popup window?

Any funny characters in the user or password?

On the Connect-VIServer did you place the user and password between single quotes?

[vmk2014]

HI LucD,

And those are exactly the same User and Password you use on Connect-VIServer and in the popup window? - Yes same user id and password

Any funny characters in the user or password? - No user name will be first letter of name and surname first 4 letter followed by number 1 to 10.

On the Connect-VIServer did you place the user and password between single quotes? Nope.

Thanks

V

[LucD]

Can you try with the single quotes?

[vmk2014]

Ok LucD,

It doesn't throws an error now after using the single quotes between the password.

Connect-VIServer <VC Name>  -user Domain\abc  -password 'xyz123'

Do i need the set the  credential store same way ? ok i added password in single quotes and it didnt prompted for credential window this time but it throws an error and report generate blank after running batch file.

thanks

V

[LucD · Accepted solution]

Ok, that means the credential issue is solved.

Rests the error message.

I suspect that your PowerCLI installation might be corrupt.

To confirm that, can you do the following

Get-View -ViewType HostSystem

Does that return your ESXi nodes without an error?

If it does, the next step I would like to try is to remove your current PowerCLI version completely.

Is this on the 11.3 station or on the 6.5 R1 station?

Pick one.

[vmk2014]

Ok, that means the credential issue is solved. Yes, for only power Cli version 11.3.0 but not for 6.5.0.  it still prompts for credential. I have remove store file also. But i'm either way fine whichever version works for me.

Rests the error message.

I suspect that your PowerCLI installation might be corrupt.

To confirm that, can you do the following

Get-View -ViewType HostSystem

Does that return your ESXi nodes without an error? see above.

If it does, the next step I would like to try is to remove your current PowerCLI version completely. - Can you share completely to remove and re-install new

Is this on the 11.3 station or on the 6.5 R1 station?  It station 11.3

Pick one.

Thanks

V

[LucD]

Ok, since this is on the 11.3 station, you could just install the latest version.

Install-Module -Name VMware.PowerCLI -Confirm:$false -Force -AllowClobber

Get-Module -Name VMware* -ListAvailable

That last line should show that there are 2 versions installed, 11.3 and 12.0

[vmk2014]

LucD,

I was thinking to close the thread here because i was feeling bad becuase even after installing it throws same error but when i tried to different vcenter it worked smoothly.

It seems something with the vCenter. Any idea why its failing for in other vCenter. Tomorrow, i will try to schedule Task scheduler and hope it wil work because my batch job is working.

Thanks

V

[LucD]

I have seen that message being mentioned a couple of times.

Most of the times it was for a specific vCenter (as in your case).

I would suggest to open a SR with VMware.

And yes, PowerCLI is supported.

If GSS comes with the remark that you need a Developer Support contract for PowerCLI, point them to PowerCLI Support Breakdown

[vmk2014]

LucD,

Finally, i was able to resolve other vCenter as well . It was due to FQDN missing in connection plugin. Also, Sequence element error still showing and its seems power cli need to  do clean uninstall.

Thanks

V