SQL Server Login failed for user 'domain\Administrator'

SQL Login failed for user 'domain\Administrator' or 'sa' or any other user.
This happens for a lot of reason, one of the reasons may be, you have changed the domain controller of your server, where SQL was already installed.
When this happens, you cannot login to the SQL server with any account.
Then the resolution would be running the SQL instance in single-user mode.
How to do this , follow the below steps :

1. In SQL Server Configuration Manager, click SQL Server Services.
2. In the right pane, right-click SQL Server (<instance_name>), and then click Properties.
3. On the Advanced tab, in the Startup Parameters box, type the parameters separated by semicolons (;).
   For example, to start in single-user mode, insert -m; in front of the existing startup options, and then restart the database. (When you start SQL Server in single-user mode, first stop SQL Server Agent. Otherwise, SQL Server Agent might connect first and prevent you from connecting as a second user.)
   

   Important note: "After you are finished using single-user mode, you must remove the -m; from the Startup Parameters box before you can restart the server instance in the normal multi-user mode. "

4. Click OK.
5. Restart the Database Engine.

 Now when you have logged in to the SQL management studio, follow the below steps:
1. Expand the security node.
2. Right click on logins, create a new login for the new domain account.
3. Also, you can reset the SA password.

There you go, now your SQL server works fine.

Hope this hepls.

Verify Domain User account SPN for the Microsoft Dynamics CRM ASP.NET Application Pool account

"Caller does not have enough privilege to set the CallerOriginToken to the specified value". If you are seeing this error when you try to open your CRM for the first time, then you have tried installing your CRM using your domain account and you have ignored the below given warning message by the EDU during installation .
"Verify Domain User account SPN for the Microsoft Dynamics CRM ASP.NET Application Pool account."

Follow these below steps to resolve it.

1. Using Windows Support Tools, setup the SPNs for the machine and service account (Important: needs to be done first)
   setspn –A HTTP/servername:5555 domain/serviceusername
   setspn –A HTTP/servername.company.com:5555 domain/serviceusername
   
   Note: Don’t forget the PORT
   Note: Don’t forget to do both the FQDN and the NetBios name
2. Trust for Delegation enabled in AD for the Service Account AND CRM Machine
   
   Note: This option is only available after you add the SPN for the both the NetBios name and FQDN) in step #1
3. Verify / add the service account to the CRM installation’s PrivUserGroup
   
   Note: This step must be done after installation. There is a known issue were setup will remove the user used for installation (the "setup user") and if this user is the same as the service account user, it will be missing.
4. The service account needs to be added to the local machines IIS_WPG group
5. Reset your IIS on the server.  OR Restart the CRM server. 

Hope this helps.

Original blog.
http://billoncrmtech.blogspot.com/2008/08/now-i-am-master-tips-for-running-crm-40.html

MS CRM 4.0 installation with SQL server 2008 R2 on WIN server 2008

I was trying to install MS CRM 4.0 on a windows server 2008, where I had SQL server 2008 R2 installed on it. Now I followed all the steps mentioned in the Microsoft KB article
http://support.microsoft.com/kb/950100

Everything seems to be fine, until I got a error saying "Service msftesql was not found on computer 'name'.
The specified service does not exist as an installed service".
Then after long hours of research found out that SQL server 2008 uses a different name for the Service msftesql".

Solution:
- Run > Regedit
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
- Rename MSSQLFDLauncher Folder to msftesql
- Reboot System
- Administrative Tools > Services > SQL Full-text Filter Daemon Launcher (MSSQLSERVER) and START the service
- Now try installing CRM, it goes fine.
- Rename back msftesql Folder to MSSQLFDLauncher.
- Restart the server.

Hurray !!! CRM got installed.