Howdy, Stranger!
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
Options
The link context does not match...
joepadmiraal
Member Posts: 7
One of our clients is having a problem with classic reports from the RTC. They are using NAV 2009 R2 with the RTC on a SQL active-active cluster. Both the classic client and the RTC are version 6.0.32558.
When they open a classic report the following error is displayed:
The link context does not match the current Microsoft Dynamics NAV Classic context.
URL context:
Server Name = fakeservername,1436
Database = fakedbname
Company = fake company name
Server Type = MSSQL
Current context:
Server Name = fakeservername\instancename
Database = fakedbname
Company = fake company name
Server Type = MSSQL
I did notice when I start the classic client and open the db on fakeservername,1436 and then look at database-information, it shows fakeservername\instancename. So it looks like the classic client is converting server,port to server\instance. The middle tier does not seems to do this and therefore we see the error message about.
Any idea why this could be happening and what we can do about it?
Thanks,
Joep Admiraal
When they open a classic report the following error is displayed:
The link context does not match the current Microsoft Dynamics NAV Classic context.
URL context:
Server Name = fakeservername,1436
Database = fakedbname
Company = fake company name
Server Type = MSSQL
Current context:
Server Name = fakeservername\instancename
Database = fakedbname
Company = fake company name
Server Type = MSSQL
I did notice when I start the classic client and open the db on fakeservername,1436 and then look at database-information, it shows fakeservername\instancename. So it looks like the classic client is converting server,port to server\instance. The middle tier does not seems to do this and therefore we see the error message about.
Any idea why this could be happening and what we can do about it?
Thanks,
Joep Admiraal
0
Comments
This is rediculous, but Server Name even case-sensetive!
you will get that error even when you try to use 'FAKEservername\INstancename' instead of 'fakeservername\instancename'
Also you may check if there is some leading/ending space character in the connection string.