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; } } }

quick question about TS_Diagnostics tool

CRB

Hello, i am on Teamsite 5.5.2 on windows 2k. and lately we are having problem with teamsite going down from time to time (every couple weeks). and i want to run the ts_diagnostics_win tool now, but i dont know if it will stop or affect teamsite services? i tried to look at the docs but it doesnt say if it will stop teamsite or affect the performance in any way!
so do you think i can go ahead and run it now, or wait till all users are logged off?

Find more posts tagged with

Comments

nipper

I have always run it with TeamSite live. It will affect performance as it puts a load on the system for a few minutes but you can live with that.

Did support tell you to run it ? Since 5.5.2 is not supported anymore, it may be moot. The XML that is produced will not mean a lot to you.

Andy

msrinivas

Havent had any issues running it. It doesnt stop services and user can still be running. Its just a bunch of command to read your log files and monitor network connectivity.

HTH

CRB

NO i havent got with the support yet, and i know TS 5.5.2 EOL that s why i am trying on my own. we are on the way to TS 6.5 SP2, we are just waiting for the new hardware that will take couple months because of the budget.

well my problem is teamsite services go down every couple weeks, and sometimes it goes very slow. it might be caused by the content that got big over time and that machine is few years old with the old version of TS...and i wanna run the diagnostic tool just in case of it tells me anything significant!
thank you.

CRB

i run this TS_diagnostics but it get stuck at looking into invalid wf this is where it gets stuck:

----------------------------
OBTAINING TEAMSITE INFORMATION........
Checking iw-home, iw-store, and iw-mount
Checking Service Pack History
Checking iw.cfg
Templating.cfg
Autoprivate.cfg
Submit.cfg
Available_templates.cfg
Front Office Configuration
iwserver.log
iwtrace.log
iwevents.log
GRC Log
iwwebd error log
servlet error log
Teamsite Registry info
Branch Information (This can take several minutes
if there hundreds or thousands of branches)
Roles files
License info
Teamsite Activity (This takes about 15 seconds)
Recent Users
Checking files in iw-bin
Finding invalid wf tasks (this can take a few minutes if there a
re many tasks to parse)

i let it go for 15 mins and it never moved pass finding invalid wf tasks. any ideas why? i am on TS 5.5.2 on w2k.

thank you!

nipper

The diagnostic tool *may* have changed from 5.5 to 6.5. That may be the issue, since it runs various iw clts those may be different.

Support may have the old on on the site.

Andy

CRB

yeah that s possible, cause i made sure i got it from the site just in case of it is updated! does any one know of newer version on the tool? what would you do if you had to run it on TS 6.x?

nipper

yeah that s possible, cause i made sure i got it from the site just in case of it is updated! does any one know of newer version on the tool? what would you do if you had to run it on TS 6.x?

No, I meant the one you have is probably for 6.X. If you want it for 5.5, then you may have to search.

CRB

well, i have to ts_diagnostics_win, one that i got from the site today, and the other they had since 2005 that they used to run on TS 5.5.2. and i saw that they have couple reports there dated 2005. so i run the old one from 2005 and it does the same thing, it hangs on trying to find invalid wf tasts...

Adam Stoller

i run this TS_diagnostics but it get stuck at looking into invalid wf this is where it gets stuck:
[...]
Finding invalid wf tasks (this can take a few minutes if there a
re many tasks to parse)

What happens when you run iwgetwfobj? Does it hang too or seem to give incomplete information?
If so - you may have a corrupted workflow store - and I believe the only fix is to stop TeamSite, remove the workflow store completely and then re-start TeamSite. You might check back through the forums to verify these instructions and/or see if Support is at least willing to tell you the proper steps for this (I don't think it's changed) if this appears to be the source of your problems.

CRB

when i run iwgetwfobj, i get hugeeeeeeeeee list of ids that ends like this:
id v="148557"/>
id v="148563"/>
id v="148573"/>
id v="148579"/>
id v="148585"/>
id v="148591"/>
id v="148597"/>
id v="148603"/>
id v="148609"/>
id v="148619"/>
id v="148641"/>
id v="148647"/>
id v="148653"/>
id v="148669"/>
id v="148675"/>
id v="148685"/>
id v="148691"/>
id v="148697"/>
/activetasks>
/wfregistry>

so i am assuming my workflow store is not corrupted?

yeah and still everytime i run the ts_diagnostics_win it hangs on finding invalid wf task... any help please? i really need to run this report. should i bypass that step that generates the invalid wf by uncommenting where it is called?

Adam Stoller

when i run iwgetwfobj, i get hugeeeeeeeeee list of ids that ends like this:
id v="148557"/>
id v="148563"/>
id v="148573"/>
id v="148579"/>
id v="148585"/>
id v="148591"/>
id v="148597"/>
id v="148603"/>
id v="148609"/>
id v="148619"/>
id v="148641"/>
id v="148647"/>
id v="148653"/>
id v="148669"/>
id v="148675"/>
id v="148685"/>
id v="148691"/>
id v="148697"/>
/activetasks>
/wfregistry>

so i am assuming my workflow store is not corrupted?

yeah and still everytime i run the ts_diagnostics_win it hangs on finding invalid wf task... any help please? i really need to run this report. should i bypass that step that generates the invalid wf by uncommenting where it is called?

Perhaps the store has just gotten too large? However, to move forward - make a note of it as a possible source of problems, comment out that portion of the diagnostic script and try again.

CRB

i tried to comment out that part but ts_diagnostics_win quits (exits) when it gets to that part. it might be hangin or taking too long because of the large store... do you think the tool has time out when to quit trying? if so, i will just leave it on for long time, and it will eventually quit and produce an error msg if it has time out?'

this is the part where it looks for invalid wf tasks: and this is how i commented it out, do you think this is correct?

----------------------------------------------

print " Checking files in iw-bin \n ";
my $iw_bin = iwbin();
print " Finding invalid wf tasks (this can take a few minutes if there are many tasks to parse) \n ";
#my $invaltasks = invalidtasks();
#my @inval = @$invaltasks;
#my $itasks = $inval[0];
#my $totaltasks = $inval[1];
#my $invalidtasks = $inval[2];
print " Finding stalled wf tasks \n ";
my $stalledtasks = stalledtasks();

print "OBTAINING NETWORK INFORMATION........\n";

------------------------
i cant attach the entire script on here because it is larger than 39kb

-----------UPDATE---------
i let the tool run for couple hours, and it was still in finding invalid tasks.. it never throws out an error or anything, just stays there...

CRB

update about this:

i got the tool working now.. it just needed more time than expected...
but i did make it print out things while it was working, and it took most of the time trying to find invalid tasks... the tool took 4 hours to finish! the tool works fine...