"Object reference not set to an instance of an object" error

(1) Share

Report

Posted on by Sirius_A

Hello all, a user is getting this error any time she goes to the main D365 screen, she enters to any workspace, then she goes back and this errors appears. It doesnt prevent to do something and it doesnt happen after a specific action other than going backwards. I checked already created topics but none was useful for me to understand or having a hint at least on how start. The strange thing is that in non PROD environment she gets the error as well, we deleted usage data just in case and the problem remains, then I totally deleted and recreated the account and the problem was still there, this tells me the problem may be in system level. Any hint? Thanks a lot!

Error: "Object reference not set to an instance of an object" (no more information than this)

Categories:

Dynamics 365 general

I have the same question (0)

All responses (3)

Answers (0)

Martin Dráb 237,976 Most Valuable Professional on at

Like (1)

Report

You'll need to find out where the error is coming from. For example, you may debug the code or (hopefully) get the error logged by Monitoring and telemetry.

It's a very generic error. It basically means that some code is trying to refer a non-existing object, such as to call a method on a variable that contains null.

Was this reply helpful? Yes No
Sirius_A 83 on at

Like (0)

Report

Thanks Martin. The problem now is that debugging needs to replicate the problem, and I cant, it is only user specific and I dont have access to user credentials of course. What is strange to me is that after deleting the account in test environment, the problem persisted, but I dont get the same error with my account nor my test user, no matter what environment I try. Also it is strange that this problem wasnt visible before, but now it is in both environments, PROD and test?, it is almost like it was specifically visible in the computer of the user. Maybe a saved view? I will check tomorrow, but any tip on how to deal with this scenario would be appreciated.

Was this reply helpful? Yes No
Martin Dráb 237,976 Most Valuable Professional on at

Like (0)

Report

There are ways. For example, you can change (in a non-prod environment) the UserInfo record so you can log as the given user (you'll use your Entra ID but get all F&O setup of the user). I used this technique recently to track down a similarly weird problem. Or you can debug code executed by the other user.

Also, don't forget the other option I suggested - logging the error instead of debugging. It can't solve everything that debugging can, but checking logs is easier than debugging of non-dev environments and it gives you data for production too. Therefore having the logging in place sounds like a good idea to me.

Was this reply helpful? Yes No

Join the conversation

Community site session details

"Object reference not set to an instance of an object" error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

"Object reference not set to an instance of an object" error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates