steve
Wed Apr 14 15:53:21 CDT 2004
Thank you - Thank you - Thank you!!!! - After much frustration this
ended up taking care of my issue.
"Derek Tinney" <dtinney@shaw.ca> wrote in message news:<e5gd0C3EEHA.3784@TK2MSFTNGP10.phx.gbl>...
> I ended up calling support for this and it was resolved when we renamed the
> application web site to be "Microsoft CRM Version 1.2".
>
> Regards,
> Derek.
>
>
> "Derek Tinney" <dtinney@shaw.ca> wrote in message
> news:Ow8I4Q1EEHA.3812@TK2MSFTNGP10.phx.gbl...
> > I'm having the same problem and having CRM come up as the default site on
> > the server is how we're configured.
> >
> > Has anyone else found any other way to resolve this?
> >
> > Regards,
> > Derek.
> >
> > "Jeremy A" <anonymous@discussions.microsoft.com> wrote in message
> > news:C27F6DAB-97C6-487C-B800-A04E7749F60F@microsoft.com...
> > > I found the solution to this MASSIVE headache, finally!
> > >
> > > Here was the scenario:
> > >
> > > I had CRM installed on a server named KONG. I had the CRM website
> located
> at a URL on that server,
> > > but I had a different website as the default website. (it was actually
> sharepoint).
> > >
> > > so, if you went to
http://KONG/ you would get sharepoint, not the CRM.
> > > You had to go to
http://crm.blah.foo to get to the CRM.
> > >
> > > So, when you try to publish objects, it give you options to choose
> servers
> to publish to.
> > > In our case, the option was "KONG".
> > >
> > > What I can only assume happens is that when it tries to hit the
> webservice
> to publish the objects, it looks
> > > at
http://kong/webservice_path/webservice.aspx without actually going to
> the properly set crm location (which I think is in the registry).
> > >
> > > So, I stopped the sharepoint site, and made the CRM also come up at the
> default location of
http://KONG/
> > > and voila! Everything works.
> > >
> > > Looks like a bug to me... Hope this helps what seems to be MANY other
> people having this same problem.
> > >
> > > Jeremy A
> > > Desire2Learn Inc.
> > >
> >
> >