Database alter and backup problem

smkolsoft
smkolsoft Member Posts: 53
edited 2007-07-15 in NAV/Navision Classic Client
Dear All
we are using Navision 4.0 SP1 with Sql server option sql 2005.
When i try to alter the database i get the error "Integer field cannot have
value above 512000 Kb....cursor in front of invalid character.

I know that for this the unlimited growth of Log file needs to be restricted.\
To do that i need to backup my db and create new Sql srvr db with that option.

But the problem is when i try to take a backup the system says

"internal error in module 19 ......
Table :customer
Company :'' (Blank is coming)
Key : No.

I have checked all the values in No. field of customer table ....there is no space or lower case character......

I am totally lost.. ](*,) ...Plz provide some suggestions.....

Thanks

Comments

  • nunomaia
    nunomaia Member Posts: 1,153
    Navision 4.0 SP1 had many errors with SQL 2005. If I’m not in error that is an error of SP1.

    Try to upgrade client to SP3
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • stryk
    stryk Member Posts: 645
    Hi!

    Firstly, I have to agree with Nuno: NAV runs only smoothly on SQL Server 2005 since SP3, else you could encounter various "strange" issues ... :bug:
    Integer field cannot have
    value above 512000 Kb....cursor in front of invalid character.
    Set the database growth chunks or restrictions with the Management Studio - NAV 4.00 before SP3 has a problem in "converting" the values you enter in "Database - Alter- etc.".
    "internal error in module 19 ......
    Table :customer
    Company :'' (Blank is coming)
    Key : No.
    I guess you're talking about error 1190. This error occurs when a "non-C/SIDE-Code-field-compatible" value is stored, as you mentioned: lowercase or special characters, etc. which C/SIDE could not interpret correctly. Unfortunately, the error message is somewhat misleading: Despite it says "No." this does not mean that indeed the field "No." is affected! The error always refers to the Primary Key, the but the "wrong" value could be stored in any other Code-type field ... this could be somewhat like "searching the needle in the haystack" ...
    Search the forum for "1190" and you'll get some hints for solving the problem: with NAV that could be tricky business, if you're familiar with TSQL scripting it could be easier to fix it ...

    Good Luck!
    Jörg A. Stryk (MVP - Dynamics NAV)
    NAV/SQL Performance Optimization & Troubleshooting
    STRYK System Improvement
    The Blog - The Book - The Tool
  • smkolsoft
    smkolsoft Member Posts: 53
    Thanks to both nuno and styrk....

Categories