You are viewing limited content. For full access, please sign in.

Question

Question

Seem to be having issues with getting the AD Look up of an email address to work

asked on November 20, 2013

 I am not receiving emails through the User Task Notification.

 

So I tested in Workflow looking up an email address via the Email Activity instead of typing an actual email just entering the AD Account.

 

I am getting no email associated. "The selected user does not have an email associated"

 

Testing an email from both Forms and Workflow in the Email configuration Setup works fine.

 

I just spoke with the System Admin and we looked at AD is seems the field email field is populated for the user, we have tried a couple users.

 

I do have the trustee setup for their AD Server in the Workflow Configuration.

 

Seems to issue is pulling the email from AD however everything seems to be configured.

 

They are running Exchange 2003 any suggestions?

Replies

replied on November 20, 2013

This is a configuration issue. You need to add these users/groups to the participants of the Forms and that should fix the issue

replied on November 20, 2013

I have had this before. I do not believe it is because of Exchange 2003 but merely an incomplete setup of Forms. Check your users listed in the (servername)/Home/Security area

replied on November 20, 2013

User is listed there.

 

Seems to be related to AD lookup as it is not working in Workflow either.

 

 

replied on November 20, 2013

Are these Laserfiche users or domain accounts? In Workflow, are you looking up their email addresses in the repository trustee provider or did you create a separate trustee provider for the active directory?

replied on November 20, 2013

Interesting that you asked.

 

You are correct I only had the Workflow Configuration set up for Laserfiche Users. I was not aware that the email attribute would not pull through a Laserfiche Trusted AD account even though the Email acitivity would show the Laserfiche AD Trusted account no email was populated in the Email Attribute column. Once I configured a DOMAIN under the LDAP Tab for Active Directory in the Workflow Trustee Directories I no longer have a problem pulling the email account.

 

However, the Workflow exercise was only to test if I was pulling an email as my actual problem is not receiving emails through FORMS USER TASK NOTIFICATIONS.

 

It seems to me FORMS is doing the same thing. Pulling the Laserfiche AD Trustee which does not have an associated email. How can I get forms to pull the LDAP/Active Directory for the user therefore having access to the email?

 

To my knowledge Forms Config is setup for Active Directory and Domain.

 

Test emails are sent from the EMAIL forms configuration page without any issues.

 

What tools or resources might be available to see what is happening when it  attempts to send the email, if it attempted, if it sent etc....

 

Any suggestions for getting emails sent from Forms gotchas etc....

replied on November 20, 2013

Is the Active Directory Domain field filled on the Forms Configuration page? See this help topic for more information. Be sure that both IIS and the Laserfiche Forms Routing Service have access to the domain.

 

If that seems to be correctly configured, you can use the Forms API to try and pinpoint the issue.

 

  1. On the Forms Server machine, navigate to the following URL, substituting a valid domain account for domain\\username: http://localhost/Forms/api/User/Email.xml?userNames=[%22domain\\username%22]
  2. If the page returns an error, it means the API is not configured correctly. If this is the case, let me know and we'll troubleshoot further.
  3. If the page returns a blank email address, it means that Forms is not communicating with the AD server. You'll want to look at your settings on the Forms Configuration page to see if there's an error.
replied on February 21, 2014

Hey Eric,

 

What happens if you enter the URL and you get a valid email address back but you're still not getting email notifications? I checked the cf_users table and there is a NULL value in the email column for my domain account - does that have anything to do with it (in other words, should domain accounts have a value in the email column or is that just for LDAP and repository named users)? Thanks!

replied on February 24, 2014

If the Forms API is returning the correct email address for the user, it should mean that Forms is correctly configured to communicate with the AD server. I don't think the null values in the cf_users table are an issue. I will investigate further and get back to you.

replied on February 24, 2014

Hi Kacy,

 

May I know which version of Forms are you testing on?

replied on February 24, 2014

Hi Johnny, I'm using 9.1.0.1441.

replied on February 24, 2014

Okay, it just started working today. That is so strange.  I tested at least 7 or 8 times last week and got no emails.

replied on February 25, 2014

Hi Kacy, in 9.1, Forms is getting email from cf_users table. And the email column in cf_users table is updated by the user synchronization service. If it's NULL then there will be no email sent. In addition to wait for periodical user sync, you could also manually force Forms to sync users by going to System Security page and clicking Synchronize Users. If sync is not working, please check out whether you put the correct domain controller in FormsConfig.

replied on November 21, 2013

Tried the following URL's (The Default Web Site is Set to HTTPS Port 8080, HTTP 8084 to support WebDAV on this Server.

 

https://localhost:8080/Forms/api/User/Email.xml?userNames=[%22cougar\\cdillon%22]

 

Get the following response:

 

Server Error in '/Forms' Application.


Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file.

Source Error:


 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:

 

[InvalidOperationException: Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file.]
   System.ServiceModel.Web.WebServiceHost.AddAutomaticWebHttpBindingEndpoints(ServiceHost host, IDictionary`2 implementedContracts, String multipleContractsErrorMessage, String standardEndpointKind) +933
   System.ServiceModel.Web.WebServiceHost.OnOpening() +244
   System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) +274
   System.ServiceModel.Channels.CommunicationObject.Open() +36
   System.ServiceModel.HostingManager.ActivateService(String normalizedVirtualPath) +184
   System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath) +615

[ServiceActivationException: The service '/Forms/api' cannot be activated due to an exception during compilation.  The exception message is: Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file..]
   System.Runtime.AsyncResult.End(IAsyncResult result) +679246
   System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +190
   System.ServiceModel.Activation.AspNetRouteServiceHttpHandler.EndProcessRequest(IAsyncResult result) +6
   System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +96


 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1           

 

 

http://localhost:8084/Forms/api/User/Email.xml?userNames=[%22cougar\\cdillon%22]

 

Server Error in '/Forms' Application.


Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file.

Source Error:


 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:

 

[InvalidOperationException: Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file.]
   System.ServiceModel.Web.WebServiceHost.AddAutomaticWebHttpBindingEndpoints(ServiceHost host, IDictionary`2 implementedContracts, String multipleContractsErrorMessage, String standardEndpointKind) +933
   System.ServiceModel.Web.WebServiceHost.OnOpening() +244
   System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) +274
   System.ServiceModel.Channels.CommunicationObject.Open() +36
   System.ServiceModel.HostingManager.ActivateService(String normalizedVirtualPath) +184
   System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath) +615

[ServiceActivationException: The service '/Forms/api' cannot be activated due to an exception during compilation.  The exception message is: Service 'LfFormService' implements multiple ServiceContract types, and no endpoints are defined in the configuration file. WebServiceHost can set up default endpoints, but only if the service implements only a single ServiceContract. Either change the service to only implement a single ServiceContract, or else define endpoints for the service explicitly in the configuration file..]
   System.Runtime.AsyncResult.End(IAsyncResult result) +679246
   System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +190
   System.ServiceModel.Activation.AspNetRouteServiceHttpHandler.EndProcessRequest(IAsyncResult result) +6
   System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +96


 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1           

replied on November 25, 2013

Could you please show us the content of the Forms/Api/Web.config under install directory? It seems to be caused by incorrect configuration.

replied on November 25, 2013

I am having the customer collect.

 

In the mean time would this be relevant.

 

I have attached a document indicating a Web Based SMTP Authentication Error.

replied on November 25, 2013


FYI. As a side note in some previous troubleshooting the customer was requested through our and your help desk to change the Listening Port on the Laserfiche Server as a method to test for performance issues.

So when Forms was installed Laserfiche was listening on Port 81.

It turns out the Port was irrelevant to performance so it has since been changed back to Port 80 could this have any affect.

Everything else has been changed accordingly and works fine including Web Access, Workflow etc....

replied on November 26, 2013

Contents of Web.config:

 

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.web>
    <compilation debug="true" targetFramework="4.0">
    </compilation>
    <customErrors mode="Off" />
    <httpRuntime maxRequestLength="67108864" />
  </system.web>
  <appSettings>
  </appSettings>
  <system.serviceModel>
    <services>
      <service name="Laserfiche.Forms.Api.LfFormService">
        <!--<endpoint address="" behaviorConfiguration="Laserfiche.Forms.Api.WebHttpBehavior1" binding="webHttpBinding" bindingConfiguration="streamedBindingSecure" contract="Laserfiche.Forms.Api.ILfFormService"/>-->
        <!--<host>
                    <baseAddresses>
                        <add baseAddress="http://rosemead.laserfiche.com/E-Forms/"/>
                        <add baseAddress="https://rosemead.laserfiche.com/E-Forms/"/>
                    </baseAddresses>
                </host>-->
        <endpoint address="" behaviorConfiguration="Laserfiche.Forms.Api.WebHttpBehavior1" binding="webHttpBinding" bindingConfiguration="streamedBinding" contract="Laserfiche.Forms.Api.ILfFormService" />
      </service>
    </services>
    <bindings>
      <webHttpBinding>
        <!--<binding name="streamedBindingSecure" transferMode="StreamedRequest" maxReceivedMessageSize="2147483648" maxBufferSize="1048576" contentTypeMapper="Laserfiche.Forms.Api.Host.RawContentTypeMapper, E-Forms">
                    <security mode="Transport"/>
                </binding>-->
        <binding name="streamedBinding" transferMode="StreamedRequest" maxReceivedMessageSize="2147483648" maxBufferSize="1048576" contentTypeMapper="Laserfiche.Forms.Api.Host.RawContentTypeMapper, E-Forms">
          <security mode="None" />
        </binding>
      </webHttpBinding>
    </bindings>
    <behaviors>
      <serviceBehaviors>
        <behavior>
          <serviceAuthorization serviceAuthorizationManagerType="Laserfiche.Forms.Api.Host.ApiAuthentication, E-Forms" />
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
          <serviceDebug includeExceptionDetailInFaults="false" />
        </behavior>
      </serviceBehaviors>
      <endpointBehaviors>
        <behavior name="Laserfiche.Forms.Api.WebHttpBehavior1">
          <webHttp helpEnabled="true" automaticFormatSelectionEnabled="false" />
        </behavior>
      </endpointBehaviors>
    </behaviors>
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true">
    </modules>
  </system.webServer>
</configuration>

replied on November 27, 2013

Please open a support case so we can further troubleshoot this issue.

replied on November 28, 2013

Case has been opened.

 

Case ID 157320

You are not allowed to follow up in this post.