InfoPath Dev

You didn't come across negatively or as spoiled.  I just wanted to share how it felt from my point of view without speaking for others necessarily.  Your 'client" situation makes sense, and I understand.  We in IT always have "clients" whether as consultants or just internal IT - it's really all the same.

I see that you are separated from the permissions that allow access to the sharepoint servers themselves and likely from Central Admin.  That's where all the attention needs to be, and if all that stuff is going on, it should be the #1 priority for the administration team or for the architect who runs it all.  I say that as an architect for a large sharepoint implementation (as a consultant to a client) who also has an administration team under me with great expertise.  I would have my top guy on this problem the moment anything got wierd like you said, and it would be top priority likely.

I hope that someone can help, but I don't think i can due to the fact that it will require a custom coded workflow to solve this, and I don't write code.  I could probably fix the Timer Service issue if given the chance, but that doesn't sound possible.  If I think of a nifty workaround on the workflow side, I'll let you know.  What timezone are you on, and do you have another form of communication you can use for real-time comms?  AIM, Skype, Live Messenger?  What timezone are you in?

Thank you for your reply back.  I've posed the (heavy emphasis on this) concern and question to my team and waiting for their reply back.  What I am proposing to do for the client is to migrate over the workflow to the working portal and showcase that piece to them, with a heavy emphasis that this needs to be fixed on the Timer Services in order for all of this to run smoothly.  I've documented all the known errors that I've spotted and will show this to my team...being a grunt worker in the field of developing these tools, I think I see alot more than being high up on the plateau?  I'll be presenting this to the architect tomorrow and will figure out a realistic timeline to get this fixed (once a project manager,always a project manager).

 I don't write code either but our programmer/developer could do that. 

I'm in the Pacific timezone...my Live Messenger handle is jungunchoi@hotmail.com It will be nice to chat with you (not pick your brain)

Trust me, I'll be documenting the crap out of all of this workflow issue, you know it'll pop it's ugly head out again if we (team) don't take care of the problem....

 Lisa

 Hi Lisa,

 A google seacrh for "pause for duration permissions" led me to this thread. I'm having the same problem with a workflow attached to aninfopath form... The workflow "pauses", but never continues!

So, I'm just wondering if you ever got this resolved.  I've been searching and messing with the server, but haven't been able to figure anything out yet. I'll keep you posted if I do find anything of value.

--mobrien118

Hello,

 Yes the workflow finally did get fixed and hurray pause duration does work.  A fellow poster assured me that pause duration does work and suggested I look into the Timer Services function.  I tested pause duration on another internal portal and what do you know, the freakin thing worked.  The short story version of this is that my team had to rebuild another portal and apply all the same functions.  It turns out that fixing Timer Services would of been too long and painful, might as well start with a brand new site and work your way back up.  Short answer is....look at your Timer Services and look at your activity logs.  Somewhere along the path, pause duration was working...something goofy probrably happened to cause it not to work.  Timer Services is so critical to making other items on your Sharepoint site work...possibly alerts and other functions are acting out of whack?  Could all of this be a coincidence?  Hmm...

 Hope that helps!

Lisa

been there and now it's soo much better...yes, I believe! ;)

 That's sort of good to know. I have some extremely complicated workflows that will take weeks to rebuild in a new site. And, as we know, they are nearly impossible to migrate too :-(

 Coincidentally, we had the Project Server Synchronization timer job disappear off of the SSP for this site as well. I am not an admin on this server, but I think "the incident" had something to do with a backup/restore and/or a service pack or KB installation. This has been the most frustrating and error ridden project I've ever worked on...ever!

You wouldn't happen to remember, off hand, which timer job is responsible for picking up that pause and resuming it, would you? I can't seem to fins any documentation on the workings of that workflow activity.

Thanks for your response, Lisa!

Hello,

 No I wouldn't know which timer job it was attached to but I do know that it was directly related to that.  We discovered it was just best to rebuild the workflow on the new site.  The pain and time to fix the error would of been longer.  Have you tried restarting the Timer Services on the server and see if that re-boots it back to normal?  Sometimes a simple kick in the "rear" is the best option....lol  Oh also check to see if there is something holding it back - McAfee Virus Scan or something in the log files....

 Good luck!