Problems with ImportCmd

I'm trying to import a doc into a workspace folder using the 8.2 api, see code below

Dim pDoc As IManage.IManDocument
Dim pImportCmd As IMANEXTLib.ImportCmd
Dim pContextItems As IMANEXTLib.ContextItems
Dim bKeepCheckedOut As Boolean

'iNRTFolder is a IManage.NRTFolder

pContextItems = New IMANEXTLib.ContextItems

pContextItems.Add("DestinationObject", iNRTFolder)
pContextItems.Add("IManExt.Import.FileName", strFile) ' Path to file to import
bKeepCheckedOut = IManage.CheckinOptions.nrDontKeepCheckedOut
pContextItems.Add("IManExt.Import.KeepCheckedOut", bKeepCheckedOut)
pContextItems.Add("IManExt.Import.DocClass", "DOC")
pContextItems.Add("IManExt.Import.DocType", "WORD")

pImportCmd = New IMANEXTLib.ImportCmd
pImportCmd.Initialize(pContextItems)
pImportCmd.Update()
If pImportCmd.Status = IMANEXTLib.CommandStatus.nrActiveCommand Then
pImportCmd.Execute()
' Get return value
pDoc = pContextItems.Item("ImportedDocument")
pContextItems.Remove("ImportedDocument")
End If

Every time I run this I get an error:

"Error Occured when trying to log the event"

The details button reveals:

IManExt: Error occurred when try to log the event!

Access is denied.

I have checked folder permissions and can manually add docs to the folder as the same user using filesite or deskite. I have also changed the code to add it to the database instead of the folder and then programtically add it to the folder and this works OK. but of course it hasn't inherited all the folder attributes if I do it this way. Anyone got any ideas ?

Paul.

Find more posts tagged with

Comments

Migrateduser

I assume the error happens at the Execute line?

Try it without keeping it checked out. Eliminate:

bKeepCheckedOut = IManage.CheckinOptions.nrDontKeepCheckedOut
pContextItems.Add("IManExt.Import.KeepCheckedOut", bKeepCheckedOut)

Sysero

I'm working on this with Paul. Yes the error does happen on the Execute statement. I tried removing the checkout lines - no change. Incidently the whole process does appear to work - the document gets imported into the folder - it just kicks up this error dialog.

jny

I think it's because the checkin option type is declared as Boolean - it should be as imCheckinOptions or CheckinOptions.

I tested with the contextitems below using the IMan Interfaces successfully:

Dim eKeepCheckedout As imCheckinOptions = imDontKeepCheckedOut

pContextItems = New IMANEXTLib.ContextItems
pContextItems.Add ("IManDestinationObject", fldr) 'IManDocumentFolder
pContextItems.Add ("IManExt.Import.FileName", strFile)
pContextItems.Add ("IManExt.Import.KeepCheckedOut", eKeepCheckedout)
pContextItems.Add ("IManExt.Import.DocClass", "DOC")
pContextItems.Add ("IManExt.Import.DocType", "WORD)"

wolfgang

I am currently trying to use the ImportCmd, too, and I am experiencing the same error messages, too. Unfortunately, the context items discussed up to now don't seem to help for me. Is there any other issue we can consider?

I have a second error message telling me the error took place when trying to add the document to the document folder, an it states an "Access is denied" from "IManExt.LogRuleEventsCmd.1". Nevertheless, the results seem ok to me -- the document is imported, it is linked to the folder, and there is a history entry for the import. An exception, though it might be caught, is never thrown.


// This is C#
//
// dms is a valid IManDMS object
// sess is a valid IManSession object, and it is successfully logged in
// aFolder is a valid IManDocumentFolder object
// sourceFileName is a valid string holding the full path name of a Word doc
// docClass is a string holding a valid document class alias
//
ContextItems context = new ContextItems();
context.Add("IManDMS", dms);
context.Add("ParentWindow", 0);
context.Add("IManExt.Import.FileName", sourceFileName);
context.Add("IManDestinationObject", aFolder);
context.Add("IManExt.Import.DocDescription", "ImportCmd Test Doc / " + DateTime.Now.ToString());
context.Add("IManExt.Import.DocAuthor", sess.UserID);
context.Add("IManExt.Import.DocClass", docClass);
context.Add("IManExt.Import.DocType", "WORD");
context.Add("IManExt.Import.KeepCheckedOut", imCheckinOptions.imDontKeepCheckedOut);
//context.Add("IManExt.OpenCmd.NoCmdUI", true);
//context.Add("IManExt.NewProfile.ProfileNoUI", true);
//context.Add("IManExt.Import.InheritSecurity", true);

ImportCmd cmd = new ImportCmd();
cmd.Initialize(context);
cmd.Update();
if ((CommandStatus) cmd.Status == CommandStatus.nrActiveCommand) {
 try {
  cmd.Execute();
 } catch (Exception ex) {
  Console.Error.WriteLine("Err: Execute(): {0}", ex.Message);
 }
 IManDocument newDoc = null;
 try {
  newDoc = (IManDocument) context.Item("ImportedDocument");
  Console.WriteLine("new: {0}_{1}", newDoc.Number, newDoc.Version);
 } catch (Exception ex) {
  Console.Error.WriteLine("Err: After Execute(): {0}", ex.Message);
 }
}

jny

I used this VBNET code to silently import a file to a document folder (belonging to a workspace) successfully:

===============================

Imports IManage
Imports IMANEXTLib
Imports IMANEXT2Lib

Public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
'Logon
Dim dms As New ManDMS
Dim sess As IManSession = dms.Sessions.Add("DSS_WIN2003SERV")
sess.TrustedLogin()

'Get target workspace
Dim db As IManDatabase = sess.Databases.ItemByName("WSDSS1")
Dim wparms As IManWorkspaceSearchParameters = dms.CreateWorkspaceSearchParameters()
wparms.Add(imFolderAttributeID.imFolderName, "myspace:")
Dim results As IManFolders = db.SearchWorkspaces(dms.CreateProfileSearchParameters(), wparms)

'Get target document folder
Dim ws As IManWorkspace = results.ItemByIndex(1)
Dim fldr As IManDocumentFolder = Nothing
Dim targetFldr As IManDocumentFolder = Nothing
For Each fldr In ws.DocumentFolders
If fldr.Name = "myProfiledFolder" Then
targetFldr = fldr
End If
Next fldr

'Import to folder (silently)
Dim cmd As IMANEXTLib.ImportCmd = New ImportCmdClass()
Dim context As IMANEXTLib.ContextItems = New ContextItems()
Dim filename As String = "C:\Temp\My test file.doc"

Dim eKeepCheckedout As imCheckinOptions = imCheckinOptions.imDontKeepCheckedOut

With context
.Add("IManExt.Import.KeepCheckedOut", eKeepCheckedout)
.Add("IManExt.Import.FileName", filename)
' Filename set here is used for easy example.
.Add("IManExt.Import.DocDescription", filename)
' DocDescription is a string.
.Add("IManExt.Import.DocAuthor", sess.UserID)
' DocAuthor is a valid user name defined in the database.
'.Add("IManExt.Import.DocType", "word")
' DocType is a valid document type value defined in the database.
.Add("IManExt.Import.DocClass", "doc")
' DocClass "doc" is an example of a valid document class value defined in the database.
'.Add("IManExt.Import.DocSubclass", "contract")
' DocSubclass "contract" is an example of a valid document subclass value defined in the database,
' and it's required by the document class.
.Add("ManExt.NewProfile.ProfileNoUI", True)
.Add("IManExt.OpenCmd.NoCmdUI", True)
.Add("IManExt.Import.FileName", filename)
.Add("DestinationObject", targetFldr)
End With
cmd.Initialize(context)
cmd.Update()
cmd.Execute()
Dim brefresh = context.Item("IManExt.Refresh")
If True = brefresh Then
Dim doc As IManDocument = CType(context.Item("ImportedDocument"), IManDocument)
MsgBox(doc.Number & "_" & doc.Version)
End If
End
End Sub
End Class

===============================

wolfgang

Hm ... please let me politely ask: Has this really been VB *.NET*?

I have been able to use the ImportCmd successfully and without any error message windows from Word VBA and from VB6, which both use pure COM interfaces. Using the --semantically-- same commands from C#.NET (via the .NET Interop construction) always gives me the two errors mentioned before -- while the result is absolutely satisfactory: the file *is* imported, and it *is* linked to the requested folder.

I am tempted to ignore the content of the error message, stating "Access denied while trying to log the event", because this access violation does not occur when calling the ImportCmd by another technology. Would you agree?

jny

Yes, this was written in VBNET. I also have just now written the implemenation in C#, and it worked successfully as well. See below.

Does your destination folder have rules set on it? Would you send in your code project as attachment? I can run in in-house to see whether or not it throws the same error.

[C#]

=====================

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.Runtime.InteropServices;
using IManage;
using IMANEXTLib;

namespace ImportCmdSilent
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}

private void Form1_Load(object sender, EventArgs e)
{
//Logon
ManDMS dms = new ManDMSClass();
IManSession sess = dms.Sessions.Add("DSS_WIN2003SERV");
sess.TrustedLogin();

//Get target workspace
IManDatabase db = sess.Databases.ItemByName("WSDSS1");
IManWorkspaceSearchParameters wsparms = dms.CreateWorkspaceSearchParameters();
wsparms.Add(imFolderAttributeID.imFolderName, "myspace:");
IManFolders results = db.SearchWorkspaces(dms.CreateProfileSearchParameters(), wsparms);

//Get target document folder
IManWorkspace ws = (IManWorkspace)results.ItemByIndex(1);
IManDocumentFolder targetFldr = null;

foreach (IManDocumentFolder fldr in ws.DocumentFolders)
{
if (fldr.Name == "myProfiledFolder")
targetFldr = fldr;
}

if (targetFldr != null)
{
string filename = @C:/Temp/My test file.doc;

ImportCmd cmd = new ImportCmdClass();
ContextItems context = new ContextItemsClass();

imCheckinOptions eKeepCheckedout = imCheckinOptions.imDontKeepCheckedOut;

context.Add("IManExt.Import.KeepCheckedOut", eKeepCheckedout);
context.Add("IManExt.Import.FileName", filename);
context.Add("IManExt.Import.DocDescription", filename);
context.Add("IManExt.Import.DocAuthor", sess.UserID);
context.Add("IManExt.Import.DocClass", "doc");
context.Add("ManExt.NewProfile.ProfileNoUI", true);
context.Add("IManExt.OpenCmd.NoCmdUI", true);
context.Add("IManExt.Import.FileName", filename);
context.Add("DestinationObject", targetFldr);

cmd.Initialize(context);
cmd.Update();
cmd.Execute();

bool brefresh = (bool)context.Item("IManExt.Refresh");
if (brefresh == true)
{
IManDocument importedDoc = (IManDocument)context.Item("ImportedDocument");
MessageBox.Show(importedDoc.Number + "_" + importedDoc.Version);
}

}
}
}
}

=====================

Migrateduser

Try importing the document into the database, then adding to the folder's contents collection. We do not use this specific method of importing...

jny

The code I provided should work fine. That what we use in our WorkSite Client source to import a document to a folder.

wolfgang

jny,

yes it does. All the weirder, the only difference to my I can see for now is you used a Form based program whereas I used a console application. Not able to believe it can have anything to do with that, I'll have to investigate further. I'll let you know.

Thank you!

Wolfgang

guido1

Wolfgang:

could it be that the difference in your example is that you are not using the actual class, but creating instead an instance of the imported interface?

When you import a Win32 type library (such as IManExtLIB) into .NET, cocreateable classes such as ImportCmd and ContextItems will ultimately generate a "Class" and an "Interface" pairing.

So, "ImportCmd" is actually the interface definition, whereas "ImportCmdClass" is the implementation of the "ImportCmd" interface.

In other words you might want to try

ContextItems contexts = new ContextItemsClass();

[font=Verdana][size=2][color=#000000]and

[/color][/size][/font]

ImportCmd cmd = new ImportCmdClass();

[font=Verdana][size=2][color=#000000][font=Verdana][size=2][color=#000000]instead of

[/color][/size][/font][/color][/size][/font]

ContextItems contexts = new ContextItems();

[font=Verdana][size=2][color=#000000][font=Verdana][size=2][color=#000000]and

[/color][/size][/font][/color][/size][/font]

ImportCmd cmd = new ImportCmd();

[font=Verdana][size=2][color=#000000][font=Verdana][size=2][color=#000000][font=Verdana][size=2][color=#000000]

just a wild guess!

[/color][/size][/font][/color][/size][/font][/color][/size][/font]

wolfgang

Indeed I tried to copy jny's way of instantiating the objects almost literally. As I only mentioned between the lines in my previous post, jny's code worked while mine did not.

Is there any rule of thumb of when to use *Class() for instantiating objects? Everytime?

Wolfgang

guido1

My understanding is that you should always use the *Class definition when instantiating a new instance of an object.

If you don't you may receive unexpected results when you're trying pass one object to another, as the .NET sees these as 2 different objects (with different GUIDs)

Again, just a guess!

jny

Wolfgang - if you still experience problems with your code, please send it in as attachment so that I can examine it closely on my end.

wolfgang

So, I'm attaching my code (as good as I am currently able to). In order to eliminate possible other error causes; I've set up a new, fresh, empty 8.2SP1RC test environment. Still, the call to Execute() leads to two error boxes:

Access denied

Document not added to folder

This is my code: Program.cs
It is almost literally copied from your previous post.

So, if you can see what obviously can't -- I guess I will slap my forehead ... ;-) Thanks!

Wolfgang

jny

I just tested your code successfully on my end. The only difference is, besides the obvious login and folder input, I now have just upgraded to SP1 Release.

I don't think it's the code though...I would check on the destination folder. Are you able to import a document to that same folder from within DeskSite/FileSite? And, what happened when you create a new folder, then add the file to it using the same ImportCmd code?

abc1234

Hi Jny,

I used the VBNET code which is written by you to upload the Documents in the worksite by using ImportCmd. As it was working for long time nicely but suddenly i getting two errors but file is imported to the worksite.

Error 1:

IManExt: Error occurred when try to log the event!

Incorrect function.

Error occurred try log event

Error 2:

IManExt: The document was imported to the database, but could not be added to the folder.

IManExt.LogRuleEventsCmd.1: Error occurred when try to log the event!

IManExt.LogRuleEventsCmd.1: Access is denied.

Error occurred when try to log the event!

But it is importing the document in the exact location in worksite but i have no clue why i'm getting this error.Could you please help in solving this issue.

jny

I would also like to point out that, by using the AddDocumentReference Method, the document will not inherit the metadata and security set on the folder.

The idea of using the ImportCmd is to automate this.

cmscmadd

I noticed the same error (IManExt: Error occurred when try to log the event) with my use of the ImportCmd too.

The method that ran my ImportCmd was running on the .net 2 BackgroundWorker, running it on the UI thread stopped the error from occurring.

I'm still investigating the exact cause, but thought this may help someone in future.

ozy

I have the same problem, I assume it has to do with a missing or an inappropriate parent window handle. I don't have a window to which I could attach.

I tried
context.Add("ParentWindow", 0);
which resulted in a noresponse-situation, but the document was imported as intended.

Then I tried
context.Add("ParentWindow", -1);
which immediatly returned an error msg "No success."

So for my part I have to look for another way to do the job, but maybe it helps those who have a parent window.

guido1

If you don't have a visible window you should set the ParentWindow to a 32bit integer representing the handle of the application executing your code

mawny

I am having the same issue.

Like a previous poster I am executing the ImportCmd using the .NET backgroundworker. The doc is imported and attached to the target folder, but i get the message boxes popping up about failure to log and access denied.

Was this issue resolved ( when running under a background worker ?)

jny

I am having the same issue.

Like a previous poster I am executing the ImportCmd using the .NET backgroundworker. The doc is imported and attached to the target folder, but i get the message boxes popping up about failure to log and access denied.

Was this issue resolved ( when running under a background worker ?)

This is a problem caused by .NET as only .NET supplies this type of background worker thread. The source code does not have implemenation to check or support this type of background process. It is currently logged as a bug so that R&D can examine it closely.

mawny

This is a problem caused by .NET as only .NET supplies this type of background worker thread. The source code does not have implemenation to check or support this type of background process. It is currently logged as a bug so that R&D can examine it closely.

Thanks for the reply.

I have managed to get it working without blowing up by setting the parentwindow context item to -1 and by not checking the IManExt.Refresh returned item for a value of true.

This is a bit ugly , but the imported document is returned correctly.

Andy