Question

Workflow 9.1 route entry to folder (also move entry) error. Invalid object name

Workflow

Updated October 9, 2015

asked on February 18, 2014

Basic workflow that grabs a value from a DB, and places that value in a token. The workflow then attempts to route the starting entry to another folder (creating the path along the way).

If I use the token in my path creation the workflow fails with the error "Invalid object Name"

If I use that token to fill in a field first, then use that field in my path creation it is fine. I can hide the field and work this way but it seems like an unnecessary step.

here is the log info:

Timestamp: 2014-02-18 16:02:16.284
Local Time: 2/18/2014 11:02:16 AM
Category: Activity
Machine: SHIPLEY-LF
Severity: Error
Application Domain: Laserfiche.Workflow.Service.exe
Process Id: 2056
Process Name: C:\Program Files (x86)\Laserfiche\Laserfiche Workflow 9\Laserfiche.Workflow.Service.exe
Win32 Thread Id: 3880 -
Thread Name:
Message: <Exception handlingInstanceId="76639d55-40c4-4bd7-88b2-3fb85ede2f05">
<Description>An exception of type 'System.InvalidOperationException' occurred and was caught.</Description>
<DateTime>2014-02-18 11:02:16Z</DateTime>
<ExceptionType>System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>Invalid object name.</Message>
<Source>Laserfiche.RepositoryAccess</Source>
<HelpLink />
<Property name="InstanceId">9d0581ab-94a5-4447-b23a-d2085aff7f11</Property>
<Property name="ActivityName">MoveDriverPaperworktoproperfolderMoveEntry</Property>
<Property name="TargetSite">System.String MakeInternal(System.String, System.String, Boolean)</Property>
<Property name="HResult">-2146233079</Property>
<StackTrace> at Laserfiche.RepositoryAccess.EntryPath.MakeInternal(String folderPath, String relPath, Boolean relPathIsEntryName)
at Laserfiche.RepositoryAccess.FolderInfo.Create(FolderInfo parent, String name, EntryNameOption options)
at Laserfiche.Connection.Lfso.RepositoryAccess91.LFFolderRA.Create(String name, ILFFolder parentFolder, Boolean autoRename)
at Laserfiche.Connection.Lfso.LFEntryHelper.CreateFolder(LFDatabase database, ILFFolder parentFolder, String name, Boolean autoRename, Boolean autoUnlock, LFVolume defaultVolume)
at Laserfiche.Workflow.Activities.EntryPathExtensions.FindOrCreate(EntryPath destination, LFDatabase database, Boolean autoRename, List`1 warnings, Boolean& createdNew)
at Laserfiche.Workflow.Activities.MoveEntry.MoveEntryTaskModule.MoveEntry(ILFEntry entry, EntryPath destination, MoveEntryAction action, MoveEntryOptionFlags moveOptionFlags)
at Laserfiche.Workflow.Activities.MoveEntry.MoveEntryTaskModule.OnExecute(List`1 results)
at Laserfiche.Workflow.Activities.LaserficheTaskModuleImpl`1.OnExecute(T options, List`1 results)
at Laserfiche.Workflow.Activities.LaserficheTaskModuleBase`1.OnExecute(ILaserficheTaskOptions options, List`1 results)
at Laserfiche.Workflow.Activities.LaserficheTaskModuleBase.Execute(ILaserficheTaskOptions options)
at Laserfiche.Workflow.Runtime.LaserficheTaskExecutorBase.Execute(Object options, SubsystemContextBase statusContext)</StackTrace>
<additionalInfo>
<info name="MachineName" value="SHIPLEY-LF" />
<info name="TimeStamp" value="2/18/2014 4:02:16 PM" />
<info name="FullName" value="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
<info name="AppDomainName" value="Laserfiche.Workflow.Service.exe" />
<info name="ThreadIdentity" value="" />
<info name="WindowsIdentity" value="NT AUTHORITY\SYSTEM" />
</additionalInfo>
</Exception>
----------------------------------------

1 0

Answer

SELECTED ANSWER

replied on February 18, 2014

This is a known issue with Workflow 9.1. It is caused by having trailing spaces in the entry name. It is fixed for Workflow 9.1.1 (due out today). You can use a custom query and trim the trailing spaces from the values or you could run pattern matching on the values to strip out the trailing spaces.

1 0

Replies

replied on February 18, 2014

I had a similar issue. In my case, it was resolved by assigning a specific volume to the new folder, instead of using the parent's volume.

0 0

replied on February 18, 2014

In my scenario my entry does not have any trailing spaces.

0 0

replied on February 18, 2014

For some data types SQL will pad the data with spaces to the column maximum length. The fact that it works if you use the value in a field and then the field in the path would indicate that there is a difference between the 2 values.

Since you are creating the folders in the path along the way, it could also be in one of their names.

0 0

replied on February 18, 2014

As usual you were correct Miruna. I applied a regular expression (removing trailing spaces) to the data being pulled back from SQL and it moved the document this time. Thanks

0 0

replied on May 12, 2014

I just came across this same issue using Workflow and Laserfiche 9.1.1, however, we're not doing any queries...we're simply using the following Fields to create the folder structure: Last Name, First Name Mi Any document that doesn't have a middle initial in the field...the Workflow errors out and gives us the "Invalid Object Name" error. We even tried doing a routing decision so that if the middle initial is blank, then it creates the folder based upon Last Name, First Name...and it still errors out. If we create a new folder in Laserfiche...we can send to that folder...if we rename the current folder (which sits on the root), it still fails. We used LF Scanning and set the default path to Folder\Last Name, First Name Mi and we were able to send a document just fine, and it created the folder and placed the document. Anyone have any other ideas...could it be something with Workflow and the fact that the folder was a folder created from an older version of Lasefiche?

0 0

replied on May 19, 2014

Please open a support case and attach the workflow.

0 0

replied on May 20, 2014

We had the same issue caused by a mix up in upper and lower case letters.

A destination folder was already created named "\Value a", but our calculated folder name was "\Value A". When creating the same folder name manually, you get a prompt asking if it's OK to rename the folder to Value A (2). But in a workflow task, it just throws the Invalid Object Error.

So it is not case sensitive relative to folder names. I am not sure we need different behavior, but what would be useful is a more descriptive error message when this takes place.

1 0

replied on October 9, 2015

I had a similar issue, turns out the folders I had items going to had trailing spaces.

0 0

replied on June 17, 2014

There has not been any info on the specific issue we had, which is similar but not identical to the ones listed earlier in the thread. Should we open a support case?

0 0

replied on June 18, 2014

We never got a solution to ours...we were told to restore from backup.

0 0

replied on June 17, 2015

I had this happen in Workflow when using a token from a database query activity to name a file. The database data contained a tab character.

0 0

replied on August 7, 2015

We have an update on the issue we posted in this thread, which related to how Workflow was handling names with upper and lower case characters. Testing with 9.2, Workflow now works in a case independent manner. The test was to use a value from a field as the folder name.

If a folder named "Ab" exists, workflow will route a document with a value of "aB" to that folder without throwing an error.

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow 9.1 route entry to folder (also move entry) error. Invalid object name

Answer

Replies

Sign in to reply to this post.