# Source Safe Login Failure

**URL:** https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078
**Category:** Discussion
**Created:** [January 15, 2009, 11:42am UTC](https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078 "2009-01-15T11:42:38Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jasonz](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jasonz](https://www.finalbuilder.com/forums/u/jasonz)
#### Post date: [January 15, 2009, 11:42am UTC](https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078/1 "2009-01-15T11:42:38Z")

</div>

Simple question and probably missing something obvious...&nbsp;

Testing on my machine under evaluation before loading Final Builder onto the build machine.&nbsp; We have source safe database on a server, I have SSUSER set as a system variable for my user however I am using FB's version control systems to specify the login for FB to use.&nbsp; I found that regardless of setting the ini file location in here to \\Server\Source Safe that it still wouldn't use that location and tried to default to the local machine (even though manually running VSS defaults to the same server directory).&nbsp; I set SSDIR to overcome this on my machine.&nbsp; The error I get is that it simply does not enter a password and sits there...

What is the obvious step I've missed?&nbsp; Any help is most appreciated...

Executing external process: C:\Program Files\Microsoft Visual Studio\VSS\win32\SS.EXE  
Starting Directory: c:\SOURCECODE\Elite2008\RolloverCommon  
Parameters: get $/Elite2008/RolloverCommon -I-Y "-GLc:\SOURCECODE\Elite2008\RolloverCommon" -Y"Final Builder",Final Builder -R -GF- -GWR  
Output from C:\Program Files\Microsoft Visual Studio\VSS\win32\SS.EXE  
Username: Final Builder  
Password:   
-  
Files Processed successfully : 0  
Files Not Processed : 0

---

<div class="post-metadata">

### Author: ![jasonz](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jasonz](https://www.finalbuilder.com/forums/u/jasonz)
#### Post date: [January 16, 2009, 12:47pm UTC](https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078/2 "2009-01-16T12:47:21Z")

</div>

I have since found the bug to be the quotes for user/pwd should be -Y"Final Builder,Final Build":

get $/Elite2008/RolloverCommon -I-Y "-GLc:\SOURCECODE\Elite2008\RolloverCommon" -Y"Final Builder",Final Builder -R -GF- -GWR

How can I fix this as it is set by FB???

&nbsp;

---

<div class="post-metadata">

### Author: ![paulsamways](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/p/e8c25b/32.png) [@paulsamways](https://www.finalbuilder.com/forums/u/paulsamways)
#### Post date: [January 16, 2009, 1:19am UTC](https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078/3 "2009-01-16T01:19:06Z")

</div>

Hi Jason,  
  
Thanks for going the extra mile and working out what was going wrong. Should have a new build available within the next few hours.  
  
Regards,  
Paul.

---

<div class="post-metadata">

### Author: ![paulsamways](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/p/e8c25b/32.png) [@paulsamways](https://www.finalbuilder.com/forums/u/paulsamways)
#### Post date: [January 16, 2009, 4:13am UTC](https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078/4 "2009-01-16T04:13:23Z")

</div>

Hi Jason,   
  
 Here’s the new build which should correctly quote the VSS username and password.   
  
 URL: [https://www.finalbuilder.com/downloads/finalbuilder/620/FB620\_1254.exe](https://www.finalbuilder.com/downloads/finalbuilder/620/FB620_1254.exe)  
  
 Regards,   
 Paul.

---

<div class="post-metadata">

### Author: ![jasonz](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/b2d939/32.png) [@jasonz](https://www.finalbuilder.com/forums/u/jasonz)
#### Post date: [January 16, 2009, 10:46am UTC](https://www.finalbuilder.com/forums/t/source-safe-login-failure/1078/5 "2009-01-16T10:46:03Z")

</div>

Thanks for the very quick resolution… Wish other companies could resolve issues as quick… Brilliant, all working fine!