I have a BizAgi process that was working. And, it still works (end-to-end) under "admon." However, for one of the initiating users, when they initiate the process, they get the correct form and complete it. But when they click on "Save" or "Next" they get a spinning timer, and eventually the process times out and an error message is thrown "This web page is not available ... operation timed out." So, then I went into the process management console and checked on the MetaData. It reported back one entity without any attributes. I then did three things: turned on (all) tracing, did a "Clean Cases" and then restarted the whole system at the O/S level. BTW, I'm using the most recent version of BAX and running on AWS's Windows Server 2008, with the default SQL Server Express installed by BizAgi's install process. When I bring the O/S back to life, the MetaData error is still there. When I fire up the same user and initiate his process, again I can complete the form but get the same time-out error on "Save." If I try another user before doing the preceding, they'll complete; if after this user, same problem. When I go to where the trace logs are for this process, the folder is empty (no trace logs).
I've attached a screen shot of the meta-data error (after doing the "Clean Case" and rebooting the server.
So, what should I do??