Share
ReportA strange error exception has started in our setup and it has our network admin and GP staff puzzled.
Background:
We have GP running on an application server as well as recently turned on GP Web Services. This machine is inside our network domain and let's call it machine GP1. I have written some code in an application that communicates over the Service to return information regarding an invoice. it works as expected when I run from my local development machine as well as when I publish it to a web server (all inside our domain).
The error happens as soon as I try and run the test application or web app code from our webserver (WS1) which inside a dmz, outside our firewall. We opened the ports for the GP web service and can successfully put the URL for GP webservices into a browser from the WS1 and see the correct information.
Here is the full exception:
System.ServiceModel.Security.SecurityNegotiationException: The caller was not authenticated by the service. ---> System.ServiceModel.FaultException: The request for security token could not be satisfied because authentication failed.
at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
--- End of inner exception stack trace ---
We must be missing a step in the setup process here, but don't really know what to do. Any suggestions?
*This post is locked for comments
All responses (
Answers (
291,280
