| | Product(s): | APM Implementation and Performance Management | |
| | Version(s): | 07.09 | |
| | Environment: | N\A | |
| | Area: | N/A | |
| | Subarea: | N\A | |
Problem
The APM application server in the Test environment cannot be started after the Test environment database was refreshed with a new back-up of the Production environment. User tried installing the application server service as a Local System with no success but was able to install the application server service as a Local Service and a Network Service.
Solution
Installation of the APM Application Server service as a Local System differ from a Local Service installation in 3 very important ways requiring careful understanding of the APM Installation Guide. When installing the application server service as Local System ensure the following 3 steps are done.
1. Using an APM thick client, add a user for the local system. Unlike for a Local Service or a Network Service where the administrator adds a user with a name of "Local Service" or "Network Service" respectively, the Local System user name will be the Machine Name or Computer Name of the server and should have a "$" at the end of the name. For example, if the server's computer name is BTLYTESTAPP1, then the user name in APM should be "BTLYTESTAPP1$". This user should also have an Employee (Personnel) record in APM linked to it, the convention is to make the employee name the same as the user name, ie username "BTLYTESTAPP1$" is linked to employee record "BTLYTESTAPP1$".
2. Network shell permissions have to be set for the Local System user. Run the cmd prompt as an administrator and follow the instructions in the APM Installation guide.
"On an elevated console, register the server user by running the following:
netsh http add urlacl url=protocol://+:port/ user=”ServerUser”
where:
• protocol is either http or https
• port is the Server Manager Port you selected in settings. When the protocol is HTTP, the default is 80. When the protocol is HTTPS, the default is 443.
• ServerUser is the user name that the service is running as, for example, LocalService."
To illustrate the difference between Local Service and Local System on a server where the application service port is 13101:
Local Service network shell permissions is set as;
netsh http add urlacl url=http://+:13101/ user=”LocalService”
Local System network shell permission is set as;
netsh http add urlacl url=http://+:13101/ user="NT AUTHORITY\Local System"
3. Local System service user needs to have permissions to write to the Bentley Licensing Registry. Use the "Grant User Permissions for SELECTServer Licensing" to add the service user. Whereas for Local Service, you would just browse for "Local Service" using the Grant Permissions tool, for a Local System you should see the computer name in the list of available user in the "Grant User Permissions for SELECTServer Licensing" automatically.