Re: WDSc 7.0.0.8 stuck in hard loop at startup

[Buck <kc2hiz@xxxxxxxxx>]

On 8/3/2010 2:50 PM, Jim Essinger wrote:

7.0 is not supported by IBM any longer so don't expect help from that
quarter.

Generally, I wouldn't muck with files in .plugins; you may need a new
workspace.  You can try that.

If it still happens with a new workspace, don't delete any cache files yet.
Exit WDSC.
Delete the lock file .metadata\.lock
Look at the log file in .metadata\.log

That may be helpful.  I may not look useful but someone here might
recognise something if you post the last couple dozen lines.

This is running on Win XP 32 bit SP2 or SP3 right?
How much RAM?
  --buck


> A quick search of the web and Midrange has not produced an answer.
>
> My coworker is just starting with WDSc.  After I installed version 7.0
> and all upgrades to her computer, twice she has had the program go
> into a loop when starting.  It displays the splash screen, and then
> brings up the Remote Systems Explorer view.  After it does that it
> says "Connecting SYSTEMNAME" at the bottom of the window int the
> status area.  The activity meter shows at the bottom also but moves
> very slowly.  Clicking on the red square to cancel the operation does
> nothing.  She has a dual core PC, and one of the cores is pegged
> solid.
>
> I got around this by deleting the files in the
> C:\Workspace\.metadata\.plugins\com.ibm.etools.iseries.core\cache
> directory.  Once this was removed, then WDSc starts as expected.  Now
> when she tries to open a source member in the LPEX editor she gets the
> message " Operation error. File system input or output Error"  The
> detail for this error is " Message reported from file system:
> Resource/RemoteSystemsTempFiles is not open."
>
> Has anyone seen the first error and what is She doing that would cause
> WDSC to go into GURU mode?
>
> How do we get back the ability to open a source member in the LPEX editor?
>
> Is it time to call IBM for support?
>
> Thanks!
>
> Jim