IFS Print Agent error

Just one addition to above...we had similar issue and found that IFSPRINT was NOT locked...instead we just had to re-enter the password.  IFS automatically adds (what appears to be) encrypted password text into the password field even if the password field is actually BLANK (like after you uninstall and reinstall the print agent) so if everything looks good and things still don’t work...make sure you have entered the IFSPRINT user’s password!  

~Tom

Where did you have to re-enter the password? Having similar issues as yourself today. 

We had to go to the server that is running the IFS print agent and then in the toolbar tray find the IFS print agent icon and RMB to select “Configure” to bring up the print agent config menu options (see screen-shot)

Hi,

Note - our IFS systems all run on IFS cloud, and we are using Crystal web services for printing (all hosted by IFS).

we are having great difficulties with setting up our IFS print agents - they run for a while, then they stop, and we find the IFSPRINT account is locked. We unlock the account, then it start, but come up with the unauthorised msg in logs and nothing prints. If we change the password in IFS back to one provided by them previously and restart the agent, it runs Ok for a while, but we get a crystal web services error saying no pdf available. We are getting conflicting information from IFS- someone tells us we must use the passwords supplied by IFS as the IFSPRINT user account is one managed by them, someone else tells us that this is a customer controlled user account, we need to set the password. We seem to be going round in circles here. 
So in summary, if IFS is running IFS and Crystal for us, do we need to use the passwords they have set for the ifsprint account in our ifs print agent config? Or should we create a different  new account for the print agents to use, with a password we can manage, and not use the IFSPRINT account for this purpose at all?

Thanks

Never mind, IFS support have now explained how this all works, and the above issue is resolved.

Hi there.. we're having the same problem.

could you possibly share what IFS told you about how it all works? 
 

thanks!