Problem connection to Navision SQL server option...
gabs
Member Posts: 6
Its a NTAuthentication database, when I connect with some clients I get
Does anyone know the solution for this problem ? It seems to be client related, as some clients connect with no problem.
g.
The BLOB Size field on the Object table does not exist in the SQL Server table or view
Does anyone know the solution for this problem ? It seems to be client related, as some clients connect with no problem.
g.
0
Comments
-
Perhaps the .stx file in use on the bad clients contain incorrect translations of field names of the object table. Check if there is a difference between a bad and a good client's .stx file. It may depend on which language is chosen on those clients, because there are separate .stx files in each language subfolder of the Navision installation.Dean McCrae - Senior Software Developer, NAV Server & Tools
This posting is provided "AS IS" with no warranties, and confers no rights.0 -
robertc wrote:Perhaps the .stx file in use on the bad clients contain incorrect translations of field names of the object table. Check if there is a difference between a bad and a good client's .stx file. It may depend on which language is chosen on those clients, because there are separate .stx files in each language subfolder of the Navision installation.
I've compared .stx files - and they are identical, problem is present in which ever language. Norwegian AND English. I've also checked the SQL tables, and the field and table / view in question is present.. All users have rights to it. .
Just don't know, could it be related to the windows installation?0 -
hmmm?
Problem goes away if I reinstall windows to a localized version. Problem now is that I can do this to clients, but not on the server..
g.0 -
Hi,
I have the same problem but with an application server (NAS) that are running on the Navision server (3.70a HF15, SQL).
Are there any other way to solve this instead of reinstalling windows?Olof Simren - Microsoft Dynamics NAV Expert | Founder of Naviona
My Dynamics NAV Blog: olofsimren.com
My Google Plus Profile
Naviona - My Dynamics NAV Partner0 -
Yes, we finally solved it by first backing up our navision database. then uninstalling NAS and any Clients on the server. We then installed a localized (NO) client, created a new database and restored the database.
You haveto make sure you create, and restore the new database with a localized version - or it will not work.
When the client can connect to the database without a blobsize error, You can install NAS, and it will work.
Good luck.
.gabs0 -
Thanks for the reply gabs,
We will try to do this.
Do you know if there are any difference between the NAS that are on the W1 CD and the NAS that are on the localized CD?Olof Simren - Microsoft Dynamics NAV Expert | Founder of Naviona
My Dynamics NAV Blog: olofsimren.com
My Google Plus Profile
Naviona - My Dynamics NAV Partner0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 328 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
