Nav 3.7 problem with SQL Server 2005

ajaybabuCh
Member Posts: 208
Hi
I have created the Navsion 3.7 database using SQL Server 2005. When I closed and again trying to open the database, It is giving the following error.
The session table contains a MBS Navision field data type which is not compatible with the SQL Server datatype.
Field : Wait Time(ms)
Type : Integer
SQL Type : BIGINT
can anybody give me the solution.
Thanks and Regards
Ajay
I have created the Navsion 3.7 database using SQL Server 2005. When I closed and again trying to open the database, It is giving the following error.
The session table contains a MBS Navision field data type which is not compatible with the SQL Server datatype.
Field : Wait Time(ms)
Type : Integer
SQL Type : BIGINT
can anybody give me the solution.
Thanks and Regards
Ajay
Ajay
0
Comments
-
1) Use search...
2) NAV 3.70 is not compatible with SQL 2005. You need at least NAV 4.00SP3 client to be fully compatible with SQL 2005...0 -
is there any way to resolve the problem for the time beingAjay0
-
Technical upgrade to NAV 4.00SP3. It means installing new client everywhere, open the database by the new version. But you need to pay maintenance fee to have license able to run NAV 4.00 client...0
-
do you mean, Nav 4.0sp3 client with Nav3.7 server databaseAjay0
-
ajaybabuCh wrote:do you mean, Nav 4.0sp3 client with Nav3.7 server database
Yes, but not with "3.70 server database" but "3.70 objects"... (because server is SQL) ;-)0 -
Hi Kine
Could you please tell me the procedure to use the SQL db only with Nav 3.7 objects. I created the Nav 3.7 demo database in SQL server 2005. I am trying to convert this using Dynamics Nav 5.0 , it is giving me the error about enumuserids and enumusergroups
Thanks and Regards
AjayAjay0 -
You need to install the xp_ndo dll into the SQL folder. Search the forum or see the XP_NDO folder on the NAV install CD.0
-
i did that , otherwise it wouldn't allow me to create sql database for navision.But still getting error message while converting database to 5.0Ajay0
-
the following is the error while converting nav 3.7 db to Dynamics 5.0
2705,"42S21".[Microsoft][ODBC SQL Server Driver][SQL Server]column names in each table must be unique. Column name 'securityoption' in table 'dbo.$ndo$dbproperty' is specified more than once.
SQL :
ALTER TABLE[dbo].[$ndo$dboproperty]ADD securityoption INTEGER NOT NULL DEFAULT 0Ajay0 -
This is well know, error is there because a prior upgrade didn't succeed.
Go to sql2005 management studio, open tabel $ndo$dbproperty in your navision db and delete field securityoption, try upgrade again after this...Rgds
Benny Giebens0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions