Blog

CRM 4.0 Installation Error - “registerasyncserviceaction failed”

For a while, I was unable to get CRM 4.0 installed because I kept running into an error stating that the “registerasyncserviceaction” failed.  I tried numerous things to resolve this issue including checking registry permissions, service permissions, completely removing all traces of CRM and starting from scratch, etc…nothing worked!

 Finally, I came across something in the Application event log which initially seemed completely unrelated.  It was event id 3012 and 3011 from LoadPerf. It basically said that the performance counter registry strings were invalid.  After researching this error, I found that the solution was to rebuild the Perf Counter strings using the command “lodctr /r”.  The command took a little while but once it was completed I was able to reinstall CRM without a hitch!

5 Responses to “CRM 4.0 Installation Error - “registerasyncserviceaction failed””

  1. Mike Says:

    also helps to make iisreset before retrying

  2. MSCRMAsyncService (CRM4) | keyongtech Says:

    […] MSCRMAsyncService (CRM4) Dear Duc, Is the following link helpful ? http://blog.kazmarek.com/2008/02/06/…action-failed/ Thomas "Duc, Nguyen" wrote: > Dear All, > > Anyone know this issue please […]

  3. Virtualspy Says:

    I had the same problem and it drove me nuts. What fixed it for me was checking and updating the organization info inside deployment manager. In my case, I copied the environment to another machine for development purposes and for some reason when I updated the copy it altered the original.

  4. Failure at Microsoft.crm.setup.common.registerasyncserviceAction | Ugh!!'s Greymatter Honeypot Says:

    […] Rebuild Perf Counter strings with “lodctr /r”  (wasn’t getting a Perf Counter error) […]

  5. Dubi Says:

    Warning:
    The full performance counter rebuild (http://support.microsoft.com/kb/300956) may take considerable time and may not give a complete rebuild. The long proccess is human error prone, too. If you can’t resolve the problem in my short way, do try it or reinstall server.
    Well, first of all, I tried the long way. In the end, counters were still corrupt. I used procmon (microsoft sysinternals tool) to catch the last performance counter registery value before failing.
    I found out the full rebuild, didn’t rebuild the Windows workflow foundation performance counters. Wow, this is actually the most important module that the crmasync uses!
    I saw the counters :
    FirstCounter
    FirstHelp
    LastCounter
    LastHelp

    Are missing there (I probably deleted them in the long proccess), but their rebuild is not in the system32 dir!

    I executed :
    C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation>unlodctr perfcounters

    Unable to open driver SYSTEM\CurrentControlSet\Services\perfcounters. Status: 2
    C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation>lodctr perfcounters.ini

    This added the missing counters.
    (should try crm repair now).

    Generally I believe one should:
    1. export the full registery tree of:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
    Into a file.

    2. Filter out lines that don’t have the word performance in their key name.

    3. Find empty performance entries and performance entries without the first and last counters.

    4. Find their INI file and reload them ( unlodctr , lodctr).

    5. Verify that the load created counter entries in registery.

    Another point: I noticed that CRM doesn’t provide a INI file for rebuilding corrupt perf counters, they use a file called tmp38.tmp . Later I belive they delete it. As if saying : If it’s broke, let repair fix it!
    Maybe it’s a good idea, but I am not sure about it.

    Hope this helps;-)
    I wish a WIN internals guru can confirm this… but it doesn’t stray from the guide lines of the MS KB.

Leave a Reply