Hi.
I have recently coded up a simple ASP.NET app
that uses the Vault Client API. On my dev box,
I am able to extract files from our repository.
However, when I deployed this to the production
web server candidate, my app hangs because the
ClientInstance.SetActiveRepositoryID()
call never returns. I can provide more info if
needed, but what situation would cause a Vault
API call to never return (a greater problem--with
the API IMO).
Thanks!
hobie
ClientInstance.SetActiveRepositoryID() Never Returns
Moderator: SourceGear
Re: ClientInstance.SetActiveRepositoryID() Never Returns
Me againhobie wrote:Hi.
I have recently coded up a simple ASP.NET app
that uses the Vault Client API. On my dev box,
I am able to extract files from our repository.
However, when I deployed this to the production
web server candidate, my app hangs because the
ClientInstance.SetActiveRepositoryID()
call never returns. I can provide more info if
needed, but what situation would cause a Vault
API call to never return (a greater problem--with
the API IMO).
Thanks!
hobie
My ASP.NET client app is running on Win2k3 Server,
and it's using the Vault API v2.0.6.
My successful run on my own machine is on Win2K Pro,
FWIW.
hobie
I don't know if this answers your question fully,jeremy_sg wrote:That's an odd place for it to hang. Are you connecting to the same server and as the same user (both windows user and vault user)?
but I am using the same Windows user account
on both dev box and production web server (same
domain acct. on both), and have the same Vault
user settings on both (hard-coded in app).
Oh, I meant WinXP Pro is the OS on my dev box,
not Win2k.
thanks for the help!
hobie
I don't know if this answers your question fully,jeremy_sg wrote:That's an odd place for it to hang. Are you connecting to the same server and as the same user (both windows user and vault user)?
but I am using the same Windows user account
on both dev box and production web server (same
domain acct. on both), and have the same Vault
user settings on both (hard-coded in app).
Oh, I meant WinXP Pro is the OS on my dev box,
not Win2k.
thanks for the help!
hobie