Options

Intername error:41-1 when upgrading in Nav 2015

Hi,
We have a customer on Nav 2015 Cu 11, build 42603.
I have done a SQL backup and restored to our dev system.
Opened the database in Dev Env and got msg that database needs to be converted.
Click ok and then got error "There are errors in the text file conversion text no. 1810-11 does not exist in the .stx file. Internal error:47-1" - See screenshot attached.

So cannot sync the objects.

The Cronus database opens ok.

Help !!!!
<img src="https://us.v-cdn.net/5022383/uploads/FileUpload/45/d24d6df9d41de6d78c6677888279be.png&quot; />

Answers

  • Options
    swpoloswpolo Member Posts: 80
    I would suggest export all objects in txt format and pay attention to TextConsts. Possibly there is some symbols that cannot be converted or it might be a problem with MLCaptions. Try to remove all languages except ENU.
    Nav Upgrades and DEV outsourcing
    Reports transformation to RDLC
    List -1h , Complex List -3h, Document -4h (dev hours)
    navisionupgrade.com
  • Options
    boraunalboraunal Member Posts: 10
    Hi,

    I think it can cause by one of the captions or name has wrong syntax.Program could not find matching system word in .stx file you can try to delete fin.zup and reopen dev envoirement and make a default file or its a translation problem
  • Options
    AquirAquir Member Posts: 23
    edited 2016-09-21
    Based on the stx file:
    // Active Session Table
    01810-00000-030-1: Active Session
    01810-00001-030-1: User SID
    01810-00002-030-1: Server Instance ID
    01810-00003-030-1: Session ID
    01810-00004-030-1: Server Instance Name
    01810-00005-030-1: Server Computer Name
    01810-00006-030-1: User ID
    01810-00007-030-1: Client Type
    01810-00207-150-1: Windows Client,SharePoint Client,Web Service,Client Service,NAS,Background,Management Client,Web Client,Unknown,Tablet,Phone,Desktop
    01810-00008-030-1: Client Computer Name
    01810-00009-030-1: Login Datetime
    01810-00010-030-1: Database Name
    01810-00011-030-1: Session Unique ID
    

    there is a problem around the Session Unique ID field in the Active Session Table

Sign In or Register to comment.