Workflow Soluiton

 View Only
  • 1.  Process Manager Issues

    Posted Jan 19, 2011 11:51 AM

    We have been having some problems getting the Process Manager repots to work consistently in our production environment.  They'll work at some point and stop.  When I look in the Log Viewer in the Configuration and Logging Tool, I see the following message:

    "Process Manager is not setup for project. This often happens when you turn on Process Manager integration when a project is open. To correct, close down the project and open again"

    Does anyone know what it means by close down the project and open again?  The project is deployed.  Does it need to be re-published to the server?  I've tried cycling IIS, but that doesn't seem to resolve the issue.

    Thanks,

    Brandon



  • 2.  RE: Process Manager Issues

    Posted Jan 19, 2011 02:47 PM

    This error gets thrown if the project property "ServerIPAddress" is not populated.

    Typically, this just defaults to the IP Address defined by your "Default Server" in the task tray (right click on Symantec Workflow in the task tray and click settings). However, it can be overriden in a project.

    I'd verify that the machine has a valid IP address populated in whatever is hooked up to the default server, or that it's populated in your project



  • 3.  RE: Process Manager Issues

    Posted Jan 19, 2011 03:09 PM

    Thanks for the response reecardo.  I think what probably happened is the workflow was deployed without the ServerIPAddress property, but we added it (we use ${MachineDefaultEnsembleIPAddress} in all of our projects) when we realized it was missing and cycled IIS.  However we're still seeing the error in the logs.  Tonight I'm going to cycle IIS and restart the server extensions to see if that solves our issue.



  • 4.  RE: Process Manager Issues

    Posted Jan 19, 2011 03:46 PM

    That ${MachineDefaultEnsembleIPAddress} is basically the setting that says "use default server in task tray". Check the task tray's default server (task tray on the machine that has the deployed project)

    Also, for fun, ensure that Process Manager "role" is checked for the default server as well (unsure what version of WF you're using, but server registration used to have "roles" associated to them, like processManager, DeploymentTarget, etc.)



  • 5.  RE: Process Manager Issues

    Posted Jan 20, 2011 02:19 PM

    I cycled IIS and restarted the Logic Base server extensions last night, but I'm still seeing the same errors in the Log Viewer and the Process Manager reports are still not working.  What doesn't make sense is that other projects which use ${MachineDefaultEnsembleIPAddress} and are running on the same server are working as expected, so I'm having some trouble understanding how that could be the problem.

    When I RDP into our production server, right-click the task tray and go to Servers, it is set to local.  As far as checking the Process Manager "role" is checked for the default server, is this done via the task tray or via Process Manager?  All I see in the task tray settings is a "Login to Process Manager" checkbox, but that sounds different than what you were referring to.

    We are currently using 7.0.13.13.28 Build 13, which I believe is SP2?



  • 6.  RE: Process Manager Issues

    Posted Jan 20, 2011 03:51 PM

    In that dropdown, click on the server: (local) regitration and hit Edit. Do this from Task Tray. On next popup scroll to the bottom. Unsure what version you're running, but pre 7.1 there was a gridview full of roles assoc. with the registration, like ProcessManager and DeploymentTarget.



  • 7.  RE: Process Manager Issues

    Posted Jan 20, 2011 04:00 PM

    ProcessManager and DeploymentTarget are both checked.



  • 8.  RE: Process Manager Issues

    Posted Jan 21, 2011 07:37 AM

    Just something to try, have you tried using the IP address of the machine vs. machine name (taspmobpa111)?



  • 9.  RE: Process Manager Issues

    Posted Jan 24, 2011 12:49 PM

    For obvious reasons, we try to avoid changes things on our production server.  As I mentioned before, I'm not sure how this could resolve this issue since the process manager reports work fine for most processes -- just not a select 3 or 4 workflows.