Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Workflow stalls on workflow dialog

Updated: 23 May 2010 | 7 comments
Jimbaland's picture
0 0 Votes
Login to vote

I was recently appointed as a "charter" member to our Workflow Solution team. I've been messing around with it by way of creating a small project in which a user creates thier own low priority ticket from a web form. When I execute the project, the debugger stops at my Workflow Dialog (see Workflow_Dialog_err1.bmp). I also receive Execution Results that can be seen in Workflow_Dialog_err_2.bmp. Can anyone help me make sense of this and possibly get it working? Thanks in Advance!
Dialog_Workflow_err2.JPG

discussion Filed Under:

Comments

reecardo's picture
12
Feb
2009
0 Votes 0
Login to vote

OK, at this point in your

OK, at this point in your debugging, your workflow is waiting for some tasks to be worked over on the Workflow Statistics tab. Once you "work through" these tasks (by navigating to that tab and clicking on the composer links that appear there), the dialog WF component will kick out an output, and the debugging will restart from where it paused.

Jimbaland's picture
16
Feb
2009
0 Votes 0
Login to vote

I took a gander at the

I took a gander at the workflow statistics tab. What I gleaned from the messages I received, is that the webservice that the form is trying to use is not correct. However, it looks like it is XML 1.1 which is supposed to be supported. Here is the text from the page that is displayed...

composer_stub_svc

The following operations are supported. For a formal definition, please review the Service Description.

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

This web service does not conform to WS-I Basic Profile v1.1.
Please examine each of the normative statement violations below. Follow the recommendations to remedy it, or add setting to the config section to turn off BP 1.1 conformance warnings for the entire vroot.

To turn off BP 1.1 conformance warnings for the entire vroot remove the 'BP1.1' value from the section of the configuration file of your application:

SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementation guidelines that recommend how a set of core Web services specifications should be used together to develop interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema.
Recommendation: Consider changing config settings in web.config file in your application or site root directory to enable SOAP 1.1 protocol for your Web service.

For more details on Basic Profile Version 1.1, see the Basic Profile Specification.
---------------------------------------------------
I tried editing the web.config file of my project with the recommended changes, but this crashes my debugger. Of course when I revert to the old settings the debugger works the same as before.

telegon's picture
16
Feb
2009
0 Votes 0
Login to vote

This smells interesting..

Try the following:

A. Confirm you've got .NET 3.5 installed.
B. Make sure you've got enough RAM.

Jimbaland's picture
17
Feb
2009
0 Votes 0
Login to vote

Verifying

Affirmative on both...
8GB RAM & 3.5 installed

Jimbaland's picture
17
Feb
2009
0 Votes 0
Login to vote

Success!!

Ok, Let me first start by saying thanks for putting up with a rookie making rookie mistakes. I was finally able to run my project with the desired outcome after changing the Workflow Type to "Form Start" and then running "composer.aspx..." in the debugger. Of course, I did have to go through and tweak my Create ticket componnent so it had everything it needed to run. Hopefully this will help others in the future. Later!

SEP_11.0.1000_Win32.msp's picture
03
Jun
2009
0 Votes 0
Login to vote

We need better documentation and examples

Hi there,

thanks a lot for the tip. I stumbled around for 3 days now until I found your suggestions which solved my problem.
And yes, I am a rookie as well but I think it's not a matter of beeing a rookie.
It's a matter of poor documentation in general and  especially poor documentation of the components. I understand
that documentation is very hard to do and that nowbody loves this job so the other solution seems to me to provide us with lot's of xamples.
Please don't misunderstand myself, I love the Altiris Workflow solution and I think it's very powerful. But I am just frustrated as it is
very timeconsuming to develop workflows by try and error ...

Jimbaland's picture
11
Jun
2009
0 Votes 0
Login to vote

Yeah, that's how I started

Yeah, that's how I started out as well. Once I got deep into it, it kind of became addicting (especially when you can get your projects to work). A good resource for workflow and examples is http://www.workflowswat.com/ . It's basically a central location for KB articles, examples, and all things workflow that are scattered throughout connect.