Endpoint Protection

Hello,

I migrated SEPM (I have two and  I  migrated only one for awhile) from version 11.0.7101 to 12.1.1

All my clients (about 4700) are on version 11.0.x.

Many clients have not a green dot and in Help and Support\Troubleshooting\Server  value is OFFLINE

someone can help me?

thanks,

Daniele.

how did you upgrade? did you create a new DB by any chance?

I upgraded using the same DB.

During upgrade, setup has updated the DB schema.

upgrade of schema is alright, do you have backup of SEP 11.x  DB and certificate, if yes return to SEP 11 version and upgrade to SEP 12.1RU1 using the link below

http://www.symantec.com/business/support/index?page=content&id=TECH174545

Hi,

Please run sylink monitor tool and  share sylink.log files from 1-2 affected clients.

After replacing sylink.xml file are they reporting back ?

Hello,

Cause: During the migration the installed asks for the port to use for communication with the clients. If you used port 80 and on IIS Default web site is still running, it will not be possible to choose port 80 as it remains in use by IIS. Since Symantec 12.1 uses Apache Tomcat only, it will be necessary to choose other port. As a consequence the clients which used to communicate with SEPM on port 80 will loose the connection.

There are several possible workarounds for this problem:

1. Stop the Default web site in IIS and use port 80 as a communication port during the migration.
2. Modify the management server list (msl) in your existing environment adding a new port number. Make sure that all your clients receive the new msl. Use the new port during the configuration.
3. Give new port number during the migration and then reconnect all the clients by replacing sylink file.

Hope that helps!!

thanks for suggestion:

the most important error in sylink monitor (IMOO) is:

12/02 13:23:10 [4712] <mfn_MakeGetIndexUrl:>Request is: action=12&hostid=85C3CD61643D016A01184326C909B5EC&chk=9942314DE671313A580A6C0CACFC0912&ck=B27A353F78BC6EF64F7201027B33014A&uchk=C53C2B69994150F6F778C4D061DF32E9&uck=E6CF5345E86E62CBE0ACABABB47543BD&hid=146C19C5769A5363BEB524FE90CB8FAC&groupid=45E31843643304B9017191A4A7D73654&mode=0&hbt=300&as=1409&cn=[hex]64315F3533323030303031&lun=[hex]3533323030303031&udn=[hex]47525550504F2E4155544F5354524144452E4954
12/02 13:23:10 [4712] <GetIndexFileRequest:>http://nts11998:80/secars/secars.dll?h=AD73DC037ECA5EFA22755AB87EEC4D0E450310570A2342B72CA1F2DB7293DFD56066254459BD9EBBAB961D2CAA694DE00DDADBA61A43EADC342E36E0EB4B3A4BDEABD386ACD69DA05960788C2169E82F387F89B11222B90F0C4263759A6229F7E981C895DE65C8644CAEB318A76555321DDF329BC04428E4FA5280BEC9FD847DFB8C1F9614DBAF4ABB75E17E72CC0040F88E9683471EC03BE8AC3B29FE298A9F89F42927E8C5B2182ACAE46EFDAA749A46F59E322FFB9D649E3D529DA37974DFC878E8F260CB20AB11A67AF4186EE2ADFA4F0275DC0DA4510825F9EEEB5DB91D8C216957A5F872A8698A81A85C5C0DCA63C63B8322EFE7E1800AD546CB0AA0A89A6A24A5EA1BF4C87ED4892CD8E6BF3171319459377BD83FE695BE323162BD0911C4088D81004FEF4A6538022BFDC72DC4E55CE80B6F3DA46B402444DC67851ED68C27A38936AE8049B36E2577240C0104371265D4BF3CD526363BCCD587AD188F51DEEF7198661635D2B60B48399B46FC9129E333E0A4854B4799E42E884BF7EBEAD5BD9CF72569854E1900FF265A2A6E68741B8A124682A511826F8A239137
12/02 13:23:10 [4712] <GetIndexFileRequest:>SMS return=503
12/02 13:23:10 [4712] <ParseHTTPStatusCode:>503=>503 SERVICE NOT AVAILABLE
12/02 13:23:10 [4712] HTTP returns status code=503
12/02 13:23:10 [4712] <GetIndexFileRequest:>RECEIVE STAGE COMPLETED
12/02 13:23:10 [4712] <GetIndexFileRequest:>COMPLETED
12/02 13:23:10 [4712] <IndexHeartbeatProc>GetIndexFile handling status: 503
12/02 13:23:10 [4712] <IndexHeartbeatProc>Switch Server flag=1
12/02 13:23:10 [4712] HEARTBEAT: Check Point 5.1

when the error 503 appear, green dot disappear.

After a couple of minutes, SEP Client retry to connect and  does not fail. So the green dot appear, like a magic.

Attachment(s)

sylink_20.txt   618 KB 1 version

Hello,

Upon Checking the Logs, Here is what we found:

12/02 12:51:46 [4984] <Start>Unable to create Session with 'User Proxy' settings - Proxy Server: Error Code: 87

12/02 12:52:51 [4712] HeartbeatProcFailed to get profile with proxy setting 1
12/02 12:52:51 [4712] <CheckHeartbeatTimer>====== Heartbeat loop stops at 12:52:51 ======12/02 14:55:07 [4712] <ParseErrorCode:>12031=>Unknown error code.

Throw Internet Exception, Error Code=4294967287;Internet Session Timeout

<ParseErrorCode:>12002=>Unknown error code.

great!! :)

very helpfull! :)

no needed to distribute sylink again.

MSL was OK.

Clients I can keep on eye in this moment have a very green "green dot" .

definitions updates goes like never gone.

thanks very much.

greetings,

Daniele.

Thank you for your help.

During SEPM upgrade I used port 8014 for client connections, I guess this is not interfering with IIS.

but I didn't know that IIS PROXY possibly interfere with client connection performance.

this is why client go in error.

your colleague Mithun Sanghavi help me in this issue when viewing sylink log.

Thanks again,

regards,

Daniele.