How to install 7.5.0.6 client on WS2012 where Postgresql is installed

[William_Brown]

I am aware that there is an EEB for 7.5GA to install on a system where Postgresql is already present;

http://www.symantec.com/docs/TECH182539

For WS2012 there is the special client install of 7.5.0.6 that is installed as a full version install.

http://www.symantec.com/docs/TECH204661

But from what we are seeing, that 7.5.0.6 kit does not have the EEB fix for an existing Postgresql installation.  Is there any way to get this to install?  I don't think that we can uninstall the application that is using Postgresql.

We cannot move to 7.6 yet as the Master Server cannot yet be upgraded, and we don't have the internal documentation and support ready to move to 7.6.

[RamNagalla]

have you tried installing 7.5.0.6 on the client...?

what i am seeing from the above tech note that you have given 

http://www.symantec.com/business/support/index?page=content&id=TECH182539

"This issue is resolved in version 7.5.0.3 and above"

so it should be fine with 7.5.0.6 install.

[revarooo]

I have seen case/s where customers get around this by deinstalling Postgresql and then installing NBU.

That might not be possible for you. I would open a Symantec case.

[William_Brown]

We did try the 7.5.0.6 kit; our install scripts for the standard client on WS2012 install 7.5.0.6 first, then patch to 7.5.0.7.   But the 7.5.0.6 special base kit for WS2012 kit hit the problem with Postgresql, hence this thread.  I was also surprised it was a problem.

I agree that the technote says 'fixed in 7.5.0.3', but 7.5.0.3 was a patch release, I interpret that to mean that an upgrade will not have a problem with Postgresql from 7.5.0.3 onwards.  But the only base install that claims to fix the problem is the 7.5 EEB kit for WS2008.   I assume that will not install on WS2012, as a minimum of 7.5.0.6 is required for WS2012.

So what I need is a 7.5.0.6 base kit for WS2012, with the EEB applied.  or another way to fool the Postgresql check.   We can't uninstall the business application that is using Postgresql.

I'm thinking someone else must have had to install 7.5.x onto WS2012 where there was Postgresql....

If no-one here has an easy workaround I will open a case.

[CRZ]

You WILL have to open a case, to request a 7.5.0.6 EEB - reference Etrack 3385159.  (So I guess the good news is you're not the first person to have this problem.  :)  )

We should probably update TECH182539 with this info.  (Maybe we were all secretly hoping people would only use 7.6 from now on?)

[William_Brown · Accepted solution]

This is solved... rather surprisingly.  the 7.5 EEB kit (http://www.symantec.com/docs/TECH182539) *does* install on WS2012, and as it says handles the existing Postgresql.  I hadn't tried it as it claimed to be for WS2008R2 only, but a colleague did and found that it installed.

So the answer turned out to be to install 7.5GA from the EEB kit, and then update to 7.5.0.7 as normal.

The EEB environment section says "64-bit Windows 2008 R2 server" but it also installs on WS2012.  I have not tested it on WS2003 x64 as I don't need to.

So TECH182539 could be updated to widen the target environment.

[CRZ]

I'm glad it worked for you, but I don't think that's a solution we ever tested or certified so I don't think it's one I could recommend in my capacity as a SYMC employee.  (I'll stick with my "ask for our EEB - or just install 7.6" answer instead.  ;)  )