Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1909
  • Last Modified:

Sharepoint Workflow Status Page

Hi,
I have an Infopath Form Library hosted on Sharepoint. This library has a workflow attached. It had been working fine up until a few days ago. Now when I click on the workflow status link under the Workflow column, the page hangs for 5-10 minutes and then times out. It then throws an 'Unknown Error'.

I have other form librarys on the Sharepoint site collection and I can access their workflow status page without a problem. So this problem is local to 1 site.

It is the same for ALL workflows within the problem site, irrelevant of what status they are at (In Progress, Completed, Cancelled etc.)

Any ideas? This is a work related issue and I need to sort it out asap so any advice would be greatly appreciated

Ben
0
Beircheart
Asked:
Beircheart
  • 6
  • 6
1 Solution
 
tstritofCommented:
Hi,

could you please post the error that is logged in your log files? Try looking for the file with your server name and today's date/time in C:\Program Files\ Common Files\Microsoft Shared\web server extensions\12\LOGS.

Also, is the workflow activated at site level or site collection level?

Regards,
Tomislav
0
 
BeircheartAuthor Commented:
Hi Tomislav,

Thank you for your reply.

I clicked the link at 11:32 and it eventually failed at 11:42

I've attached the log file

I think the webparts error is particularly relevant. Other pages in other sites within the same site collection were failing to load also. Removing certain web parts and adding them in again fixed those sites. Unfortuantely, I couldn't access the WrkStat.aspx page to try the same on the problem site...

Thanks again Tomislav
Log-File.txt
0
 
tstritofCommented:
Hi,

you are having serious issues with your SQL transaction log.

Check if the solution described here can be applied in your situation - however be careful since your content database is about everything your MOSS is about (at least when users whose data is stored there are concerned).

Regards,
Tomislav
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
tstritofCommented:
Also, the problem with transaction log might have been caused by some WP gone wild so monitor the sites and WP in question to see if this reoccurs at some point.

Regards,
Tomislav
0
 
BeircheartAuthor Commented:
I think you're on to something...
It's starting to make sense. I'll look in to it and get back to you later today

Good man Tomislav
0
 
BeircheartAuthor Commented:
Hi Tomislav,

RE: Transaction Log
I spoke to the Sharepoint admin and he fixed that particular problem. As you probably know, this was causing problems throughout Sharepoint.

However, my problem with the workflow status page remains. Can you tell me anything about the WebParts errors in the previously attached Log-File.txt?

Ben
0
 
tstritofCommented:
Hi,

could you please retry the "error generation" and repost the log? Just to get a fresh picture.

Regards,
Tomislav
0
 
BeircheartAuthor Commented:
0
 
tstritofCommented:
The only error logged here relates to the search web part (SearcBoxEx).

Do you have a search web part added to your site master (default.master)? Or application master directly (application.master)?

I've seen folks report problems with it (check this article) but not related to workflow.

Have you tried restarting the application pool for this site in IIS? Maybe it's down to some config change that hasn't propagated properly.
0
 
BeircheartAuthor Commented:
Hi,
My apologies for leaving this question for so long but in the meantime we have found the problem:

The Workflow History list was logging at an enormous rate (~40 entries per second). This equated to over 10 million entries over a weekend!! This list then affected the WrkStat.aspx page. As a temporary workaround, I went to the workflow settings and pointed the workflow to a new workflow history list. I say this is temporary because this list would then 'overflow' and the same problem would occur. The external contractor that developed the workflow simply forgot to turn this excessive logging off but they have now been contacted and have disabled the workflow.

Now though, we have another problem of trying to clear these lists (The largest is over 26 million). Anytime we tackle them the server crashes. Anyway, that's another issue

I consider this closed.

Tomislav, I appreciate your time and effort on this and even though I'd like to award points for effort, I'll have to mark this post as the solution for the sake of accuracy

All the best,
Ben
0
 
tstritofCommented:
No problem. I hate looking up an answer on EE just to find out there was no actual answer :) So I agree this is the way to go. Glad you resolved the issue.

Regarding the logging, I've seen the "log flood" happen on SharePoint but not in a list though.

How are you performing the delete that crashes the server?

Regards,
Tomislav
0
 
BeircheartAuthor Commented:
Reason in previous post
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now