Endpoint Protection

Tried this procedure.

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

1. Stoped SEPM and IIS services

2. Wend to MS SQL 2005 management studio

3. Detached the database

4. Copied everything from the SEPM db folder

5. Attached the database

And no, I can't log on to SEPM.

Netstat shows that clients are attempting to communicate, but the Secars test failed and all the ports for SEPM is not up.

Already tried restarting the services and the server.

:(

Hi mon, 

        What is the error ? Check whether the Serivces are started and then stops after some time ?

       Please run the Management server configuration wizard  the database server as " DB server ip address" and once finished . Login and check it . 

There's no error when I restarted the services.

Although the Event viewer showed numerous Application errors:

I'm currently reconfiguring the management server. If this fails. I'm thinking of changing this to a Load-balancing server with no db.

Hi , 

  Check These Link From Microsoft :

 http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL%20Server&ProdVer=10.0&EvtID=17832&EvtSrc=MSSQLServer&LCID=1033

http://support.microsoft.com/kb/169521

Thanks for the link.

The database in question that I detached was in its original place. I just detached it so I can copy it.

I'm not sure if I stopped all the other services. But the copy got attached just fine. So I assume that the db has no problems in it.

Are you able to Login right now ?

Was able to log in now. No changes were made. Probably caused by high traffice from clients getting updates.

Were you able to check the IIS logs for any errors? Can you also bring up the client console, click on :>

Help and Support > Troubleshooting

Now Check for the General Information > Server field.

This should be listing out the IP address or the hostname of your SEPM server.

Let us know if it says "Offline". You might then have to check for the communication between the SEPM and one of the affected clients.

Trying pinging into the server from the client and vice-versa.

Do the same with telnet <ip address> 8014

Let us know the outcome of this.

I'll have to see in 2 days if the current config is stable.

On the old machine:

1. Stopped the SEPM and IIS services.

2. Went to the SQL Management Studio and disconnected/detached the database.

3. Created a shared folder to the target server and copied ALL of the contents of the SEPM db path. Just to be sure. I know that it isn't necessary to copy the log files.

4. Then on the new server. Opened the SQL Management Studio and attached the db.

5. Re-configured the SEPM to use the database.

6. On the old one, we also configured it to use the new database. Although I could just reattach the old db just the same.

And the attaching and reconfiguring of the database for use by SEPM takes a bit of time. Usually over 30 minutes. So make sure you have patience. I left mine at home when I first posted this.

But then again, the old server has hung up on us quite a number of times already. So I really can't tell.