Video Screencast Help

SEP 12 Rollback during Installation....HELP!!!!

Created: 27 Aug 2012 | 6 comments
cec.kadu's picture

I am trying to install SEP 12 on Windows Server 2003 Enterprise, but during installing the setup.exe give rollback, and do not finish the install.
 

I need a help.

 

Comments 6 CommentsJump to latest comment

Ashish-Sharma's picture

Hi,

Try to use Cleanwipe tool and restart server after install sep client.

Thanks In Advance

Ashish Sharma

 

 

Viachaslau Kabak's picture

Hi,

can you remove all Symantec folders and registry keys

also is this a new installation?

Mithun Sanghavi's picture

Hello,

As per the Logs, we see as below:

 

ShowServiceProgress: incrementing tick
ShowServiceProgress: incrementing tick
ShowServiceProgress: incrementing tick
ScriptGen: ShowServiceProgress() script execution failed.
ScriptGen: ShowServiceProgress() reset script failure event.
ScriptGen: ShowServiceProgress() is returning an error (so close to the end!)
Action ended 17:26:25: InstallFinalize. Return value 3.
 
MSI (s) (FC:A0) [17:27:05:737]: Executing op: ActionStart(Name=CommunicateRollback,,)
MSI (s) (FC:A0) [17:27:05:753]: Executing op: CustomActionRollback(Action=CommunicateRollback,ActionType=3393,Source=BinaryData,Target=CommunicateRollback,CustomActionData=12.1.1101.401;C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\Symantec\;;105)
MSI (s) (FC:C8) [17:27:05:768]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI38.tmp, Entrypoint: CommunicateRollback
Communicate RB:  calling communicate state with the following arguments: 
Communicate RB: Prodversion = 12.1.1101.401
Communicate RB: PathToSylink = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\Symantec\
Communicate RB: Oldversion = 
Communicate RB: ReasonStr = 
Communicate RB: StatusCode = 302469120
MSI (s) (FC:A0) [17:27:07:109]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (FC:A0) [17:27:07:109]: Error in rollback skipped. Return: 5
MSI (s) (FC:A0) [17:27:07:124]: Closing Terminal Server registry propogation window. Discarding Changes.
MSI (s) (FC:A0) [17:27:07:233]: No System Restore sequence number for this installation.
MSI (s) (FC:A0) [17:27:07:233]: Unlocking Server
MSI (s) (FC:A0) [17:27:07:265]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 17:27:07: INSTALL. Return value 3.

 

 
MSI (c) (AC:CC) [17:27:13:453]: Windows Installer installed the product. Product Name: Symantec Endpoint Protection Client. Product Version: 12.1.1101.401. Product Language: 1033. Installation success or error status: 1603.
 
MSI (c) (AC:CC) [17:27:13:453]: Grabbed execution mutex.
MSI (c) (AC:CC) [17:27:13:453]: Cleaning up uninstalled install packages, if any exist
MSI (c) (AC:CC) [17:27:13:453]: MainEngineThread is returning 1603
=== Verbose logging stopped: 24/08/2012  17:27:13 ===
 
Suggestion -
 
I would suggest you to restart the Server machine and try installing SEP again.
 
If the above does not help, then work on the steps provided in the Article below:
 
Symantec Endpoint Protection 12.1 client install rolls back, returning 1603
 
 
Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

A. Wesker's picture

Hi Cec,

 

Since SEP 12.1 and the last versions, there are plenty extra stuff that have been added to make the installation troubleshooting easier.

1) SEP_inst.log

2) SIS_inst.log

3) roru.log in some install roll back situations is getting generated as well.

If you can add them, it might be more easier to find out where and why it roll backs all the time before the end of the installation workflow.

You can get these extra installation debug logs on the directory below.

C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\12.1.1101.401\Data\Install\Logs\

 

Kind Regards,

A. Wesker

 

Ashish-Sharma's picture

hi cec.kadu,

Any update on this ?

If you have received solution please don't forgot Mark as Solution.

Thanks In Advance

Ashish Sharma