Could not detect the file type in the supplied stream.

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
rlepard
Posts: 8
Joined: Wed Jul 18, 2007 3:20 pm

Could not detect the file type in the supplied stream.

Post by rlepard » Mon Dec 15, 2008 10:03 am

I have a twist on an error that's been posted a couple of times (http://support.sourcegear.com/viewtopic.php?t=8646).

I have an x64 bit Windows PC that I get the "Could not detect the file type in the supplied stream." error on when I attempt to connect to a Vault 3.1.8 database using a homegrown application that calls Vault DLLs. I am successful connecting to a different instance of Vault 3.5.2 through the client UI though. I don't remember exactly when the problem started, but for quite a while, I was able to connect to both databases.

On a secondary x86 PC, I am able to connect to both databases. There are a handful of other users that connect to both databases and none of them have this problem either, making me think it is x64 related.

Questions:
If the file cleanup in topic 8646 applies, how do I know which Repository-GUID to clear out?
If topic 8646 does not apply, what else can I look at?

Thanks!
Rob

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Could not detect the file type in the supplied stream.

Post by Beth » Mon Dec 15, 2008 11:20 am

Vault 3.1.x is not supported on a x64 machine. That could be contributing.

With our clients, you can't use the same client to connect to two very different versioned databases. I would suspect that it would be the same for the API.

Basically, you have two things that could be in your way from the start.

On the actual question you asked, send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread, and I can provide the information you need to find out which GUID to go into.
Beth Kieler
SourceGear Technical Support

Post Reply