Scheduler Not working- not triggering on the server

[RakshithN]

Hi Team- Please help to fix the scheduler run
We are getting this  below error in activity logs when Scheduler started the run    "Failed to create session on XXXXXXXXXX server - Failed to get effective run mode -
Unable to calculate run mode - object Hand".
Please check and suggest action at earliest

------------------------------
Rakshith N
------------------------------

[PabloSarabia]

Hi @Rakshith N

Its looks like Blue Prism is not finding the Business Object. Did you change the object's name or something similar?

In addition, there are many threads in the community speaking about this error, but nothing conclusive. Also check if you have permissions to see the Object of ir the object is in a hidden folder or similar.


See you in the community, bye 🙂

------------------------------
Pablo Sarabia
Architect
Altamira Assets Management
Madrid
634726270
------------------------------

[RaviKumar3]

One helpful thread-
https://community.blueprism.com/communities/community-home/digestviewer/viewthread?GroupId=85&MID=3562&CommunityKey=d8a0860f-1370-4a8d-a272-ad61dbc9b3f3&tab=digestviewer&ReturnUrl=%2Fcommunities%2Fcom...

------------------------------
Ravi Kumar
Sr Automation Designer
Ericsson
Asia/Kolkata
------------------------------

[Walter.Koller]

- Solved - 

Hi

I am replying here to continue the thread instead of creating anew thread with the exact same topic:
Failed to create session on <VDI> - Failed to get effective run mode - Unable to calculate run mode - object <Object Name> does not exist

• The object in question is: <Utility - Image Manipulation Extended>

However, the object is not known to be used by any current process. I have checked the VBO if it knows of any reference but there is none. 

• The error occurs when Scheduler tries to start this process and when the process is moved to the VDI in Control manually. The error message appears immediately, so the process does not even start (eg compared to VBO is missing error). All of the 6 VDI do not have any issues to run processes except this particular process that won't start of any of those VDI.
• There was no change in license files and all existing licenses are still valid.
• The VBO was imported into this environment two years ago and didn't change since then (so no changed ID or name or something)
• The processes (it is a main process with several sub-processes) have been imported again into this environment as release with all existing dependencies.
• The VDI and the BPServer process was restarted but didn't help
• I did a search in BP Customer Support KB but only found two articles both saying the root cause was fixed in 6.2 We are using BP 6.9

Reason: developers didn't check the dependencies correctly 😞

------------------------------
Walter Koller
Solution Manager
Erste Group IT International GmbH
Europe/Vienna
------------------------------