Finance | Project Operations, Human Resources, ...

Installation of Web Client

(0) Share

Report

Posted on by Bill Campbell

We have a situation with our Web Client installation. In early Feb 2022 a new IT consultant changed the Certificate which we had web client connected to and from that point forward the access to Web Client has failed.

We have added new certificate, validated and dated for the next year and the IT provider confirms that the certificate works.

Now when we connect to the Web Client we are experiencing "the Correlation" error when attempting to connect. We have spent many hours working on the security issues - all users have been confirmed to have access to the Web Client user, we have confirmed that the services 'appear' to be intact - however, we are not able to confirm as no one can access any of the Web Components.

At this point the decision has been made to re-install the Web Client

We have removed:

- - Web Client Component

We have repaired

-- eConnect GP2018

We are now trying to reinstall that Web Client and we have encountered the following error message:

This message appears as we are processing through the Installation wizard. Each time we complete a screen we get this message - clicking on Continue allows the Wizard to complete

Once the wizard reaches the last screen, we click on OK and then we get the following message:

We have attempted the installation 3 or 4 times and get the same message set each time.

HELP

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (18)

Answers (0)

Suggested answer

Derek Albaugh on at

Like (0)

Report

I mentioned this in another forum here, but the steps I usually recommend using, when removing Web Client, before reinstalling it, are the following:

1. From Control Panel > Programs > Programs and Features, uninstall Microsoft Dynamics GP Web Components.

2. Browse to C:\Program Files\Microsoft Dynamics\ and verify the Web Components directory is completely gone or empty.

3. Run the 'netsh http show urlacl' script in the Command Prompt: Admin window and verify that you don't see any URL reservations for the following:

-- https://+:443/RuntimeService/

-- https://+:48651/SessionService/

-- https://+:48650/SessionCentralService/

If you see any URL reservations for the port numbers/services mentioned above, use the example script to delete the URL reservation:

netsh http delete urlacl url=https://+:443/RuntimeService/

4. In SQL, delete the existing GPCONFIGURATION database.

5. In IIS Manager, for the site that you’re installing Web Client onto, click on ‘Bindings’ or right-click on the site and choose ‘Edit Bindings’.

In the Site Bindings window that opens, select the HTTPS binding and click the ‘Edit…’ button.

In the Edit Site Binding window that opens for HTTPS, make sure the IP Address field is set to ‘All Unassigned’, the port is normally 443, the Host Name field needs to be blank/empty and the ‘Require Server Name Indication’ option should be un-marked.

In the SSL Certificate field, select your self-signed SSL certificate you’re using for Web Client and click OK to save any changes and close that window, then click Close to close the Site Bindings window.

6. At this point, you can then launch the reinstall of Web Client for Dynamics, again.

On the IIS/web server, for the Session Central Service, we only need to enter the domain account that will be running that service, which is what you have/had setup. We don’t want to tie the certificate to this service.

On the session host server(s), for the Session Service, again you only need to enter the domain account that will be running that service and not tying the certificate to this service either.

For the Runtime Service on the session host server(s), we have to add the certificate to it, thus it’d get the host name of the new SSL certificate being used with Web Client and bound to the IIS site in step 5 above.

7. Once the reinstall of Web Client is completed successfully including the creation of the GPCONFIGURATION database again, if you're using a wildcard certificate or a certificate that is setup with a host name different than the FQDN of the server where the Runtime Service is installed, you may need to setup some type of DNS or forwarding from the host name of the SSL certificate to the IP address of the server Web Client is installed onto, otherwise, you'd be able to test launching Web Client again and see if users can access Dynamics GP through it.

If it doesn’t work still, we’d want to look at the Event Viewer/Dynamics log again to see what error information it is showing, to go with any errors that are seen in the browser window, if any.

Thanks

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Derek, thanks for the step by step information - I got to 're-start' the installation, however, I got the same error. As noted about the Web Components - Unhandled Exception

Index was outside the bounds of the array

Here are the details from the Details button

*****

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.IndexOutOfRangeException: Index was outside the bounds of the array.

at Microsoft.Dynamics.GP.Deployment.UI.Controls.CertificatePanel.LoadCertificates()

at Microsoft.Dynamics.GPWebClient.UX.Dialogs.SessionCentralService.OnShown(EventArgs e)

at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

************** Loaded Assemblies **************

mscorlib

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3920.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

----------------------------------------

Microsoft.Dynamics.GPWebComponents.UX

Assembly Version: 1.0.0.0

Win32 Version: 6.0.61.0

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Dynamics.GPWebComponents.UX.EXE

----------------------------------------

Microsoft.Dynamics.Deployment

Assembly Version: 3.10.0.0

Win32 Version: 3.10.1.13

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Dynamics.Deployment.DLL

----------------------------------------

System.Windows.Forms

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3835.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3650.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1586.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

Microsoft.Dynamics.Deployment.WindowsInstaller

Assembly Version: 3.10.0.0

Win32 Version: 3.10.1.13

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Dynamics.Deployment.WindowsInstaller.DLL

----------------------------------------

Microsoft.Deployment.WindowsInstaller

Assembly Version: 3.0.0.0

Win32 Version: 3.10.0.2026

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Deployment.WindowsInstaller.DLL

----------------------------------------

Microsoft.Dynamics.Deployment.UI.Forms

Assembly Version: 3.10.0.0

Win32 Version: 3.10.1.13

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Dynamics.Deployment.UI.Forms.DLL

----------------------------------------

Microsoft.Dynamics.Deployment.UI.Controls

Assembly Version: 3.10.0.0

Win32 Version: 3.10.1.13

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Dynamics.Deployment.UI.Controls.DLL

----------------------------------------

System.Xml

Assembly Version: 4.0.0.0

Win32 Version: 4.7.2612.0 built by: NET471REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Configuration

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3630.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Core

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3920.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

Accessibility

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1586.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

Microsoft.Dynamics.GP.Deployment

Assembly Version: 16.0.0.0

Win32 Version: 16.00.0305.000

CodeBase: file:///C:/Users/Dynadmin/AppData/Local/Temp/2/tmp88C8.tmp/Microsoft.Dynamics.GP.Deployment.DLL

----------------------------------------

Anonymously Hosted DynamicMethods Assembly

Assembly Version: 0.0.0.0

Win32 Version: 4.7.3920.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll

----------------------------------------

System.Data

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3905.0 built by: NET472REL1LAST_B

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

System.Transactions

Assembly Version: 4.0.0.0

Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll

----------------------------------------

System.EnterpriseServices

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1586.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

*****

End of Details section

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh on at

Like (0)

Report

When does this exception error show, when attempting to install Web Client? If so, at what window, exactly or does it show when just launching the re-install?

Thanks

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

I am running Setup again - Web Client - Repair - when I click to open this screen - the message

If I click ok - I can complete the screen - this is the second time I get the message -

Again, click continue and the wizard completes - the system goes through the motion of running the repair - updates a number of files and comes to a completed sucessfully screen.

Then starts the Web Component Config - completes - click continue

Now when I connect to gp/gpweb on browser - I get to SIGN IN - however it does not complete - I have left it sitting (in waiting mode) for 30 min and nothing happens.

Not sure what to do next.

Thanks.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi Bill,

What helped in my case (see my reply on the other thread here : community.dynamics.com/.../unable-to-access-gp-web-client-after-certificate-updates) was that I went thru the IIS rebuild step.

Your error looks like related to some .NET or IIS setup issues and I'd simply try to remove IIS (unless there are some other instances setup on this same system) and completely un-install the GP Web Client (if not done already). Make sure everything is clean slate and then start from scratch. Keep a copy of some of the GPCONFIGURATION tables handy in an Excel workbook, as they serve as a reference for the security settings of users & groups to grant access to the Web Client UI.

If that still doesn't help, try to run a repair on your .NET 4.5 or 4.6 libraries.. it could be caused by a recent windows updates that has screwed something up.

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Hi all, so once again I have followed the steps outlined above and still after starting the installation of Web Client - I enter the SQL Name and login, then click OK - goes to Session Central Service - and POP goes the same message about the Web Components. If I click on CONTINUE the wizard allows me to continue, then on GP Services - same message - at the end of the wizard, it appears to be complete, but then the final message appear - and nothing is installed.

I have - uninstalled all the web components, including the GPConfiguration database are removed.

Stopped dead in the water - need assistance as the client is not able to access GP AT ALL.

Thanks.

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh on at

Like (0)

Report

Recently saw a similar case and found a series of things that you can verify:

1. Verify all the required roles and features are installed on the server, as per the Web Client install guide, such as ASP.NET, HTTP Activation, the Common HTTP features, Windows Authentication under Security, etc.

2. Verify the binding on the IIS site you're installing Web Client onto is correct for HTTPS, such as nothing is in the Host Name field and the 'Require Server Name Indication' doesn't need to be marked. The IP address should be set to 'All Unassigned' and the SSL certificate selected. Everything else can be un-marked or blank.

3. I've seen where using an IIS site other than the Default Web Site has resolved issues with Web Client. We just need to make sure the new IIS site is extended with ASP.NET.

4. If trying to install Web Client with a external certificate or CA certificate, try testing with a self-signed certificate created in IIS Manager, making sure it is setup as a 'Personal' store certificate and see if that resolves the .NET / JIT error seen on the install windows where the certificate is selected, i.e. Session Central Service, Session Service and the required Runtime Service.

The customer where we saw this same type of issue also had some extra LDAP setup that was requiring additional authentication which caused Web Client to act differently.

Even though we got the .NET/JIT messages, we were able to select the certificate on the Runtime Service where it was required and the install did go through and they could access Web Client and get into Dynamics GP, but I think they still had an issue with the Web Mgmt Console.

I would check the above though and if I find out any more information, I'll update this forum and let you know.

Thanks

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Derek, thanks for the detail steps - I have (1) removed all IIS sites and recreated them (2) the ASP extension appears to be automatic in .Net 4(x) so that did not work (3) created new Web Site and ensured on https: to port 443 was bound to the SSL certificate - as noted all other points are blank.

So now I started to re-install the web components.

After entering the SQL Server name - Login as SA + password, then click enter - then I get the error message

Unhandled exception has occurred - same as posted in this thread above - clicking on the continue will allow me to continue to step through the wizard - however at the end get the final message

Clicking OK at this point closes the wizard. Looking then at the Add / Remove Programs - there are no Web Components installed.

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh on at

Like (0)

Report

Not that I think it'll resolve the error, but for the Dex Service Control, if you don't plan on using Service Based Architecture (SBA), you don't need to install it along with Web Client, de-selecting all the SBA features in that window.

I'd be curious if you had another IIS server, if the same error showed when installing Web Client on that other server?

Also, have you tried completely removing IIS from the web server, if nothing else uses it besides Web Client, and then rebooting the server before re-installing again?

That and using a self-signed, basic certificate is what I would try to see if we get past this .NET/JIT error.

Thanks

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Greetings all,

So very frustrated by this issue and nothing provided above seems to have made any difference.

We have now got a new - fresh VM computer started that was blank. We followed the Web Client installation guide as provided for GP2013 and while there are a number of differences in some of the options that are presented, working with the client IT team, we are confident that the IIS installation is correct.

We then proceed to install the Dynamics Client on the machine, applied the necessary patches to get the versions alligned and we had / have correct access to Dynamics on the machine - as a desktop client.

Then we move onto the installation of the Web Client - and POW - same error message as before - happens immediately after enter the Server Name, entering the login - using SA - then client enter- and there is the message that we are out of bounds.

Not that I am upset, I just can not believe that I can not install the software using the same tools we all have and that we are all running with for the pasts (uncountable) years.

How do I escalate this to get a Microsoft Tech to connect with us and do a deep dive on the problem, connected to the client machine, and assist us to resolve.

Thanks.

Was this reply helpful? Yes No