post the install log file from the failed agent install.

can you please provide me screen shots of error. beacuase at agent side tcp port might be conflicting

before installation of agent, how can you enable prevention on agent??

This is not possible to enable or disable prevention on agent until and unless you install agent on machine and restart it.

after restart of system then you can able to enable prevention on agent.

Thank You,

Ritesh

Gentlemen,

Thank you for your assistance....

Pete, there is no install log. As soon as I click ok on the error, the install backs out and removes all traces. Attempting to force a log via command line failed, it seems that this install doesnt support all the msi package installer functions.

Ritesh , It is not possible to post a screen shot here, unfortunately. Security Policy prevents me from doing that. However i did check the current open ports on the system in question. During install, I've left the port defaults (2222 for notification, 443 for agent port..).Running netstat, there are currently no other application using these ports.

Also, to address your second post: during the install, second screen after the license agreement, is the agent configuration screen (this is agent v5.2). Third option down is "Enable Intrusion Protection". Further, I believe the install guide states that during install, the IPS componant is enabled by default - unless you specificly deny it.

So... no apparent TCP conflicts.... no security policies on the system preventing me from running it... anything else I can check?

Please check to see that the Windows Installer Service is not disabled.  It can be set to Manual, but not disabled.

Are there any logs left in the Windows System or Application log files?

 Error while installing the IPS TCP Filter is the error that I get. My situation is very similar to CKpolaris. Has anyone found a fix for this yet?

Chuck Edison,

Windows installer service is indeed set to manual. I haven't gone line by line through the event logs, but nothing stuck out that would hinder this. I'm out for a week  - when I get back I'll continue to troubleshoot.

Thank you all though for your suggestions..

Orkin, responded to your pm..

I have gone through the windows event logs and i cannot find anything that even slightly hints to the install failure. I've looked in the registry under HKLM\System\CurrContSet\Services\Tcpip\Parameters, expecting to see a TCP setting that was out of range, all settings check out to be correct. I've looked at services that may be at fault, nothing leaps out as a problem.

Question: Is SQL express or MDAC required for agent.exe to install?

I went through some old cases that were experiencing the same IPS TCP Filter issue, and here are some suggestions:

1. If you are installing using RDP or another solution like VNC or Citrix, try installing locally instead of remotely.
2. If installing remotely is not possible, one customer resolved this by using add/remove programs instead of the command line.  Apparently, the OS looks at that differently.
3. If you are using a terminal server, try putting the session into install mode.  From the command line enter "change user /install".  To go back use "change user /execute"
4. If you are using RDP, try getting to session 0 before executing the installer "mstsc /console"
5. Check the HKLM\System\CurrentControlSet\Services key for SISIDS* entries.  If you see anything, there was a previous failed partial install that could be blocking the current install.  This would require a manual removal of the leftover parts
6. Check add/remove programs for a SCSP entry.  If found, uninstall
7. Make sure you are looking in the correct directory for the install log.  From the run menu, enter %temp%, which will bring you to the current user's temp folder, the default log location.  Look for SISAgentSetup.log  If you find it, please post.
8. Unfortunately, there were 2 out of the 5 cases I found where a reimage of the Win2k3 machine was the solution.

Chuck,

Using the %temp% from start run line, accessed the install log. I've requested permission to send over that file to you, Still waiting for approval. Meamwhile, is there anything in particular that I should look for in the log?

Please find setup file attached.

Researching . . .

Are you using Terminal Services or RDP to install this?

As a test, can you completely uninstall McAfee and try to install SCSP after a reboot?

Also, ensure that the user has local admin/domain admin rights to this machine when installing.

I am still researching this issue, but I am sorry to say I am not finding a whole lot of info besides what I previously posted.

We uninstalled the McAfee, removed all items from the Temp folder and rebooted the machine. We then attempted another install of scsp agent.exe and still the error message persists.

I have not found much in my research, and I think it is time to open a case with support so we can get this looked at.

Thanks

Thanks for the info!  I will be creating a KB doc on this.  If you do find out which GPO was blocking this, please PM me.