# Parameter File &#91;params&#93; does not exist

**URL:** https://www.finalbuilder.com/forums/t/parameter-file-91-params-93-does-not-exist/3610
**Category:** Bugs
**Created:** [November 19, 2015, 4:44am UTC](https://www.finalbuilder.com/forums/t/parameter-file-91-params-93-does-not-exist/3610 "2015-11-19T04:44:06Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![fredriktenbrink](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/f/a5b964/32.png) [@fredriktenbrink](https://www.finalbuilder.com/forums/u/fredriktenbrink)
#### Post date: [November 19, 2015, 4:44am UTC](https://www.finalbuilder.com/forums/t/parameter-file-91-params-93-does-not-exist/3610/1 "2015-11-19T04:44:06Z")

</div>

Running on FB 8.0.0.1351  
Windows 7 Enterprise SP 1  
  
When trying to run our installer through fbcmd using the -params: or -@: for our command line variables it kindly repeats the kind message above.  
  
“C:\Program Files (x86)\FinalBuilder 8\fbcmd.exe” “installer.fbp8” -@:“C:\Temp\Params.txt” for example.  
“C:\Program Files (x86)\FinalBuilder 8\fbcmd.exe” “installer.fbp8” -params:"C:\Temp\Params.txt"  
  
output: Parameter File [params] does not exist  
The variable file exists by the way

---

<div class="post-metadata">

### Author: ![nevar](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/n/c4cdca/32.png) [@nevar](https://www.finalbuilder.com/forums/u/nevar)
#### Post date: [November 22, 2015, 10:48am UTC](https://www.finalbuilder.com/forums/t/parameter-file-91-params-93-does-not-exist/3610/2 "2015-11-22T10:48:58Z")

</div>

Hi Tenbrink,   
  
 I have a build awaiting release with a fix for this exact issue with the parameters option. I will be releasing it today, just needing to get NUnit 3 support also completed so that we have a single update instead of two.   
  
 In answer to your second question the params file specification has also changed. The file is now expected to carry options from the new command line for FinalBuilder 8. Therefore the options you have specified would actually appear as so;   
  
 -v:Service.DestinationServer=127.0.0.1   
 -v:Service.WebsiteName=xyz.ci.local
