VersionControlGetStatus throws error

[Eric Johannsen]

Hi,

When my C# code runs this line:

int checkoutCode = currPack.VersionControlGetStatus();

an exception is thrown at one of our clients:

The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

The currPack object is known to be a valid EA.Package object corresponding to a package that already exists in the model.

Any ideas what might cause this?

Thanks!

[«Midnight»]

What happens if you declare the return value as an object instead of an int? With COM errors it sometimes helps to know if anything is being returned at all.

Have you been able to track an inner exception from the COM result? Some but not all COM errors will provide a message at the top level or one down.

[Eric Johannsen]

The code works fine as-is in our development and QA environments, it just fails for one of our customers.  It would be a bit involved to give them a special build and have them try and track down the issue.

There is no inner exception :-(

They are using the Borland source control provider.  We suspect it might be related to that particular provider (we test with SVN and VSS).

We have a way to work our business logic around the source control provider throwing an exception, but it's less than optimal.

[«Midnight»]

I hear you Eric,

If only we could control these external configuration dependencies. But then again that's the world we develop into...

There's not a whole lot you can do from your end without tweaking their build, so for now that's a loss.

Can you get them to try another provider? This could even be on a one-time basis. The whole idea is to see if using a provider you've tested against would solve the problem in their environment. If not, then you've avoided a lengthy and fruitless debugging exercise on your end.

If changing the provider avoids the error, then you could look into rigging up a Borland provider on your end. Then you could try custom builds or other strong medicine to isolate the error. Once you get to that point you can either solve the problem, pass it to Sparx (if it appears internal to EA) or do both.

This is not the rosiest picture, but there could be a happy ending.

David