Skip to main content
D
Davy
Contributor
April 14, 2022
Solved

Access to the registry key 'Global' is denied.

  • April 14, 2022
  • 1 reply
  • 0 views

I may have found a bug in OneStream.

I build a small CV - 10 by 3 columns with a row that has column override calling a small Dynamic Calc formula.

I'm getting this error message, in System> Error log,  when I run a cubeview. Has anyone seen this error message before.
. If you can give me a clue to narrow down, that's fine as well. 

Unable to initialize XF App Server Metrics Thread on application server APP01. Access to the registry key 'Global' is denied. ---------------------------------------- Description: Unable to initialize XF App Server Metrics Thread on application server APP01. Error Time: 4/12/2022 4:57:02 PM Error Level: Error Tier: AppServer App Server: APP01 App Server XF Version: 6.1.1.11424 App Server OS Version: Microsoft Windows Server 2012 R2 Standard (6.3.9600.0) Session ID: 00000000-0000-0000-0000-000000000000 Error Log ID: 7053dc3d-9ea3-4da1-b144-d91a4bc70328 Total Memory: 34,359,201,792 (32.00 GB) Memory In Use: 2,713,128,960 (2.53 GB) Private Memory In Use: 3,351,609,344 (3.12 GB) Peak Memory In Use: 3,154,239,488 (2.94 GB) Maximum Data Records In RAM: 6,442,350 Number Of Threads: 68 ---------------------------------------- Exception Type: XFException Thread Id: 21 Message: Unable to initialize XF App Server Metrics Thread on application server APP01. Source code: XFServerMetricsThread.cs, line 138, method PerformInitialProcessingInThread Stack Trace: at OneStream.Shared.Engine.XFServerMetricsThread.PerformInitialProcessingInThread(SessionInfo si) in

D:\Source\Shared\Engine\SharedEngine\BackgroundThreads\XFServerMetricsThread.cs:line 138 at OneStream.Shared.Engine.XFServerMetricsThread.WorkerThreadFunction() in D:\Source\Shared\Engine\SharedEngine\BackgroundThreads\XFServerMetricsThread.cs:line 63 ---------------------------------------- Exception Type: Unknown Message: Access to the registry key 'Global' is denied. Stack Trace: at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) at Microsoft.Win32.RegistryKey.InternalGetValue(String name, Object defaultValue, Boolean doNotExpand, Boolean checkSecurity) at Microsoft.Win32.RegistryKey.GetValue(String name) at System.Diagnostics.PerformanceMonitor.GetData(String item) at System.Diagnostics.PerformanceCounterLib.GetPerformanceData(String item) at System.Diagnostics.PerformanceCounterLib.get_CategoryTable() at System.Diagnostics.PerformanceCounterLib.CounterExists(String category, String counter, Boolean& categoryExists) at System.Diagnostics.PerformanceCounterLib.CounterExists(String machine, String category, String counter) at System.Diagnostics.PerformanceCounter.InitializeImpl() at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly) at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName) at OneStream.Shared.Engine.XFServerMetricsThread.PerformInitialProcessingInThread(SessionInfo si) in D:\Source\Shared\Engine\SharedEngine\BackgroundThreads\XFServerMetricsThread.cs:line 138

Best answer by Davy

KB0011308:

search for Knowledgebase articles by navogating to the URL below then selecting "Knowledge Base". : https://onestreamsoftware.service-now.com/sp_cloud?id=index_3

 

Cause

1) The OneStream Service Account is not a member of Performance Log Users and Performance Monitor Users groups.

2) The Performance Counters need rebuilding on each OneStream Server.

Solution

1) Add the OneStream Service Account into the Performance Log Users and Performance Monitor Users groups.

2) Complete these steps below as an Administrator to rebuild the Performance Counters on each OneStream Server:

  1. Launch the Command Prompt by clicking Start, type cmd and then right click the Command Prompt that should now be displayed. Select 'Run as administrator'.

  2. b. Within the Command Prompt change your Directory to C:\Windows\SysWOW64 by using the cd command.

eg cd c:\Windows\sysWOW7=64


  1. c. Type lodctr /r and press ENTER (after which you should get the following message displayed - "Info: Successfully rebuilt performance counter setting from system backup store")

  2. d. Reboot each OneStream Server.

1 reply

D
DavyAuthorAnswer
Contributor
April 14, 2022

KB0011308:

search for Knowledgebase articles by navogating to the URL below then selecting "Knowledge Base". : https://onestreamsoftware.service-now.com/sp_cloud?id=index_3

 

Cause

1) The OneStream Service Account is not a member of Performance Log Users and Performance Monitor Users groups.

2) The Performance Counters need rebuilding on each OneStream Server.

Solution

1) Add the OneStream Service Account into the Performance Log Users and Performance Monitor Users groups.

2) Complete these steps below as an Administrator to rebuild the Performance Counters on each OneStream Server:

  1. Launch the Command Prompt by clicking Start, type cmd and then right click the Command Prompt that should now be displayed. Select 'Run as administrator'.

  2. b. Within the Command Prompt change your Directory to C:\Windows\SysWOW64 by using the cd command.

eg cd c:\Windows\sysWOW7=64


  1. c. Type lodctr /r and press ENTER (after which you should get the following message displayed - "Info: Successfully rebuilt performance counter setting from system backup store")

  2. d. Reboot each OneStream Server.
Terms & ConditionsAccessibility statement