Server 2012 R2 Clustered role not failing over

I have a Clustered role consisting of an Bitvise SSH SFTP Server not failing over. The windows service does not start. I have other clustered roles on this cluster that have no trouble.  

When it tries to fail over, the following error appears in the Event log

event
  time: 2014-09-03 16:32:10.255235 -0400
  app: BvSshServer 6.07
  name: E_SERVICE_COMPONENT_INIT_ERROR
  desc: Error initializating component.
  parameters
    component: CompSec
  error
    type: Exception
    message: Error looking up local ComputerSid: [WVIVR-SFTPCLU01] First LookupAccountName() for 'WVIVR-SFTPCLU01' failed with the following error: Windows error 1332: No mapping between account names and security IDs was done. [WVIVR-SFTPCLU01\] First LookupAccountName() for 'WVIVR-SFTPCLU01\' failed with the following error: Windows error 1332: No mapping between account names and security IDs was done.
DTUserAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
have you checked the account being used is not locked out, disabled, or recently had password changed?
have you verified any security policy rights that user account should have is granted on that server?
0
DTUserAuthor Commented:
Which user account should I be looking at?  The Windows service is running as Local System.
0
Cliff GaliherCommented:
Sounds like the SSH service is running as an account that is neither a domain account nor a "well known" account such as the network service. So the SID lookup not successful during failover and the new node cannot start the service because it does not have an account to start it under.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

DTUserAuthor Commented:
I tried changing the SSH service to the domain administrator account, but afterwards the service would not start.
0
Cliff GaliherCommented:
Well, getting the permissions so the service can run under a domain account, a well known account, or a managed service account (which is a specific type of domain account) will be essential to failover working. Which means understanding the requirements and poet tally working with the app vendor.
0
DTUserAuthor Commented:
I spoke with the vendor, but they could offer no support.  I ended up removing the service from the cluster.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DTUserAuthor Commented:
None of the solutions worked, so I abandoned the process.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.