Welcome Guest! To enable all features please Login or Register.



Go to last post Go to first unread
#1 Posted : Friday, March 16, 2018 1:05:55 PM(UTC)

Rank: Administration

Groups: Administrators, Registered
Joined: 1/2/2018(UTC)
Posts: 9
United States

Recently, after installing the service based architecture for a client, navigating to the diagnostic URL (https://localhost/GPService/Management/Diagnostics) would fail with a 500 error. After digging through the logs, we saw the following logged repeatedly in the DexterityServiceControl log (where the server name, domain name and service account name have been modified):

2018-03-16_11:37:22.809 (E) --> InternalManagementCallError :: CallId:[75], Uri:[http://servername:48665/Control/Management/HostStatus], Method:[GET], OuterCode:[200], InnerCode:[403], InnerError:[CorrelationId:[], HttpCode:[403], ErrorType:[ManagementAuthorizationFailure], Source:[DexterityServiceControl], Message:[The user 'OURDOMAIN\serviceaccount' is not authorized to make this management request.]], ElapsedMs:[2]
2018-03-16_11:37:22.809 (E) --> NonFatalError :: Context:[RetrieveStatuses], Content:[One or more errors occurred retrieving host status data.]

Ultimately, we noticed that the account name logged wasn't fully qualified (e.g. OURDOMAIN.local\serviceaccount), which is what we had entered when walking through the installation wizard. After dropping the .local from the service accounts (through a repair of the Web Components), the service started working successfully.
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.