|
David, I tried the rollback option when I first had this proble, it would not let me rollback , and reported the error that I wanted to rollback to fix, as the reason it would not rollback cheers colin.W ----- Original Message ----- From: "David Gibbs" <david@xxxxxxxxxxxx> To: <wdsci-l@xxxxxxxxxxxx> Sent: Monday, December 29, 2003 2:21 AM Subject: [WDSCI-L] Re: Problem with 5.1.0.1 upgrade with multiple workspaces > Joe Pluta wrote: > > Actually, it doesn't quite fit this profile. I have no plugins, I only > > have WDSC. > > My theory is that WDSC is shipped with a set configuration already in > place ... if something is changed in the configuration (I'm not sure > what is changed, but installing a plug-in definetely triggers it) then > WDSC is forced to re-examine the plugin & feature set ... and finds the > inconsistancy with the lpex feature. It then reports the error. > > >>You will probably have to roll your WDSC config back to before the > > error > >>first manifest in order for the fix to work at all. > > I don't even understand this. You're saying I need to "roll back" my > > config. Having never done this, I'm not sure what you mean. > > Using the update manager, you can restore a previous configuration in > the "Configuration History" node of the "Install Configuraton" tree. > > david > > _______________________________________________ > 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 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.