Microsoft Dynamics NAV 4.0 Client unable to run on Windows Server 2008r2 Terminal Server

[crescendas]

I was told by vmware that thinapp will allows every single Windows XP compatible programs to run on higher version of Windows (but not the other way round of course). Unfortunately, the first program I tried - Microsoft Dynamics NAV 4.0 Client, failed to run on Windows Server 2008r2 Terminal Server.

What did I do wrong? Or is it that Thinapp is not as compatible as Microsoft XP Mode where a real Windows XP is running on top of the higher version Windows?

[BradI100]

There are some limitations to the "all xp programs can be converted".  Device drivers, for instance, cannot be Thinapped.

However, this is more likely a case where you haven't got your attributes set right for the components in the program.  Experience with Thinapp and using the troubleshooting tools helps figure this out.  But to start, what error message are you getting?

Do they offer a trial?  If so, I will see if I can help you get it running.

[crescendas]

Hi Bradl,

Where can I get these troubleshooting tools from? And where can I set these attributes?

After I have converted it into thinapp, do I copy the whole folder to the target system and run the executable from the bin folder? I have install the MSI file and run from it as well. But Windows just prompt that it has stopped working immediately.(see attached screen capture)

Note that NAV 4.0 client is officially not support on Windows 2008r2 and Windows 7. Does this mean thinapp will not be able to help too?

[BradI100]

Troubleshooting tools are included.  One is log monitor.  You run that and it generates a trace file that you can read with a text reader.

In effort to help you, I have to say ThinApp can be very complex.  I believe you've probably started out with a project that is too ambitious for your first.  I recommend starting with a program that has no external dependencies.  A self contained program such as notepad+ or Firefox without extensions should get your feet wet.

I read up on the Nav client specs earlier and from what I see, it looks like it would run via thinapp fine on Windows 7 and 2008 Server.  I think some work under the hood will need to be done first.  If you have access to a trial for that version, I will try to help.  But in the meantime, start with some simple apps and work your way up

[crescendas]

There is no license required to install the client. You can download the client at: https://docs.google.com/leaf?id=0B72r18GyeLa6MGY4MGM5OTQtZmQ2NC00MzgxLTk4MzUtZTFiYmE2ZDUzZjBj&hl=en&...

Thanks for helping. I have mark your reply as helpful.

[BradI100]

ok, I will try this now.  Hopefully I won't need to connect to a NAV server to get it running.

[BradI100]

Crescendas, is there a hidden system32 folder in the install directory?  This install keeps failing looking for components within an installdirectory/system32 folder.

[crescendas]

Hi,

The unzip file should have 7 folders inside, including System and System32 folders. Do you not see them?

[BradI100]

They didn't appear in the original, but I found another source.  After a few swipes at it, I'll tell you this is going to be a tough one to decode.  Hopefully will have a recipe for you soon though.

[BradI100]

Ok, here's what I think would help.  Do you have access to the MS Dynamics site for patches, etc?  There is one for NAV 4.0 client: Dynamics NAV IT 4.0 SP3 (KB931841) v03  link

I cannot access it.  But if you can get that, I'd try Thinapping with that rollup installed.

[crescendas]

I can't use SP3 yet because it will upgrade every SQL table it access and cause SP2 client unable to read those upgraded SQL tables. To upgrade to SP3 mean that I need to upgrade each and everyone PC individually for about 50 PCs. Not practical at the moment, until we migrate them to VDI or Terminal Server later. That is why I have to trial SP2 client on Windows 2008r2 as Terminal Server for them to migrate into first.

[BradI100]

Right, I understand what you're saying.  But sometimes it is helpful to "use" components from a working build.  I can keep trying, but it would be helpful to see the difference between a working and non-working install.  Also, which is your default install method?  I was going with minimal.

[crescendas]

Yes, it's minimum installation.

Does this mean that if an WinXP or Windows Server 2003 app cannot be install or run on Windows Server 2008r2, it will never able to run even thru ThinApp?

[BradI100]

I am not sure I understand your question. All I am saying is that apps that fail going from xp to windows 2008 give clues as to why they are failing. In this case it appears to be something to do with the user32.dll --> kernel32.dll, but I don't have enough clues to solve the puzzle.

-Brad

[crescendas]

I manage to get NAV 4.0 Client to run on Windows Server 2008r2 thru Ericom Webconnect 'RemoteView' installed on Windows Server 2003. What Ericom does is to present NAV 4.0 Client display on Windows Server 2008r2 while executing it on Windows Server 2003. It appears as native apps on Windows Server 2008r2 and can even do copy and paste with local apps, except that when you save a file, it get saved into Windows Server 2003 instead of Windows Server 2008.

What impress me is that Ericom claims that these Windows Apps can even run and appear as native apps on Linux and MacOS platform! I think Microsoft has something similar which they called RemoteApp.

I guess ThinApp is mainly for enabling running of multiple conflict versions on the same platform provided that these versions are compatible with the platform in the first place. It won't be able to make old apps to execute on new OS if these apps are not compatible with the new OS in the first place?