Has anyone generated this error while using MIMS Connector?
It only occurs occasionaly but necessitates rebooting the server. Does anyone know what causes this error, or where I can find documentation on it?
I've seen this error when launching a second mims, or connector session, while a login dialog is still active.
ie launch a connector script, but don't log on and then launch another connector script.
Earlier versions of middleware required killing the asia32 process to recover but our current version (4.16.37) just reports the error.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.