× 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 do not know if you can even do this wrong, but when you re-installed and
installed the patches, you installed the update to WSSD, followed by fix
packs 1 and 3 and then finally WDSC?

I think fixpack 3 is the one that is supposed to fix this.

If you want to manually install the plugin you can download the JAR for the
plugin.

http://www.softlanding.com/free_plugins/plugins/com.softlanding.spooledfiles_1.1.14.jar

Then open the JAR file using a tool like WinZip and then extract it to your
C:\Program..\IBM\WebSpher..\v51\eclipse\plugins folder being sure to
maintain the folder name.

This would cause the plugin to be installed as what is called an
"unconfigured" plugin which has the advantage of not being borked by the
Configuration Manager and the configuration problem.

You might also contact IBM support as this problem will prevent any new
plugin from being installed.

Mark



      To      Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
      cc&nbsp;&nbsp;
      bcc&nbsp;&nbsp;
      Subject&nbsp;&nbsp;     Re: [WDSCI-L] Reinstall of WDSc not working
Jim Essinger <esinger@xxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/11/2004 04:07 PM CST
<HR><font size=-1>Please respond to
Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx></font><HR>         <font size=-1></font>







































































Thanks, Mark, for the reply.

I did the search before I posted, and tried to rename the .config folder
in the .metadata folder of the workspace.  It did not work then, and still
does not work to fix the problem.

I re-read the previous postings, and tried to rename the feature.xml file
in the com.ibm.lpex_1.4.x folders in program files.  That did not help
either.

I have set the names back, but am still having the same problem.  Update
will not find any updates to do on it's own, and when I try manually, I
still get an error.

Any other suggestions?

At 01:20 PM 6/11/2004, you wrote:

wdsci-l-bounces@xxxxxxxxxxxx wrote on 06/11/2004 02:54:43 PM:

> Current configuration contains errors that are not corrected by the
> requested operation. See details for more information.
>    WebSphere Development Studio Client for iSeries (5.1.0.2): Feature
> requires feature "com.ibm.lpex (1.4.3)", or compatible.

I would try searching the archives.  I know there was a while where this
came up a lot.  I think there was some resolution that worked most of
the
time, like deleting the .config folder that lives in your .metadata
folder
of your workspace.

Mark

_______________________________________________
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.
_______________________________________________
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 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.