I’ve created a new NAV Instance, setup the correct database name then tried to run the Service and I’ve received the following error message:
Error
—————————
ServerInstance ‘MicrosoftDynamicsNavServer$NewInstance’ failed to reach status ‘Running’ on this server due to the following error: ‘Cannot start the service.’. Additional information may be in the event log of the server.
—————————
OK
—————————
As suggested by the error message I’ve opened the Event Log to look for additional information and I’ve found the following error message:
Cannot access a disposed object. Object name: ‘NavSystemTenant’.
What does this error mean? Well the error message does not help us to fix this issue but I’ve found a solution and I’m here to share it with you (this is the mission of my website, share my solutions).
Cause:
The new instance is setup to use a port (Management Services Port, Client Services Port, SOAP Services Port or OData Services Port) that is already in use by an existing running NAV Instance. In my case was the SOAP Services Port.
Solution:
Change the port number to a one which is not being used by any other instance, or stop the other service using this port.
Did my solution fix your issue? Leave a comment.
4 replies on “Cannot access a disposed object. Object name: ‘NavSystemTenant’”
Cannot access a disposed object. Object name:
[…]Typically such problems arise because neither the staff nor the management team hold themselves truly accountable.[…]
Thank you Sergio, I got this error today, and resolved it because of your help 🙂
Really helped, thank you
It is typically because the port for development s not registered with the instance:
Try running this in an elevated command prompt:
netsh http add urlacl url=http://+:7049/[Instance Name]/ user=[Service Tier user]