Error initializing company in NAV 2013

YTA
YTA Member Posts: 9
edited 2013-10-20 in NAV/Navision Classic Client
I've done a few NAV 2013 installations in 2-tier setup using NetworkService account and have not experienced any hassles. I have now done my first 3-tier setup using a domain account provided by the client.

Everything appeared fine, I can connect to Dev environment, RTC, & even create new companies by renaming Cronus & restore backup of cronus. When I create a completely new company in Dev Env, everything seems fine until I try to access it via RTC. The initialise process starts and I get the following error:
'You do not have the following permissions on Table Required Fields: Execute'.

I am set up as a super user and all my colleagues get the same error. I am of the opinion it has something to do with the domain account used during installation. There are no messages in the event log.

I came across this post http://msdn.microsoft.com/en-us/library/hh166150(v=nav.71).aspx which talks about Provisioning the account. I cannot confirm the first 2 points myself ('Enable the account to log in as a service' and 'Enable the account to register an SPN on itself'). It's now almost midnight on a Friday, so I will only be able to get hold of the client's IT staff to confirm on Monday.

I checked up on the last point (Give the account necessary database privileges in SQL Server) and apart from the domain account existing as a SQL login, nothing else was done. I believe the rest should have been done via NAV install. I manually did each step, restarted SQL and NAV service but still have the same issue. ](*,)

Can someone please help or at least confirm if I am heading in the right direction [-o<

Thanks in advance

Comments

  • JMA
    JMA Member Posts: 10
    Maybe you still have the Cronus NAV license active therefore you cannot do all the things you want.
    For identifying the responsible C/AL code you could start the debugger.

    There is no delegation required in NAV 2013, so you don't have to do the SPN stuff.
  • YTA
    YTA Member Posts: 9
    Thanx for the reply.

    It is at the onset of the project, so we are using our partner license until the client license arrives...... but it made me think. Our partner license was updated a month or 2 ago.

    We implement 3rd party software. The vendor has multiple products and it turns out they are referencing objects that we are not licensed for.

    Thanx for your contribution

Categories