Problems with creating Company via PowerSehell

(0) Share

Report

Posted on by Community Member

Hi,

I had problems with nav2016. We think it is caused by the demo database we started with as base for production database. So I create a new database in the Development Environment. After that I wanted to create a new company . I cannot create a new company via the client because I cannot login there. I think it misses some objects. So I used the powershell cmdLet command:

New-NAVCompany -ServerInstance DynamicsNAV90B -CompanyName OURCOMPANY

This gives an error:

New-NAVCompany : The following SQL error was unexpected:
Invalid object name 'dbo.$ndo$tenantproperty'.

et. etc.

So I think this is not the way to create a 'clean' start database or I do something wrong.

Can somebody give me a good hint?

Thanks,

Patrick

New-NAVCompany -ServerInstance DynamicsNAV90 -Tenant CRONUS -CompanyName 'CRONUS Subsidiary'

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Community Member on at

Like (0)

Report

RE: Problems with creating Company via PowerSehell

Check via SQL Dev Env the presence of dbo.$ndo$tenantproperty table in your db.

Check also login account permission of nav service user

Was this reply helpful? Yes No
aavio 895 on at

Like (0)

Report

RE: Problems with creating Company via PowerSehell

Please try to import a valid license to app database and restart nav server instance.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (2)

Report

RE: Problems with creating Company via PowerSehell

Hi,

The problem is solved by starting 'Sync. Schema for all tables' in development environment. After that creating of company via Powershell was successful.

Thanks.

Was this reply helpful? Yes No
Krupesh on at

Like (0)

Report

RE: Problems with creating Company via PowerSehell

Hi Patrick,

After we finished upgrading all objects from NAV 2013 R2 to NAV 2016 and resolving conflicts we were getting the error The following SQL error was unexpected: Invalid object name 'dbo.$ndo$tenantproperty'. We used the Sync Schema for all tables as mentioned in your mail and the error is now resolved.

Thank you for posting the solution it helped us in resolving the issue.

Regards,

Krupesh Daiya

Mumbai, India.

Was this reply helpful? Yes No