Skip to main content

Specified path was invalid (During Cluster creation for File Witness server)

Specified path was invalid (During Cluster creation for File Witness server)


Hey Guys, 
I just want to explain how small things can impact you while working on New cluster creation.
recently we were working on cluster creation and file witness share was not accepted by Cluster, After 
troubleshoot we come to know there were 2 issues one with Share permission and other is Security permission.

In our case we were using comman id for creating cluster and Id was having permission to login to server. 
but the same id was not part of administrator group on server where file witness share was created and in share permission also it was not showing listed hence cluster was not accepting file Path.

 Please make sure id under which you are ruing cluster services should be added in the security permission along with computer account which get created as cluster name.

 on a side note will like to inform you, You should give cluster name (computer account) which get created in AD should be part of group which has permission to do domain join (This will allow Cluster account to create and register AG in active directory).

Comments

Post a Comment

Popular posts from this blog

"kerberos: the specified credentials were rejected by the server", "unreachable": true" Ansible

Hello Friends, I was getting following Error while deploying my Ansible script, Basically my credential were getting rejected by server. SSH password: PLAY [Playbook_Name] ***************************************************************02:00:30 TASK [Gathering Facts] *********************************************************02:00:30 fatal: [Server_Inventory_Name]: UNREACHABLE! => {"changed": false, "msg": "kerberos: the specified credentials were rejected by the server", "unreachable": true} PLAY RECAP *********************************************************************02:00:30 Server_Inventory_Name    : ok=0    changed=0    unreachable=1   failed=0  It was resolved using one additional parameter in Inventory  i.e  "ansible_winrm_server_cert_vaildation:ignore"
1 comment
Read more

NBSUTIL commands

Frustrated with syntax finding hence decided to post all NBSTLUTIL related commands so people will not face same problem. Common SLP Related Commands Show EMM Image list of Images that were backed up to an SLP STU [ -I / -U ] nbstlutil list nbstlutil list –lifecycle <name> nbstlutil list –backupid <id_value> nbstlutil list -image_state <value> nbstlutil list -copy_state <value> nbstlutil list -frag_state <value> nbstlutil list –mediaid <media_id>_–state 3 Activate /Inactivate SLP operations nbstlutil inactive –lifecycle <lifecycle name> nbstlutil inactive –backupid <backupid> nbstlutil active –lifecycle <lifecycle name> nbstlutil active –backupid <backupid> Cancel pending operations on selected image nbstlutil cancel -backupid <backupid> nbstlutil cancel -lifecycle <lifecycle> Show status on Incomplete copies of Lifecycle Managed images nbstlutil stlilist –lifecycle <lifecycle name> nbstlutil stlil
Post a Comment
Read more

OSD or Onscreen menu is locked.

OSD or Onscreen menu is locked. I am having HP 20 Inch monitors on my Desk and was not able to change brightness and Sleep Timer etc for my monitor and was not able to get into the menu due to On Screen menu locked error. I know it's irritating issue. fix what i found for this is "Just hold menu button for 30 Sec and it will be solved. :)
Post a Comment
Read more