mibuso.com
Home› NAV/Navision Classic Client
Options

Internal Error 47-1

ManosAManosA Member Posts: 40
edited 2006-09-19 in NAV/Navision Classic Client
Hello.

I am trying to upgrade a client from 3.70 to 4SP1.
Yesterday I managed to take a back up and go through the whole
procedure of updating and everything looked well.
Then today I went to do the same procedure again in order to
go Live but...... the backup could not be obtained. Table
2000000061 User Menu Level produced the following error message:

There are errors in the text conversions (Text No. 1961-0 does
not exist in .stx file). Internal error 47-1.


I have tried to change the stx file but with no luck.
I cannot change/alter/design the table cause its a non editable one.
I cannot even delete it or alter it from the SQL server.
I cannot run the table from the Object Designer.
I cannot use it in a report.
I cannot use it in a dataport.

In all cases I try to open/alter the table I get the exact same message.
The table holds no values in the SQL server.

And the most annoying thing is that I can no longer get a back up from
Navision, since it cannot get through that table.

Any ideas are more than welcome.

thx in advance guys.

Answers

  • Options
    kinekine Member Posts: 12,562
    Try to import the table from clear 4.00SP2 database. Try to import MenuSuite. It seems like some "bug" in the MenuSuite part...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    ManosAManosA Member Posts: 40
    It seems that this table is a 4.01 object that was left in the 3.70 version.
    I haven't got the slightest idea how that happened.
    Now SP2. I haven't tried it yet and don't know how it will react.
    The customer must go to SP1.....

    The object cannot be accessed by the 3.70 .stx file because the lines there
    do not include the object itself (lines 1961-*).
    I cannot import the lines from the 4.01 .stx. There is an error message
    coming because it cannot validate it.

    I am now trying a different approach by working the DB locally to
    transform it in 4.01 and then take an .fbk and try to make a new DB.
    Lets hope this works.
  • Options
    ManosAManosA Member Posts: 40
    How can I delete this table?
    Whenever I try to do it I get a message that I don't have the rights to
    do it. Is there a way around this?

    (It seems that this table is a ghost of the 4.01 version left in the
    3.70. I thing that is the reason why I get all the problems, but I can't
    find out how the hell this bloody table got in there in the first place)
    ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,)
  • Options
    kinekine Member Posts: 12,562
    For me it is like backup created within 4.00 client restored into 3.70 client (downgraded backup). You can try to delete the table from Objects table and drop it on SQL, but this is lowlevel access and I cannot grant that there will be no problems in the future because that.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    ManosAManosA Member Posts: 40
    The problem with that is that I cannot delete the table either
    from the SQL nore Navision.
    The cause of the problem seems to be right only that the original
    DB on the client's side was never "touched" with Navision 4.01.....
    Puzzling.......Hope on Monday I have an answer.
  • Options
    PhennoPhenno Member Posts: 630
    ManosA wrote:
    The problem with that is that I cannot delete the table either
    from the SQL nore Navision.
    The cause of the problem seems to be right only that the original
    DB on the client's side was never "touched" with Navision 4.01.....
    Puzzling.......Hope on Monday I have an answer.


    you could always try to manage db through ODBC (if it's native DB, or SQL enterprise).
  • Options
    ManosAManosA Member Posts: 40
    That is true if ODBCs could work properly.
    The SQL server service pack 4 does not seem to have any problem.
    They have different DNS name in the local settings on each PC,
    but up to know they did not have any problems.
    I'm still trying to restore it locally and take a 4.01 back up.
    I'll post the results.
  • Options
    ManosAManosA Member Posts: 40
    Finally the whole transform is completed.
    I think Kine was right regarding the downgrade of the object.
    We also had a lot of problem with the SQL Server (its protocols and
    drivers), but know after 4 days we managed to do the whole procedure
    in our office. We restored an SQL backup in 4.01 and open it. After that
    everything was as normal. We just got an fbk and restored it in our
    customers site with 4.01. After overcomming a few SQL problems
    the DB was operational.
    Thanx for the support.
Sign In or Register to comment.