Parsing error when upgrading NW6sp4 (eDir 873) to NW6sp5
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\ST
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-
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\ST
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-
ASKER
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> https://www.experts-exchange.com/questions/21202777/DS-nlm-no-long-load-after-a-successful-upgrade-from-NW6-sp4-to-sp5.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-
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> https://www.experts-exchange.com/questions/21202777/DS-nlm-no-long-load-after-a-successful-upgrade-from-NW6-sp4-to-sp5.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-
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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-
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-
ASKER
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-
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-
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?