?
Solved

Parsing error when upgrading NW6sp4 (eDir 873) to NW6sp5

Posted on 2004-11-12
5
Medium Priority
?
361 Views
Last Modified: 2008-03-10
Any one running into this issue?

We are running into problems upgrading a batch of NW6sp4 servers with eDir 873 to NW6sp5.

The exact error is:
=====
An error occurred while parsing file
"sys:\nw6sp5\sp\INSTALL\STARUP.ICS", line
1033, at or near word or symbol ",".  Error
description:  Syntax error.  (nwconfig-6-232)
=====

The same media files work fine upgrading NW6sp2 to NW6sp5, or NW6sp4 eDir86x to NW6sp5.

I don't see anything on Novell for this issue.  The closest is "Error occurred while parsing file - TID10093646 (last modified 28OCT2004)" http://www.novell.com/inc/pf/pf.jsp?url=http://support.novell.com/cgi-bin/search/searchtid.cgi?/10093646.htm for installing NW6.5 sp2.

We actually followed that TID and ended up bombing another batch we upgraded earlier in the week.  

My thinking is eDir873 is causing the problem...  Any ideas?

Thanks!

-Silly-
0
Comment
Question by:Mighty_Silly
  • 3
  • 2
5 Comments
 
LVL 35

Expert Comment

by:ShineOn
ID: 12585840
Based on what I see in the startup.ics file at line 1033, I concur that it would have something to do with eDirectory, since it is the "extend schema" section of the file.  Since I currently have NW6SP4 with eDirectory 8.7.3.3, and hope to go to SP5 someday, I have a vested interest in the resolution to this issue.

Does this occur after doing an Admin login?  Are you logging in using an Admin ID that has rights to extend the schema?  What version of eDir873 are you running - have any of the IR's been applied?
0
 
LVL 11

Author Comment

by:Mighty_Silly
ID: 12586841
Hey ShineOn,

Thanks for responding!

Here are two references to this "Parsing Error" on Novell - one is a TID for NW6.5sp2 install (which got us into hot water - refer to my other post <DS.nlm no long load after a "successful" upgrade from NW6 sp4 to sp5> http://www.experts-exchange.com/Networking/Netware/Q_21202777.html), and one on the Discussion Forum.  Check'em out.  I'll update this as I get more info.

Error occurred while parsing file - TID10093646 (last modified 28OCT2004)
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10093646.htm

NW6SP5 Error in STARTUP.ICS - Is this a BUG?
http://support-forums.novell.com/group/novell.support.edirectory.netware/readerNoFrame.tpt/@thread@12823@F@10@D-,D@NONE/@article@12778

-Silly-
0
 
LVL 35

Accepted Solution

by:
ShineOn earned 1500 total points
ID: 12587453
I'd guess it's a similar, yet different issue than what is presented in TID10093646, since 6.5 starts out at 8.7 and gets updated to 8.7.3 in SP2, IIRC, while if running 8.7.3 on 6.0SP4, the SP tries to update 8.6 eDirectory to 8.6.2 SMP build 10350.30.00, so you don't WANT the eDirectory update to run, IMHO. Since the C:\NWERVER update wants to put an older version of DSLOADER.NLM there, that's what's throwing the error.

Is there an option to bypass the eDirectory update?  If so, that part of SP5 shouldn't even be run on the servers that have 8.7.3.
0
 
LVL 11

Author Comment

by:Mighty_Silly
ID: 12587492
No, we couldn't even get past the authentication screen (after the login part).  It started copying the files, then just errored out w/ that Parsing Error.

We WERE successful in updating a batch of NW6.0sp4 w/ eDir 8.6 to NW6.0sp5 - just like you stated above.  

We're opening an incident w/ Novell soon.  I'll keep you posted.

Thanks!

-Silly-
0
 
LVL 11

Author Comment

by:Mighty_Silly
ID: 12867145
ShineOn,

Sorry for leaving this out there for so long.  To date, we haven't had any good response from Novell about a *fix*, only two workarounds - both worked.

1) re-download iso and burn cd again, making sure antivirus is disable
2) on servers that went thru the initial process ok but insist that they're still sp4,
    simply replace SERVER.EXE from a sp5 box.

Thanks for taking the time to respond.

-Silly-
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Office Picture Manager was included in Office 2003, 2007, and 2010, but not in Office 2013. Users had hopes that it would be in Office 2016/Office 365, but it is not. Fortunately, the same zero-cost technique that works to install it with …
With more and more companies allowing their employees to work remotely, it begs the question: What are some of the security risks involved with remote employees and what actions should we take to secure them?
Despite its rising prevalence in the business world, "the cloud" is still misunderstood. Some companies still believe common misconceptions about lack of security in cloud solutions and many misuses of cloud storage options still occur every day. …
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
Suggested Courses
Course of the Month16 days, 10 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question