Kofax Ascent Capture Documentum release script

[Eugene]

Hello,

I installed the release script that Kofax provides for Documentum.
However, when I click on the document class in the batch class window
and try to add the DCTM release script to the doc class, it gives me
the following error:
Error Number: 91
Error Description: Object variable or With block variable not set.
Looks to me like the VB error in the code, but I cannot figure out why
it's present. Has anyone seen this before?
How hard would it be to write my own release script?
Did anyone hear of a good DCTM release scripts except for the ones
that are listed on the Kofax website?

Thank you very much,
Eugene

[Russell H]

Make sure that workstation you're trying to release from has the Documentum
client installed. Typically the release scripts use the APIs that are part
of the client that you are trying to release to.

Also, did you install the release script on the workstation you're trying to
run Admin on? You have to. Even though it shows "installed" in ascent,
typically you have to install it on each release and admin workstation.
Depending on the release script install style, you may be best off to place
the DLL file in a central location where all the machines can find it using
the same UNC.

"Eugene" <ezay...@optonline.net> wrote in message
news:93648428.03071...@posting.google.com...

[Eugene]

Russell,

Thanks for your reply. I have a single machine that houses DCTM
server, client and Kofax standalone workstation with all the modules.
I do have the release script installed on this machine as well. I
have tried to put the path to the directory where the script resides
and when this didn't work, copying the files over to c:\winnt. No
results either.

Thanks,
Eugene Zaydens

"Russell H" <Rus...@noconctact.com> wrote in message news:<bf5bq7$7kt$1...@ngspool-d02.news.aol.com>...

[Russell H]

I don't have any ideas. It's clear that the release script either isn't
installed right or is incompatible with the version of Kofax Ascent you
have. Generally older release scripts will work with never versions of
Ascent but not the other way around. Also you may have to make sure what
you have matches the version of Documentum.

That's about all I can suggest. The only time I've seen release scripts
blow at that point is if the release script's DLL isn't registered on the
local machine. Usually if you just use Ascent's Release Script manager and
re-install it it works fine.

"Eugene" <ezay...@optonline.net> wrote in message

news:93648428.0307...@posting.google.com...

[Brian]

If the dll didn't get registered correctly, or it's a different version than was
used when the release script was installed, you can use the regsvr32 command
from a command prompt to register the dll. I know if I ever put an updated dll
for a release script on a workstation, I have to do this.

Also, does the DCTM release script come with the source code? I know most of
the release scripts do (at least the ones I've worked with). If so, you might
be able to debug the code and find exactly where your error is.

In article <bfa4mh$ikq$1...@ngspool-d02.news.aol.com>, "Russell says...

[Russell H]

"Brian" <Brian_...@newsguy.com> wrote in message
news:bfpi0...@drn.newsguy.com...

> If the dll didn't get registered correctly, or it's a different version
than was
> used when the release script was installed, you can use the regsvr32
command
> from a command prompt to register the dll. I know if I ever put an
updated dll
> for a release script on a workstation, I have to do this.
>

That would probablly work. I've just used the Release Script Manager in
Admin to re-install the script.

> Also, does the DCTM release script come with the source code? I know most
of
> the release scripts do (at least the ones I've worked with). If so, you
might
> be able to debug the code and find exactly where your error is.

FYI, Ascent has gone to licensing release scripts. Expect source code to
dry up. :-(