WFBATCH sign on problems

[Huba H]

HiJacqui,
Could be caused by password change for WF-BATCH, or any user related issues
(authorization, user type, etc.). If the WF RFC connection test tool does
not  report any error, and still not working, then look into the type of
WF-BATCH in the user master (in newer systems should be 'System').
Anyhow, it wouldn't hurt to test it with different users of type 'Dialog' or
'System', worth the experiment.
So much for now,
Huba
 
 
-----Original Message-----
From: Jacqui Whittingham [mailto:Jacqui.Whittingham at pearson-pbs.co.uk]
Sent: Wednesday, August 22, 2001 4:05 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: WFBATCH sign on problems
 
 
Sadly we are still using 3.1i and I am fairly new to workflow, so I'm
hoping some of you veterans out there may be able to help me!
 
We have a problem which seems to ocurr periodically , causing us much
frustration and then seems to clear over the week-end on its own (probably
after a system bounce).  I'm not entrely sure what causes it nor exactly
what clears it!
 
We start to see the following message appear which indicates that there is
a problem with the WFBATCH RFC user.
'System in trouble (CALL_FUNCTION_SIGNON_REJECTED)
 
 We have tried synchronising the passwords for WFBATCH in SWUD but we get
the following message:
 
'WZ116 Function is not possible for user who has already logged on once
today. '
 
The appearance of the first message seems to to be linked to the use of
functions which are normally carried out by a workflow being carried out
outside of the workflow,  for example release of PO's being carried out
manually using transaction ME28.  We have never to my knowledge had this
problem in our production systems becasue we always use workflow to process
items, but in our training and testing environments where the users are not
in the organisation structure, the manual release is used regularly. When
things get to this stage all workflow tasks no longer function.
 
I have been advised that there is a simple way around thsi but as yet we
have not been able to find out what it is!  If anyone out there has any
ideas, please could you advise us!
 
Jacqui Whittingham