Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SEE Management Server installation problem

Updated: 30 May 2010 | 5 comments
danielt's picture
0 0 Votes
Login to vote

Hello,
I am beginner with SEE 7 and I would ask you for help with SEE Management Server installation.
I have follow instructions in "SEE-FD 7.0.4 Installation Guide.pdf"
During installation I recieve following error:

Error 27506. Error executing SQL script CreateSEEMSDb. Line 228. Timeout Expired (0)

My test enviroment is installed in vmware before it will be deployed in productin enviroment.
Both servers: Win2003 Standart R2 SP2 + available WindowsUpdate
I have test installation with SQL2005ExpressAdvanced, SQL2005Standart, SQL2008ExpressAdvanced.
SQL is always local instance with enabled remote connection (TCP/IP and named pipes)
Installed version is SEE 7.0.4 , FullDisk Management Server
Application is installed using domain administrator account.

Setup fails always at same point: (part of setup logfile)

1: ADO Error: Number: -2147217871 Description: Timeout expired Source: Microsoft OLE DB Provider for SQL Server SQL State: HYT00 Native Error: 0
MSI (s) (B8!F8) [22:37:58:781]: Closing MSIHANDLE (2600) of type 790531 for thread 3064
MSI (s) (B8!F8) [22:37:58:781]: Creating MSIHANDLE (2601) of type 790531 for thread 3064
MSI (s) (B8!F8) [23:30:37:808]: Product: Symantec Endpoint Encryption Management Server -- Error 27506.Error executing SQL script CreateGEMSDb. Line 228. Timeout expired (0)

MSI (s) (B8!F8) [23:30:37:823]: Closing MSIHANDLE (2601) of type 790531 for thread 3064
MSI (s) (B8:7C) [23:30:37:933]: Closing MSIHANDLE (2367) of type 790536 for thread 2712
Action ended 23:30:37: InstallFinalize. Return value 3.
MSI (s) (B8:98) [23:30:37:980]: User policy value 'DisableRollback' is 0
MSI (s) (B8:98) [23:30:37:980]: Machine policy value 'DisableRollback' is 0
MSI (s) (B8:98) [23:30:38:026]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=997438613,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (B8:98) [23:30:38:026]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (B8:98) [23:30:38:026]: Executing op: DialogInfo(Type=1,Argument=Symantec Endpoint Encryption Management Server)
MSI (s) (B8:98) [23:30:38:026]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (B8:98) [23:30:38:026]: Executing op: RegisterBackupFile(File=C:\Config.Msi\3adde5.rbf)
MSI (s) (B8:98) [23:30:38:026]: Executing op: ActionStart(Name=ISSQLServerInstall,,)
MSI (s) (B8:98) [23:30:38:026]: Executing op: ProductInfo(ProductKey={4D5FA4A0-C423-4FA2-B104-9BE294C95CF4},ProductName=Symantec Endpoint Encryption Management Server,PackageName=Symantec Endpoint Encryption Management Server.msi,Language=1033,Version=117440516,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={0185E068-46C4-4E36-9B23-8FA620C9A3AA},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (B8:98) [23:30:38:026]: Executing op: ActionStart(Name=Rollback_Services.Unreg,,)
MSI (s) (B8:98) [23:30:38:026]: Executing op: CustomActionRollback(Action=Rollback_Services.Unreg,ActionType=1382,Source=On Error Resume Next

Const msiMessageTypeInfo = &H04000000
Set msgrec = Installer.CreateRecord(1)
msgrec.StringData(0) = "GINFO: [1]"
msgrec.StringData(1) = "Rollback: Unregistering Services..."
Session.Message msiMessageTypeInfo, msgrec

FileName1 = """" & Property("CustomActionData") & "Services\Symantec.Endpoint.Encryption.NovellSync.exe" & """"
FileName2 = """" & Property("CustomActionData") & "Services\Symantec.Endpoint.Encryption.ADSync.exe" & """"

Windir= CreateObject("Scripting.FileSystemObject").GetSpecialFolder(0)
CommandName = """" & Windir & "\Microsoft.NET\Framework\v2.0.50727\InstallUtil"" /u "

Set WshShell = CreateObject("WScript.Shell")

'Stop Services
WshShell.Run "net stop ""GEADSync""", 0, true
WshShell.Run "net stop ""GENovellSync""", 0, true
If (Err.Number <> 0) Then
 msgrec.StringData(1) = "Error stopping Services: " & Err.Number & vbcrlf & Err.Description
Else
 msgrec.StringData(1) = "Stopped Services"
End If
Session.Message msiMessage
MSI (s) (B8:98) [23:30:38:026]: Creating MSIHANDLE (2602) of type 790536 for thread 2712
MSI (s) (B8:B4) [23:30:38:026]: Creating MSIHANDLE (2603) of type 0 for thread 3252
MSI (s) (B8:B4) [23:30:38:026]: Entering MsiProvideComponentFromDescriptor. Descriptor: peir@WkWZA]*]oq(TeUw>M5KDYSUnf(HA*L[xeX)y, PathBuf: FBF2D8, pcchPathBuf: FBF2D4, pcchArgsOffset: FBF22C
MSI (s) (B8:B4) [23:30:38:026]: MsiProvideComponentFromDescriptor is returning: 87
MSI (s) (B8:1C) [23:30:38:042]: Entering MsiProvideComponentFromDescriptor. Descriptor: peir@WkWZA]*]oq(TeUw>M5KDYSUnf(HA*L[xeX)y, PathBuf: B1ED04, pcchPathBuf: B1ED00, pcchArgsOffset: B1EC58
MSI (s) (B8:1C) [23:30:38:042]: MsiProvideComponentFromDescriptor is returning: 87
MSI (s) (B8:1C) [23:30:38:042]: Creating MSIHANDLE (2604) of type 790531 for thread 3612
GINFO: Rollback: Unregistering Services...
GINFO: Stopped Services

any idea will be helpfull
best regards
danielt

discussion Filed Under:
Group Ownership:

Comments

Nitin Lal's picture
21
Nov
2009
0 Votes 0
Login to vote

 Hi Daniel  During the

 Hi Daniel 

During the installation process for the SEE Installer.msi, this error will be received if the database user login defined in the installation process already exists. To resolve this, open MS SQL Management Studio and remove the Login for the database user account defined. This can usually be done from Object Explorer under Security > Logins. More information on the cause of the error will be listed in the Application Event Logs.  Or you can perform an installation again by using the different login credentials for SEE Database. Please let me know if you have any questions.

Regards
Nitin L

Davinci_uk's picture
23
Nov
2009
0 Votes 0
Login to vote

Daniel,I am also getting

Daniel,

I am also getting this - does not matter which user accounts I try and specifiy.

Dont beleive it is the above answer.

Could it be a bug in the new 7.0.4 files Symantec??  Logged a call with Support - will post when have an answer - the Encryption forums are so quiet :0(

Davinci_uk's picture
23
Nov
2009
0 Votes 0
Login to vote
Davinci_uk's picture
23
Nov
2009
0 Votes 0
Login to vote

My worked in the end. Follow

My worked in the end.

Follow above advice/link.

Then MAKE SURE you use a complex password (I had capital, letters and digits and more than 8 characters) - if not complex password, you can still get the error message!!

Paul Murgatroyd's picture
29
Nov
2009
0 Votes 0
Login to vote

another reason is simply the

another reason is simply the database is taking too long to create.

I have seen this several times when installing into VMWare, you can either retry the install straight away and it normally works, or reduce the initial database size in the advanced configuration options for the database, during the install wizard (from 7.0.3 onwards)

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint