This post is part of the Hands on with the Microsoft Dynamics GP Fall 2020 Release series where I am hands on with the newly released Microsoft Dynamics GP Fall 2020 Release.
Before installing any of the Microsoft Dynamics GP components, you need to make sure the system requirements are met. On top of this there is also some prerequisites which need to be met before the Microsoft Dynamics GP client or other components can be installed.
Most of these prerequisites can be handled by installer process, there is one which cannot; this is the .NET Framework 3.5 feature which is installed using the Add Roles and Features Wizard available via Server Manager on Windows Server or using Turn Windows features on or off accessible via Program and Features on Windows.
If the PC or server you’re planning to install Microsoft Dynamics GP onto has an Internet connection, then the .NET can be installed simply by using the wizard. However, if, for whatever reason, you don’t have an Internet connection available, the install process isn’t quite that smooth.
However, for both server and PC you can do an offline install and I have blogged about this several years ago:
Offline install on Windows.
Offline install on Windows Server.
The above articles are for older versions of Windows Server and Windows, but the process is exactly the same on current versions.
One of the prerequisites of Microsoft Dynamics GP 2016 R2 is .NET 4.6. However, occasionally when installing it, the Microsoft Dynamics GP 2016 Bootstrapper Setup will throw an error showing that the .NET Framework installation failed:
Microsoft Dynamics GP 2016 Bootstrapper Setup
An error occurred while installing system components for Microsoft Dynamics GP 2016 Bootstrapper. Setup cannot continue until all system components have been installed.
The problem is that neither this error message nor the error log it directs you to contains information as to the cause of the error.
Continue reading ".NET 4.6 Installation Error When Installing Microsoft Dynamics GP 2016 R2 Prerequisites"
In the past when I have needed to manually register DLLs they have been C++ or VB ones which are registered using the regsrver command.
A recent project for a client was done using C# which requires the assembly to be registered using a different command. I am posting this here as a reminder to myself next time I need to do this.
When you register the assembly, you may receive a warning message about registering unsigned assemblies using the /codebase switch which is intended only with signed assemblies. If you trust the origin of the assembly then you can safely register the assembly and ignore the warning.
To register the .NET DLL, open a command prompt and type the following (the highlighted section is the name of the assembly being registered):
%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\regasm.exe reportprinter.dll /codebase
To unregister a .NET DLL type the following:
%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\regasm.exe reportprinter.dll /unregister
The highlighted section is the dll being registered or unregistered.
This is not something I need for the series of posts I am currently writing on the Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment as my web server is running Windows Server 2012, but you may be performing the install on Windows Server 2008 R2 so I thought I would include this for completeness.
If you are running Windows Server 2008 R2 then extending a website with ASP.NET 4.5 required the use of the command line.
Open a Command Prompt with Administrative permissions and type the following and then hit Return:
Then type the following and hit Return:
Once the command has finished running, the website will be extended with ASP.NET 4.5 and be ready for the Session Control Service to be installed.
Extending a website with ASP.NET 4.5 required the use of command line (which I will cover in the next post), but Windows Server 2012 requires this be done using the Server Manager (there may be a PowerShell command to do this, but, if so, I don't know what it is).
As I mentioned in a comment in the last post, if you're installing IIS to configure the web client then you don't need to treat this step separately, but merely add the step to the installation options for IIS.
To extend IIS on Windows Server 2012, you need to open Server Manager and click Add roles and features:
Continue reading "Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Extending IIS With ASP.NET 4.5 On Windows Server 2012"
Before we can start installing the Microsoft Dynamics GP 2013 SP2 Web Client, there are a few steps which need to be completed.
The first of them is to install the IIS Web Server on the machine which will operate as the Session Control Server. In my case, this is the SC1 machine which is running Windows Server 2012. IIS is installed via Server Manager by clicking Add roles and features:
Continue reading "Microsoft Dynamics GP 2013 SP2 Web Client Scale-Out Deployment: Installing IIS On Session Control Server"
In the last post I took a look at how to install the .NET Framework 3.5 while the server is not connected to the Internet. At the same time I installed the server I was also installing a Windows 8 client as well and needed to install the .NET Framework 3.5 on it as well. Being client software I expected the process to work, if not better than, then the same as the one on Windows Server 2012.
Continue reading "Offline Install Of dotNET 3.5 On Windows 8"
I recently encountered a problem trying to install the .NET Framework 3.5 in a virtual machine on my test server which is not connected to the Internet (I wish it was but I am currently renting and don't have a broadband connection). I am used to dealing with Windows Server 2008 R2 where the install just happens, but in Windows Server 2012 the Add roles and features wants to download the install files from the Internet.
In this post I'm going to do a step by step guide to installing the .NET Framework 3.5 on Server 2012 when there is no Internet connection available; many to serve as a reminder to me next time I try to do this.
The first step is to open Server Manager and click on Add roles and features;
Continue reading "Offline Install Of dotNET 3.5 On Windows Server 2012"