Pegasus Web Xchange - ERR_TOO_MANY_REDIRECTS

Afternoon, All,

I recently installed PWX on a customer's web server.

The PWX Website installed in the Default Web Site site which, at the time of the PWX installation was bound to Port 80, but subsequently rebound to Port 180 to avoid clashing with another Site that requires to be bound to Port 80.

If I browse to the PWX Website - WebXchange - either directly from within IIS, or by browsing to http://<server name>:180/webxchange, I receive error ERR_TOO_MANY_REDIRECTS.

I ran a Chrome add-in - Redirect Path - which advised as follows:

Error 302: Temporary redirect to "http://pwx:180/webxchange/WebsiteException/Error?aspxerrorpath=/webxchange/WebsiteException/Error"

which, I presume, is the PWX bespoke error webpage? I have included a full screenshot of the add-in page in the attached document.

Pegasus Support suggested the following:

"Change the web.config file for the PWX Website, changing all occurrences of:

TargetFramework="4.7.2"
to
TargetFramework="4.0"

and restart the site.

It shouldn't affect the main site because the web.config is per site. In the case of PWX: C:Program Files (x86)PegasusWeb Xchange Website."

I am not sure about the "4.0" as I would have thought that this number should probably reflect the currently installed version of.NET Framework? I'll try the change with a more appropriate version number on Monday.

Anyway, I made the change, as directed, and stopped and restarted the Default Web Site (that contains the PWX Website - WebXchange).

I attempted to browse to the PWX Website, and the ERR_TOO_MANY_REDIRECTS no longer occured, but...

If I browsed directly to the PWX Website (on Port 180) from within IIS, I received error "Server Error in '/WebXchange' Application.".

If, in Chrome, I browsed to http://<server name>:180/webxchange, I received error "HTTP Error 400. The request hostname is invalid."

My knowledge of IIS simply isn't up to attempting to resolve errors, so I am left stumped, other than if a change of TargetFramework version, in the PWX Web config file, resolves the issue.

I have attached a Zipped copy of the explanatory document that I sent to Pegasus Support, that contains (hopefully) helpful screenshots of the various errors.

I just wondered if anyone else had seen the initial ERR_TOO_MANY_REDIRECTS error and, more importantly, had managed to resolve it?

Any help will be gratefully accepted.

In the meantime, have a good weekend, everybody.

Kind regards

Steve

[View:/cfs-file/__key/communityserver-discussions-components-files/35/PWX-_2D00_-ERR_5F00_TOO_5F00_MANY_5F00_REDIRECTS.zip:320:240]

Find more posts tagged with

Pegasus - Partner General Discussions

Accepted answers

All comments

alan-bourke

Steve, yes I have had that redirects issue with a PWX site. Changing the TargetFramework setting is what solved it for me. I think it might be to do with .NET being updated to 4.8.

In my case the redirects message was a bit of a red herring.There is a customErrors setting in the web.config which defaults to "On", meaning any errors in the site will just redirect to a custom error page as you do not want users getting a screenful of .NET exceptions. It was this attempted redirect that was going in circles for some reason when TargetFramework was 4.7.2

If you change that setting to "Off", restart the site and then browse to it then any errors in the site itself will get dumped verbosely into the browser, which may give a clue as to what is wrong.

Steve Loader

Hi Alan,

Thanks, as usual, for your comprehensive reply, much appreciated.

It does seem then that the "targetFramework" setting in the PWX Web Config file is the likely culprit.

I can't quite determine which version of .NET is installed on the customer's server, it looks like it's v4.0, although it may be v4.6.

Anyway, as recommended, I turned off CustomerErrors, and amend the PWX Web Config file to reflect each of .NET versions 4.0, 4.5, 4.6 and 4.7.2 in turn. Each version generated pretty much the same .NET error.

I have provided Pegasus with a document describing that actions that I took, and the errors that I received and, again, have attached a Zipped copy of that document to this discussion.

I suspect that it may not be a case of setting all three instances of targetFramework, in the PWX Web Config file, to the same version, but attempting to determine which version each should be set to.

In addition, if it is indeed .NET v4.0 that is installed on my customer's server, then this appears to have been out of support for many years, and could itself be part of the issue.

I am in discussion with my customer's IT provider, to see if I can install .NET v4.7.2, or even[View:/cfs-file/__key/communityserver-discussions-components-files/35/Central-Construction-Services-Ltd-_2D00_-Incident-16579955-_2800_targetFramework.zip:320:240] v4.8, on the server, as this may simply resolve the issue in one hit.

Anyway, thanks, as always, for your help on this matter, Alan, I'll keep you appraised of any progress.

Kind regards

Steve

alan-bourke

Steve

I use this free, no-install tool to determine exactly which versions of .NET are present, if it's of help:

http://www.asoft.be/prod_netver.html

I believe 4.7.2 is the minimum version required for Opera and PWX, which is why that's the version in the web.config.

4.8 is an in-place, fully backward compatible replacement for 4.7.2 and *should* work transparently.

Steve Loader

Hi Alan,

Thank you for your help with this.

The raw error messages showed the problem to be a communication issue between the Web server, and the Opera 3/SQL server, irrespective of on which server the PWX Configuration Utility was run.

I made some progress by addressing permissions issues, but being restricted to only late night access to the Web server made it difficult to achieve any real break throughs.

Eventually, due to the lack of access to the Web server, increasing frustration from the customer, and concerns from the IT provider that I might destabilise a business-critical server, I abandoned the multi-server installation. I suspect, if the truth be told, I probably needed to work, painstakingly, through the PWX Installation & Implementation Guide, and follow the multi-server setup instructions to the letter.

However, the IT provider kindly agreed to install IIS on the Opera 3/SQL server, and so I installed a single server implementation of PWX which, as you might expect, was an absolute breeze.

A bit frustrating to have to concede defeat, but all's well that ends well.

Thanks for input, Alan, much appreciated.

This Incident is now closed.

Copyright © 2025 Infor. All rights reserved.