Unable to parse repository info from project file

If you are having a problem using Vault, post a message here.
Post Reply
dbaltz
Posts: 17
Joined: Thu Dec 14, 2017 12:07 pm

Unable to parse repository info from project file

Post by dbaltz » Tue Aug 27, 2019 11:25 am

I am getting the following message when opening a solution:
Failed to register project PageXaml with SourceGear Vault Pro
Visual Studio Enhanced Client

Unable to parse repository info from project file.
[RESOURCECOMPILE]
PageXaml is not a project in my solution, yet it lists some of the files in the project that fails to load. Per another topic here, I deleted the VsipClientProjectSettings.xml file from the cache but that didn't work.

I'm running VS2017 on Windows 10 Enterprise.

Tonya
Posts: 684
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: Unable to parse repository info from project file

Post by Tonya » Tue Aug 27, 2019 1:13 pm

Hello,

What version of Vault do you have installed? How are you opening the solution (please provide detailed step by step instructions)?

Can you please email your Vault Server log to support@sourcegear.com? The Vault Server log is in %windir%\temp\sgvault\sgvault.log on the server machine.

Thanks,

Tonya

dbaltz
Posts: 17
Joined: Thu Dec 14, 2017 12:07 pm

Re: Unable to parse repository info from project file

Post by dbaltz » Wed Aug 28, 2019 2:15 pm

Vault v10.0.2 (30936)

I Open Solution from VS2017 and it gives me the error immediately.

Tonya
Posts: 684
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: Unable to parse repository info from project file

Post by Tonya » Thu Aug 29, 2019 10:14 am

Working on resolving the problem offline.

Tonya

jclausius
Posts: 3663
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Re: Unable to parse repository info from project file

Post by jclausius » Tue Sep 03, 2019 1:23 pm

Just to post a follow-up to this thread.

It seems doing a manual unbinding of the solution and projects ( viewtopic.php?f=13&t=18956&p=70077#p70077 ), and subsequently re-binding the items resolved the issue.
Jeff Clausius
SourceGear

Post Reply