Two users are testing from assistant. One user is getting the error “Object reference not set to an instance of an object.” The other user is not receiving any errors when running it through. Any ideas on what may cause this issue?
“Object reference not set to an instance of an object.” comes when variables are not assigned properly. Run it in debug mode to see where the error comes from.
Also you can copy the workflow from the user where it works and test it out in the machine of the other user.
We are running from assistant, so shouldn’t the workflow be the same. Are you saying copy the workflow from studio and try it there?
Thanks for your response!
Is the user running the same project in two different machines or two projects?
It is two different users. I am trying to test from assistant and I am now getting the object error. When the other user runs it from assistant they get no error.
Hi @jholstine,
Welcome to the community
“Object reference not set to an instance of an object”
This error occurs when the BOT control tries to access/read any object which has not been initialized or a collection which is empty.
A little more info is required to answer the query but, as you say its working for 1 BOT and not working for another, It implies that there may be an external factor for it.
According to me experiences I can suggest some possible reason for this issue.
- The data in the an config file related to second bot is missing.
- You must be accessing or extracting data from a source(Database, web, excel… ) which is returning null in the second BOT scenario, and when the BOT tries to access the data the “Object reference not set to an instance of an object” exception gets invoked.
I am suggesting some investigation on your part for second scenario.
Thanks and Regards
Rishabh
Hello,
BOT1.
User 1 - Runs BOT1 from assistant with no issues.
User 2 - Runs BOT1 from assistant and gets “object reference not set to an instance of an object”.
mpraveen1902
Anil_G
supermanPunch
Sagar_Sukla
Puneet_Singh1