error in "My Tasks" ...JUICE.DNDisplayCtrl

The approver for a workflow that was initiated by an un-authenticated user, 
receives the following error (in a Windows Internet Explorer popup window) 
upon opening up "My Tasks"

"an error occurred Control instantiation of JUICE.DNDisplayCtrl failed. 
(Object expected).  Please contact your system administrator.  Detail can be 
found in the console."

I don't find anything in the logs (perhaps that not "the console?), but I
do 
notice that the recipient, "GuestUA" cannot be resolved to a DN on the
my 
Tasks page.    If I acknowledge the error twice, it disappears and the 
workflow functions.

Then, after completing ("Submit") the workflow, I get the same two
errors on 
the acknowledgement of successful completion.

Any ideas?

Rob. 

On 05/08/2008 11:21 PM, Rob.S wrote:

> The approver for a workflow that was initiated by an un-authenticated user,

> receives the following error (in a Windows Internet Explorer popup window)

> upon opening up "My Tasks"
> 
> "an error occurred Control instantiation of JUICE.DNDisplayCtrl
failed. 
> (Object expected).  Please contact your system administrator.  Detail can
be 
> found in the console."
> 
> I don't find anything in the logs (perhaps that not "the console?),
but I do 
> notice that the recipient, "GuestUA" cannot be resolved to a DN
on the my 
> Tasks page.    If I acknowledge the error twice, it disappears and the 
> workflow functions.
> 
> Then, after completing ("Submit") the workflow, I get the same
two errors on 
> the acknowledgement of successful completion.
> 
> Any ideas?
> 
> Rob. 
> 
> 


Is GuestUA in the container for users that the User Application is 

John,

Yes.  All users are subordinate to the container ou=usr,o=data, and that is 
the container set as User Root in the UserApp config.
===== shifting gears.....

I had started a long, diagnostic reply, and when I went to verify some 
behavior.  It had spread.  Now the juice error was coming up when I 
initiated the unauthenticated workflow.  That had never happened before.  I 
restarted my server, and hence my UserApp, and now the entire process works 
flawlessly.

So, was the problem likely a DS issue, or an improperly restarted JBOSS 
server (I did restart the UserApp once yesterday using the script for making 
Userapp auto-load as a service), or...?

Sorry for the disappearing symptom.

R.


"John DaSilva" <jdasilva@novell.com> wrote in message 
news:MiRUj.11124$Dh4.715@kovat.provo.novell.com...
> On 05/08/2008 11:21 PM, Rob.S wrote:
>
>> The approver for a workflow that was initiated by an un-authenticated 
>> user, receives the following error (in a Windows Internet Explorer
popup 
>> window) upon opening up "My Tasks"
>>
>> "an error occurred Control instantiation of JUICE.DNDisplayCtrl
failed. 
>> (Object expected).  Please contact your system administrator.  Detail
can 
>> be found in the console."
>>
>> I don't find anything in the logs (perhaps that not "the
console?), but I 
>> do notice that the recipient, "GuestUA" cannot be resolved to
a DN on the 
>> my Tasks page.    If I acknowledge the error twice, it disappears and
the 
>> workflow functions.
>>
>> Then, after completing ("Submit") the workflow, I get the
same two errors 
>> on the acknowledgement of successful completion.
>>
>> Any ideas?
>>
>> Rob.
>
>
> Is GuestUA in the container for users that the User Application is 
> configured to use? 

On 05/09/2008 03:39 PM, Rob.S wrote:

> John,
> 
> Yes.  All users are subordinate to the container ou=usr,o=data, and that is

> the container set as User Root in the UserApp config.
> ===== shifting gears.....
> 
> I had started a long, diagnostic reply, and when I went to verify some 
> behavior.  It had spread.  Now the juice error was coming up when I 
> initiated the unauthenticated workflow.  That had never happened before.  I

> restarted my server, and hence my UserApp, and now the entire process works

> flawlessly.
> 

> So, was the problem likely a DS issue, or an improperly restarted JBOSS 
> server (I did restart the UserApp once yesterday using the script for
making 
> Userapp auto-load as a service), or...?
> 


Do you still have the log from the error was occurring. Wondering if 
something happened earlier that caused JBoss to get freaky, maybe a 
memory leak.

> Sorry for the disappearing symptom.
> 

I'm seeing it again, after no changes, and am thinking that perhaps this is 
a "timeout" issue?  I'm operating over slow VPN.   I logged in to a
VNC 
session at the location, and the browser on-site does not seem to get this 
error.

Feasible?

Rob.

"John DaSilva" <jdasilva@novell.com> wrote in message 
news:ULZUj.11223$Dh4.10089@kovat.provo.novell.com...
> On 05/09/2008 03:39 PM, Rob.S wrote:
>
>> John,
>>
>> Yes.  All users are subordinate to the container ou=usr,o=data, and
that 
>> is the container set as User Root in the UserApp config.
>> ===== shifting gears.....
>>
>> I had started a long, diagnostic reply, and when I went to verify some

>> behavior.  It had spread.  Now the juice error was coming up when I 
>> initiated the unauthenticated workflow.  That had never happened
before. 
>> I restarted my server, and hence my UserApp, and now the entire process

>> works flawlessly.
>>
>
>> So, was the problem likely a DS issue, or an improperly restarted JBOSS

>> server (I did restart the UserApp once yesterday using the script for 
>> making Userapp auto-load as a service), or...?
>>
>
>
> Do you still have the log from the error was occurring. Wondering if 
> something happened earlier that caused JBoss to get freaky, maybe a memory

> leak.
>
>> Sorry for the disappearing symptom.
>>
>
> It is nice when the disappear, especially when they don't come back :)