Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.17 - Administration Guide

About the Migrator for Notes to Exchange documentation Notes Migration Manager NABS Discovery Wizard Internet Domains Discovery Wizard Directory Export Wizard Collection Wizard Groups Provisioning Wizard Notes Data Locator Wizard Provisioning Wizard Send PAB Replicator Wizard Data Migration Wizard SSDM Statistics Collection Wizard The Log Viewer Using the Qsched.exe task-scheduling utility SSDM Scheduling Administration utility Microsoft 365 Admin Account Pool utility PowerShell cmdlets for Migrator for Notes to Exchange Appendix A: How do I ...?
Post-installation configuration Pre-migration preparations Batch-migration process Other features

How do I troubleshoot service startup permissions?

If the MNE Task Scheduler experiences logon failures when trying to start the service, the following information will help you resolve them.

When a service does not start because of a logon failure, you might find error messages in the system event log when you restart the server:

Source: Service Control Manager
Event ID: 7000
Description:
The %service% service failed to start due to the following error:
The service did not start due to a logon failure.
No Data will be available.Source: Service Control Manager
Event ID: 7013
Description:
Logon attempt with current password failed with the following error:
Logon failure: unknown user name or bad password.
No Data will be available.

When you attempt to manually start the service, you might see the following error message, even though the user account is a valid user:

Microsoft Management Console
Could not start the %service% service on Local Computer
Error 1069: The service did not start due to a logon Failure.

This behavior can occur for any of these reasons:

•
The password has changed on the account that the service is configured to use to log on.
•
The password data in the registry is damaged.
•
The right to “log on as a service” is revoked for the specified user account.

To resolve these issues, you can configure the service to use the built-in system account, change the password for the specified user account to match the current password for that user, or restore the user's right to “log on as a service”.

How to configure user rights

If the right to “log on as a service” is revoked for the specified user account, restore the right by performing the following steps:

in the Domain controller domain

If the user is in an Active Directory domain:

1
Start the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in.
2
Right-click the Organizational Unit (OU) in which the user right to log on as a service was granted. By default, this is in the Domain Controller OU.
3
Right-click the container and then click Properties.
4
On the Group Policy tab, click Default Domain Controllers Policy and click Edit.
This starts Group Policy Manager.
5
Expand the Computer Configuration object by clicking the plus sign (+) next to the policy object.
6
Under the Computer Configuration object, expand Windows Settings, and then expand Security Settings.
7
Expand Local Policies, and click User Rights Assignment.
8
In the right pane, right-click Log on as a service, and click Security.
9
Add the user to the policy, and click OK.
10
Quit Group Policy Manager, close Group Policy properties, and close the Active Directory Users and Computers MMC snap-in.
On a member server

If the user is a member of a stand-alone member server:

1
Start the Local Security Settings MMC snap-in.
2
Expand Local Policies and click User Rights Assignment.
3
In the right pane, right-click Log on as a service and click Security.
4
Add the user to the policy and click OK.
5
Close the Local Security Settings MMC snap-in.

How to configure service logon information

To configure the password for the specified user account to match the current password for that user, use the following steps:

1
Click Start, select Settings, click Control Panel and double-click Administrative Tools.
2
Double-click Services.
3
Right-click the appropriate service and click Properties.
4
On the Log On tab, change the password and click Apply.
5
On the General tab, click Start to restart the service.
6
Quit the Services tool.

How to configure the service to start up with the built-in system account

If the service still does not work with the specified user account, you can configure the service to start up with the built-in system account using the following steps:

1
Click Start, select Settings, click Control Panel, and then double-click Administrative Tools.
2
Double-click Services.
3
Right-click the appropriate service, and then click Properties.
4
On the Log On tab, click Local System Account, and then click Apply.
 
* 
NOTE: You typically do not need to configure a service to interact with the desktop, so you can leave the Allow service to interact with desktop check box clear.
5
On the General tab, click Start to restart the service.
6
Exit the Services tool.

When you attempt to open the properties of a service using the Services tool in Control Panel, the computer may stop responding (hang) and/or can display this error message:

The RPC Server is unavailable

This message can occur due to a logon failure with the Remote Procedure Call (RPC) service or some other dependent service. Some services cannot start until after dependency services have started (for example, the Workstation service).

If you cannot start the Services tool, follow these steps to configure the service to use the built-in system account:

1
Start Registry Editor (Regedit.exe).
 
* 
CAUTION: These steps tell you to modify the registry. Serious problems might occur if you modify the registry incorrectly. Ensure that you follow these steps carefully. Quest strongly recommends that you back up the registry before you modify it so you can restore the registry if a problem occurs.
2
Locate the ObjectName value in this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceName
3
On the Edit menu, click Modify.
4
In the Value Data box, type localsystem and click OK.
5
Exit the Registry Editor.
6
Attempt to restart the service. You may need to restart the computer for some services to restart properly.

If you cannot start Registry Editor, you can modify the service account information by performing a parallel installation. See the Microsoft Knowledge Base for information about parallel installations.

Although most system services are configured to use the system account credentials for logon by default, you can configure them to use a specific user account instead. When a user's password is changed, the password information field is not automatically changed for services.

You can start a service with the local system account or by specifying a specific user account and password. If you choose to specify a user account and password, it is important that the account name and password remain constant. For example, this account should not be required to change password or be renamed. If these two events (or other similar events) occur, you should also update the logon credentials for the service.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating