Windows Forum

Ask something
Discussion Locked

NT Errors after reboot

0 helpful
11 replies

by teinfo

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After reboot a application server,I got the following two Errors:
1st error from Application SQL server:
From: NETLOGON at \\
to: User
Subject: **ADMINISTRATOR ALERT**
Date: 3/9/01

Failed to authenticate with , a Windows NT Domain Controller for
doamin

2nd error message from same server:

An application error has occurred and an application error log is being generated
SURVEYOR.EXE
Exception: access violation(0xc000005), Address: 0x004557f4

Then I checked the application server event view:

error record:

No Windows NT Domain Controller is available for domain
(This event is expected and can be ignored when booting with the 'NO Net' hardware
Profile.) The follow error occurred:

There were currently no logon server availabel to service the logon request.
[Event ID: 5719]
Source: NETLOGON
Type: error
Category: None

Problem: Now a user tried to run a pipeline program on the application SQL server from a NT workstation and got a Dr. Watson error: access violation 0xc000005 (This is a student credit history update on personal information changes such as home address, credit record and other related inoformation. This program came with M/S Excel, then rewrite with Infomake program) **The user ran the same program on a test application SQL server with same database with no problem.

Any expert know its cause and solution will be very appreciate.

EDD

11 replies

by ntoz

The very first thing I would check is, is the box on the network. Can you ping from the server to any other computer on the network? Ping the Domain Controlers, BDC, PDC? Is this a member server or a domain controler on which this application is running? When you logon to this server, does it say your using localy caches cridentials? If this is a member server and you cannot access the network or reach an authenticating PDC or BDC then your other problems are more then likely related to services and authentication with a source such as a PDC or BDC. If this is SQL running on a server thats a PDC or BDC then you may have issues related to problems with the security sub-system. If these are not the issues, then I will post a follow up with step two.

Pete

by teinfo

Yes, I can ping from PDC & BDC. Users has no problem connecting to this server
SQL database.
This is a member server(application server with SQL)
No, it did not said using localy caches cridentials. I can ping it and see it on PDCserver group. This server can access to network after reboot.
This is not a PDC or BDC. It is a member server only.

These eror message appears for a while before I work here. Now the problem is that the Dr. Watson terminate stop from running pipeline on SQL database( this application server).

[Run pipeline: We receive a file with excel format and need to update the information with our database to keep the accounts up-to-date.]

Thank much very much. I wish your step two will help me out on this issue

EDD

by mckaytech

In Compaq servers, I've seen this sort of scenario from two causes: stale NIC drivers and switches that do not autonegotiate well.

Most likely, once you resolve the connectivity problem and don't get the NETLOGON error, you won't get the SQL error either.

paul

by teinfo

This member server can connect to PDC & BDC. I can ping from PDC & BDC. This
server also shows up on server group. All users can connect to this SQL server
with no problem and do their work as usual.

The problem is when we try to run a pipeline on this server database from workstation, the Dr. Watson terminate it and said "access violation". I know this is not a permission because I use administrator account to run.

by mckaytech

Ah, now I'm starting to get the picture. I don't know what the exact problem is, but the "access" violation means the pipeline program tried to write to the wrong area of memory so it is not a permissions problem.

In your c:\winnt directory, there should be a Dr. Watson log file that might provide some clues. Generally, a Dr. Watson error is a program problem rather than hardware and the log should tell you what in what program or process the error occurred so you can narrow your focus to that piece.

paul

by teinfo

I have checked DrWtsn32.log to app file. This is my first time look at Drwtsn.log.
I do not know how to identify which program causes problem by checking the headers:

-->tast list<--

State Dump for Thread ID 0xcf

function: ZwReadFile
*--->Stack Back Trace <----*

*--->Raw Steak Dump <----*

by winssuresh

1. If You are using Wins Server, check the WINS . Also Check the protocol properties for proper wins configuration.

2. If there is no wins environment , make a LMhosts file.

3. Surveyor , if the application is made to System account, instead of specifying a logon account for startup, You will not get the errors.
Suresh

by mckaytech

A couple lines down from the top of the Dr. Watson file, you'll see something like this:

Application exception occurred:
App: exe\iexplore.dbg (pid=206)
When: 1/27/2001 @ 16:3:36.642
Exception number: c0000005 (access violation)

Make sure you're looking at the right event by checking the date and time and then look at the process ID (pid=206 in this case).

A little further down the log, you'll see the list of tasks that were running at the time. It will looksomething like this:

213 HOTSYNC.exe
215 AboutTime.exe
206 iexplore.exe
134 drwtsn32.exe
0 _Total.exe

In this case, process 206 is Internet Explorer (iexplore.exe) and that is the culprit in this case.

If you would like me to take a look at your Dr. Watson log, you can mail it to me off the forum and I'll see what it tells me.

paul

by teinfo

Ho Paul,

I like to go back to this question again. Please help me if you can. Now I found
what application caused DR. Watson error. for example, it was excel.exe. What I need to do in order to fix this problem that Dr. Watson will notcome out again.

Thank you very much

This discussion is closed to new replies.