Skip to main content
commvault.com commvault.com
Solved

After CommServe Hardware refresh, Content Extractor and Data Analytics Services won't start

  • October 31, 2022
  • 2 replies
  • 609 views
LukeBrett
Byte
Forum|alt.badge.img+5

Hi,

After a Hardware refresh (SP24 MR 69) from Windows Server 2012 to Windows Server 2019 (including a database upgrade from SQL Server 2014 SP3 to SQL Server 2019), the Content Extractor and Data Analytics services won’t start.

As a temporary workaround, I can make them start if I change the ‘Log On As’ from Network Service to Local System, but I would like to recover the default behavior. When I restart the services with this workaround, they get their default values back as I would expect (Network Service as Log On As).

I was wondering if any of you had a similar problem and have suggestions on how to troubleshoot this.

Thanks!

Best answer by Damian Andre

Hi @LukeBrett,

The likely reason is that the required folders that the services need to access no longer have the network service account permissions. There is a KB on this that may help:

https://kb.commvault.com/article/54391

This is not an exhaustive folder list although may help. Alternatively you could use procmon on the services to see which folders it is trying to access and is denied, then apply the network service user to those folders.

View original
Did this answer your question?

2 replies

Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Damian AndreVaulter
  • Vaulter
  • 1301 replies
  • Answer
  • November 1, 2022

Hi @LukeBrett,

The likely reason is that the required folders that the services need to access no longer have the network service account permissions. There is a KB on this that may help:

https://kb.commvault.com/article/54391

This is not an exhaustive folder list although may help. Alternatively you could use procmon on the services to see which folders it is trying to access and is denied, then apply the network service user to those folders.

LukeBrett
Byte
Forum|alt.badge.img+5
  • LukeBrett
  • Author
  • Byte
  • 10 replies
  • November 1, 2022

Hi @Damian Andre, thank you for your answer. Actually, the following folder “\Program Files\Commvault\ContentStore\iDataAgent\JobResults\DM2CacheDir\PreviewIndex\Cache” was missing.

I created the folder with the right permissions and added the following missing registry key (REG_Z) : “HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\ContentAnalyzer\ContentPreviewTempOutputDir” with the folder path as the data value.

This solved the problem of the Content Extractor service. I’m now working on the Analytics service, I’ll keep you updated!

Thanks again!

Damian Andre
1 person likes this
  • Damian Andre
    Damian Andre

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings