[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1899
  • Last Modified:

WSCL0100E: Exception received: com.ibm.etools.archive.exception.NoModuleFileException

My partner and I are finished a websphere assignment and it worked last week in the same computer lab we are in today.  Now we are printing off our work to hand-in but decided to run the test yet again just to be sure.  Well now we are getting errors.  And after consuming an hour of the teacher's time another pair is also having the same problem.  We tested in another lab but it also is giving the same error.  And worse the teacher gave us some labs to do to prepare us for the assignments and when we try to run these (which previously worked) they don't work anymore.

No changes have been made to the lab (checked with the head guy himself and they have deep freeze so no student can mess em up).

The assignment involves EJBs.  We create a Calculator, CalculatorBean, and CalculatorHome using JNDI.  We have a testCalculator.java file we run as a Websphere v.5 Application Client.  It worked last week but this week when we import the .EAR file we get this error message:

'WSCL0100E: Exception received: com.ibm.etools.archive.exception.NoModuleFileException: A file does not exist for module element having uri: PayrollClient.jar
      at com.ibm.etools.commonarchive.impl.ModuleRefImpl.checkType(ModuleRefImpl.java:715)
      at com.ibm.etools.commonarchive.impl.ModuleRefImpl.initModuleFileFromEAR(ModuleRefImpl.java:270)
      at com.ibm.etools.commonarchive.impl.ModuleRefImpl.getModuleFile(ModuleRefImpl.java:247)
      at com.ibm.ws.client.applicationclient.ApplicationClientMetaData.<init>(ApplicationClientMetaData.java:404)
      at com.ibm.ws.client.applicationclient.ClientContainer.<init>(ClientContainer.java:146)
      at com.ibm.websphere.client.applicationclient.launchClient.createContainerAndLaunchApp(launchClient.java:589)
      at com.ibm.websphere.client.applicationclient.launchClient.main(launchClient.java:420)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)'

Does anyone have any idea?  Non of the com.ibm.etools, com.ibm.ws or com.ibm.websphere files mentioned exist in the workspace.  We are running off the c drive because we were told that it has been known to have issues running off a server drive.  The labs the teacher was testing he has used for years (he says) and this is the first time he's seen this error.

Searching it gives me solutions regarding launchClient command but the teacher says we don't use that since we go Run - Run as.. - Websphere v5 Application Client.  
2 Solutions
SweetChastityAuthor Commented:
We thought of that, that perhaps when we exported it we missed something, but the teacher tried his labs which, as he said, he's used for several courses now (I originally took this course back in jan of last year, hate the course but that's another issue) and his labs have always worked.  Now his labs are even giving him the same error.

My partner said the issue was resolved because he was specific about making sure we set the workspace to the C drive and for some strange reason when the option to set the workspace came up the directory started off C:\\IBM\etc... He said to remove the extra \ and it would be ok but I thought I tried that in the lab.  

Anyway I'll have a look at those links thanks!  I have one more assignment due and I dont' want any surprises.  Give me a day or two please to accept.

I removed the EJB module then I saved the server configuration. Finally, I added the application again.
It works fine for me.


Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now