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
updating exe 3.60 to 4.0 - WARNING 3.60 XP UNINSTALL ISSUE
itinkiam
Member Posts: 37
:roll: I just finished updating a customer to 4.03.03 from 3.60. I did not remember the uninstall problem in 3.60 on XP machines (the ticking time-bomb). ](*,)
REMEMBER THE INSTRUCTIONS!!! If you uninstall 3.60 on an XP machine, and don't immediately reinstall 3.60, you have to re-install the XML parser.
I didn't and boy. #-o What a mess. My installation to 4.0 went fine. I didn't see any problems. Then on Monday when the client got in, none of the search features worked on the local machine. Many Webpages didn't work. No mapping programs worked.
MBS did their best to help. The only hint of what the problem was came in the form of an error message when I tried up do a Windows update and the MS website said that my client's license was not valid. There was a message code that came with this. However, MBS didn't know what the message code was.
Eventually (4 days on the phone with MBS :-({|= with no solution except 'reinstall all of the operating systems') I found a blog searching in Google.com that referenced my error message. It was something about the XML Parser. After re-installing the XML Parser, I had to re-register jscript.dll and vbscript.dll and everything came magically to life.
:arrow: If you reinstall the XML Parser immediately after uninstall, you won't experience the issues that I had.
REMEMBER THE INSTRUCTIONS!!! If you uninstall 3.60 on an XP machine, and don't immediately reinstall 3.60, you have to re-install the XML parser.
I didn't and boy. #-o What a mess. My installation to 4.0 went fine. I didn't see any problems. Then on Monday when the client got in, none of the search features worked on the local machine. Many Webpages didn't work. No mapping programs worked.
MBS did their best to help. The only hint of what the problem was came in the form of an error message when I tried up do a Windows update and the MS website said that my client's license was not valid. There was a message code that came with this. However, MBS didn't know what the message code was.
Eventually (4 days on the phone with MBS :-({|= with no solution except 'reinstall all of the operating systems') I found a blog searching in Google.com that referenced my error message. It was something about the XML Parser. After re-installing the XML Parser, I had to re-register jscript.dll and vbscript.dll and everything came magically to life.
:arrow: If you reinstall the XML Parser immediately after uninstall, you won't experience the issues that I had.
0
Comments
I am glad that you got it working...
Maybe you could notify MBS about the solution... :evil:
The great thing is that you have learned to play the violin... \:D/ =D>
Could you write the error message here and put a [Solved] in the post subject so that we can have the solution as a future reference?
Someone else might do a search with the error message here and it would be nice to have the exact error that was raised...
Arhontis
https://forum.mibuso.com/search