CRM Workflow Configuration and Deployment Manager Add-in Probl

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by WWVsaX » Wed, 09 Jan 2008 21:26:01


guess I have found my problem. The CRM web application is using port 80
instead of 5555. However RetrieveCrmTicketResponse returns the crm metadata
service url with port 5555. I have manually corrected the metadata address
while debugging, and retrieved the list of primary entities correctly.
However it makes no sense. Can't I configure the web application to use a
different port? I have changed localsdkport registry entry from 5555 to 80,
serverurl, still the metadata service port does not change.

"Yeliz" wrote:

 
 
 

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by Matt Park » Thu, 10 Jan 2008 01:07:32

ou may need to refresh the web references. They store the URL & Port from
when they were intiially generated.

--

Matt Parks
MVP - Dynamics CRM


"Yeliz" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
I guess I have found my problem. The CRM web application is using port 80
instead of 5555. However RetrieveCrmTicketResponse returns the crm metadata
service url with port 5555. I have manually corrected the metadata address
while debugging, and retrieved the list of primary entities correctly.
However it makes no sense. Can't I configure the web application to use a
different port? I have changed localsdkport registry entry from 5555 to 80,
serverurl, still the metadata service port does not change.

"Yeliz" wrote:




 
 
 

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by WWVsaX » Thu, 10 Jan 2008 16:43:01

did refresh the web references but there was no change.

"Matt Parks" wrote:

 
 
 

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by WWVsaX » Thu, 10 Jan 2008 17:01:07

y the way, the problem is not with the web reference url. There is a method
called
GetCrmMetadataFromDiscovery in the Helpers class. Which contains the code
block below:

CrmSdk.Discovery.RetrieveCrmTicketRequest request = new
CrmSdk.Discovery.RetrieveCrmTicketRequest();
request.OrganizationName = organization;

CrmSdk.Discovery.RetrieveCrmTicketResponse resp =
(CrmSdk.Discovery.RetrieveCrmTicketResponse)crmDiscoveryService.Execute(request);

//Create the crmService
crmMetadata.Url = resp.OrganizationDetail.CrmMetadataServiceUrl;

The url of the discovery service is correct (using port 80 and host header
like "crm4"), however the url of the metadata service returned is the
http://machinename:5555.



"Yeliz" wrote:

 
 
 

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by Chris » Thu, 10 Jan 2008 18:36:30

I would search all my project code, config files and crm registry
settings for :5555, can't believe this would be hardcoded anywhere :-)
 
 
 

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by WWVsaX » Thu, 10 Jan 2008 18:56:00

Yes, it would be funny :)
 
 
 

CRM Workflow Configuration and Deployment Manager Add-in Probl

Post by WWVsaX » Thu, 10 Jan 2008 19:05:01

I did search the entire solution for 5555, the web.config file of crm website,
and the registry. Found nothing....