This content has been marked as final. Show 4 replies
I have faced the same error, but unfortunately I am not a technician, i had to take my system to a technician and he solved the problem some how:D i think it has something to do with the RAM:rolleyes:
yeah it did that for me too using ePO 4.5 and SQL Express 2008 w/SP1. Not sure why, but I wasn't too fussed as this is all this database is being used for.
if you turn off SQL browser, and click next, it'll fail then give you the option for a port.
By default ePO installs SQL Express as a named instance called EPOSERVER. Port 1433 is reserved for the default instance of SQL and so is not available to a named instance, so the ePO installer (I believe) starts looking for the first available port starting at 1040.
Thanks for the reply Joe. I suspect it'd only happen with the SQL on the same box (i.e. with me installing 2008 express rather than opting for the bundled 2005 express).
Seems a bit silly mind you... considering you tell the installer that you don't want to use the bundled 2005 express. It should know to free up the default port reservation.
Anyway, it works, so I'm not too concerned happy