Yeah sure i have the same problem. I couln't even install at first so I had to remove all databases due to some TCP port beeing duplicate I saw the fix in Sp1 of netflow but that is just to late since the base 3.0 installation fails which you need for 3.0 Sp1 update.
Also what happened to the memory, network and cpu usage of this whole suite? Only 1 year ago we could do fine with a P3-1000, 512Mbyte and WIn2k3 + dedicated SQL. Now we need an Xeon 2,4Ghz, 2 Gbyte memory and an SQL that has to keep up with 2-5 Mbit of flow of data all the time for no apparent reason?
Getting fed up with bugs and resourcehoging. DotNET seems to be the source for most hoging of resource. There are other software upgraded to DotNET that appears to have the same issues.