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

Question

Question

Workflow subscriber error 9013

Workflow
Updated November 4, 2015
asked on November 3, 2015

One of our customer has an issue in the workflow server,

all workflows suddenly stop working,if we try to run the workflow from the designer it works fine but from the client is not working, we created a sample workflow has one condition and still not working.

we checked the Error Log in workflow administration console and it show an error on subscriber_error_log 

"AccessDenied"

 

Is there any solution for this issue?

0 0

Replies

replied on November 3, 2015

It sounds like the Workflow Subscriber is being denied access to the Repository.  The subscriber is what monitors the repository to trigger the workflow rules.

Go through the subscriber configuration and make sure it is able to reach the desired repository.

0 0
replied on November 3, 2015

Can you post the entire error message? This can happen in 2 cases:

  1. A second subscriber is connected to the repository incorrectly, so it changed the password for the account the Subscriber uses to log in
  2. The repository is a copy of an existing repository and it has its unique identifier incorrectly edited.
0 0
replied on November 3, 2015 • Show version history

thanks ,please find the entire message:

 

Timestamp: 2015-11-03 02:26:25.052
Local Time: 11/3/2015 5:26:25 AM
Category: Errors
Machine: *****
Severity: Error
Application Domain: Laserfiche.Workflow.Subscriber.exe
Process Id: 5044
Process Name: C:\Program Files\Laserfiche\Laserfiche Workflow 9\Laserfiche.Workflow.Subscriber.exe
Win32 Thread Id: 980 - ************ Notification Thread
Thread Name: ****************** Notification Thread
Message: <Exception handlingInstanceId="1aa7db6b-8b02-475f-978b-40cf8bc4d999">
  <Description>An exception of type 'Laserfiche.Connection.LFSOException' occurred and was caught.</Description>
  <DateTime>2015-11-03 05:26:25Z</DateTime>
  <ExceptionType>Laserfiche.Connection.LFSOException, Laserfiche.Workflow.Common, Version=8.3.0.0, Culture=neutral, PublicKeyToken=d8428ff9263e6cda</ExceptionType>
  <Message>Access denied. [9013]</Message>
  <Source />
  <HelpLink />
  <Property name="LFROError">False</Property>
  <Property name="LFSOError">False</Property>
  <Property name="ErrorCode">9013</Property>
  <Property name="TargetSite">&lt;undefined value&gt;</Property>
  <Property name="HResult">-2146233088</Property>
  <StackTrace />
  <additionalInfo>
    <info name="MachineName" value="*******" />
    <info name="TimeStamp" value="11/3/2015 2:26:25 AM" />
    <info name="FullName" value="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    <info name="AppDomainName" value="Laserfiche.Workflow.Subscriber.exe" />
    <info name="ThreadIdentity" value="" />
    <info name="WindowsIdentity" value="NT AUTHORITY\SYSTEM" />
  </additionalInfo>
  <InnerException>
    <ExceptionType>Laserfiche.RepositoryAccess.AccessDeniedException, Laserfiche.RepositoryAccess, Version=9.1.0.0, Culture=neutral, PublicKeyToken=3f98b3eaee6c16a6</ExceptionType>
    <Message>Access denied. [9013]</Message>
    <Source>Laserfiche.RepositoryAccess</Source>
    <HelpLink />
    <Property name="ErrorCode">9013</Property>
    <Property name="TargetSite">Void GetRows(Int64)</Property>
    <Property name="HResult">-2146233088</Property>
    <StackTrace>   at Laserfiche.RepositoryAccess.Activity.ActivityLogReader.GetRows(Int64 nextChunkAsn)
   at Laserfiche.Connection.Lfso.RepositoryAccess91.LFDatabaseRA.GetActivities(Int64 startSequenceNumber, Int64 endSequenceNumber)
   at Laserfiche.Workflow.Subscriber.Runtime.Threads.NotificationThread.CheckForNewDatabase(LFDatabase database, Int64 lastASN)</StackTrace>
  </InnerException>
</Exception>

 

0 0
replied on November 4, 2015

That looks like it could be the second case. It's probably best you open a support case at this point so we can take a closer look.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...