Trouble installing Fabric Manager 5.0.7 on 2008R2

Question

Hello all,
We are about to upgrade our older MDS-9124s to MDS-9148s and I wanted to install the new Fabric Manager. I am trying to install version 5.0.7. I am having a couple issues but am not sure if they are all related. First if I try to select the install links from within start they do not work. The only way I can get the install to start is double clicking the jre file direct. The installation process starts and the dies at what appears to be trying to start postgresql with an error message that initdb cannot be processed because the libpq.dll file cannot be found. If I try to re-run the install it dies becuase the postgre user already exists. I can delete that local account and the installation process will restart only to once again die with the dll error.
Just for grins I ran the postgresql install seperate and it seems to go through a lot more prompts but figured this was not the proper way to get it installed so canceled it. I also tried running the install from the cmd line as I found in another post and it dies at basically the same point but has a net error message 2221. It looks at though this to means that the user created cannot be accessed so postgresql will not start.
I am disabling my virus software while trying all of these items.
Suggestions??/
Brent

Answer 1

@dynamoxxx,
     This is a new install and I just completed getting it installed on Friday. I had to actually log onto the server as the local administrator to get it to install. An Admin equivalent account apparently was not good enough. Once I did that it completed just fine. I have come across another apparetly known isse and that is if you exit Fabric Manager and try to go directly back in a box pops up that says Fabric Manager is already running. This is apparently because java never shuts down. You kill the javaws servise and Fabric Manager starts back up without any issue. Of course this also works if you log off the server and back on. This was somthing that I talked with TAC about this morning and since they have quit working on Fabric Manager is not going to be fixed.
That brings me to DCNA. I am moving to Cisco Prime for the rest of my infrastructure and TAC says that DCNA is a part of that or that basically is DCNA. They were telling me that based upon the code level I am running (5.0(1a)) on my switches that Fabric Manager is better. If  I was running newer 6.2 or 5.2 code then use the DCNM and apparently 5.2(8) is newer than 6.2. They also recommended me waiting until 5.2(8b) come out before upgrading the switches and then moving to DCNA. I will figure out that step once I get my SAN migration completed in a few weeks. Until then I am planning to keep what I have.
Brent