× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've had this before after an install.  My preventative solution so far has
been to not use the auto-update.  It seems like if I update too many times
I start getting this error.  For me, the update was some SVN product I
don't even use.  Usually I end up doing a full uninstall and re-install to
correct it.  During the last uninstall and manual cleanup, I noticed a
directory where old versions of installations were being stored, and the
path had gotten so long that even Windows couldn't reference or delete the
directory.  My guess is that during an update, WDSC stores entire directory
paths under some kind of archive directory.  Perhaps as this archive grows,
it exceeds Window's ability to handle it and then WDSC starts blowing up.
This is separate from the Rational Product Updater I think, because that
product has a way to cleanup the archive.

Only a theory.  I don't recall the long path name of the "corrupt"
directory structure, but it began with "C:\Program
Files\IBM\Rational\SDP\6.0"




                                                                           
             phil.groschwitz@f                                             
             edex.com                                                      
             Sent by:                                                   To 
             wdsci-l-bounces@m         wdsci-l@xxxxxxxxxxxx                
             idrange.com                                                cc 
                                                                           
                                                                   Subject 
             05/17/2006 11:03          [WDSCI-L] parser errors after       
             AM                        installing latest rational update   
                                                                           
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
             <wdsci-l@midrange                                             
                   .com>                                                   
                                                                           
                                                                           




I was prompted by Updater that there was an update, so I elected to install
it.  Now, I get parser errors:

"Uncaught exception in class
"com.ibm.etools.iseries.editor.ISeriesEditorRPGILEParser". Document parser
was disabled"

I've restarted wdsc, and when that didn't work, I rebooted my laptop.  No
luck.

Anyone have any suggestions?

Thanks,
Phil

--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.