Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 4583 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Awaiting Policy Transfer & SavService.exe 99% CPU

SyrianHamster

Hi all,

We are experiencing a strange issue wiith the clients (Version 9) and EC (Version 4) where they do not seem to be reporting correctly and getting hammered with 99% of the CPU.

One of the issues was the number of messages that were still waiting to be processed in the Envelopes folder, there was roughly 1GB's worth of files sat waiting to be processed.  This was rectified by following supports instrcutions, but unfortunatley there is still an issue with clients reporting to the console.  A lot of machines are showing awaiting policy transfer or differs from policy, although they dont seem to be different from the policy if you check locally.

The second issue is based around the policies being applied from the console.  If we modify the policy in the console and apply it to the clients a number of machines sit get hit by the savservice running at 99%.  The only way I have found of stopping this from happening is to remove the messages from the envelopes folder and then end the process on the clients.  If the policy is then reapplied the same happens again.

This has been logged with support but I was hoping some of you guys might have some idea's.

Thanks

:2091


This thread was automatically locked due to age.
Parents
  • 0

    I see. Yes, I had similar to that once too. I made a new schedule and it stopped all my schedules from working because it was corrupt, even though you could inspect the settings for it and it was all fine. Good news on fixing it by making a new identical policy (rather than copying the faulty one which presumably would have been corrupt too).

    One more thing to check regarding your clients is to look in your 3/CertificationManger/IssuedCert folder. How big is your CMIssuedCertifices.log file? It should be very small, i.e. a few hundred KB. Once I looked there and it was getting on 10MB so I had to wipe them out and start again which you can do by:

    1. Stop Message router.

    2. Stop certification manager.

    3. Delete your envelopes and CMIssuedCertificates.log file.

    4. Delete your table_router.txt file from your router folder (contents should be one line per PC).

    5. Start up certification manager.

    6. Start up message router.

    The above will make all your clients ask for a connection certificate again and clear out the history of client connection. I've not needed to do that since the ES2 days but if your certificates file is enormous it's worth doing.

    As for your trouble MALeonard, I bet you're really annoyed with that. You upgraded properly and then found it hadn't done it. I've only done an upgrade once (ES2 to ES3) - this time round I started again on a new server and migrated my clients across.

    :2133
Reply
  • 0

    I see. Yes, I had similar to that once too. I made a new schedule and it stopped all my schedules from working because it was corrupt, even though you could inspect the settings for it and it was all fine. Good news on fixing it by making a new identical policy (rather than copying the faulty one which presumably would have been corrupt too).

    One more thing to check regarding your clients is to look in your 3/CertificationManger/IssuedCert folder. How big is your CMIssuedCertifices.log file? It should be very small, i.e. a few hundred KB. Once I looked there and it was getting on 10MB so I had to wipe them out and start again which you can do by:

    1. Stop Message router.

    2. Stop certification manager.

    3. Delete your envelopes and CMIssuedCertificates.log file.

    4. Delete your table_router.txt file from your router folder (contents should be one line per PC).

    5. Start up certification manager.

    6. Start up message router.

    The above will make all your clients ask for a connection certificate again and clear out the history of client connection. I've not needed to do that since the ES2 days but if your certificates file is enormous it's worth doing.

    As for your trouble MALeonard, I bet you're really annoyed with that. You upgraded properly and then found it hadn't done it. I've only done an upgrade once (ES2 to ES3) - this time round I started again on a new server and migrated my clients across.

    :2133
Children
No Data