Unable to load IExplorerUtil throw exception

[mnav]

Hi

I am using Vault 2012 from my client machine i want to get the working folder. i am using IExplorerUtil but its throwing  following excetion.

"Exception has been thrown by the target of an invocation."

Here is my code throwing exception on LoadExplorerUtil call.

            UserPasswordCredentials login = new UserPasswordCredentials("Vault2012", "Vault", "Administrator", "");
            WebServiceManager serviceManager = new WebServiceManager(login);
            IExplorerUtil VaultExplorer = ExplorerLoader.LoadExplorerUtil(login.ServerName,
                                                                          login.VaultName,
                                                                          serviceManager.SecurityService.SecurityHeader.UserId,
                                                                          serviceManager.SecurityService.SecurityHeader.Ticket);

            string workingFolder =  VaultExplorer.GetWorkingFolder(serviceManager.DocumentService.GetFolderRoot());

thanks for your help

[Redmond.D]

Are you using base Vault?  IExplorerUtil will not work with that product.  It only works with Vault Workgroup, Collaboration or Professional. If you are in base Vault, you can use DocumentService.DownloadFile.  That function gets the file but doesn't do the more complex features, like fixing broken references.

[mnav]

Hi Doug Thanks for your reply

i have tried with both basic and collaboration error is same.

i want to get the path for working folder on local machine.

thanks.

[Redmond.D · Accepted solution]

So you have the Vault Collaboration 2012 client installed on the computer but you are still getting the exception.

TargetInvocationException doesn't usually have anything useful.  Always dig deepr into the InnerException for these cases. That will tell you the real error.

What context is your code running in?  If you are running your own EXE try altering your project settings to match Vault Explorer's settings by using .NET 3.5 and the x86 platform target.

[mnav]

Thanks Doug

Changing the .net framework from 4 to 3.5 solve the issue.

thanks a lot once again