Originally posted by: edi1999

I'm attempting to start up v9.0 for the first time with one .msl file on a Windows server and get the following error.  I also have v8.4 on this server and it starts fine.  I do not have v8.4 running when I attempt to start v9.0.

Cannot recognize if the system RecordChangeSystem.msl; has started. Reason: Server is unable to get the status of the system on port number 6,002.

I have the port range set to 7000/8000.  I've never seen this error before.

Any help?  Thanks.

Originally posted by: PaulBrettIBM

My guess would be a corrupted LauncherAdmin.bin file.  Rename it, and create from new.

Thank you.

Paul

Follow me on Twitter

Originally posted by: edi1999

I tired that and now I get the same error but for port 7002.

Maybe I'll try reinstalling the Launcher.

Originally posted by: edi1999

Uninstalled it.  Deleted the folder and reinstalled.  Same error.

Tried installing it on another server and get the same error.

I'm stumped.

Originally posted by: PaulBrettIBM

It is possible that other software is using 7000-8000, so try a new range (in the Launcher administration page).

Thank you.

Paul

Follow me on Twitter

Originally posted by: edi1999

Yes I tried different port settings.  During upgrades we will have 2 versions of WTX running on the server at the same time but in this testing I only have the v9.0 service running.  We've done it this way for 20 years so I'm not sure what the issue is this time.

Originally posted by: PaulBrettIBM

Does the mercntsvns64.exe process appear in the process list?  I'm guessing not, and the Launcher is not starting.  Activate the Launcher startup logs (LauncherLog=ewsc in dtx.ini) and see what that tells you.

Thank you.

Paul

Follow me on Twitter

Originally posted by: edi1999

No the mercntsvns64.exe does not appear in processes.  I do have the log files enabled.  See attached.

Attachment(s)

CompoundSystem04-11-17-12-38-24-PM.log   2 KB 1 version

Launcherlog4-11-17-12-38-23-PM.log   1 KB 1 version

Originally posted by: PaulBrettIBM

I see:

File Trigger FATAL Error : ValidateEKDirectories:  Cannot find correct card index for watch 1 (m4file.c:722)
SAM error : Additional error info from adpt collection: err=-1,  (rmadpt.c:973)
Rminittriggers failure <error> : **RMInitTriggers 1687 rc=-1 pos=0:  (rmtrig.c:1691)
Init adapters failure : rminittriggers returned -1 (adptstuf.c:987)

Neither of these files are the Launcher startup log I requested.

   "Activate the Launcher startup logs (LauncherLog=ewsc in dtx.ini) "

http://www-01.ibm.com/support/docview.wss?uid=swg27023621&aid=1

http://www-01.ibm.com/support/docview.wss?uid=swg27021765

Thank you.

Paul

Follow me on Twitter

Originally posted by: edi1999

Here's the launcher startup log you requested.  I did enable all of the logging files and am sifting through it now.  For fun I deleted all maps on my server and put fresh copies on it from our backups.  I started v8.4 with one .msl file active and it started normally.  I stopped the v8.4 service and moved the same .msl to the v9.0 folder and it gets the error.

Attachment(s)

CompoundSystem04-12-17-11-51-01-AM.txt   3 KB 1 version

Originally posted by: SteveBrock

Did you make sure your

• MRC has the MSL in it and the MRN is listed?
• is the DTX.INI file show the location and name of your *.MRC
• Windows service called dtx900_launcher is running
• deployed the msl to the X:\IBM\Websphere Transformation Extender 9.0.0\system\
• Launcher Admin has the msl added in.
• Can connect management console and see the msl?

I think that is all i had to do to get the WTX9.0.0.1 to work, oh one more thing, there is a fixpack i had to download.

for the launcher and it's called "ITX Fix Pack 9.0.0_ITX-wsdtxl-windows-FP1" (rabbit, vo or mcfadden can help with that)

thanks

-Steven

Originally posted by: edi1999

This is a known issue.  I Googled the error message in the log file and found the solution.

http://www-01.ibm.com/support/docview.wss?uid=swg21986219

Originally posted by: PaulBrettIBM

Applying Service Pack 1 will resolve this issue.

Thank you.

Paul

Follow me on Twitter