IManBrowseCmd error

Hi there,

I am using IManBrowseCmd to allow a user to select a document or folder from within a database, however once in a while when the dialog is executed, an error message is displayed which states "Access is denied".

Sometimes this is all that happens, although sometimes, the dialog is displayed only the database is not available under WorkSite explorer.

Does anyone have any idea what causes this and how I might fix it please?

Many thanks!

Ben

Find more posts tagged with

Comments

jny

I'm not sure how that could happen. Don't think it's the code. Perhaps the database is corrupted?? What happens when you connect to another DMS?

Benp44

Thanks for the reply jny.

The strange thing is I have built a test application which does almost exactly the same thing as the application with the problem, connecting to the same database as the same user and it seems fine.

The application is an unmanaged executable calling into managed code, in which I am using IManBrowseCmd.

I have discovered that sometimes rather than this message appearing, the IManBrowseCmd never gets shown, and I get memory exceptions (access is denied again) occuring at arbitrary locations in my host application (the unmanaged code). My guess is that somehow memory is getting corrupted which leads to the somewhat undeterministic exception behaviour.

Any ideas? Perhaps threading models or .NET garbage collection?

Is there another way to raise a dialog which can allow my users to browse the database/workspace structure and select documents/folders?

Many thanks again,

Ben

jny

I have no idea why that would happen if the IManBrowseCmd is code is correct. If you could send in a simplified project of that code which can reproduce the problem, I can take a look at it as soon as I can. Please also include the specific version of the SDK and WorkSite Server you're using.

The IManBrowseCmd is the command to use to bring up a dialog for end-users to select WorkSite containers. You may also opt for the IIntegrationDlg.DocOpenDlg. I don't however think that the problem you've encountered has anything to do with the invocation of the IManBrowseCmd object itself though; thus you could potentially encounter the same problem behvaior somewhere down to road in using other command or dialog objects.

Migrateduser

I have seen this happen a lot while you are debugging the application. If you actually compile the code and run the application, the error will go away.

Benp44

The problem has gone away,

suspect it was a memory leak in my code.

Thanks for the help anyway!