Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2881
  • Last Modified:

Login Script "hanging" for some (not all) users

Mid morning yesterday Users started complaining that they could not access the network.  We have a Netware 5.1 SP5 Server, 250 User Lic., W98,W2K & WXP workstations running clients v.4.43 SP2 and v4.90SP1a.  Everything was working properly, login script started "hanging"...the script file would just freeze...had to do an "end task" to get out of it.  BUT.....approx. 60% of the users logged in fine and had resources without any problems, any user that came in later in the day, just booted their machine...they would have the problem.  I had some users log into Workstation Only, then Browse the Novell Server and see everything fine.  I have run DSRepair, Vrepair, update DS to 7.62c.  Ran DSTrace logs...In the Sys$log.err I have several instances of:  Policy Manager: Update Connection License failed (for individual user objects).  The DSRepair.log file have 7 instances referencing my Server object (with the correct ID) ERROR: Invalid server ID in backlink obituary is purged.  I have run the DSTRACE with the +j switch and nothing changes.  Also, as another test this morning, thinking maybe the script file is corrupt I deleted all entries in the script, saved the file, tested my ID, logged in properly, tested with another standard user and attached properly to the server, browsed to the server, saw the volumes, browsed down thru, attempted to manually map a drive (with both Netware map a drive and Microsoft's Map a drive), received error that the drive was unaccessable!...I could go on more but for now I will quit.....I'm sure I have lost your attention by now!  :-)  Has anyone out there seen something like this?

Thanks,

Pam
0
ESTPIT
Asked:
ESTPIT
  • 3
  • 2
1 Solution
 
PsiCopCommented:
Hey, Pam. Let's see what we can do.

One important thing is that Login Scripts are not stored in separate files. They are part of the OU's directory object, just like the Full Name field of a User object or the Location field of a Volume object. IF DSRepair did not report any errors, then removing and replacing the text of the script didn't really do anything.

It would be very helpful to know if there is a specific command in the login script that is causing the hang. I would suggest that you employ an old programming trick to try to determine where it is hanging up. You could insert a series of statements into the script like this:

WRITE "Start of script"
...
...some script commands...
...
WRITE "Check Point #1"
...
...some more script commands...
...
WRITE "Check Point #2"
...
...some more script commands...
...
WRITE "Check Point #N"
...
WRITE "END OF SCRIPT"

This would allow you to determine WHERE in the script the hang was occurring. If it always hangs between Check Point #1 and #2, then you could remove the other WRITE statements (I'd keep the "Start" and "End" ones no matter what) and concentrate on just the series of commands between those two checkpoints (putting a WRITE statement before and after each one).

Once you've narrowed it down to a specific statement (or statements) it will probably be easier for us to help you.
0
 
ESTPITAuthor Commented:
I created login script with a "write check#n" after each drive mapping (I had 4 different mappings), the results on each was:  Login-lgnwnt32.dll-430:   The following drive mapping operation coulld not be completed.  The error code was 8901.  
0
 
PsiCopCommented:
Pam,

Hmm.. Was your initial setup does using Evaluation licenses? Novell TID #10067152 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10067152.htm) suggests that the problem you're experiencing may be due to un-removed Evaluation licenses. The TID includes corrective actions.

Also, please confirm that you have an SLP Directory Agent (SLPDA.NLM) running on a NetWare server in your Tree and that it is either unscoped or has the right scope.
0
 
ESTPITAuthor Commented:
Hi, my initial setup did not use Eval Licenses, this Server was put in place in Sept. 2000.  As for SLP Directory Agent is unscoped.

Novell is saying it is corrupt servcfg.* files in the nwserver directory.  After deleting them a few times (which the said would probably be the case), I have succussfully ran DSRepair's without errors. I have made a new ds copy, my login script is working properly now.  Am in the process of downloading SP7 which we will apply.
0
 
PsiCopCommented:
Pam,

Glad to hear its working.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now