Q & A Home
Customizing SNF
Errors
False Positives
Functionality
Integration
Log Files
Resellers
Result Codes
Rulebase Updates
Software
Spam
Subscriptions
Trials
Version 3 Architecture
Documentation Home
Rulebase Updates
Why am I receiving a "Bad Command Line" error in my getRulebase.cmd file?
If the LICENSE_ID variable in getRulebase.cmd is set with one or more spaces after the license ID then the getRulebase.cmd script will fail in an unusual way reporting that the host ".new" was not found, and with snf2check complaining that it was given a bad command line.
The quotes here are included so that you can easily see the space that causes the problem:
This does not work:
"SET LICENSE_ID=abcd1234 "This is correct:
"SET LICENSE_ID=abcd1234"
Note that the correct version does not include an extra space before the line ends.
getRulebase.txt will look something like this:
< HTTP/1.1 404 Not Found
< Date: Thu, 26 Mar 2009 20:25:42 GMT
< Server: Apache/2.0.46 (Red Hat)
< Content-Length: 310
< Connection: close
< Content-Type: text/html; charset=iso-8859-1
<
{ [data not shown]
* Closing connection #0
* Could not resolve host: .new; Host not found
* Closing connection #0
curl: (6) Could not resolve host: .new; Host not found
* Could not resolve host: .snf; Host not found
* Closing connection #0
curl: (6) Could not resolve host: .snf; Host not found
snf2check: Bad Command Line
use snf2check.exe rulefilepath authentication
