Wors World
All About Wor

After sorting out the client asynch issue I then ran into this

This MSDCRMDMM was working a month or so ago.  What causes s/w to silently explode like this? In this case I’ve no idea so what I’ve done is removed the app and reinstalled it from here.  You must delete the MSCRM_MIGRATION db that is left over before reinstalling.

That seems to have fixed the problem.  It might haMSCRMve been due to a password change on the account I was logged on as – MSDCRMDMM only seems to ask for this at setup.  If it wasn’t so late (23:00) I’d try to figure out why but "times a pressing….."