• Office Software Protection Platform Registry
• Install Software Protection Platform Service
• Office Software Protection Platform Removal

You couldn't really describe it as a bug since the SPP service is only doing what it should, which is logging requests that are being made to it. The real task you have is to identify what the calling task is and then determine if there's a reason it's checking the licencing status so often and potentially lessening those checks. Going back to the previous post as an example, if it's Server Manager, then you can actually configure the refresh interval or turn it off entirely (you'd have to tell the people running it to do this as there's no central way of doing so as far as I know).

One thing you can do purely as a testing mechanic is to disable the firewall rules for 'Windows Remote Management' (there's two of them: port 5985 and port 80). If you do this, then keep an eye on the event log and see if that stops the licensing events from generating. Just don't forget to re-enable the firewall rule once you're done. Cheers, Lain. Hi, It shouldn't be running every five minutes unless something is wrong with the licencing status or you have a monitoring/management tool checking the licencing status of the server, which will require the service to start. You can double-check the frequency of the scheduled task that usually handles the starting of the service within the Scheduled Tasks MMC here: Task Scheduler Library Microsoft Windows SoftwareProtectionPlatform If the value for 'Last Run Time' isn't correlating with the timestamps you're seeing on the event log entries, then you've got a monitoring/management process tripping the service.

Cheers, Lain. Okay, that probably explains why the scheduled task is disabled then, as there's no recurrent checks once a MAK key has been initially activated. That still leaves your original problem, of course.

What are the actual event IDs that are being generated? (They should still be from the Security-SPP source) I'll have to go away with those event IDs and see how they bear relevance to MAK activations, as we only use a KMS infrastructure here, and I'd expect to see some differences in the generated events given the 12288 and 12289 that we get only relate to KMS (as far as I understand it). Cheers, Lain. Hi, So, I've done a little reading but I don't have anything definitive. What are I do have are two links and some speculation. First, the links:. For the first post, I took the easy path and run Server Manager locally thinking it'd use the same behaviour and trigger the events, but it didn't.

I made sure I had the Refresh option (down the bottom of Server Manager) enabled, but it made no difference. Running it remotely did yield quite a different result. Not only does it generate the events, and does so according to the refresh interval, it handles the licence checks differently. Whereas the 'normal' on-host process seems to handle the licence checks in bulk, logging a single 1003 event as a result, Server Manager - when run remotely, actually handles each licence check 'individually' (I don't know the actual SPP API well enough to be detailed about it) which results in a 1003 event for each and every licence type check. Anyhow, once I closed Server Manager on the remote host the events also stopped. I wouldn't class any of this as absolute proof of cause, but it at least fits into my expectation that it was something outside of the service's normal operation from my original post, which also corresponds to the second article referenced above, so I'm happy enough to accept that. Of course, this doesn't mean it's Server Manager in your case, but it does seem to point to something that is in fact talking to the Software Protection service on that machine.

Cheers, Lain. You couldn't really describe it as a bug since the SPP service is only doing what it should, which is logging requests that are being made to it. The real task you have is to identify what the calling task is and then determine if there's a reason it's checking the licencing status so often and potentially lessening those checks. Going back to the previous post as an example, if it's Server Manager, then you can actually configure the refresh interval or turn it off entirely (you'd have to tell the people running it to do this as there's no central way of doing so as far as I know). One thing you can do purely as a testing mechanic is to disable the firewall rules for 'Windows Remote Management' (there's two of them: port 5985 and port 80). If you do this, then keep an eye on the event log and see if that stops the licensing events from generating. Just don't forget to re-enable the firewall rule once you're done.

Cheers, Lain. The Software Protection service (SPP) is designed to verify activation of any app that is registered with it. This includes Office and many Windows services. I would guess that services like Exchange, SQL, and most others are also a part of this. Every time a registered app starts, it will send a request to SPP to verify the activation. If your copy of Windows is not activated, SPP will not start. If SPP does not start for any reason, SPP registered apps will fail to verify activation and they will not be permitted to run.

After 30 seconds of inactivity, SPP will shut down. The problem is that SPP can take a long time to start and will often time out, even though your system is properly registered.

A second attempt will usually get it started, but I don't want to retry 2 and 3 times just to open a Word doc. Server apps will not automatically retry once they fail the activation check. My workaround is to increase the InactivityShutdownDelay for the SPP. The setting is located at HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion SoftwareProtectionPlatform. I set the InactivityShutdownDelay to 0x0000). Once it starts, the SPP will run for 24 hours without shutting down.

Office Software Protection Platform Registry

This should be enough for a workstation. For server apps, try this and check your logs.

If needed, you can try a longer timeout. I do agree with Lain from an earlier posting. Even with this, you should check the logs and make sure what apps are calling for the service. Hi Guys, I too have the same problem, in my case it started after I change ACL Rule is my ASA 5505 Firewall for SQL Server which is running on my DC. The SQL Server communicates with our web server for live data. We are running a Software that uses SQL Service.

Recently, I was asked to permit only https to communicate with the web server and the SQL Server in the Office. All for good reasons (Have been seeing loads of Log on request coming to SQL Server from varies countries, masked of course) Once I include a sub-rule only to use https i saw the SPP Log been created. At one point the SPP did a licence stack check with Event ID 1003. Afterwords, SPP was creating logs.

Install Software Protection Platform Service

At present It has stopped. So far I do not know if there is any problem for our web server to communicate with the SQL Server in office. I do not know how to check that.

Office Software Protection Platform Removal

I do not know if I should go ahead and increase the InactivityShutdownDelay for the SPP I am confused.

I have a user with a new PC with Windows 7 64 bit and Office 2010 32 bit. He is set up like 10 other people who got new PC's this year. No difference. He seems to be experiencing a lot of freezing in Excel 2010 but no one else in his department with the same setup is experiencing it. I checked his logs and the only things I've seen that are worth mentioning are: Office Software Protection Platform Service - The Software Protection service has completed licensing status check. VSS - The VSS service is shutting down due to idle timeout. Application Error (when we task killed Excel) - Faulting application name: EXCEL.EXE, version: 14.0.6117.5003, time stamp: 0x4f622ef8 Faulting module name: EXCEL.EXE, version: 14.0.6117.5003, time stamp: 0x4f622ef8 Exception code: 0xc0000005 DNS Client Events - Name resolution for the name PCNAME.domainName.local timed out after none of the configured DNS servers responded.

He did have an IP conflict and I had two DNS entries with the same IP in DNS, so I deleted his, removed and re added to the domain and he pulls a new IP address but a DNS entry wasn't created. So, I decided to make him static and see what happens. Just wondering if anyone knows if that may have been the cause of it. Since no one else has ever experienced this problem, it was my first guess.