70-210 - Spid's Thu (1/16) Win2k Pro QoD

Author

Spid's Thu (1/16) Win2k Pro QoD

Spid

2003-01-16, 2:52 pm

Let's see how we do with this one....

Tharg is the administrator of his company's network.

You have login scripts applicable to both NetWare 4.x and Windows servers. The user of a Windows 2000 Professional computer logs on and receives this message:

An application error has occurred and an application error log is being generated. NWSCRIPT.exe Exception: access violation (0xc0000005), Address: 0x01cae84b

What should Tharg do to resolve this problem? (Select the best choice).

A. Avoid using NetWare login scripts entirely.

B. Avoid the use of ELSE statements in NetWare login scripts.

C. Avoid the use of external DOS commands in NetWare login scripts.

D. Avoid the user of ELSE statements with external DOS commands in NetWare login scripts.

You'll probably need to do a little research.

Good luck and see you tomorrow for the answer!!

deltree

2003-01-16, 3:28 pm

gcw123

2003-01-16, 10:02 pm

SYMPTOMS
========

During the normal Windows NT logon process, when a NetWare login script is run
by Client Service for NetWare (CSNW) or Gateway Service for NetWare (GSNW), the
following pop-up error message appears:

An application error has occurred and an application error log is being
generated. NWSCRIPT.exe Exception: access violation (0xc0000005), Address:
0x01cae84b

This problem occurs when the NetWare server in use is Novell NetWare version 4.x.
It does not matter whether or not the CSNW or GSNW computer is attaching to the
NetWare server as a bindery or NDS user.

CAUSE
=====

Windows NT's Nwscript.exe logon script processor cannot interpret the NetWare
login script properly. The most common cause of the problem is the use of
conditional statements using the ELSE statement, when combined with external DOS
commands. External DOS commands may be called from NetWare login scripts by
using the #. For example, the following login script will cause the problem:

IF MEMBER "MYGROUP" THEN
#CAPTURE Q=QUEUENAME
ELSE
#CAPTURE Q=OTHERQUEUE
ENDIF

NOTE: Capitalization and layout as above is not required, and changes to
capitalization and layout from above will not affect the problem.

WORKAROUND
==========

Avoid the use of ELSE statements with external DOS commands in NetWare login
scripts as shown above. Check for any possible syntax problems in the NetWare
login scripts (both in the System Login script and users' personal logon
scripts). If the problem is difficult to track down, try eliminating a section
of the login script at a time to find the problem.

or http://support.microsoft.com/defaul...=KB;en-us;Q1642

from above explanation, I go for D...

Slinky

2003-01-16, 10:17 pm

Sounds good to me.

Guess I'll go with D.

WPFossil

2003-01-17, 8:14 am

D sounds good.

gcw123 gives a good explanation, but the MS link is no good.

Forsaken

2003-01-17, 8:23 am

D.

http://support.microsoft.com/defaul...ben-us%3b164281

Spid

2003-01-17, 9:18 am

quote:
Originally posted by Spid
Let's see how we do with this one....

Tharg is the administrator of his company's network.

You have login scripts applicable to both NetWare 4.x and Windows servers. The user of a Windows 2000 Professional computer logs on and receives this message:

An application error has occurred and an application error log is being generated. NWSCRIPT.exe Exception: access violation (0xc0000005), Address: 0x01cae84b

What should Tharg do to resolve this problem? (Select the best choice).

A. Avoid using NetWare login scripts entirely.

B. Avoid the use of ELSE statements in NetWare login scripts.

C. Avoid the use of external DOS commands in NetWare login scripts.

D. Avoid the user of ELSE statements with external DOS commands in NetWare login scripts.

You'll probably need to do a little research.

Good luck and see you tomorrow for the answer!!

And the answer is.....D

This article says it all.

http://support.microsoft.com/defaul...ben-us%3b164281

You guys are good

jonhiker

2003-01-17, 11:47 am

might be late, but...

D)
http://support.microsoft.com/defaul...kb;en-us;164281

gcw123

2003-01-17, 9:05 pm

Sorry.... for typo error on URL link.

Sponsored Links