I am getting some weird errors in a workflow that hasn’t changed in years. The error states:
Error in PreprocessXML, plugin 'JRF06_FetchFilteredUD100Out_FTP' not found in plugins collection.
Is there some way to refresh the plugins collection?
Very odd; I chose the output channel it uses, changed nothing and saved, and now it works. God I hate service connect
Hi Aaron,
The way to refresh the plugin collection is to restart SC Services (Don’t do that when messages are being processed) or to do graceful shutdown of the services using ScaServiceManager and then start them up again (graceful shutdown allows processing of already picked up messages to complete).
Do you happen to have more than one server listed under Connectivity\Communication Setup in SC Administration Console? Did you copy the SC database to another server to spin up a test instance of SC?
1 Like
Hey Alexander,
Sorry to dog on SC, now I kinda feel bad.
I can say that I do not have more than 1 server listed in the connectivity area, nor have I copied the SC database or spun up a new instance. This is actually the only workflow that we use, and it’s a simple database call and FTP poster workflow. It failed randomly (silently) about a week ago, so I just found out today. Perhaps when we were doing routine server maintenance one of the services wasn’t started correctly?
Could be that ScaDESRouter failed to initialize everything on startup, but that would not have been fixed by adjusting the workflow.
Are there any errors from ScaDESRouter in SC event log, before the issue with plugin started to occur?
It looks like something occurred on 5-15 that caused a service ScaDESRouter to fail
Then, consistently after that, it looks like the error “Error in Preprocess XML…” occurred
Hi Aaron,
Yes, the errors about loading plugin types and list are most probably it.
Any details in the error messages of those?
I guess those might be related to MS SQL not being available, but not sure, as ScaLogonSrv waits for the database to become available before starting up all the other services including ScaDESRouter.
Document Tracking (ScaTrackSrv) could be another victim of SQL DB not being available (the Warning in your log), but that operation it was trying is a repair, it will be retried after the next restart of ScaDESRouter + ScaTrackSrv.
1 Like