Sort of... that DLL is implemented in WINE but it's not allowing kms.exe to run properly. This is what I get (the fixme line is generated by WINE): Code: KMS Server started and ready fixme:rpc:RpcMgmtWaitServerListen not waiting for server calls to finish Ended listening. On another site I read that a workaround is to sleep forever after calling RpcMgmtWaitServerListen, as the function does work but it doesn't wait. But without source code I can't do that.
Hi, I was able to fix my issue as mentioned on an earlier page. This is only caused if you had the beta version installed prior to installing the RTM-Escrow. You have to remove the registry key mentioned below prior to installing the RTM-Escrow or the activation will give you an error code and office will not be activated. The Registry file is: Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform
How long will this KMS activation last, i read somewhere that you need to reactivate every few months!
Ok I fixed the "0x8007000D" error on my Windows Pro x64 after a lot of tests I can say this: When you activate your edition via OEMSLP (offline) / RETAIL (online) the activation files got changed and you may have a problem with the KMSVL activation so you need to restore the ORIGINAL files (like when you install windows without a key, it use the trial default key) TO DO THIS: you need to REARM your windows. just type this command: "slmgr.vbs /rearm" it will restore all to the original state, reset eveything and restore thr orginal activation files (like when you install windows with the default keys) and give you another 30 days and then slmgr /ato command will be able get the activation code from the the server emulator and activate your machine. -"slmgr /ato" command will not work at the first try everyrime.. you may get some errors at the first time (like key is blocked, kms is unavaliable, DNS error.. ) so run "slmgr /ato" couple of times (like 4 tries, of course make sure the keygen is open). -"slmgr /rilc" does not help and does not related, it will re install the license files that should never ever changed and even if they do, they will not affect KMS activation method, -the LAN suggestion does not related to this error, a different error will appear if you have some LAN problem. but it will better to do this: disable and re enable the local area connectin adapter. make sure that it's connected - Network. -also make sure to allow access to ZWT KMS server emulator with your firewall. BTW- on my case, I ran out of rearms, so I used Napalum program to reset my rearms count, and then I rearmed my windows.
@Tuvi123: I did not have to do all that when I upgraded from a MAK activated office 2010 beta to the RTM-Escrow with your method. Like I said, all I had to do was remove that one registry key above. IDK about the XP x64 though, have not used that one in quite a while now cause of incompatability. Just to point that out lol
sam3971 on office it's different, you don't have command to rearm office, instead of this you need to remove the "OfficeSoftwareProtectionPlatform" key from the registry and then when you open office it will recover and repair the files (restore office activation files - back to the orginal state).
I personally have not tried it because I run Pro but I hear it is a lot better then the first one. IDK if it really works but it should. I can always check in a VM for you though if you want dude. It is also supposed to be automatic using a task schedule system.
no man.. don't waste your time i can do that myself.. that would be selfish of me to put work off on you when i can do it myself .. Unless you were planning to install Enterprise w/Phazor's 5.0 before this NOTE I did not know that it automatically sets a "Scheduled Task" to reactivate That's a def. perk ! F.Y.I i am currently testing other Activators currently.. but eventually i will get around to testing Phazor's 5.0 .. hopefully.. 6.0 will be out by then