Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Hotfix 37221 doesn't give "client mismatch" warning
bknopp
Member Posts: 37
I hope this saves some folks some of the time I wasted yesterday. I created a new NAV Service Tier instance, running hotfix 37221. I restored the blank database that came with the hotfix, I created a 37221 Development environment folder via the "copy my 36281 folder and then copy the hotfix items over it" method, I made sure that I could access the new instance... All was sweetness and light.
HOWEVER... [cue ominous music]
When I created the RTC client folder via the "copy my 36281 folder and then copy the hotfix items over it" method, I somehow missed the "copy the hotfix items" part of the process. So when I tested, I was using the 36281 RTC client to connect to a 37221 Service Tier.
I got no "client mismatch" warning, the way I do (and have come to expect) when I use earlier versions. The first indication that I got that something was amiss was the sudden NAV RTC crash with the message "The server [servername] was unable to process the request. Close the application and start it again." and an "Input string was not in a correct format" error in the Application Event log on the server.
Now, I'll admit that I'm typically using the developer tools rather than RTC, but still... ](*,)
I've got it fixed now. I share the embarrassment in hopes that it will save some other folks some head-bashing.
HOWEVER... [cue ominous music]
When I created the RTC client folder via the "copy my 36281 folder and then copy the hotfix items over it" method, I somehow missed the "copy the hotfix items" part of the process. So when I tested, I was using the 36281 RTC client to connect to a 37221 Service Tier.
I got no "client mismatch" warning, the way I do (and have come to expect) when I use earlier versions. The first indication that I got that something was amiss was the sudden NAV RTC crash with the message "The server [servername] was unable to process the request. Close the application and start it again." and an "Input string was not in a correct format" error in the Application Event log on the server.
Now, I'll admit that I'm typically using the developer tools rather than RTC, but still... ](*,)
I've got it fixed now. I share the embarrassment in hopes that it will save some other folks some head-bashing.
0
Comments
we've had the same problem and we asked the Microsoft Support about that.
Here is the answer from Microsoft:
NAV Development Team started a very restrictive control between Client and Server with NAV 2009 (do not remember if this was SP1 or they started with R2). They reverted quickly their mind since the advent of NAV 2013 due to the complexity of deployment and the number of the Client it has to be targeted for.
The reason that lies beneath has been provided as per the following
“.. As long as the WCF interfaces (that we use internally – e.g. how we look into record or define a connection -) between client and server have not changed, there is no reason to force the build between them.
This way, people can only patch the server, IF needed, or the Clients IF only functionality broken is on the clients.”
Joerg