Issue installing GP10 with .Net Framework 2.0 SP1

Installing Great Plains Version 10 on .Net Framework 2.0 SP1

By Jivtesh Singh

I read in the newsgroups about this and didn't believe it, till I ran into the issue today.

If you try and install GP 10 on a machine that has .Net 2.0 SP1, the installer would fail. It installs just fine on machines that have .Net 2.0.

Patrick from MSFT Developer support wrote -

I actually ran the install of GP 10.0 and sometime during it I get the error
as well.  So something in the install yet again is checking incorrectly.  I
don't see how development is going to resolve this unless they rebuild the
installs for 10.0 RTM and 10.0 SP1.

I ended up uninstalling .Net framework 2.0 SP1 from the machine and then installing .Net 2.0. I had this luxury with the machine being a new machine, but this would be impossible in most cases. What complicates matters is the fact - that .Net 3.0 requires .Net 2.0 SP1 to be installed. And you can't uninstall .Net 2.0 SP1 if you don't uninstall .Net 3.0. Phew!

There is no knowledgebase article or hotfix about this yet.

However, I just read that if you open a support case with Microsoft - " There is a transform file you can use to install both the Dexterity Shared Components and another one to install Dynamics with. Because this is an issue with our install, the case shouldn't be chargeable unless you have other issues outside this scope. "

I am very interested in knowing how Microsoft resolves this in the long run. Would they release a new setup file ? Will they send out this information to partners ?

I kind of sympathize with them, because I know it can be a pain testing against all versions of frameworks. Windows update would install .Net 2.0 SP1 on most machines, so this probably something we need to be aware of.

Comments

[Andy Nifong]

I've seen this issue a couple of times in the field, and it seemed to do the trick each time, so definitely wanted to save it here for later use.

[No name]

The article ID is 947538.

[No name]

I ran into same issue on a test machine today.  I found this article (though not precisely my or your problem) and it did the trick.