Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Auto Protect is stopped but auto protect services are enabled.

Created: 11 Feb 2008 • Updated: 22 May 2010 | 2 comments
Auto-Protect Status = Stopped
but its enabled and in event log found below Error:
 
Registry Write Failure.
HRESULT = 0x5.  This error occurred while attempting to write to registry key
"InputThreadsInUseDword".
 
I am using SMSMSE 6 in Exchange 2007, total number of servers are 4.we have 2 mail box and 2 Cas/Hub servers.
only the above problem came in one mail box server rest of another servers are working fine. 
 
Please any body give me the solution to solve this issue
Discussion Filed Under:

Comments 2 CommentsJump to latest comment

S Cheung's picture

Question/Issue:

You open Application Event log, you notice a number of Symantec Mail Security for Microsoft Exchange (SMSMSE) events. The category is Auto-Protect. The description begins with ‘Registry Write Failure.’

Symptoms:

When you open the Windows Application Event log there are number of Symantec Mail Security for Microsoft Exchange information events that display the following data:

Type: Information
Source: Symantec Mail Security for Microsoft Exchange
Category Auto_Protect
Event: 176
Description:
Registry Write Failure.
HRESULT = 0x5. This error occurred while attempting to write to registry key "InputThreadsInUseDword"

The text “InputThreasInUseDword” may be replaced by the following text:
CommandQueueLengthDword
SPsInUseDword
SPsInUseDwordPeak


Solution:

The events do not have an impact on the program.

Symantec Mail Security for Microsoft Exchange (SMSMSE) 6.0.5 fixes this problem. Information about what is included in SMSMSE 6.0.5 is included in Release Notes for Symantec Mail Security 6.0.x for Microsoft Exchange / Symantec Information Foundation Mail Security for Microsoft Exchange

Marlon's picture




Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

I got a similar problem.

The client shows this error, and it is a AD / DNS / File Server

When the shield show a yellow dot, the network jam.

Nobody can login or access application that need connection with this server. Any ideas?