nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Meta tagger Issue

gundu

Hi , I have installed MT 4.1.1 on a windows 2003 box with SP1, but when i do a upload of a document from civiewer the process hang and reports socket error.

I have also installed both the patches available on the support site but still I face the same issue,

Any thoughts on this

Find more posts tagged with

Comments

Migrateduser

Can you post the exact error on the client side + any log entries in the MT log?

gundu

In the client side i am getting "Socket Error" from civiewer
and in the server logs I am getting

"child on port :9095 died"
"This child is being terminated"

nipper

Check your logs, there should be a reason that it is being terminated, likely a config issue.

r2 - weekly attendance report.pdf

crosstab.JPG

crosstaboutput.JPG

Migrateduser

MetaTagger patches are cumulative and inclusive(usually). In this case Patch ID 1731 is a superset fix on Patch ID 1690. Since you mentioned you installed both the patches, I wonder if you installed the latest patch first and then an older patch next.

Can you make sure you have the latest patch. If true you build number will be 59794, other wise it will be 57246. You want the former.

Migrateduser

go to bin, run "iwmtdiagnostic.exe -o diag_test.log" and post the diag_test.log.
This will report to us your configuration (you could have a config file that is tweeked) and your license validation.

boskovuk

MetaTagger patches are cumulative and inclusive(usually). In this case Patch ID 1731 is a superset fix on Patch ID 1690. Since you mentioned you installed both the patches, I wonder if you installed the latest patch first and then an older patch next.

Can you make sure you have the latest patch. If true you build number will be 59794, other wise it will be 57246. You want the former.

How do I exactly check which patches have been applied on our MT installation (4.1.1)?

I see you refer to build numbers - where to find these?

aggregation.bmp

Migrateduser

in windows stop the "Metatagger Admin Server":
1. cmd.exe > cd MetaTagger-bin directory
2. iwmtadminserver

will start mtserver and studio server, printing the build numbers.

in Solaris, stop /etc/init.d/iw.mtadminserver(ice):
1. $cd Metatagger-bin directory
2. ./iwmtadminserver

will do the same start/print build information

-there could be other ways as well.

boskovuk

in windows stop the "Metatagger Admin Server":
1. cmd.exe > cd MetaTagger-bin directory
2. iwmtadminserver

will start mtserver and studio server, printing the build numbers.

in Solaris, stop /etc/init.d/iw.mtadminserver(ice):
1. $cd Metatagger-bin directory
2. ./iwmtadminserver

will do the same start/print build information

-there could be other ways as well.

thanks - quite helpful Smiley Happy

I am just watching logs coming out (as MT server initializes).
This is my build number: BN: 56452

How do I go from here (current build number) to the list of patches being applied on th box?

Migrateduser

you have a vanilla MT 4.1.1 you can grab the 1731 patch from Interwoven support site and replace your binaries(instructions in readme), which should pull you up to buld 59794(also in the readme file as Build Number)

there is problem with mtlicenseinfo binary-executable, it keep s reporting the vanilla version, even if after patching a system. So I go with the method I suggested to work around it.