Cannot access a disposed object. Object name: ‘NavSystemTenant’

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.

Cannot access a disposed object. Object name: ‘Tenant’

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: ‘Tenant’.

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.

Google AdMob Ads Windows Phone 7 – “Xap packaging failed. Object reference not set to an instance of an object.”

When you try to build Google AdMob Ads Windows Phone 7 sample show the following error message:

Xap packaging failed. Object reference not set to an instance of an object

In Italian

Xap packaging failed. Riferimento a un oggetto non impostato su un’istanza di oggetto.

Cause:

Into the WMAppManifest.xml file there is the following line:

<BackgroundImageURI IsRelative="true" IsResource="false">Background.png</BackgroundImageURI>

but in the project not exists the Background.png file.

Solution:

Add Background.png image file like this:

Google AdMob Ads Windows Phone 7 sample Background missing

to the project, then right-click your Background.png in Solution Explorer, select Properties and set Build Action to Content

NOTE: Apply these steps for Google.AdMob.Ads.Sample.Fundamentals and Google.AdMob.Ads.Sample.Intermediate projects.

Note 2: The very first time AdMob sees your publisher ID it may take up to two minutes to receive an ad. This initial two minute lag will recur every time the app goes unused for 24 hours.

Did my solution solve your problem? Leave a reply.