Hello everybody!

Could someone please help me with this case.

I just got my new Symantec Endpoint Protection 12.1.4 for small businesses which I was supposed to install it on a windows server 2008 R2 platform. During the installation of the first part (the Protection Manager) a Windows Script Host error message pops up few second before the end of this part with an error type of invalid procedure call or argument, code#: 800A0005. The installer indicates that the first part was installed successfully through a green tick and moves on to the second part (the Management Server Configuration Wizard). The problem that I am facing is that this part keeps loading for ever and nothing else happens.

I already downloaed the most recent updates for the server, uninstalled the windows security essentials, disabled the windows firewall and tried to google that error but all I have done so far seemed to be helpless.

Any help or suggestions would be highly appreciated.

Thanx.

See below thread and mithun comments

https://www-secure.symantec.com/connect/forums/wsh-error-when-installing-sepm

Disable the fips and try

Important notes to consider before configuring SEP for FIPS 140-2 compliance mode

Is this an upgrade over a previous version?

Thank you James007 and AJ_01 for your help. I tried both methods but unfortunately, none worked!

Any other suggestions?

Thanx

Ahmed

No Brian, it is a first time installation.

Please submit the sepm installation log.

Have you try installation on another system ?

may be some problem in windows OS or installation media.

Well James007, I havn't tried this yet, I will give it a shot and come back to you once I'm done.

Thanx

Where can I find this file or, under what name can I find it?

Bests

sepm_inst log in the %temp% folder

See here:

How to debug the Symantec Endpoint Protection Manager

Although I got my 1.8 GB installation file from the Symantec website, I couldn't go ahead with the process on another comuter as I am facing a different error now.

I think after all that Mr. James007 was right, when he asked me to try to install it on a different PC. 

Many thanks for you all guys for your cooperation. I will try to find another installation copy and let you know with the updates.

Peace.

Ahmed

As user has abandoned post, am marking split solution across James007 first comment and his comment about trying a new server.

As a side note, if someone could post up the VBScript referred to in this post then we could figure out what call generated the issue here... would help isolate whether this was a WMI issue or similar.