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

Ts6.5.0 Sp2

nirali

I am working on TS6.5.0 SP2.

When I click on the workflow tab, the screen for workflow comes up, but details dont. I just get the message "opening page.........." on the status bar and after 5 minutes or so, I grt the error message on the screen saying "page can not be displayed".

What can this be due to ?

I dont have any problems while using TS6.7.1 SP2

Pls esplain.

Find more posts tagged with

Comments

Migrateduser

I am working on TS6.5.0 SP2.

When I click on the workflow tab, the screen for workflow comes up, but details dont. I just get the message "opening page.........." on the status bar and after 5 minutes or so, I grt the error message on the screen saying "page can not be displayed".

What can this be due to ?

I dont have any problems while using TS6.7.1 SP2

Pls esplain.

I have seen that happen under 2 situations..

1 - the teamsite UI needs to be restarted
2 - there are a ton of jobs (usually pages and pages of them) that are old and are just sitting there.. killing all old jobs via command line over (for example) 120 days old and then restarting stops the issue.. in general something in the workflow should be doing this automatically (i.e. timeouts) but that is a different issue.

spayal

In the task manager, I can see OpenDeploy UI Admin service.

I dont see any TeamSite UI service. I can see only Interwoven Teamsite. But I think its iwserver.svc, right ? So which service to check foe TeamSite UI ?

How to kill jobs using CLT ? I dont have any job IDs or other details. From where to collect the information required to kill a job ?

thanks.

Migrateduser

In the task manager, I can see OpenDeploy UI Admin service.

I dont see any TeamSite UI service. I can see only Interwoven Teamsite. But I think its iwserver.svc, right ? So which service to check foe TeamSite UI ?

thanks.

yes, I am referring to restarting TeamSite.. or iwreset -ui

spayal

I guess we should be careful for using iwreset.

nirali

How to kill jobs using CLT ? I dont have any job IDs or other details. From where to collect the information required to kill a job ?

All the services are running eventhen shall I use iwreset ?

thanks

Migrateduser

How to kill jobs using CLT ? I dont have any job IDs or other details. From where to collect the information required to kill a job ?

All the services are running eventhen shall I use iwreset ?

thanks

i would say you have your sysadmin restart IWOV first and see if that fixes the issue.. I would not go restarting servers based on my (or anyone elses) responses except for IWOV support themselves..

as for killing jobs.. well I would make sure teamsite is running properly before I started doing that.. and then you can write a script to get all the job IDs over a certain day old and kill them.. I think i recall even posting one myself on the forum sometime back.

Adam Stoller

How to kill jobs using CLT ? I dont have any job IDs or other details. From where to collect the information required to kill a job ?

Simple answer - go to a shell / command prompt on your TS server and run iwhome/bin/iwgetwfobj

More complex answer - learn how to program in Perl and read the Perldoc on TeamSite::WFsystem, TeamSite::WFworkflow and optionally TeamSite::WFtask.

The CLT for killing jobs is iwrmjob - run it with the '-h' option for usage information (or read the CLT manual)

Also, if you search the forums, you can find various bits of code to do this kind of thing - you may have to modify it for your purposes, but it does save you the time of figuring out how to write it yourself (though I generally like to do that anyway ;-)

Migrateduser

see the following post on a sample script to kill based on the number of days old:

http://devnet.interwoven.com/forums_vb/showpost.php?p=127702&postcount=2

nirali

Thanks guys. I will start from simple options and move to writing perl code.

Thanks again.