Forum Discussion

Marcde's avatar
Marcde
Moderator
6 years ago

Indexing backlog increasing - Event 41352

Hello everyone, we do have an environment where the indexing backlog for all index volumes / archives is increasing. A few minutes after restarting the indexing service Event 41352 is occuring for m...
  • GertjanA's avatar
    GertjanA
    6 years ago

    Hello Marc,

    The only reference I found to the error you mention is below: errorcode

    Interestringly, this points to firewall, which you say is disabled. See if the advise in the entry resolves it. It might also be that a MS KB patch causes this. That however is hard to find, as you need to figure out when you started getting these events, and then figure out what changed on the system.

    I don't have further ideas, sorry.

    <edit> Further Googling showed:

    https://www.veritas.com/support/en_US/article.000087698 

    other articles indicate firewall issue.

  • Marcde's avatar
    Marcde
    6 years ago

    Hi everyone,

    Gertjan might have been right. A few hours after installing September Windows updates on the EV server the issue is completely gone. DCOM messages stayed away and the indexing backlog went below the threshold within a few hours. Except of the Windows updates nothing else has been performed on the EV server.

    Kind Regards

    Marc

     

Marcde's avatar
Marcde
Moderator

Hi everyone,

hostname and alias are correctly resolved. We entered the VSAs credentials in the vac and restarted the service without any improvement. We also entered the password again for every EV services but no change.

Any other idea? 

 

Regards

Marc

GertjanA's avatar
GertjanA
Moderator
6 years ago

Hello Marc,

The only reference I found to the error you mention is below: errorcode

Interestringly, this points to firewall, which you say is disabled. See if the advise in the entry resolves it. It might also be that a MS KB patch causes this. That however is hard to find, as you need to figure out when you started getting these events, and then figure out what changed on the system.

I don't have further ideas, sorry.

<edit> Further Googling showed:

https://www.veritas.com/support/en_US/article.000087698 

other articles indicate firewall issue.

  • GertjanA's avatar
    GertjanA
    Moderator
    6 years ago

    Hi Marc,

    Any update on this issue?

  • Marcde's avatar
    Marcde
    Moderator
    6 years ago

    Hi Gertjan,

    unfortunately not. A few things that we did: 

    -Execution of get-service powershell cmdlet showed that service RPCSS (Remote Procedure Call (RPC)) was not listed which I thought could be relevant. However the service is there, started and seems to be working. 

    -Executed FileReRegister.bat without a change

    -Checked if any DCOM restrictions have been applied (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DCOM)

    -Double checked firewall and the firewall status of the AV solution

    We are not allowed to involve technical support at this point.

     

    Regards

    Marc

  • Marcde's avatar
    Marcde
    Moderator
    6 years ago

    Hi everyone,

    Gertjan might have been right. A few hours after installing September Windows updates on the EV server the issue is completely gone. DCOM messages stayed away and the indexing backlog went below the threshold within a few hours. Except of the Windows updates nothing else has been performed on the EV server.

    Kind Regards

    Marc