go to post Richard Rael · May 9, 2019 Without research It is hard to say what might have caused this. Definitely something you should open with support if it keeps happening.For completeness I'm adding below the steps to check on the status of the task manager and how to start or resume it if necessary:In cache terminal:%SYS>d ^TASKMGR 1) Create a Task2) Edit a Task3) List Tasks4) Delete a Task5) Suspend a Task6) Resume a Task7) Run a Task8) Task Reports9) Task Manager Options10) Exit Option? 9 1) Task Manager Information2) Start Task Manager3) Suspend Task Manager4) Resume Task Manager5) Task Manager History6) Define Mail Settings7) Exit Option? 1Task Manager Version: 2.9Task Manager is currently suspendedTask History purged after 7 days 1) Task Manager Information2) Start Task Manager3) Suspend Task Manager4) Resume Task Manager5) Task Manager History6) Define Mail Settings7) Exit Option? <---Here you can choose to resume or start the task manager depending on the status from the Task Manager information returned in the step above. 00 Reply go to post Richard Rael · Feb 12, 2018 For client certs to be sent to the LDAP server one needs to wrap a given cert and its associated private key into a PKCS#12 file and import that into the Personal Certificates certificate store. This can be done with the OpenSSL pkcs12 command. Below is a document I on how to perform this process:Importing Certificates to a Windows Certificate StoreConvert the certificate from PEM format to PKCS#12 format.e.g. C:\demoCA\newcerts>openssl pkcs12 -export -in newcert.pem -inkey "..\newkey.pem" -out newcert.pfx -name "New Certificate"Loading 'screen' into random state - doneEnter pass phrase for ..\newkey.pem: <hidden>Enter Export Password: <hidden>Verifying - Enter Export Password: <hidden> Add the Certificates Snap-in to the Microsoft Management ConsoleStart->Run->”mmc”File->Add/Remove Snap-inAdd…->Certificates->AddFor client and client-side CA certificates select ‘My user account’; for server and server-side CA certificates select ‘Computer account’->’Local computer’. Finish.Close->OKImport the certificates to the appropriate storeFor client certificates, navigate to ‘Certificates – Current User’->’Personal’->’Certificates’Right-click to select All Tasks->ImportSpecify the certificate, enter the private key password (the “export password” from step 1 above) if applicable and specify ‘Personal’ as the certificate store.For client-side CA certificates navigate to ‘Certificates – Current User’->’Trusted Root Certification Authorities’->’Certificates’ and repeat steps b and c.For server certificates navigate to ‘Certificates (Local Computer)’->’Personal’->’Certificates’ and repeat steps b and c.For server-side CA certificates navigate to ‘Certificates (Local Computer)’->’Trusted Root Certification Authorities’->’Certificates’ and repeat steps b and c. 00 Reply go to post Richard Rael · Dec 12, 2016 You may want to open a WRC issue for this since the route to failure is not well understood based on the details in the question. It is possible for a tied terminal session to change namespaces. For instance, I created the following routine in %SYS:TestTerminal ;test what happens when switching namespaces w !,"I am in %SYS",! d THIS^%SS h 5 ZN "USER" w !,"Now I am in USER" d THIS^%SS h 5 qI called this routine from a command prompt like so:c:\C2K16\bin>ccontrol cterminal C2K16 TestTerminal %SYSThis popped up a terminal window which ran the routine producing the following output:I am in %SYS Cache System Status: 10:43 am 12 Dec 2016 Process Device Namespace Routine CPU,Glob Pr User/Location 2092 CONTROL 0,0 8 2248 WRTDMN 50,366 9 2256 GARCOL 0,0 8 2268 JRNDMN 175139,0 8 2276 EXPDMN 0,0 8 3972 //./nul %SYS %SYS.TaskSuper 2247760,90501 8 TASKMGR 3096 //./nul %SYS MONITOR 941163,87 8 3240 //./nul %SYS CLNDMN 20530,1179 8 3016 //./nul %SYS RECEIVE 605864,31894 8 3656 //./nul %SYS ECPWork 0,0 8 ECPWORK 3224 |TCP|1972 %SYS %SYS.SERVER 0,0 8 4004 //./nul %SYS LMFMON 18319,31 8 6992 |TCP|RRAEL5550:1972 %SYS %SYS.BINDSRV 329537,34024 8 UnknownUser 3152* |TRM|:|3152 %SYS %SYS.ProcessQuery 8889,110 8 UnknownUser 3680 //./nul %SYS %SYS.Monitor.Control 68980082,1191614 8 3 user, 12 system, 1024 mb global/33 mb routine cache Now I am in USER Cache System Status: 10:43 am 12 Dec 2016 Process Device Namespace Routine CPU,Glob Pr User/Location 0 user, 0 system, 1024 mb global/33 mb routine cache As you can see the namespace switch happened and the routine ran to completion, so it is possible to switch namespaces within a tied terminal routine.Thoughts on the specifics of what might have failed for your process.1. Were you trying to quit out of the routine to get into programming mode? You cannot exit from a tied terminal session (one that enters cache calling a routine) to a programming mode session. When the routine quits the terminal session exits.2. After execution the terminal screen will exit. Was the work done in that second namespace something that you would expect to see output from, or have to enter text to a read command? or would it run fast and then quit? IE, did the work get done, but you not see it?3. Do you have error trapping in your routine in that namespace, and did an error get trapped. This may help understand the behavior.If this is not helpful please open a WRC issue and get help from support in addressing your issue. 00 Reply Followers:Richard has no followers yet.Following:Richard has not followed anybody yet.Global Masters badges:Richard has no Global Masters badges yet.