Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
wbrunc Trusted Contributor.
Trusted Contributor.
187 views

DP Services Domain Account logon failure

Jump to solution

I"m running DP 10.04 on a Windows Server 2016 box. All of the Data Protector services are running under an AD user. Every so often, the IDB service ( and all the other DP services ) is  unable to start because of :

Error 1069: The service did not start due to a logon failure.

I'm able to fix this by going into the "Services" window,  double clicking on the "Data Protector IDB" service and then re-entering the AD user's password.  Once that's done I can start the IDB and all the other DP services with no problems.

Does anyone know why I have to re-enter the password every so often ?

Thanks,

Bill

 

 

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: DP Services Domain Account logon failure

Jump to solution

Hello @wbrunc,

Has someone changed the password for dp_user@GNS? If this is the case, remove it and add it again from a elevated command prompt.

omniinetpasswd -clean
omniinetpasswd -add GNS\dp_user
omniinetpasswd -inst_srv_user GNS\dp_user

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Re: DP Services Domain Account logon failure

Jump to solution

Hello @wbrunc

I had this situation once. The problem there was that user was in domain A and server in domain B. 

For example: The server was cellmgr.domain.com and the user was dpuser@domain.local. 

The problem was directly with OS and AD, something like lost the access until we refresh adding the user again. 

Check that with your AD admin. 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: DP Services Domain Account logon failure

Jump to solution
Hello,

Please check where the service account is used and when the lockout occurs. Please check omniinetpasswd -list on the Cell Manager. If there are credentials stored, replace them with the current password. Other possible places in Data Protector are credentials used for the VMWare or other integration backups.

Are you regularly deploying Windows agents to clients in another domain or not only part of a workgroup? Cross domain push installations have been improved in 10.20 and later. Any 10.x release before that was a nightmare.

Regards,
Sebastian Koehler
---
Please use the Like button below, if you find this post useful.
0 Likes
wbrunc Trusted Contributor.
Trusted Contributor.

Re: DP Services Domain Account logon failure

Jump to solution

 

omnipasswd -list  gives:

dp_user@GNS   ( my AD domain ) .

 

All clients are in the same AD domain. 

Thanks,

Bill

 

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: DP Services Domain Account logon failure

Jump to solution

Hello @wbrunc,

Has someone changed the password for dp_user@GNS? If this is the case, remove it and add it again from a elevated command prompt.

omniinetpasswd -clean
omniinetpasswd -add GNS\dp_user
omniinetpasswd -inst_srv_user GNS\dp_user

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.