Skip to main content
Kofax

Adding a new autorun station and the machine name dropdown is empty

Article # 3018529 - Page views: 285

3018529

Question / Problem: 

When adding a new auto run station, the machine name dropdown is empty, the logger has the following error, what else could I check to fix it?

2019-12-09 12:59:03,782 [7] FATAL Source App: eFlowAutorunStationStarter.exe, A SamlAssertion requires at least one statement.  Ensure that you have added at least one SamlStatement to the SamlAssertion you are creating.

TISAppenderLog4net.Log4NetException: A SamlAssertion requires at least one statement.  Ensure that you have added at least one SamlStatement to the SamlAssertion you are creating. ---> System.ServiceModel.FaultException: A SamlAssertion requires at least one statement.  Ensure that you have added at least one SamlStatement to the SamlAssertion you are creating.

Server stack trace:

   at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)

   at System.ServiceModel.Security.IssuanceTokenProviderBase`1.GetTokenCore(TimeSpan timeout)

   at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)

   at System.ServiceModel.Security.Tokens.IssuedSecurityTokenProvider.GetTokenCore(TimeSpan timeout)

   at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)

   at System.ServiceModel.Security.SecurityProtocol.TryGetSupportingTokens(SecurityProtocolFactory factory, EndpointAddress target, Uri via, Message message, TimeSpan timeout, Boolean isBlockingCall, IList`1& supportingTokens)

   at System.ServiceModel.Security.SymmetricSecurityProtocol.TryGetTokenSynchronouslyForOutgoingSecurity(Message message, SecurityProtocolCorrelationState correlationState, Boolean isBlockingCall, TimeSpan timeout, SecurityToken& token, SecurityTokenParameters& tokenParameters, SecurityToken& prerequisiteWrappingToken, IList`1& supportingTokens, SecurityProtocolCorrelationState& newCorrelationState)

Answer / Solution: 

The windows user running the service and the AppPool was not included under the DomainSecurity.xml, after adding the user the machine name was populated.

 

Applies to:  

Product Version
eFlow 5 & 6

 

 

  • Was this article helpful?