MR on remote server can longer see GPserver

(1) Share

Report

Posted on by Richard Wheeler

75,852 Moderator

On a client's remote server users can no longer launch Report Designer as it claims the server address is incorrect. All the W10 workstations can run MR as MR is running on the server.

This is the message in the event viewer.

SOAP security negotiation with 'greatplains2020.mydomain.com:4712/FontStyleService.svc' for target 'greatplains2020.mydomain.com:4712/FontStyleService.svc' failed. See inner exception for more details. Machine: LINDEN-RDS-1

MR had been working fine for years until this morning. All firewalls are off.

Any suggestions?

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (5)

Answers (0)

Sort by

jbeck2014 365 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm having the same problem. The only thing that changed on both the GP server and the terminal server are the November Windows updates from Microsoft.

Julie

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Damn those Windows updates!!! If we find what is I will post it here.

Was this reply helpful? Yes No
Gavin 2,510 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

I had a similar issue with Management Reporter just this week, and although it wasn't the exact same error message, I created an SPN as per cause 9 in this article which fixed the issue https://learn.microsoft.com/en-us/troubleshoot/dynamics/gp/cannot-connect-to-server-error-message-when-starting-management-reporter

Just thought I'd post as it might be worth a shot.

Thanks

Gavin

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks, I saw that as well. We loaded Windows updates on both the GP and RDS servers. Once both rebooted the connection for MR worked again.

Was this reply helpful? Yes No
Greg Byer 2,588 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Richard,

Thanks for posting this. We've seen an increase in cases with connection errors in the last few weeks and suspect that they are related to Windows update KB5019964 from November 8.

support.microsoft.com/.../november-8-2022-kb5019964-os-build-14393-5501-5c195bd1-91d5-402e-a973-813373ba4357

If you view the article above, there are known issues with Kerberos authentication and installing on Windows Servers with the Domain Control role.

As was mentioned in this thread, the SOAP security error is usually resolved with running the SETSPN commands. But it's good to know that rebooting the server, the connection worked for you again. If rebooting worked for anyone else, let me know.

Was this reply helpful? Yes No