You might want to elaborate, or better yet, post a link to a picture on photobucket. I have no idea what you mean by "Microsoft# #SSEE".

Most people maybe get a yellow exclam about not having antivirus, etc, or all green. If you get all green, you never read them, you just hit next. So most people are unlikely to have ever read that list. I have been using the product for 10 years, and never have read it, since I just get the same benign yellow exclams from time to time.

By the way, I am guessing that it will matter.

Thanks for your reply.

Attached photobucket screen shots of error messages:

http://i550.photobucket.com/albums/ii404/jc-10000/bck2.jpg

http://i550.photobucket.com/albums/ii404/jc-10000/bck1.jpg

I also receive an error for Symantec anti virus products. But am using another product trend) which uses sql express as its database, will this affect my install of Backup Exec?

Note I had a look at the port 3527 and it was listening UDP. 

Ok, thanks for the photos. They helped a lot.

First, regarding the port 3527: That is an issue, but it can be easily addressed after installation. Installation will complete normally despite that warning. After installation, a service will not start until you edit the registry as in the document below.

http://seer.entsupport.symantec.com/docs/274583.htm

http://seer.support.veritas.com/docs/275017.htm

Second, I had never heard of SSEE (SQL Server Embedded Edition) before, but now that I see the error, it is not an issue. When you get to the point where you can choose a SQL instance in which to install the BE databases, you will be fine just as long as you don't try to install your BE databases to that specific SQL instance as it is incompatible for some reason.

This is for those who read this topic later, not just Jeremy. For more information on SSEE, you can read this:

http://en.wikipedia.org/wiki/Windows_Internal_Database

Thanks for this information Kevin it is really helpful. Is there a preferred alternative port recommended for Small Business Server 2008 by Symantec? I like to try adher to standards and recommended configurations.

Secondly you mentioned "when you get to the point where you choose a SQL instance in which to install the BE databases" Are you prompted for a location (eg c:\Program Files\Backup Exce)? Justing making sure that I have the correct procedure before starting the install as unfortunately do not have a test environment for this Small Business Customer. 

As far as the port goes, it technically does not matter as long as it is not un use, but my preference is to pick a number that is still close to 3527, or a private port in the range below.

Just for additional reference, ports 1-1023 are known as the "Well-known ports", and should not be used except by the official service that it is normally used by; 1024-49151 are "Registered ports", meaning that programmers need to think twice before using them since they may be in use by other programs and cause problems like the one you are having; and 49152-65535 are "Private ports", which although they have nothing to do with IP addressing, they are similar in nature to the private IP address ranges like 192.168.x.x  in that they can be used by anyone.

When you get to the SQL selection, it is not a file location, but a choice: BE finds any currently installed SQL instances and lists them or you can choose to install a different instance. If it offers it, choose the one listed as the "default instance". That may not be listed since when SQL was installed, they may have chosen to name the instance rather than keeping the naming as "default instance".

I highly recommend that you download VMWare server at vmware.com and load up a test server. The nice thing is that once it is loaded the way you like it, you can save it as your default server, and when you need a test server, you just copy the directory, and you are ready to go. I also recommend that you, or your company invest in a copy of Technet Direct (the version with the DVDs is $525.00, but not worth the extra money since you don't get everything on DVD). This cost about $325/year in the U.S. Here is what you get: The main reason to get it is that you get two Microsoft Support incidents for the year included, which normally cost $265 a piece; you get access to a portal where you can download most of the Microsoft library, including all of the server stuff (standard, enterprise, datacenter, and Itanium editions). You can use as many copies as you want for testing, just not production.

I have virtualized demos of Exchange and SQL clusters, SQL active failovers, and of course, Backup Exec on 2003 and 2008 Server. It is a great learning tool, and you would be amazed at what you can do.

The nice thing is that after you set up your default servers, to create a scenario is simple. To do a 3-node cluster with a domain controller is as simple as copying my original Enterprise server 4 times, set the IP address and NETBIOS names, dcpromo the one to be a domain controller, then do any cluster configuration and installation necessary. I can be ready to start configuration in the amount of time it takes me to copy about 100GB in VMs.

If you had some VMs, you could do a test run on this in 30 minutes tops. That said, you should just go for it. The install is simple and if you get a little way in and you are not comfortable, you can hit cancel...I doubt that will happen.

I am going to send you a private message too.

Thanks very much for all your advice. I will take an image of the server before starting. I will also set up a virtual environment. Thanks again.