We have recently tried to use of the existing nodes as a schedular. I went to the nodes and enabled the schedular service on the node (The node is already having a schedular service running in it)
In morning, all the reloads that went to this node failed. I tried to check the log script but it did not even generate the log files. I went to the engine trace logs and found this
Server: App Load: Beginning open of app bcfd5dea-8849-4a97-beb4-c0de51c158bd with user
DOC loading: Beginning load of document BCFD5DEA-8849-4A97-BEB4-C0DE51C158BD
Exception raised in AppSerializer::Load: 'int': -500 0 INTERNAL
ServerDocumentEntry: DoLoad caught extended exception 1003: App not found
Document Load: The document bcfd5dea-8849-4a97-beb4-c0de51c158bd failed to load
StdServer: OnRemoteClosed entered for socket
Session stop reason: Socket closed by client
DOC loading: Unloading document bcfd5dea-8849-4a97-beb4-c0de51c158bd, state UNLOADING
Is there something that I have missed in order to reuse this node as a schedular?
