Workflow doesn't work, Imports never happen, emails don't flow and Outlook clients cannot connect
Update 23 June 2008: See The official way to change MSCRM ports for an official way to do this. Update 12 March 2008:
The discovery service is a web service which gives back the real URL to the web services in MSCRM, so if you changed IIS it still gives back the old ones. There is also a bug in the RTM of MSCRM 4.0 which causes it to use the machine name instead of the host header after upgrades. So you go to http://<nice name> and the discovery service gives back to http://<machine name>/mscrmservices/2007/crmservice.asmx which doesn't exist since yourhost headers should have it as http://<nice name>/mscrmservices/2007/crmservice.asmx
You can pick this up using fiddler on the email server or desktop machine when trying to configure the email router or outlook client respectively. So I went though this with Microsoft PSS and they came back with a SQL command you can run to fix this.
NOTE: As this is a DB change it is unsupported. If you are a little worried about the impact do backups then try it. If you are very worried contact PSS directly for help.
Example, if your server is called: myserver and runs on port 50000
Once done do an IISReset and restart the Async service and everything should start to work fine! As I said before this came from PSS (in particular Justin Thorp)and I would really like to thank him for the hard workand great responses I got on it.
- An easier way exists to do this now. See Workflow doesn't work, Imports never happen, emails don't flow and Outlook clients cannot connect - Reloaded
- Another issue causing the same problems has been found and solved. See: Request IP Address has different address family from network address.
The discovery service is a web service which gives back the real URL to the web services in MSCRM, so if you changed IIS it still gives back the old ones. There is also a bug in the RTM of MSCRM 4.0 which causes it to use the machine name instead of the host header after upgrades. So you go to http://<nice name> and the discovery service gives back to http://<machine name>/mscrmservices/2007/crmservice.asmx which doesn't exist since yourhost headers should have it as http://<nice name>/mscrmservices/2007/crmservice.asmx
You can pick this up using fiddler on the email server or desktop machine when trying to configure the email router or outlook client respectively. So I went though this with Microsoft PSS and they came back with a SQL command you can run to fix this.
NOTE: As this is a DB change it is unsupported. If you are a little worried about the impact do backups then try it. If you are very worried contact PSS directly for help.
USE MSCRM_CONFIG Update DeploymentProperties SET NVarCharColumn = '<server>:<port>' WHERE ColumnName= 'AsyncSdkRootDomain' Update DeploymentProperties SET NvarCharColumn = '<server>:<port>' WHERE ColumnName = 'ADSdkRootDomain' Update DeploymentProperties SET NvarCharColumn = '<server>:<port>' WHERE ColumnName = 'ADWebApplicationRootDomain'
Example, if your server is called: myserver and runs on port 50000
USE MSCRM_CONFIG Update DeploymentProperties SET NVarCharColumn = 'myserver:50000' WHERE ColumnName= 'AsyncSdkRootDomain' Update DeploymentProperties SET NvarCharColumn = 'myserver:50000' WHERE ColumnName = 'ADSdkRootDomain' Update DeploymentProperties SET NvarCharColumn = 'myserver:50000' WHERE ColumnName = 'ADWebApplicationRootDomain'
Once done do an IISReset and restart the Async service and everything should start to work fine! As I said before this came from PSS (in particular Justin Thorp)and I would really like to thank him for the hard workand great responses I got on it.
[...] MSCRM. You may also get this in the event log. If you are seeing it in the event log it means that Workflow doesn’t work, Imports never happen, emails don’t flow and Outlook clients canno.... Lastly it is likely you are using Windows 2008 (although I suspect this can hit [...]
You are a legend!!
Many many frustrating hours of continuous mucking around with settings to figure this out and a SQL script resolves the issue. Figures :)
Thanks Man
[...] Para maiores detalhes, basta acessar os links abaixo: http://crmhacks.blogspot.com/search/label/MSCRM4%20Workflow http://www.sadev.co.za/content/workflow-doesnt-work-imports-never-happen... [...]
[...] Но этим проблемы не исчерпались. Как выяснилось, не работают Workflow. Нужно было поправить еще и зстоку, содержащую AsyncSdkRootDomain. Описание проблемы и решение здесь - http://www.sadev.co.za/node/155. [...]
[...] Robert MacLeanhttp://www.sadev.co.za There ended up being a bit more to get it fully fixed. See http://www.sadev.co.za/node/155 on how to fix it completely. -- Robert MacLean [...]
[...] dass diese Info von Microsoft bereitgestellt worden w
[...] or Waiting (http://support.microsoft.com/kb/957701/) – fixed. I am hoping this refers to my previous posts on the [...]
[...] server. Replace <server>:<port> with your CRM URL and port. To learn more click here.USE MSCRM_CONFIGUpdate DeploymentProperties SET NVarCharColumn = [...]
[...] articles that I’ve found regarding the subject are: http://www.sadev.co.za/node/155 [...]
I runned the script you provided, restarted IIS and Microsoft CRM Asynchronous Processing Service.
And now it works...
Thanks ;-)
Great article, really helped us out.
Also, if you've made the mistake to install the CRM 4.0 Data Migration Managar (DMM) on the same server as your CRM installation and then unistalled it some of the configuration properties are reset.
Thanks for this advice. I am however facing an Outlook configuration issue with 401 unautorized error after SQL Deployment properties table changed.
In our environment 3 servers are running - 1st one is CRM application/platform role, 2nd is CRM deployment service role, 3rd is CRM SQL server.
In this configuration, Outlook has to point the url for deployment service where discovery service is running, I think.
Could anyone advise what should I check - such as regedit, DB table, IIS setting, etc.
Thank you in advance.
Hmm what I would suggest is grab a copy of Fiddler (a google search will find it) and pop it on your client box and then run the Outlook client. You should the HTTP requests going through it, check that the URLs in that match what you are expecting.
Thanks rmaclean,
I did verify the URL with Fiddler and it was confirmed the request was redirected to "/MSCRMService/2007/SPLA/CrmDiscoveryService.asmx" on the deployment service server as I expected. However the request is still not accepted (error 401)... it is ugly.
[...] Resolution: Run a following query against your database server. Replace : with your CRM URL and port. To learn more click here. [...]
Nice job a guy. You save me from madness
For me
USE MSCRM_CONFIG
Update DeploymentProperties SET NVarCharColumn = 'myserver:50000' WHERE ColumnName = 'AsyncSdkRootDomain'
was all that was required.
Thanks v much for you help
[...] MSCRM web site ports correctly. This also fixes the workflow doesn’t work et al issues (see here). This is great to have, not because details a third way to do it (so besides the SQL edit and IFD [...]
Thank you very much!!!! It works!!!
It Works!!! Thank you very much!!!
[...] http://www.sadev.co.za/node/155 [...]
Thank you so much for your solution! I was beating my head against the wall.
FYI: I tried the IFD solution first, but it never filled in the needed value for AsyncSdkRootDomain, I had to enter it manually.
I hate this fucking-piece-of-shit software.... and now it's finally working!
I hope I never need to touch this abomination again.
Cheers rmaclean. I have spent weeks looking for this bit of information.
after 2 days of searching it works!!!
Finally it worked. Thank you.
I just wanted to drop you a line to say thank you! I was banging my head against the wall this entire installation because I used host headers for the crm web site. This was the last hurdle to get over.
-Steve
Thank you so much!
You are my hero of today.
This solution rocks.
I changed the port number in the IIS instead to the one which was used while installing MS CRM 4.0
Thanks.
Post new comment