NT Service access violation in lhsrvc.exe (Networking Products) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== NT Service access violation in lhsrvc.exe (Networking Products) ====
=== At 06 APR 2001 02:29:15PM Martin Bell wrote: ===
 
{{tag>"Networking Products"}}
 
<QUOTE>
We've recently started to hit an intermittent access violation in lhsrvc.exe -- NT reports an access violation (0x0000005)at address (0x21005883) and creates a Dr Watson log file.  The recovery is to cycle the server.  Does anyone have any ideas?



Note that I ran VERIFYLH against all locations two weeks ago when this last hit.  No GFE's were found.



Any help would be appreciated.



Environment:

Server has Dual PIII 833 w/384 Mb RAM

WinNT 4.0, sp 6

ARev 3.12 running NT Service

35 Win98 clients on 10/100 ethernet

Backup Exec 8.5 for NT

Replication to old server for scripts & ids



The previous environment has been active and very stable (zero GFE's) since May '97.  The new server went in Jan '01, and this problem started.  Other changes: new Backup Exec 8.5, Replication turned on and then off, dual processors, sp 6.



Martin Bell

480-854-7284

bellmgt@attglobal.net
</QUOTE>
----

=== At 07 APR 2001 12:44PM WinWin/Revelation Support wrote:  ===

<QUOTE>Any correlation between Backup Exec activity and the problem?  



Bob

</QUOTE>

----

=== At 08 APR 2001 06:31AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>What does the Event Manager error record look like?



Have you tried to disable devices (eg. sound card, video card, drop video resolution, disable screensaver) to see if/when the problem goes away? Once you run out of NT devices then try disabling BIOS features like shadow RAM support, caching, etc. It could be as simple as a buggy driver having been loaded. You can also use task manager to unload any programs which can be safely unloaded. Then try your application in the simplest PC configuration that you can provide it. Ensure that a default printer is set, operational and available to your application.



You could also try altering the environment size and the path length.



http://search.support.microsoft.com/kb/c.asp?ln=en-us&sd=gn

has 200 articles on access violation errors (search with keywords

ACCESS VIOLATION under the NOS Windows NT Server 4.0). Most errors pertain to buggy hardware drivers or configuration issues.



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]World Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=F2BB3490064661A785256A2600658E45|View this thread on the  forum...]]