Microsoft Dynamics CRM 4.0 - Invalid User Authorization
Set up a new Windows 2008 Standard x86 VM and installed MS CRM 4.0. CRM check before the file copy gives 100% success. Custom install of both server roles, Default Web Site, using Local Service account. Finishes install, reboot, install CRM Update 15, restart and go to http://localhost/. Error comes up "Invalid User Authorization The user authentication passed to the platform is not valid." I try to launch Deployment Manager and get an error as well "Only the Deployment Administrators are able to use Deployment Manager. You are not a Deployment Administrator."
Tried the same thing with a Windows 2003 R2 x86 VM with the same results. I also tried to install Update 16 and when I go to http://localhost/ it gives a page cannot be displayed.
I have to be missing something somewhere. I bet this is a quick fix, I just don't know what it is.
Tried the same thing with a Windows 2003 R2 x86 VM with the same results. I also tried to install Update 16 and when I go to http://localhost/ it gives a page cannot be displayed.
I have to be missing something somewhere. I bet this is a quick fix, I just don't know what it is.
Hi mvalpreda,
Using which user you installed CRM? It seems you are not using the domain A/C. If you are using local account I suggest you try login in with a domain logon in login screen.
Regards,
Chinmay.
Using which user you installed CRM? It seems you are not using the domain A/C. If you are using local account I suggest you try login in with a domain logon in login screen.
Regards,
Chinmay.
During installation I use Network Service for the CRM Service accounts. You might want to try that.
ASKER
This was installed as a domain admin.
Great and are you using the same A/C to login to CRM?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry to accept my own answer.
Before you try this again try running IE in Administrator mode and see if you can get to the URL. This doesn't solve the deployment manager problem though.