Server Principal Name (SPN) error while connecting to TM1

Sometimes when you connect to your TM1 server you may get an error message that says:

“Server principal name (SPN) or the security context of the destination server could not be established”

• Issue: Client is not able to connect to TM1 server because of above error message.
• Cause: ServicePrincipalName Parameter is an optional parameter of TM1. It’s used to as below:
  ServicePrincipalName=SPN
  Read more details here:http://publib.boulder.ibm.com/infocenter/ctm1/v9r4m1/index.jsp?topic=/com.ibm.swg.im.cognos.tm1_rdm_941_fp3.9.4.1.3.doc/tm1_rdm_941_fp3_id281T9413RN_DU_SPN_prm.htmlBut you don’t need to worry about this. It is used when using integrated login with TM1. Now if you’re not using kerberos security and don’t plan to use active directory server, there is no need to use integrated login anymore.
• Resolution: Just go to options in your client and in login parameters (options at the left top), uncheck “Use Integrated Login” check box.

If it still doesn’t resolve your problem, you may check some other approaches at tm1forum:
http://www.tm1forum.com/viewtopic.php?p=3466