Hi,

in our installation we have a 32 bit WAS 8 (32 bit IBM JDK) on Windows 7 64 bit.
I installed MyEclipse Blue 32 bit.

When I try to start WAS 8 I get the following error (partly translated from German by me):

Code:

ADMU0111E: Program exiting with error: java.lang.UnsatisfiedLinkError:            Ws60ProcessManagement            (%WAS_HOME%\AppServer\lib\native\win\[b]x86_64\Ws60ProcessManagement.dll[/b]            is not a valid win32 application. ) ADMU1211I: To obtain a full trace of the failure, use the -trace option. ADMU0211I: Error details may be seen in the file:            %WAS_HOME%\AppServer\profiles\base\logs\server1\startServer.log

I can overwrite the 64 bit DLLs with the 32 bit DLLs.
( %WAS_HOME%\AppServer\lib\native\win\x86_32/64 )
That works as a workaround, but it would be nice if this was fixed.

striebhz,

Thanks for reporting this, our team is looking into the launching code.

Q: Are you able to start this installation of WebSphere without problems outside MyEclipse Blue (without your modifications, of course).

I'm sorry, I haven't seen your question.
But we only start WebSphere from MyEclipse, so i'm not able to answer it.

striebhz,

In your appserver\bin folder there is a versioninfo.bat file. Can you please run that and paste/attach the output here? Of specific interest is what it says under Architecture and Installed Features.

Unfortunately it's partly in German, but I shouldn't be a problem I think:

Code:

%WAS_HOME%\bin>versionInfo.bat WVER0010I: Copyright (c) IBM Corporation 2002, 2005, 2008; All rights reserved. WVER0012I: VersionInfo reporter version 1.15.1.47, dated 10/18/11 -------------------------------------------------------------------------------- IBM WebSphere Product Installation Status Report -------------------------------------------------------------------------------- Report at date and time 12. September 2012 16:08:27 CEST Installation -------------------------------------------------------------------------------- Product Directory        %WAS_HOME% Version Directory        %WAS_HOME%\properties\versio n DTD Directory            %WAS_HOME%\properties\versio n\dtd Log Directory            C:\ProgramData\IBM\Installation Manager\logs Product List -------------------------------------------------------------------------------- BASE                     installed WEB2MOBILE               installed Installed Product -------------------------------------------------------------------------------- Name                  IBM WebSphere Application Server Version               8.0.0.2 ID                    BASE Build Level           cf021148.03 Build Date            12/2/11 Package               com.ibm.websphere.BASE.v80_8.0.2.20111202_1708 Architecture          x86 (32 bit) Installed Features    IBM 32-bit SDK for Java Version 6                       Tool EJBDeploy für Module einer Version vor EJB 3.0                       Integrierbarer EJB-Container                       Eigenständige Thin Clients und Ressourcenadapter Installed Product -------------------------------------------------------------------------------- Name                  Web 2.0 and Mobile Feature Pack Version               1.1.0.0 ID                    WEB2MOBILE Build Level           web21122.15 Build Date            5/25/11 Package               com.ibm.websphere.WEB2MOBILE.v11_1.1.0.20110525_0308 Architecture          x86 (32 bit) Installed Features    Komponenten von Feature Pack for Web 2.0 and Mobile -------------------------------------------------------------------------------- End Installation Status Report --------------------------------------------------------------------------------

striebhz,

Thanks, we've located the problem, we check the OS architecture instead of the WAS installation architecture and use that information to start WAS. In most cases it matches, but there can certainly be cases where it does not, as in your case.

I've filed this as a bug and we will attempt to get a fix into 10.7. I'll post further updates to this thread, thank you for your support and for reporting the problem.

striebhz,

This issue has now been fixed in release 10.7. You can use the Configuration Center to update to 10.7. Alternatively download the MyEclipse Blue installer from our download page.

Thanks again for reporting it.