Vulnerability in EPiServer.Forms
Been trying to reinstall Commerce on a new server, but I'm having trouble with the ECF installation, step 4 (Setting up the site database).
First I installed a new EPiServer CMS 6 site (on a Windows Server 203 R2 server).The site's database was installed on an SQL Server 2008 server (webserver and database server have separate IPs, but are on same subnet).Then proceeded to install EPiServer Commerce on same webserver and same database server as CMS 6 site. Error during ECF installation:" 'sqlcmd' is not a recognized internal or external command, operable program or batch file"at Mediachase.EcfConfiguration.EcfInstallForm.SetupDB()(at step 4: Setting up the site database)I tried to RDP into the database server and run 'sqlcmd' from command line, which works fine (proving that sqlcmd is in the PATH variable).
This also happens if I try to use SQL Server 2005 for the databases.
According to the MediaChase installation requirements doc for ECF 5.1, both SQL 2005 and 2008 should be supported, and database does not have to be on the same machine as the ECF program files.
I think you need the sqlcmd utility on the machine you are running the installation from. I don't know if you can download and use them seperately, or if you need to install SQL Server as well though.
As far as I know, sqlcmd can not work standalone (see http://stackoverflow.com/questions/2290903/run-sqlcmd-without-having-sql-server-installed/2291123#2291123)
If it turns out sqlcmd (and hence, SQL Server) needs to be installed on the machine where the installation is running from, this is a pretty serious flaw in the installation concept. I mean, the whole point of using separate servers is to keep web and database separated.
Also, the Commerce install guide or MediaChase ECF doc does not mention this dependency at all - in fact, it specifially says you can have your db on a server other than where you're installing ECF. :-O
According to your link you can run the sqlcmd stand-alone.
How did I miss that?? *shamed by own poor research* I'll try to install that.
EDIT: Oh, and after re-checking, I see that SQL Server Native Tools and Command Line Client is also mentioned in the ECF doc. So that's 2 out of 2 eff-ups from me then. However... :
Still, it is a requirement that is not mentioned anywhere, and it is still mixing SQL Server components into a Web server environment - not necessarily something that all server admins would agree to immediately.
I see your point, but then again you could just uninstall the components once your are done installing Commerce.
Great work, thanks for expanding on my post and provided a download link :)