CASM 17.4.1 SrvicePoint - seslcted Offerings - screen 'dies'

[Peter Schmidt]

Hi,

at a customer we are still running 17.4 RU01.

After integrating products and doing additional integration steps manually, searchserver is running ok with xFlow and ServicePoint.

in ServicePoint searching shows the expected results and Catalog-Offerings are presented as expected.

In Catalog offerings can be worked on.

If we now select an offering beneath Servicepoint selected form starts but dies and we fall back to view where more-button can be used.

There is an toast-message which comes as soon as offering is selected (no wait-time):

which means Activity timed out. Try it again.

In view.log of catalog you get get 2 lines at this moment:

2025/04/04 12.47.22.962 INFO  [http-nio-9090-exec-6] [WPFServlet] END: Time taken for GET request, Node=icguinode.request_create&NspPath=&Args=10004&Args=true&ObjectID=10004&b2b=json-html&portal=true&locale=de-DE&callback=jQuery36206009683693751773_1743760989755&_=1743760989759 is:0
2025/04/04 12.47.23.321 INFO  [http-nio-9090-exec-10] [WPFServlet] END: Time taken for GET request, Node=icguinode.buiticketsstatus&b2b=json-html&X-AccessToken=9a952804bae2d58d1faf8309559688eebb8f672cbce565c02c96d153e7e72a61fe9c799fc84a74f203a3e7f8b369404b282a307b74972397be3cf10151dabb38&callback=ng_jsonp_callback_5 is:0

When starting ServicePoint (when catalog-login is running in the background) we have NO error.

I checked configuration as far as I know it and compared it with other installations at other customers where it is running well.

Any idea for it?

Regards,

Peter

PS.: Headline should be: CASM 17.4.1 ServicePoint - selected Offerings - screen 'dies'

[Peter Schmidt]

Additional Info,

I switched xFlow from NTLM to BASIC-authentication and problem is gone.

I'm now searching further for NTLM-Problems in configuration.

[Peter Schmidt]

Seem to be a NTLM-Problem in customer's env in combination with Browser-Rules.

I'll come back later