If the install still fails please:
Make sure to install Postgres on the CONSOLE of the server. If you are using
RDP (remote
desktop) for the installation, make sure to start it like this:
Start-->Run-->mstsc
/v:
If the installer fails:
* Manually create a LOCAL "postgres" user account (not domain account)
* Make sure the password is a STRONG Password (upper/lower case, digits,
etc)
* Assign the user to the "Power Users" or "Users" group
* DO NOT add the user to the local or domain Administrators group
* Under Local security policy > grant user rights assignment:
o Log on as service
o Log on locally
Once the user has been added, do the following:
* Make sure the postgres user can get a command prompt
o As the LOCAL Administrator, get a command window
(Start-->Run-->CMD)
o In the command shell, type "runas /user:postgres cmd" - this should bring
up a new
command window as the postgres user.
o If this fails, adjust the security policy (via the "cacls" command) to
allow the user to
run the command window (specifically, "cmd.exe")
o Example (in a command shell as the Administrator):
CD \WINDOWS
CACLS *.EXE /E /G "AUTHENTICATED USERS":R
CD SYSTEM32
CACLS *.EXE /E /G "AUTHENTICATED USERS":R
* Make sure the postgres user can write to "NUL" (taken from here:
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00111.php)
o In the command shell (as the Postgres user), type, "dir > NUL"
o If this fails, download and install the "subinacl" tool from Microsoft
(see below for
download location)
o As the Administrator, get a command prompt and type the command, "Subinacl
/service NULL
/grant="authenticated users"=QSEILU"
o Retry the "dir > NUL" command again - it should succeed
If the installer still fails
* Make sure the postgres user can access the files and directories listed in
the section
below (Directories and Files)
* Disable any/all domain policies for the postgres user
* Take the server out of the domain and use local authentication only
* Download the "filemon" utility to identify which file(s) is/are
causing the issues
Filemon - http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx
Subinacl -
http://www.microsoft.com/downloads/details.aspx?FamilyID=E8BA3E56-D8FE-4A91-
93CF-ED6985E3927B&displaylang=en
2. If it is new install make sure you unistall any postgres installation.
-----------------
Things to collect and look for:
- Collect FMs_snmp.log, fmweb.log, Fmserver.log (both PM and FM logs are in there)
- enable snmp trace for the FMS using LogLevel gui; do demand polling
of the fabric;get the fms_snmp.log . ( right click on Log tab and enable snmp
trace), do "circular Arrow on top of FM " to do demand polling and bottom right hand side should say "polling")
- Please do this with Cisco Engineers
In MDS 9000 directory we created debug.properties with allowed=localhost
and did telnet localhost 9197
show fabric
show fabric 2 status
persist 3 ( based on the show fabric)
