Quantcast
Channel: Symantec Connect - Products - Discussions
Viewing all articles
Browse latest Browse all 6827

upgrading Symantec 12.15 to 12.1.6 error

$
0
0
I need a solution

 I  presently   have a  multiple  server topology  replicating  to each other  over  satellite  connection.  I have  decided  to upgrade  one  of  the small site server from 12.1.5 to 12.16.  After i have  launched  the  executable ,  i got the  above error  message  capture in the  screenshot.  The error message  was also  link to an  existing  article  https://support.symantec.com/en_US/article.TECH228988.html  I  read   through  the  article  and  went to the  local  group policy  setting  for  log as  service.  The  two default  Symantec  users were  enact .  NT SERVICE\semsrv

NT SERVICE\semwebsrv

 I  later  restarted the sever and  re-launched  the setup  file. I  was  given the  option  to  re-configured  management server.  After the  reconfiguration  of the server, i finally  log on the  console  and  saw that the  new version  was 12.1.6.  I couldn't see  the  new client  packages  which  was very surprising  to  me. I  manually  imported  the  *.info file  in  order to  get the  package.

I am  about  to upgrade the   centralized servers   but i want  to avoid  the  above error  from  disrupting   the  upgrade process.  Do  i need to installed  new release on the 12.1.5  before  upgrading  to 12.1.6?   I  also want to  upgrade my existing  client  easily . Below  is  capture  of the  error message.

 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2016-01-20 12:08:41.254 THREAD 1 SEVERE: ================== Server Environment ===================

2016-01-20 12:08:41.258 THREAD 1 SEVERE: os.name = Windows Server 2008 R2

2016-01-20 12:08:41.258 THREAD 1 SEVERE: os.version = 6.1

2016-01-20 12:08:41.258 THREAD 1 SEVERE: os.arch = x64

2016-01-20 12:08:41.258 THREAD 1 SEVERE: java.version = 1.7.0_80

2016-01-20 12:08:41.258 THREAD 1 SEVERE: java.vendor = Oracle Corporation

2016-01-20 12:08:41.258 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM

2016-01-20 12:08:41.259 THREAD 1 SEVERE: java.vm.version = 24.80-b11

2016-01-20 12:08:41.259 THREAD 1 SEVERE: java.home = D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre

2016-01-20 12:08:41.259 THREAD 1 SEVERE: catalina.home = D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat

2016-01-20 12:08:41.259 THREAD 1 SEVERE: java.user = null

2016-01-20 12:08:41.259 THREAD 1 SEVERE: user.language = en

2016-01-20 12:08:41.259 THREAD 1 SEVERE: user.country = US

2016-01-20 12:08:41.259 THREAD 1 SEVERE: scm.server.version = 12.1.6608.6300

2016-01-20 12:08:41.260 THREAD 1 INFO: Main> Main>> Checking upgrade arguments... Command-line argument length is: 1

2016-01-20 12:08:41.260 THREAD 1 INFO: Main> Main>> Upgrade args length = 1

2016-01-20 12:08:41.260 THREAD 1 INFO: Main> Main>> Upgrade args = SQL

2016-01-20 12:08:41.260 THREAD 1 INFO: Main> retrieveAdminInfo>> Waited for 1 seconds to get info from stdin.

2016-01-20 12:08:41.261 THREAD 1 INFO: Main> retrieveAdminInfo>> Get string from stdin = username=sa

2016-01-20 12:08:41.261 THREAD 1 INFO: Main> retrieveAdminInfo>> adminUserID = sa

2016-01-20 12:08:41.261 THREAD 1 INFO: Main> retrieveAdminInfo>> Password is received.

2016-01-20 12:08:41.261 THREAD 1 INFO: Get string from stdin:END_INPUT_FROM_STDIN

2016-01-20 12:08:41.261 THREAD 1 INFO: Main> Main>> Unable to retrieve the admin password.

2016-01-20 12:08:41.262 THREAD 1 INFO: Main> Main>> Server Home = D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat

2016-01-20 12:08:44.350 THREAD 1 INFO: Main> Main>> Database server is MSSQL. Testing DB connection... Current time = Wed Jan 20 12:08:44 UTC 2016

2016-01-20 12:08:44.350 THREAD 1 INFO: DatabaseUtilities> testDBConnection>> Testing DB connection using 'DefaultDatabaseConnection' method. Parameters used (needDateFormat: false, isRetryUntilDBUp: false, defaultConnectionMaxRetry: 20)

2016-01-20 12:08:44.603 THREAD 1 INFO: Main> Main>> DB(MSSQL) test connection succeeded. Continuing with upgrade process...Current time = Wed Jan 20 12:08:44 UTC 2016

2016-01-20 12:08:44.865 THREAD 1 INFO: Has valid SAV license

2016-01-20 12:08:44.865 THREAD 1 INFO: Info>> No SNAC license file in D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license

2016-01-20 12:08:45.098 THREAD 1 INFO: Main> executePreLaunchSteps>> Config schema format is getting upgraded from (schema version from db): 12.1.5.4

2016-01-20 12:08:45.719 THREAD 1 INFO: Saving disaster recovery data to: D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Server Private Key Backup\recovery_2016-01-20-12-08-45.zip

2016-01-20 12:08:45.971 THREAD 1 INFO: Main> executePreLaunchSteps>> DbVersion: 12.1.5.4 schemaVersionFromDB: 12.1.5.4 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 0 dbConnected: true isTelemetryOptedInFromDB: true

2016-01-20 12:08:45.972 THREAD 1 INFO: Main> checkUpgradeFeasibility>> Checking for upgrade feasibility, current schema version = 12.1.6.4, schema version from db = 12.1.5.4

2016-01-20 12:08:45.974 THREAD 1 INFO: VersionToBeSupported: 12.1.5.4

2016-01-20 12:08:45.975 THREAD 1 INFO: SchemaVersion>> isSupported> versionToBeSupported '12.1.5.4  is supported for this release

2016-01-20 12:08:46.068 THREAD 1 INFO: Main> displayOnlineServerListIfAny>> Checking online servers. siteId = 9D4C31970ABCF1B2019EAC0247A4B369

2016-01-20 12:08:46.160 THREAD 1 INFO: SYSOUT : Checking onlist status for server min-mpti-sepm01

2016-01-20 12:08:46.161 THREAD 1 INFO: SYSOUT : Not checking status. offline status detected

2016-01-20 12:08:46.161 THREAD 1 INFO: SYSOUT : [name=min-mpti-sepm01,id=F4A034370ABCF1B20045B0DE4451C909] is offline

0

Viewing all articles
Browse latest Browse all 6827

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>