It's not missing, their are two of them. 9.0.0 and 9.1.0 versions and it wont resolve itself

What files are we talking about?

It's specifically the RepositoryAccess references.

 error CS0433: The type 'Laserfiche.RepositoryAccess.Session' exists in both 'c:\Windows\assembly\GAC_MSIL\Laserfiche.RepositoryAccess\9.0.0.0__3f98b3eaee6c16a6\Laserfiche.RepositoryAccess.dll' and 'c:\Windows\Microsoft.NET\assembly\GAC_MSIL\Laserfiche.RepositoryAccess\v4.0_9.1.0.0__3f98b3eaee6c16a6\Laserfiche.RepositoryAccess.dll'

What if you remove the reference to RA 9.0?

I only have 1 reference in there (9.0) and removing means I cannot compile it. I have tried switching around which reference I use.

Currently, It compiles and runs fine in the Script Editor but will not allow me to publish the workflow that contains it.

If you right click on the Laserfiche.RepositoryAccess under References and choose Details from the context menu, is it listed as 9.0.0.0 or 9.1.0.0. If it is 9.0, can you remove it and add the reference to 9.1 back?

I have tried that and have just now tried that again.

It does not work. It gives the exact same error when I try to publish the Workflow. 

You would need to change the script to only use methods from the 9.1 version.

Okay....How do I do that? rewrite the code word for word?

Miruna,

I appreciate your help, but I do not know how to go about doing that. This is the entire reason I had posted this question. After a bit of troubleshooting, I had still not accomplished this goal of getting the workflow to publish. At that point, I tried to live chat with a Laserfiche employee and have not been able to get through, so I decided this morning to post the question. I need to get this workflow republished immediately so it can continue to be used.

I'm seeing both version of RA in the references after upgrades, so I'm not entirely sure how you ended up losing RA91. You don't need to re-write the entire script, just the calls that referenced RA90 specifically.

Things like

Dim wrapper as ConnectionWrapperRA = Me.ConnectToRA(ConnectionMethodRA.RepositoryAccess90)

would be just be obsolete.

Or

dim docinfo as Laserfiche.RepositoryAccess.Documentinfo = wrapper.BoundEntry

would be just

dim docinfo as DocumentInfo = me.BoundEntryInfo

From the error message is sounds like you were making your own connection. You don't need that anymore either.

I'm sorry Miruna, but I cannot understand how that is supposed to of helped me. I am using C# not VB.

And again, I have not lost any references, I merely have two libraries that should be able to resolve the code, and it doesnt know which to use.

What might happen if I manually removed those 9.0 resources?

I'd really like to resolve this, I haven't been able to get through to anyone on Chat all day, is something going on?

C# would have similar calls. And, yes, that's exactly what i am asking you to do: change the reference to RA91 and then go through your script and change calls that were referencing RA90 directly to use RA91.

How would I go about doing that when both references appear the exact same? The reference in my script is:

using Laserfiche.RepositoryAccess;

That's how it looks with either 9.0 and 9.1

In the Object Explorer pane in the Script Editor, open the References node. If you right click on the Laserfiche.RepositoryAccess under References you can delete it. Then right-click on References, browse to the GAC and add the one for Laserfiche.RepositoryAccess with version 9.1.0.0.

Hi Miruna,

I have tried that several times without any success. I get the exact same error when trying to publish the workflow. 

Miruna,

I have still been unable to publish my workflow. After trying to reference the RepositoryAccess91 library when possible, I am getting a warning when I compile that indicates I may need to supply runtime policy. How can I do this? It's telling me that the assembly reference for Laserfiche.RepositoryAccess 9.0.0.0 matches the reference for 9.1.0.0.

How can I set runtime policy?

Also worth pointing out, I now can also not run the script from inside my Script Editor. It gives a "Entry point was not found" message on a call to a function member of DocumentExporter

Can you post a screenshot of the References node in the script editor?

The "Entry Point not found" error is probably caused by the same issue discussed here.