Hi all,

CRM flying along without an issue. I will quickly reel through the things we
have done so far:
CRM mobile has installed correctly.
Certificates created using the online MS CA on the server.
FQDN was used for friendly and common name.
Can get to the 3 pages (ssCERDA, mobilecustomization and mobile
subscription) from both the laptop that is connected to the handheld and also
the handheld.
It is a 2003 device so the FQDN was used for the URL in the installation item.
An example URL is https://server1.domain.local:446/ssCERDA.
All 443(OWA), 444(sharepoint), 445(terminal server) were all in use so 446
was needed to be used for CRM mobile.
The package installs the app and certs sucessfully onto the handheld

What happens is when I run the app it churns through a bit, asks for a
username and password, it then churns through a bit more and then throws up
two errors.
Firstly it is "A connection cannot be esablished at this time please try
later" and when that is cleared it then throws up "Device Registration has
failed".

We have had this before but the fix from then hasn't fixed the error now!

Anyone have any ideas????
Any info appreciated.
Thanks.

Regards,
Nathan Warner

I am haivng the same problem. Do you mind telling me what your original fix
was?

Ben

"Nathan Warner" wrote:

TO ADD: I am getting the same error and also see the following:
CRMMobile.exe
MissingMethodException
at
Microsoft.BusinessSolutions.Mobility.DeviceApp.CRM AppShell.Main()


"Nathan Warner" wrote:

Hi Ben,

What we found to be the issue for us was that we were installing to a 2005
device but we were using FQDN (eg server.company.local) not just server name
in the deployment package.
After using just that it went through fine. But with a 2003 device
installation we found that it needs the FQDN. Also ensure the integration
service is started.

Hope that helps!

I wish there was somthing I could do to get mine working! unfortunatly in
these groups things that look difficult get thrown to the "too hard" basket
and never get resolved or replied to.
Due to CRM mobile having so many annoying little qwerks, I have heard that
Microsoft are going to handball the mobile side of things to a 3rd party
company for the next version of CRM! Should be interesting...

Cheers,
Nathan

"Ben Ortega" wrote:

Hi! Ben,

Did you solve your problem? I go exactly the same error message.
If you can solve, please help. I will appreciate of your help.

Regards,
Mike


Ben Ortega wrote: